OpenStreetMap logo OpenStreetMap

Changeset When Comment
116088255 over 3 years ago

With all due respect Adamant1, you don't get to dictate how the map is made just because you live nearby, and Bradley undid his changes because you bullied him into it. The way we classify highways in the US has evolved based on extensive discussions and is a collaboration of many, many, mappers working together to find common ground. The principles are well-established in osm.wiki/United_States/2021_Highway_Classification_Guidance
I'm sorry you find it vague. Consider it an opportunity to improve the guidelines for California to make it less vague.

116088255 over 3 years ago

Right now there's a glaring gap in the trunk network where CA 299 abruptly changes classification at Buenaventura Blvd. That's not an acceptable situation and is at odds with the wide community acceptance of tagging highway classifications based on the connectivity importance of roads. CA-299 needs to either continue as trunk until it meets another trunk or motorway, or else get downgraded all the way back to Blue Lake.

116088255 over 3 years ago

OSM is a collaborative project. In no uncertain terms I say, nobody "owns" an area. We're all in this together.

116088255 over 3 years ago

This edit is broadly consistent with the principle of tagging the principal, long-haul routes between cities of regional importance as trunk, regardless of physical quality of the road. As the principal, long-haul route between Eureka and Redding, CA-299 clearly qualifies as a trunk road and is consistent with the consensus that has emerged in the US for classifying highways after months of national discussions on this topic.

84843710 over 3 years ago

It was there from the original import, looks like. I'd recommend deleting it.

115925481 over 3 years ago

They should be corrected also.

115925481 over 3 years ago

admin_centre roles are used for nodes that represent the capital or seat of something.

115461391 over 3 years ago

Did you really review over 100,000 buildings manually in a single day?

115360150 over 3 years ago

DWG revert requested; ticket #Ticket#2022011410000126 due to quality & conflation issues with undiscussed fire station import.

115360170 over 3 years ago

DWG revert requested; ticket #Ticket#2022011410000126 due to quality & conflation issues with undiscussed fire station import.

115360182 over 3 years ago

DWG revert requested; ticket #Ticket#2022011410000126 due to quality & conflation issues with undiscussed fire station import.

115815501 over 3 years ago

I agree with this changeset. It is broadly consistent with the emerging consensus in the US to tag trunk roads on the basis of importance and not physical characteristics. As the major, long-haul route between Albuquerque and Wichita, US-54 is a pretty obvious case for trunk based on the guidelines in:
osm.wiki/United_States/2021_Highway_Classification_Guidance

Mappers in 26 states have drafted guidelines consistent with this guideline, and there's no reason that Oklahoma should be an outlier from the rest of the country.

115897081 over 3 years ago

Hi folks. It would be great if we could spend some time doing a real analysis of Texas roads and coming up with a scheme that everyone can agree with. It's really not useful to keep having these pointless edit wars.

Please see:
osm.wiki/United_States/2021_Highway_Classification_Guidance

This topic is pretty actively discussed on Slack (slack.openstreetmap.us) channel #highway-classification

As far as I'm aware, the draft by Clorox is really the only work on classifications so far, and it doesn't go below trunk. So running around reclassifying roads without first deciding as a community how things should be tagged isn't really helpful. As far as I'm aware, there's no mapping between TxDOT functional class and OSM highway classification that anyone has discussed and agreed on.

115781467 over 3 years ago

See this example also of how park boundaries and land cover are layered:
osm.org/#map=17/47.56564/-122.65959

115781467 over 3 years ago

The tagging scheme is here:
osm.wiki/United_States/Public_lands

See also: osm.wiki/Tagging_for_the_renderer

We do not add tags to "make the map look better", we enter valid geodata. natural=wood/landuse=forest is used on the actual areas that are tree-covered, not on boundary tags.

115781467 over 3 years ago

This is not correct. Wilderness areas are supposed to render as a boundary only. Land cover needs to be mapped as separate polygons.

100560876 over 3 years ago

Great catch! I just improved the river relation to follow USGS's definition. (see https://en.wikipedia.org/wiki/Suwannee_River#/media/File:Suwanneerivermap.png) Thanks for reviewing.

96224041 over 3 years ago

Surfer's End is the local name given to the westernmost section of Second Beach. I'm open to other ways to tag this.

115655313 over 3 years ago

Hi, the US consensus view on highway=trunk is currently:
osm.wiki/United_States/2021_Highway_Classification_Guidance

115299576 over 3 years ago

Wow, these relations are COMPLETELY messed up! I'm trying to untangle them currently, wish me luck.