Navigation systems use the "name" and/or "ref" fields of roads when giving directions. Giving something a name that doesn't reflect the signs on the ground causes those systems to give bad directions.

Yes, the shortest route from eastbound WA-24 to westbound WA-26 is via Columbia Street, but that doesn't make Columbia Street part of WA-24. Calling that just serves to confuse people.

I drove this a few weeks ago. There are no markings to indicate that Columbia Street or Wahluke Street are part of WA-24, or that WA-24 starts north of the WA-26 underpass. There is, however, a very nice "End WA-24" sign just *south* of the underpass.

(It was somewhat disconcerting to have my GPS tell me to take a left turn on to a narrow, unlit road it called "WA-24".)

Or at the very least, use more dots. It's tricky to click on a changeset link that small.

Thanks for your contributions.

Elevations in OpenStreetMap are always measured in meters. I've changed the elevation for Pendleton back, but keep it in mind for the future.

I noticed that you've mapped a number of things as "parking space". That's meant for mapping individual spaces in a parking lot; the tag for a parking lot is "car parking".

I'm not sure what you were trying to do with this edit, but it left a number of roads stretched across the map. I've reverted the dragging, while leaving the change to the road type of way/352858026 alone, but you should probably review things to make sure I got it right.

Unless I missed something, there weren't any good edits. The two surviving changes (which I reverted) were to turn Hallmark Apartments from "landuse=residential" to "natural=residential", and turn Walla Walla University into a park.

This one's an odd case: the county has the name as "Highland *Drive*", which would imply a public road ("Lane" denotes a privately-owned road), but the parcel map doesn't have a right-of-way for it, instead showing it as running on private property. I don't recall a street sign at the intersection with Waikiki, which argues for a private road, and there is a large "Private Road" sign, but no "keep out" or similar sign.

Thanks for your edits.

The "name" field should only be used for actual names, not descriptions. To indicate that an area is a football field, you can give it the type "American Football Field", which lets it show up in searches for football fields, and lets mapping software draw it with an appropriate symbol.

Wrong "Grandfather Mountain". The links you added were for one in North Carolina, not the one in Idaho.

The best place for finding out about existing tags is the wiki: for example, water=* or waterway=riverbank (there are two competing standards for tagging riverbanks: one groups them with lakes, ponds, and other water areas, while the other groups them with rivers, canals, and other water flow paths). Another good source of information is the "taginfo" website, where you can see how a tag is used: https://taginfo.openstreetmap.org/tags/water=river

If you want to propose a new tag, you can just start using it, though it's better if you go through the proposal process: osm.wiki/Proposal_process. Changing existing tags on an object should generally be avoided unless the new tags are more accurate and reasonably widely adopted.

If you want to do test edits, it's generally better to set up an account on the development server: osm.wiki/Sandbox_for_editing

In the continued absence of a response, I've un-done this change.

I've fixed it already, but about ten hours ago, the ways making up the relation created in changeset/47194830#map=9/45.8153/-119.9671 had no tags and were not part of any relation. However, stale rendering of map tiles showed that they had recently been tagged and/or part of a relation that marked them as a riverbank.

Could you do this in smaller chunks? I suspect this changeset is responsible for deleting the banks of the Columbia River between John Day Dam and McNary Dam, but it's such a huge changeset that none of the usual review tools works well with it.

Is there a reason why you're changing the river from the commonly-used "waterway=riverbank" to the rare "natural=riverbank"?

I've reverted the deletion. There's a tool in the JOSM editor to do this, but it's a bit tricky to get right if you're only trying to undo part of a changeset.

Consensus is that unofficial trails should be mapped, but should be marked as "informal=yes" (and "access=no" if people aren't supposed to use them).

See the discussion at osm.wiki/Talk:Proposed_features/Social_path and the linked mailing list discussions for why hiding these paths is a bad idea.

I'm not familiar with the Vespucci editor, but when you're changing the layer/tunnel information for I-90, make sure you're selecting an individual way making up the freeway, rather than the relation that groups all of the ways together into a single unit.

You've turned I-90 into a tunnel across the entire state of Washington twice now. Whatever you're doing, stop it.

Gossard Field still exists -- "Juno Elevator Road" doubles as the runway, the building with the curved roof is a hangar, and the FAA says that five airplanes operate out of it. I've restored the airport node and improved the mapping.