Looks like part of the river (osm.org/node/7805262616) was glued to a bridge that carries I-86 here, resulting in a misshapen bridge when you fixed the river's geometry. I'll unglue the bridge from it.

Hi,

It looks like you meant to just trace one building, but you (presumably accidentally) also mangled some road geometry around the intersection of Maple Street (NY-129), Wells Avenue, and Van Cortlandt Place. From the changeset tags, it looks like your editor tried to warn you about this. Please make sure to pay attention to these warnings, and make sure you haven't done something wrong accidentally. For now, I'll go ahead and revert all of the changeset except for the building that you added.

Additionally, I noticed that you added address information to the house that you traced, presumably from the node that was located on it. I would encourage this, as long as it's a simple case like this one, but just make sure to delete the node afterwards. Otherwise there would be two objects with the same address, unnecessarily.

With all that said, thanks for contributing to OSM! If you have any questions, feel free to message me.

You changed Broadway into a foot path. Please, be more careful in the future.

Hi,

I noticed that the value for the key "source:hgv:national_network" was altered on the ways of 198 that you touched. A space in the value was changed to the hexadecimal ASCII encoding of a space.

Do you recall doing this intentionally? If not, I suspect that this was a flaw in the iD editor, and I would want to make sure it's addressed.

Thanks!

Can you please explain why you made these roads tertiary?

Please don't do that. This data is already represented in the ref value on the motorway_junction node, and the junction:ref value on the exit way.

Hi,

Looks like you set `name=US 9` on a way here. If this wasn't an accident, please don't use name for this.

Hi,

If I was reading the history correctly, it looks like you added name=OH-44 to some ways. This is not the appropriate place to put this data. It is already represented in the tag "ref=SR 44".

Hi,

There has been discussion over this issue, and there proponents of either putting what is signed (in this case, just "M", not "MSP"), or nothing at all in ref for these parkways.

If possible, would you mind sharing which drivers you have feedback from?

Also, I have talked about a tagging scheme where something like "MSP" would be tagged as name:abbreviation=MSP, which could go together with ref=M. Perhaps any navigation app that might be used by these drivers could use this tag instead?

We have been discussing this issue in the #local-nyc and #local-newyorkstate channels in the OSMUS Slack. If it's convenient for you, we'd appreciate hearing from you there. Otherwise, you could continue to respond here.

Thanks!

Hi,

Adding barriers as ways makes it difficult for software to understand what is being blocked. Instead, you could try adding a node on the road at the point where the barrier is blocking access.

I'm personally not too familiar with the area, I'm just looking at the map and imagery. Whatever the locals say is good with me, I just wanted to make sure it was addressed. Thanks for putting in the work!

Hi,

Just from looking at the map, maybe the trunk classification should stay on US-9W to Delaware Avenue, and then onto Broadway? It seems like the more likely route for traffic, especially since it seems that the Kingston-Port Even Suspension Bridge is going to be closed for an estimated two years.

I see. My understanding is that highway=construction is for fairly significant construction, whereas as access=no could be used for shorter duration, and/or lighter repair work. Not sure which would be appropriate for this one, but both are an option.

If this ramp is truly under construction, and not just temporarily closed, please also add construction=motorway_link

From osm.wiki/Key:name :

Do not use name=* if:
...
- The feature is known by a generic term or description. Use a feature tag to indicate the type in a language-neutral, machine-readable way. You can also use description=* or note=* if other tags do not quite express what differentiates the feature from others of the same type.

In this case, I think a "generic term or description" would be something like "the ramp from NY-199 to NY-32", or simply "NY-199 Ramp". Basically, if the name is just describing what it is, that's better left to other tags. "Frank Sottile Boulevard" is an example of a name, where it's more than just a description of the object.

Hi,

Please don't tag ramps with things like name="NY 199 Ramp". If you really need to satisfy a validator, maybe noname=yes would work?

Hi,

In a case like this, where the name of the road on either side of a bridge is the same, it makes sense to tag the bridge way with the same name as the rest of the road. In this case, these bridges should have name="Southern Tier Expressway".

To tag the name of the bridge, one can use bridge:name="Chautauqua County Veterans' Memorial Bridge", and/or create a bridge outline and tag that with name="Chautauqua County Veterans' Memorial Bridge". If you'd like the name to be rendered on the map, you'll have to make the outline.

Hi,

You've somehow, perhaps unintentionally, created two overlapping motorways that do not exist. They seem to go back and forth between two parallel bridges that carries I-86. Please try to be careful with this sort of thing.

There are some turn restrictions that prevent against entering roads tagged as access=no. These kinds of relations are unnecessary.

It looks like you drew a service road on top of a cycleway (old NSP). This does not make sense.