Hello map per,
Thank you for working to make our tagging more consistent in the United States. I agree that in most cases, leisure=park on a national park or protected area is a mistake. However, in some cases this will be correct tagging. I would ask you to note the following for working with protected areas in the US:

1. Please review osm.wiki/United_States/Public_lands, which documents our community consensus on how these lands should be tagged. If you believe something there is documented incorrectly, it should be discussed and not unilaterally edited.

2. Please inspect overhead imagery before removing the leisure=park tag. If it looks like a leisure=park, it's probably a leisure=park, even if it's also a protected area or national park.

Happy mapping!

Oh look, the latest sock puppet.

Yes.

Unfortunately "it's complicated". This section of road is currently in the midst of a low-speed edit war with editors changing it back and forth between trunk and motorway. (See: osm.org/way/646162724/history).

The bottom line is that mappers are changing this road back and forth and not having an open dialogue about what it should be and documenting that consensus. So just continuing to toggle it back and forth is not particularly helpful to getting the issue solved.

The US community is currently in the midst of developing national and state-by-state guidelines for highway classifications. That work in progress can be found here:
osm.wiki/United_States/Highway_classification

While mappers in 14 states have drafted or implemented these national and state-specific guidelines, nobody has yet to step up and do that for Wisconsin.

The appropriate place to discuss this with the community would be either the talk-us mailing list (https://lists.openstreetmap.org/pipermail/talk-us/) or the OpenStreetMap US Slack (https://slack.openstreetmap.us/) in the #highway-classification or #local-us-midwest channels.

Hope to chat with you soon.

Hi,

Please explain why you've downgraded this section of US-151 from motorway to trunk.

Also osm.org/changeset/112597165

Reverted in osm.org/changeset/112597141

Have these roads been restored yet?

Lee's commentary is larger than this bounding box.

Hello,
It appears that you are editing on behalf of a company. If so, that's perfectly fine, but we require that you comply with OpenStreetMap's organized editing guide:
https://wiki.osmfoundation.org/wiki/Organised_Editing_Guidelines

Please confirm that you understand this request. Thanks!

Can you clarify the source of this data and whether it is ODbL compatible?

Hello MusLak,

Please remove the waterway=riverbank that you added and restore the original tagging of natural=water + water=river. This is the preferred tagging.

May His noodly appendages bless us all.

Hi, this change broke a boundary:
osm.org/relation/125662#map=14/42.3449/-87.9509

Are you able to fix it?

Hi, this edit broke the Forrest Park boundary, are you able to fix it? osm.org/relation/133493#map=17/39.01482/-77.03169

Hey, just curious if there's documentation somewhere about what "old-style multipolygons" are, how to identify them, and what the fix is?

Mapping things that you actually know are there is hardly a new concept. Especially when your data source is a smart watch GPS under tree cover and roughly in the same location as an existing trail. Please, do not make things up and map what you know to be actually there.

We are not asking you to exclude "this particular trail" We are asking you to stop mapping trails from Strava heat map which are not visible on imagery and you haven't personally surveyed.

Have you surveyed these trails or are you just assuming that there are parallel trails? GPS bounce is very common in the woods.

Have you surveyed this trail to confirm that what you're seeing isn't just GPS drift?

Thanks!