Merci pour l'avis, j'ai supprimé les routes.

Thanks for noting these issues (and comments on other changesets), I'll be starting to work through these areas and address problems noted.

Hello and welcome again to OpenStreetMap! This particular historic district is based on the former location of a mill which sat along that river. Though I agree that putting it directly in the river is probably not the right location, so I've moved it a few meters south to where descriptions have the mill ruins.

JOSM swallowed my changeset comment. Should have said: "Move historic district node over the mill ruins"

JOSM swallowed my changeset comment, should have read "Cleanup water and natural features, retrace and align to imagery"

Yeah, I'm not sure either, except that I'm confident this funny looking polygon is not actually what's real on the ground. But in any case, I just resurrected, merged, and simplified the original stream geometry here: osm.org/way/76748067

I guess it's a local problem now :)

Thanks for the note, I've restored the missing section of stream in osm.org/changeset/109162161 and marked it intermittent as it is completely dry in the Ortho HR imagery. Note that there is not much of an issue with tree cover in that spot and the water geometry was clearly mapped through open areas without trees (and without stream). I updated the stream so that it matched the ditch line that was visible in several spots.

The stream way is here: osm.org/way/587928916

Hi,

It seemed like this tiny stream was better represented by a waterway=stream. The areas looked like they were bad import data. Is there a better imagery source I should be using? I was using "Ortho HR" which indicated it was less than a year old? Is there a different source that is better for mapping water features?

Generally speaking, these changes were all corrections to issues identified by the JOSM validator on a sparse download of river areas and waterways. The most common issues were geometry overlaps and islet tagging.

@Lee Carré I am well aware of the various discussions (many people at this point are subscribed to the changesets given the recent community interest in @Friendly_Ghost's large changesets), and I am following them with great interest. I realize that you are passionate about this topic, but personal attacks are simply unacceptable and I ask you to stop.

@Lee Carré: please stop with the insulting language. It is not helpful and does nothing to advance the discussion.

Okay, now you're just showing off :)

Hello, this edit has caused a gap in the boundary of Cleveland:
osm.org/relation/115393

JOSM swallowed my commit message. Changeset comment should have said "Fix tagging issues on Ohio boundaries"

Hey there, can you give a bit more detail about what these changes were? It's kind of a large changeset so we're not quite sure what actually changed. It looks like some route relations were deleted?

Hi, you tagged this as a track road, however, it looks like there are houses on this road, therefore it should probably be highway=residential with the appropriate surface tags for unpaved roads.

This does not appear to be an administrative boundary.

Also, be sure to validate in JOSM, as there were a bunch of errors reported for me. You can use Shift+Y to simplify nodes.

Here's a YouTube video I created a few months ago describing the ins and outs of river area tagging for a more detailed explanation :)

https://www.youtube.com/watch?v=c5YwXDKGr2Y&t=10s

Also, I noticed that you used area=yes, which is not needed, and water=intermittent, which is a mistake - it should be intermittent=yes.