Previously, I had used network=US:NY:Parkway:PIPC on a couple of these roads, as part of the 2022 NY Parkway cleanup. This was kind of a questionable value from the beginning, since the PIPC is an interstate compact. To reflect this, I have moved it up to the US: namespace, rather than having it below US:NY.

In addition, most of these initialisms are seldom used by the general public to refer to the roads. Even if they were used, they should go into another tag, such as short_name. I suspect that they were originally added into ref so that they would appear on Carto, which is tagging for the renderer.

Hi,

I believe that highway=motorway_junction nodes generally aren't supposed to have name=* values in the US; to express where the exit leads to, use destination=*, destination:street=*, destination:ref=*, etc.

I reverted this because I didn't hear back. Please feel free to comment if you disagree

Hello,

I appreciate your contribution here, but there are a few issues that I'd like to point out, so that you can avoid making them in the future.

First, please break up your changesets by geographic area. In this changeset, you made unrelated changes across the whole state of New York; these ideally should have been one changeset per city, approximately. This helps other mappers verify your work. Other mappers have informed you of this issue, but it seems like you have still been making large edits since.

Secondly, you changed a few road classifications in this changeset. Aside from this not being represented in the changeset comment, the roads that you upgraded to motorway should not be motorways. Please refrain from upgrading short segments of road to motorway, and try engaging with the community (see OSMUS Slack and Discord) before making such changes. Many states have their own guidelines which should be followed now.

The previous two issues were the most important ones here, but there are a couple more. You specified `damage:event=tornado` on way/442540277, without citing any sources. Please clarify what happened here, and how you know about it. The last thing is that descriptive names such as "Drive-in Cinema (disused)" should be avoided; "disused" should never go in `name`, and instead should be conveyed in either the opening_hours tag or by prefixing the amenity tag with `disused:`. If "Drive-in Cinema" is not the official name of the location, this should not go in the name either.

I appreciate you reading through these issues, and look forward to your response.

Thanks,
John

Hi,

This name is not signed anywhere along the road. Supposedly, it was once the commonly used name, but as a local I only ever hear it referred to as "route 17". As such, I believe that noname=yes with ref="NY 17" is the appropriate tagging for the road.

Note that this does not apply to NY-17 west of Binghamton, which is a separately constructed road that does have a signed name.

Hello,

This change is incorrect. Since there are traffic lights, traffic in the circle does not always have the right of way, and thus junction=roundabout is not appropriate. junction=circular is indeed the correct tag here, which is how it was tagged before.

Best,
John

It looks like you did, so I went ahead and fixed this one.

Hi,

It looks like you also made a mistake on this way: way/956455770

Did you mean 45 mph, instead of 445 mph?

Hi there,

It looks like you made a mistake with the speed limit on this way: way/826790148

Did you mean 35 mph instead of 435 mph?

Hi there,

It looks like you made a mistake with the speed limit on this way: way/9276911

Did you mean 30 mph, instead of 302 mph?

I didn't think the Bear Mountain section was as important, so I left it as tertiary. If you disagree with any part of this changeset, please leave a comment here.

Apologies for the large changeset here. There are likely a few unclassified roads here that may be better off as residential, but I feel that most of the changes are accurate. Note that unclassified does not mean "the classification is unclear"; it's just the next level below tertiary. Feel free to comment if you think I got something wrong.

I forgot to include it in the source field, but I also used Bing Streetside here in a few places.

Sorry about the bbox on this one; I got a bit carried away. I may have been slightly heavy handed with tertiary here, but I wasn't just marking any road with a yellow line as such either. If local opinion disagrees with any of these changes, please let me know and I'll happily readjust the classification.

Hi,

I know this is late, but you may be interested in the "Gridify" plugin in JOSM. It makes mapping parking spaces much, much easier.

Hi there,

I've moved "Saw Mill River Parkway Lands" to the note tag, since this isn't really a common name for these woods. Since there isn't really a commonly used name for them, I've gone ahead and added noname=yes as well.

Best,
John

Ah, I see now that I looked at OSMCha. Sorry to bother you.

Hi there,

It looks like you named several woods "Saw Mill River Parkway Lands". Is this name sourced from anywhere, or did you create it yourself? If it's the latter, I believe it would be better to provide no name value at all, following the "on the ground" rule.

Hi,

As a local, I disagree with this change. The path gets about 50/50 foot/bicycle traffic, so I feel that the old tagging is more appropriate. highway=cycleway, in my opinion, is better suited for cases where the path is primarily used by bicycles. bicycle=designated already results in Carto rendering it in blue, even if it's a highway=path.