Well, they had it before, and I left them alone as a TODO in case they were supposed to be converted into a a proper park polygon (as some historic districts are like that), or merged with a nearby one. But if that's definitely no the case for these, my recommendation would be to remove the park tag.

Hello Matthew,
I noticed that you used the tag road=legislative on Oregon's highway relations. This tag does not appear to be documented anywhere and there are currently a series of organized edits to attempt to remove usages of the road=* key. Hoping you can help determine what the intended meaning is of that tag, and whether it can be either removed or perhaps replaced with more standard/documented tagging.

Hello Mister Vaccine,
I've been working hard over several days to clean up river issues in SC. As you know there's quite a mess in the data set and I've been doing my best to try to sort it out. Overlapping geometry, features that don't match imagery, stream objects in the middle of rivers, etc. The wetland mapping seems to be especially problematic. In any case, if there is an area that you think I've mangled or needs particular attention I'd be happy to put a special focus on it.

Thanks for catching this! There's a lag issue in JOSM that caused this problem :(

So there's actually no such thing as IUCN Category I -- there is only Ia and Ib -- protect_class=1 was an OSM invention. Of course mappers simply used 1a and 1b if that's what the IUCN category was. We've been working to slowly eliminate protect_class values outside of (1a,1b,2-6) in the United States and we've got pretty broad consensus here to replace them with plain English tagging. We recently finished removing protect_class=27, for example, replacing it with an ownership= tag instead. No-fishing areas tagged fishing=no, and so forth. We felt that the plain English was more useful to everyone and that there was no point in a classification system that didn't have global meaning. Anyways, happy to collaborate any time on protect_class issues, and if any more detailed information comes up on on Australia-specific usages, feel free to shoot it my way!

Great, thanks. Is the Australian usage of protect_class documented somewhere? I've been attempting to track and maintain global usage of protect_class on osm.wiki/Key:protect_class, and there isn't a lot of detail on Australia. Some of the more obscure values like 22 aren't terribly widely used.

Are you sure these are tailings ponds? This looks like wastewater.

Hey there! Looks like you deleted quite a few path areas in the memorial area. We had a fairly extensive discussion about these changes on the OSM US Slack (https://osmus.slack.com/archives/CCJ2P6KCH/p1612218171034700)

We agree that highway=pedestrian was the wrong tagging for these path areas, but rather than deleting them, they could be tagged area:highway=footway which is wiki-accurate and preserves the area geometries. What do you think?

Also as a general invitation, we hope you will join us on the OpenStreetMap US Slack! https://slack.openstreetmap.us/ channels #mappingdc #local-maryland #local-virginia)

Hi, welcome to OpenStreetMap! Feel free to join us in the OpenStreetMap US slack site, at https://slack.openstreetmap.us/

I'm username ZeLonewolf there, and you can also find me in the #local-rhode-island channel.

I am removing them as part of the current import of Maine boundaries:
osm.wiki/Import/Maine_Admin_Boundary_Import

Thanks for the fix! I maintain streetferret.com, so when a boundary gets broken it pops up on an internal to-do list.

Hey there, welcome to OpenStreetMap! So, this change actually left a gap in a couple town boundaries, and that's not easy see in the iD editor. Don't worry - I've fixed it already.

I'd like to welcome you to join the OpenStreetMap US slack (https://slack.openstreetmap.us), especially the channel #local-newyorkstate, where we try to coordinate on mapping. We'd be happy to help give you a tutorial on using JOSM which has more sophisticated validation.

Looks like this change left a gap in the boundary polygon?

Hello - parking aisles should be tagged highway=service + service=parking_aisle. The overall area of the parking lot should be tagged with amenity=parking. I've updated this parking with that tagging.

Hi there fellow Rhode Islander and welcome to OpenStreetMap!

We encourage you to join the discussion with fellow US mappers in the OpenStreetMap US Slack (https://slack.openstreetmap.us/), especially the channels #tagging and #local-rhode-island . Hope to chat with you there!

We discussed the change you made to Route 4 / Route 1 and concluded that the stretch south of Oak Hill road should be tagged as highway=trunk based on the presence of at-grade intersections, traffic lights, and driveways which make this road incompatible with highway=motorway.

See the Slack discussion here:(https://osmus.slack.com/archives/C2VJAJCS0/p1611623166062800)

Regards,
Brian (ZeLonewolf)

It's your call, it just came up in my list of new administrative boundaries and it didn't look right compared to other entities tagged admin_level=8 in Canada.

Hello, this boundary is a fragment and appears to be an error.

Is it correct that Old Town and Ndilo are both admin_level=8 and not simply neighborhoods of Yellowknife?

Thank you!

Thanks for fixing a broken boundary, do you maintain a list of boundary problems somewhere?