Please also don't reabbreviate addresses, they should be fully spelled out like they were before (K Street Northwest, not K St NW)

I should add, a lot of discussion of highway classification in the US goes on on the OSMUS Slack, you're welcome to join there! https://openstreetmap.us/get-involved/slack/

The #highway-classification and #local-california channels are probably most relevant here

I don't understand how this road could be tagged differently in either direction. Hw=trunk should denote importance to the overall road network, not access or whether there are driveways or something.

Hi Yushclay, please note that this exact road is documented (as "CA 1 north of I 105") in the wiki: osm.wiki/California/2022_Highway_Classification_Guidelines, and has been subject to switches in its tagging in the past. I stand by my assessment that the road's importance undergoes no change south of La Tijera, only a build change, hence hw=primary + expressway=yes is appropriate. Why did you upgrade it to trunk?

Hi Yushclay, I can't say I agree with tagging this road as highway=trunk + expressway=yes. It seems like you've been on a flurry of reclassifications across SoCal, can you explain what logic you're using here? These seem to violate the agreed consensus on the classifications page (osm.wiki/California/2022_Highway_Classification_Guidelines) by signficantly expanding the definition of highway=trunk in California to include nearly any "built-up" road.

Ah makes sense, thanks for fixing!

These two restaurants was also moved to the wrong buildings, basically on top of their neighboring businesses, when they were previously in the correct places: node/11265325019 node/490254362. So I'm not sure how your import method is deciding to move nodes around but its accuracy is worse than the existing OSM data.

Hey, thanks for adding all this info. There are a couple of edits in here that look a little weird to me though. For one, it seems like for a couple of points you moved them out of their buildings? Such as node/490254388 and node/4111902590.

Also, from taginfo, I think cuisine=salvadoran is much more common than cuisine=el_salvador. And this doesn't really matter much, but I don't really think you need to add source= tags to the objects you modify, since it's on the changesets and there's info on the existing objects that isn't sourced from meta.

Most highway=pedestrian can be used by other modes and can fit motorized vehicles, see highway=pedestrian for examples. Given that hw=pedestrian is used for this situation both elsewhere in Rock Creek Park (way/6061851) and on other similar roads that were made exclusive to pedestrians and bikes in other cities (e.g. way/318476063 in New York and way/27031304 in San Francisco), I really think this should be switched back to conform to the normal usage.

Highway=pedestrian render plenty prominently in all the OSM-based apps and maps I use. Frankly, if a service isn't rendering/routing along these correctly, even with bicycle=designated, then it should be updated, rather than mistagging for the application.

(PS sorry for the delayed response, busy week for me non-OSM-wise)

Hey there! Please note that place=district is a specific administrative division in some countries: place=district?uselang=en. The tag is basically unused in the US: https://taginfo.geofabrik.de/north-america:us/tags/place=district#overview.

place= tagging is a little counterintuitive to Americans since the names come from British English: the urban hierarchy within cities goes 'suburb' > 'quarter' > 'neighbourhood' (see place=*#Populated_settlements,_urban). So since place=neighbourhood is the smallest possible urban place, it's OK for it to be within, say, Capitol Hill (a place=suburb node/158502198). Neighborhoods also don't have to be official to be mapped, they just have to be a name for an area known to locals. So I would be in favor of switching Lincoln Park back to place=neighbourhood.

Happy mapping!
Will

I was just here a couple days ago and the road was closed to traffic, can you clarify what prompted you to change this from hw=pedestrian to =unclassified?

Thanks for regularizing these tags! But please note, in the United States, a "ton", or 2000 lbs, is actually a short ton, not a metric ton. So a weight limit of 10,000 lbs should be mapped maxweight=10000 lbs or maxweight=5 st, not maxweight=5 t as you've changed a few to here. See maxweight=*#United_States for tagging examples.

These appear to be fictional edits, so I'm reverting them. OSM is not a toy. If you want to create fictional maps, you might enjoy UMap: https://umap.openstreetmap.fr/en/.

Hey, thanks for going through and improving these routes! I was just looking in this area and it seems like this changeset added a lot of duplicate bus stop nodes right next to existing ones, with slightly differently formatted names. Maybe the conflation was a little off somehow?

Great, thanks for addressing this so quickly!

Hello, are you sure there are traffic signals at this crossing? It doesn't look like there are from the Bing street-level imagery or aerials.

Ah sorry to hear that! If it's OK with you, I (or you) can reach out to the Data Working Group, [email protected]. They have tools to handle these kind of vandalism issues by mass-reverting the affected objects. Then folks like me will probably stop pinging you. Glad you've regained control of your account though, sorry about the hassle!

Sorry, what's going on here? Seems to be a spam link in note=* for a bunch of restaurants and roads?

Hey, thanks for monitoring these! Just in case you're not aware, there's an ongoing OSM community effort among locals in the area to switch the Better Bus routes in for the old routes, which we're keeping track of here: osm.wiki/Washington_DC/Better_Bus_Network. One thing to note is that since some of the new routes closely parallel discontinued ones, it's nice to keep the old ones in OSM until the replacement route has been mapped. For instance, it was really handy to have the Z8 relation when I was mapping the new M54. I took care of the ones you deleted in this changeset earlier this evening (as maybe you saw), but just something to be aware of! Feel free to join in if you see any routes missing!

Hi, it looks like this bank is already mapped at this location! node/12342520794. Please make sure to check that the location isn't already there when you add things to the map. Thanks!
~willkmis