Hey Yushclay, I was looking at this and some other changes around (see also changeset/176153902) and I have to say it seems to me like many of these streets are overclassified. Walking around this area, most of these roads you've upgraded to tertiary seem like they're not really for through traffic: you'd only use them if you were accessing the direct area. Not every road in a business district should be tertiary, that makes the road classifications too flat and obscures which roads are actually used for through traffic IMO. What was your rationale for upgrading these?

I don't really understand why you removed the building tag here, POIs are commonly tagged as both the building and what's inside of them. And if you want to separate them, please at least draw a separate building=roof way rather than deleting valid data.

Hey, I noticed you edited the end point of this freeway, which has been the subject of edit wars in the past. My understanding, per osm.wiki/California/Map_features#Highway_classifications, is that freeways ends should be mapped to agree with the signs. There are big signs announcing the freeway start at 4th St (//www.openstreetmap.org/node/9523487420) and end at Lincoln (node/9523487423), more similar to how the road was mapped before. It also matches where the road undergoes a significant downgrade from 65mph to 45mph speed limits and other construction issues that I think are better tagged highway=trunk + expressway=yes. Could you explain why you decided to upgrade these segments to motorways, and do you have a more authoritative source than wikipedia that would justify overruling the ground truth?

Yes, but none of those seem to me to be population centers of regional importance, nor are these roads part of a network of expressways, so I don't really think they meet the criteria of osm.wiki/United_States/2021_Highway_Classification_Guidance#Trunk. I'd say that in other parts of CA and the US, roads connecting freeways to colleges, retail districts, and midsize military facilities are typically highway=primary.

I wasn't sure if it was meant to be this: node/8254222443, which is a lot closer, but also in a location that might be hard to survey...

I'm not really sure I buy Rosecrans/Lytton/Barnett as a trunk, what important destinations do they lead to?

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?