I've reverted this change in 134951199

In Newport I go with what's signed on the ground as they're generally pretty good about putting signs on their roads and it lines up with OSM's "on the ground" rule. There isn't a sign here like there is for every other city street, so I figured it was more appropriately tagged as the internal road system to an apartment complex. But feel free to run up it anyways :-D

Relation: Wenmiao Subdistrict (9882827) is broken, are you able to fix it?

I've reverted changes to borough tagging in New York City to restore the status quo pending community discussion. Thank you HeadAsylum432 for attempting to improve the map, but it is important to discuss significant changes with the local mapping community before making them. I would encourage you to join the OSM US slack server (slack.openstreetmap.us) in the channel #local-nyc to connect with other mappers in the city on mapping issues. The tagging of NYC boroughs is a fairly contentious topic that shouldn't changed unilaterally.

Please don't edit boundaries in iD, it will not warn you of a mistake. This edit left a member way with a missing relation role.

At the time there were active discussions on how to tag State Parks, and this was something I came up with at the time to express the concept. If I were tagging it today, I'd probably change it to leisure=nature_reserve or boundary=protected_area + protected_area=recreation, perhaps with a protect_class=5 to preserve osm-carto compatibility. There's some extensive discussions in the #protected_area channel in Slack. Feel free to improve the tagging if you like.

A better practice may be to place the node close to the entrance and well-map all driveways and walkways. Then routers should be able to make the most correct choice. I would do that and if the router is still not behaving correctly, open a ticket with Magic Earth. Note that many apps that do routing will have a significant delay between data changes and when it shows up in the app. Putting the address node in the deliberately incorrect spot is bad practice for what I hope are obvious reasons.

Please do not vandalism OSM for your golf game.

Hi, this boundary is broken (Menasha), are you able to fix it?

Hi, can you please provide a more descriptive changeset comment?

Hi! Thanks for fixing the boundary of Anderson Township. Unfortunately two of the segments (Burney Lane) had a role of "inner" when they should have been "outer". I see that you're using JOSM. If you hit the JOSM validator before uploading, it should give you a warning "multipolygon is not closed" - that's the indicator that there's something that need to be corrected.

I've fixed the problem on this boundary, so nothing to do on your part, just wanted to make you aware of the issue in case you were wondering why the JOSM validator was give you an warning!

Can you take a look at the weird seams in this location?
osm.org/query?lat=29.7514&lon=-83.1565

Restored the original node history in changeset/130984993

Looks like it was. How did you manage to find that?

Thanks!

Fixed in changeset/130888580

Hi, this changeset marked part of US 412 as a dirt road, is that accurate?

This is a geographically wide-scale edit of items copied from an external database. That's an import in my book. Looking at each item manually to check that it was copied correctly out of the book doesn't turn it into a survey.

The source provided is CC-BY 4.0 and must be reverted because the license is incompatible with OSM.

Yeah, I would regard these one-by-one boundary updates to be completely routine, casual mapping activity in the US. This is also being discussed in OSMUS Slack #imports and there seems to be general agreement on this point.