Looks good. You're spot on about the fence ending there and that's fine as is. I connected the eastern end to the adjacent road in front of 4001 so that a routing tool could send users down that path. I also added some other connecting paths yesterday. Above all (i.e. regardless of the path type) make sure paths connect to other roads for route-ability. Keep up the good work!

Interesting area here. Is there any connection between Bay Drive and the park? How about on the other side? For routing purposes, be sure to connect a path to a nearby road. Also, the footway tag implies bikes and other modes are prohibited. If there's no specific bike/horse/ski/etc. sign then use highway=path instead. Generally I'll use highway=path for any path except sidewalks and narrow paved walking paths.

Hey there and Welcome to the OSM community (if no one has reached out yet). I see you've been doing a lot of park mapping in the Baltimore region, something I do a lot of, too. Thanks for all the hard work!

Hey, I saw this one in person. I love that you guys are adding them to OSM. Bravo!!

I forgot to mention that I put the Magnolia town boundary into a relation in this changeset

Hello! Welcome to the OSM project and thanks for this edit. When mapping paths, make sure to connect them to other features, that way computer routing systems can make the connections. If you have time, log back in and draw a connecting path from Central Park to the road.

Mostly out of curiosity, what data file are you using for the parks here?

nice work mapping parks around Maryland. I see you've been doing a lot of them.

What river misuse?

In your changeset comments, please add more information. Added "stuff" is not acceptable. osm.wiki/Good_changeset_comments for more

In your changeset comments, please add more information. Added "stuff" is not acceptable. osm.wiki/Good_changeset_comments for more

This changeset is flagged for mass deletion. Please explain the "incorrect data" here.
---

Published using OSMCha: https://osmcha.mapbox.com/changesets/59885716

Hello there. What was incorrect about the data that you edited here? Please provide a longer changeset comment when you edit.

Thinking back on this, what do you think about having eruv=rope, eruv=wire, versus eruv=yes paired with eruv:type=rope or wire. Tags like barrier and highway have their 'type' as the tag name.

The revert failed to fix the natural=water tags.

The edges of a river should not be tagged as such if there is a relation for the river.

Hey there, thanks for doing some editing around Baltimore. I noticed you deleted one of our new protected cycletracks. I reverted this changeset because it used old Bing Imagery. If you're editing Maryland, use the "MD Latest 6 Inch Aerial Imagery" in iD. It is higher resolution, leaf-off imagery that is updated regularly. As for this changset, we have a number of new protected bike tracks that are separate from the sidewalk and the car lanes. Watch out for those. Thanks!

user_5359: the OP and I are colleagues and so I walked him through changing this to a more appropriate tag (leisure=common). Cheers!

Phil, I've been looking for a dataset for adding hydrology to OSM that is both high-resolution and accurate. This changeset matches those characteristics, but the NHD data (even NHDPlusv2) isn't very accurate in my experience. For instance, look at https://i.imgur.com/a4Z9hTw.png and see how off the NHD flowline is. Are you manually correcting each flowline with imagery, or is there some other NHD source that I am missing. Thanks!

changeset under discussion on OSM US Slack: https://osmus.slack.com/archives/C1YP8DZ0A/p1502233346926171