Hi there, deleting a trail because it’s ‘not a trail,’ is not the way to go. Why isn’t it a trail? Is it closed? Private?

FYI osm.org/user_blocks/6865

This was not a cleanup, but rather a full scale replacement with invalid data. It appears that the source was highly generalized and this erases much of the work by other editors.

Hi there and welcome to OSM fellow Wandrer! I love your goal here. Keep it up. One note on the OSM side (I represent the OSM Data Working Group, in effect the regulator of the map). No Trespassing signs are better to be tagged as "access=no" as in, no trespassing. Private access is meant for things like driveways where private access is allowed. Add this to your OSM repertoire. Thanks!

Hi DUGA, I know that a lot of the fire roads in the reservoir are not maintained regularly but the track highway classification is a matter of designation rather than use. The idea is that tracks can support a four-wheel drive vehicle for forestry access, exactly what these are for. Many are now overgrown; I have seen it too.

This occasionally comes up in discussions whether they should be downgraded. The standard is to leave them as-is based on the designated use. Take a look at this recent discussion. https://community.openstreetmap.org/t/conflicting-global-wiki-definitions-for-deciding-between-tracks-and-paths-based-on-passability/4540/4?u=elliottplack

Hi there, was there any discussion or documentation for this import? As you may be aware, we have a policy for importing data, such as these E-911 addresses. In this case, the all-caps addresses are in incorrect form for OSM. A community driven import would have flagged this. Please let us know within the next 7 days how you would like to proceed, i.e., fix this or have it reverted. Thanks!

Elliott Plack, OSMF Data Working Group

edit. that is set to a hiking trail so it may not show up on the bike maps, maybe it shouldnt? Do you know if the Mason Dixon Trail is also a bike trail? I saw you added the bike tags here.

Good point, I think you're right that the second name is that of the relation, edited by someone else not aware of adding those. I'd drop that name and leave it on the route. If you look on OpenCycleMap, you can see the relation clear as day.

Hi, thank you for mapping this. I have done some trail mapping in here but was unsure where the MD Trail runs. Do you know of any good reference maps for it (beyond OSM of course)?

Is that section actually named "Lower Susquehanna Heritage Greenway Trail / Mason-Dixon Trail" with the slash like that? Sometimes folks get a little over enthusiastic about OSM trail naming (I realize you did not assign the name). osm.wiki/Names#Name_is_the_name_only

Hi there, I see you recently surveyed the lower section of the Mason Dixon trail. The bridge towards the lower end is closed for construction, so I'm curious if that should still be a part of the trail.

Fixed it for you: changeset/131210571

Hi there, please do not name things with a description. The name is for the name only. You can put the opening date in the opening date tag in the name tag.

—
Elliott Plack
OSMF Data Working Group

Uh huh. This is a street complete edit. Are you familiar with app?

Hi there Trail Runner,

While we all appreciate your dedication to trail mapping, this sort of renaming of the C&O by milepost is a violation of the OSM policy that "Names are Names Only". See below. You need to correct these names immediately, to whatever they were before.

This edit split the path into dozens of unneeded segments to break it up by milepost too. That is unnecessary and adds a lot of clutter to the database, such as for the management of the plethora of relations that use this route.

The more I look at this, the more it looks like a full revert of this and the other C&O changeset may be warranted. Please help me understand what inspired you to name the trail this way and if there are any others that have been named this way.

Thank you,

--
Elliott Plack
OSM Foundation
Data Working Group

Yes, there’s a photo of it on the wiki, the one with the giant “NO”

Sent a warning via this block osm.org/user_blocks/6717

Hi there Mykol404. I didn't see an entry for these parking lots in the osm.wiki/Import/Catalogue

Could you provide us with any documentation on this import, e.g., discussions with other mappers, a source dataset, a wiki page, etc.?
--
Elliott Plack
OSM Foundation
Data Working Group

Hi there,

Please don’t invent access tags for roads on military bases. This causes problems for data consumers that interpret OSM data. access=military has no definition on the OSM wiki. Private access means that the general public is not allowed. That is certainly the case at NSA / Meade.

Thanks for understanding,

Elliott Plack
OSMF Data Working Group

Hi there, welcome to the OSM project. I see you requested a review. These edits look good at first glance. What inspired you to try your hand at lane editing?