Additional note: See osm.wiki/Proposal:_New_York/Highway_Classification for the new NY guidelines and osm.wiki/United_States/2021_Highway_Classification_Guidance for the overall project.

Additional note: See osm.wiki/Proposal:_New_York/Highway_Classification for the new NY guidelines and osm.wiki/United_States/2021_Highway_Classification_Guidance for the overall project.

See the comments on your other changeset at osm.org/changeset/114507228. The NY DOT has given this section of roadway ACC=3 (which makes it highway=primary) because it just provides a local/suburban connection rather through connectivity to other major cities.
---

Published using OSMCha: https://osmcha.org/changesets/114507515

Additional note: See osm.wiki/Proposal:_New_York/Highway_Classification for the new NY guidelines and osm.wiki/United_States/2021_Highway_Classification_Guidance for the overall project.

See the comments on your other changeset at osm.org/changeset/114507228. The NY DOT has given this section of roadway ACC=3 (which makes it highway=primary) because it just provides a local connection to downtown Albany and not through connectivity to other cities.

See the comments on your other changeset at osm.org/changeset/114507228. The NY DOT has given this section of roadway ACC=3 (which makes it highway=primary) because it just provides a local connection to downtown Albany and not through connectivity to other cities.

Hi Himké, For NY highway classifications, we're now using the state's Arterial Classification Code (ACC) to determine which highway=* value to use. The State DOT developed the ACC to inform routing importance (rather than physical structure of a road), which maps directly to the new process for categorizing highways that we're moving to in the US. highway=trunk no longer means "expressway" but rather now is being used for the the most important long-distance routes so that US mapping practice matches how highway=trunk is used in the rest of the world.

The NY DOT has determined that this section of the Lake Ontario State Parkway has ACC=3 due to it being a local connector rather than a long-distance regional connector. This maps to highway=primary+expressway=yes in OSM.

See osm.wiki/Proposal:_New_York/Highway_Classification for the new NY guidelines and osm.wiki/United_States/2021_Highway_Classification_Guidance for the overall project.

A large community of mappers are working on highway classification and discussing in the OSMUS Slack's #local-newyorkstate and #highway-classification channels: https://osmus-slack.herokuapp.com/ . It would be great for you to join us to discuss there before undoing these changes.

Hi Himké, For NY highway classifications, we're now using the state's Arterial Classification Code (ACC) to determine which highway=* value to use. The State DOT developed the ACC to inform routing importance (rather than physical structure of a road), which maps directly to the new process for categorizing highways that we're moving to in the US. highway=trunk no longer means "expressway" but rather now is being used for the the most important long-distance routes so that US mapping practice matches how highway=trunk is used in the rest of the world.

The NY DOT has determined that this section of the LaSalle Expressway has ACC=3 due to it being a local connector rather than a regional connector. This maps to highway=primary+expressway=yes in OSM.

See osm.wiki/Proposal:_New_York/Highway_Classification for the new NY guidelines and osm.wiki/United_States/2021_Highway_Classification_Guidance for the overall project.

A large community of mappers are working on highway classification and discussing in the OSMUS Slack's #local-newyorkstate and #highway-classification channels: https://osmus-slack.herokuapp.com/ . It would be great for you to join us to discuss there before undoing these changes.

An additional note that I just remembered: in the New York-specific guidance, the Niagra Scenic Parkway (957A) is specifically called out as a candidate for highway=primary+expressway=yes. osm.wiki/Proposal:_New_York/Highway_Classification#3._highway.3Dprimary

Hi andrepoly, thanks for asking! The short answer is that the New York DOT gives the northern part of the Niagra Scenic Parkway an Arterial Classification Code (ACC) of 3, which has been determined by other mappers in New York to correspond to `highway=primary`. Even though this road is of a grade-separated construction it has a low speed limit and doesn't serve as a connection to large regional cities like most of the motorway network.

Here is info on the update US Highway classification guidance:
osm.wiki/United_States/2021_Highway_Classification_Guidance
and here are the New York-specific guidelines developed and discussed by other New York-based mappers which draw on the DOT's ACC classification for top-level highway classification.: osm.wiki/Proposal:_New_York/Highway_Classification

I've gotten a lot of feedback on this project by mappers in the OSMUS Slack's #local-newyorkstate channel: https://osmus.slack.com/archives/CJ4QKU40H/p1636421497086700

As I worked through reclassify the top-levels of highways in upstate New York I've been compiling a list exceptions, and places where the ACC values given by the DOT don't necessarily make sense to me:
osm.wiki/New_York/Highway_Classification/2021_Classification_Project
A portion of the Niagra Scenic Parkway south of I-190 and the Rainbow bridge has an ACC=2 which would likely make it `highway=trunk`+`expressway=yes`, but it then seems to peter out into a network of ACC=4/5 city streets at its southern end rather than obviously serving a top-level connection in the road network. It you have local knowledge of this roadway, feedback would be very welcome!

Ha ha! You beat me too it -- I was going to reach out in the OSMUS #local-newyorkstate for local guidance after finishing more of the secondary->primary upgrades in this area.

Here's a screen-shot of the ACC classifications from NewYorkState Streets that I'm using in the Kingston area:
osm.wiki/File:NYS_Streets_-_Kingston_NY_ACC_classification.png

Given that Delaware and Hasbrouck have an ACC of 4 I was hesitant to upgrade them for the duration of a project as I'm not that familiar with this area. I'm personally OK with a small trunk-gap with a construction detour on more minor roads, but if the alternate connection makes more sense to you I'm OK with that as well. :-)

Oops, I meant from I-86 to NY-31.

I've fixed a missing section of NY-37 west of Massena and some overlapping roads caused by this change-set in osm.org/changeset/112510817

This change is a rounding up of the Shelburne Falls-Hinesburg road from a FC of Town-maintained "Major collector" to secondary, but it allow the lower part of Spear, Irish Hill and Dorset which have an FC of Town-maintained "Minor arterial" to avoid being stubs. As well, connecting the larger town centers of Hinesburg and Shelburne via secondary makes sense from a connectivity standpoint.

Note that Irish Hill/Falls/Marsett Roads have a functional classification of "Major Collector", but I'm rounding up to prevent Spear from being a spur in the secondary network.

Thanks, Ewen! :-)

Years of software development has ingrained in me this mantra for version-control comments: What changed? Why did you change it?

See comments on osm.org/changeset/111570311

See comments on osm.org/changeset/111570311

Hi tcarlisle, welcome to mapping in Open Street Map! I've reviewed a number of your change-sets and see that you're adding a lot of great detail to the map. Thanks for all of the good contributions!

I want to flag an issue with this and several other similar change-sets that you might not be aware of. In this change-set you added landuse=retail and highway=pedestrian areas to "paint" end-zones, lettering, and symbols on a sports field. This is a practice known as "Tagging for the renderer" and something we want to avoid in OSM. See: osm.wiki/Tagging_for_the_renderer

When mapping in OSM we want to be both precise and accurate. In the case of these sports fields, there aren't actually commercial areas or pedestrian areas on this field, so we shouldn't add these fake areas in an attempt to represent paint colors. There are many many different systems that use OSM data in addition to the map-renderings shown on openstreetmap.org, and by adding fake data to get a certain effect in one map we potentially confuse other users of the data, such as a data-user comparing the density of residential to commercial areas in a city.

To fix these fields I recommend removing these fake areas that represent paint colors.

If you have more questions about this or other mapping topics you're welcome to reply here or join other mappers discussing all sorts of topics on the OSM-US Slack channel at https://slack.openstreetmap.us/ .

Best,
Adam

Hi Alex, I just noticed that this change-set demoted Middlebury from a Town to a Village. Even though the place is referred to in Town documents as "the village" I don't think this demotion is correct due to the level of services available in the village compared to other communities. I've started a thread in the #local-us-northeast channel of the OSMUS slack to get more regional input on the town/village distinction as there is a wide difference in application across NY, VT, NH, and ME. If you'd like to join in that discussion, head here:
https://osmus.slack.com/archives/CC0LMFWBH/p1631729815087000