Not sure if this was an accident or not, but you set `maxspeed=80 mph` on a road in downstate New York. This is certainly not correct.

Hi,

In the future, please try not to delete the old way, and instead reuse it. This helps mappers understand how things have changed better.
---

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

Can you please be more descriptive with your changeset comments? This helps other mappers understand what is changing.
---

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

This one looked perfect, but it's gone now: osm.org/way/1017967759

For example, this way was not connected to any road, and looks fine to me, but it was deleted anyway: osm.org/way/1023058680

Okay, I looked more closely over the things being deleted. I'm okay with many of the grass landuses being deleted and remapped. Each of them are not very significant, and many of them are very poorly mapped.

However, the shopping centers, schools, and residential areas I would say to fix by hand. These are more significant features that have history more worth preserving. Please read osm.wiki/Keep_the_history .

Also, please use your changeset comments to communicate to other mappers why and what you're cleaning up.

May I ask which navigation program was being used, and which overpass the issues were happening at?

Although I dislike it, I don't think landuse being connected to roads should cause navigational issues. Are you sure the issue wasn't that she accidentally connected the two crossing roads as she drew the landuse?

Why did you delete the landuse for "Indian Trace Shopping Center"?

Oops, meant to ask why you were deleting so much landuse.

https://osmcha.org/changesets/118841412

Why are you deleting so much landuse?

See comments on osm.org/changeset/97404922

Also, destination is probably not being used correctly here. It is supposed to be used on ways that have signage nearby saying where a driver will end up if they choose to follow that way. Shortly after the signage, the destination tag should be dropped.

I'm going to remove this tag, but if there is signage saying McAllen, please add the tag back only where that sign is.

Hi,

There's a couple oddities with the way you're tagging I-2 here. First of all, network=US:I and direction=west should go on the route relation, not the ways in it. This may have been an accident, let me know if so.

The other thing is that ref on ways isn't supposed to contain the direction of travel. It was already fine as it was: `ref=I 2;US 83`.

I agree, name=I-95 would also be wrong. But if the feature doesn't have an actual name, and is instead mainly referred to by its ref, it shouldn't have a name at all. official_name might have been originally created for that, but it is also used for this purpose in quite a number of places.

I'll join the CT discord if you give me the link, but you should also join the OSM US Discord and/or Slack if you're not in them already.

No, this is not signed. Where did you get this information?

Still waiting on a reply here. I think this tagging is not correct. Would anyone refer to this road by this name in common conversation? Or would they just say I-95?

Hi,

Please refer to the wiki when using new tags. For this one (barrier=cable_barrier), here's the wiki page: osm.wiki/Tag:barrier=cable_barrier

This page says to draw a way _along the barrier location_. You put the tag on NY-17 instead, which is not correct.

I'm going to remove the tag from the road, and if there is indeed a barrier here, please draw a NEW line where it is, and put this tag on it.

Thanks,
John

Hi,

Welcome to OSM! There's a couple things I'd like to point out here.

First of all, it looks like you didn't remove the node after mapping out the pool as an area. Please do so when doing tasks like this.

Second, please don't put things like "pool" in the name tag. It looks like your editor warned you about this too, and you must have clicked to ignore the warning. Please give careful consideration to any warnings shown to you, as it will help reduce issues with the data you produce.

Specifically, "pool" would be an example of a descriptive name. Essentially, you're describing the element with your own words. This is not really useful to anyone; the fact that it's a pool is already represented in the other tags. If you want to know whether something in OSM should have a name, consider how you'd mention it to someone in conversation. Would you say "that bridge by the park"? If so, don't put a name on it. Or, would you say "the George Washington Bridge"? In this case, you would put a name on it.

Hopefully my examples help you understand the rules for this, but please let me know if you still have questions about this or anything else in OSM.