This changeset introduced a few proposed lanes that haven't been installed. I rolled those ones back.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/109945329

Rolled back most of the new lane added along Carroll because it is marked as proposed by the official SBY map.
---

Published using OSMCha: https://osmcha.org/changesets/109944551

No park found here. Reverted in full changeset/110467699
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/109944041

Rolled back the cycleway update in this changeset by adding a shared lane to Division Street here: changeset/110467395
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/109943923

Hello again, I want to help fix some of this bike infrastructure you've added here to OSM standards. Do you have some time to chat about these, virtually? I think we could figure out what goes where.

Now, speaking of this edit, I think it would be fine to make the name "Bureau of Land Management - San Luis Field Office" though it is a mouthful. However, I must strongly advise against abbreviating the name. That is likely how "Tom" found this area in order to delete it. Acronyms run against OSM standard practices because a computer algorithm can easily abbreviate something, but abbreviations are hard.

You do sound cranky, but I get it! I have been mapping and importing protected areas on the east coast for years and am frustrated by what I call "landuse mappers" that have throwaway accounts and swoop in to untag major land reservations I've spent hours working on. I get it, seriously! That is why I support the well documented US PL Tagging schema, in defense of those edits. The landuse mappers are often of a different worldview where parks and nature reserves are not massive 10K+ acre areas but rather tiny parks in urban centers (or should I say 'centre'). The standard is not convoluted, it considers all of what OSM has to offer, and various ways people tag these federal places all over the US. Please join us in discussing this further. Most of this conversation happens in the #protectedlands channel in OSM US Slack. I stopped following the mailing lists in the 2014 ish era but stay heavily involved in the project through Slack, discord, and other outlets. There are a lot of enlightened people working on these problems.

Speaking of Slack, the way I found myself here in Colorado was via a request Andy Townsend posted on the Slack (see below).

Andy Townsend 1 day ago
Following a DWG request I've reverted http://osm.mapki.com/history/relation.php?id=9197995 . If there's a more that needs changing there changeset/99092967 may be the place to start. (edited)

elliottplack:maryland: 1 day ago
on it

elliottplack:maryland: 1 day ago
relation/9197995 tagged in accordance with osm.wiki/United_States/Public_lands#Bureau_of_Land_Management

Andy Townsend 1 day ago
It'd probably be worth pointing JOSM's validator at it as I suspect that might be some multipolygon issues that need looking at.

elliottplack:maryland: 1 day ago
Yes I noticed some of those. I’m not sure how to fix. It is the issues when two right angle corners share a node.

Read more: osm.wiki/Naming_conventions

Hi there. I made the update at the request of the DWG on OSMUS slack after they reverted it from someone that’d deleted the whole thing. Thought I was doing you a favor.

As for the tagging, it is a standard based on considerable discussion on slack, the mailing lists, and amongst people that are interested in such things. Please join us.

You’re welcome to change the name to something locals agree on. I took the name from the official source PADUS which is probably where you got the boundaries from. By OSM standards we shouldn’t put acronyms or abbreviations in names, which is why I removed it. Also, names aren’t descriptions, the two part name seems like a descriptive designation but again, I’m not a local.
Cheers

Hi there, appreciate the efforts here to add bicycle lanes and infrastructure around Salisbury, but this is not the way to do it. There are a couple of issues here. One, the cycleway should be tagged on the same roadway as the roadway--you should not ever create a new "way" for a cycleway unless it is a physically separated lane, like a buffered bike lane. cycleway=*

You will need to revise or remove all of these bike lanes.

Second, in OSM, we never abbreviate anything. Road names and lane names (if they are really named) should have their full spelled out name.

Third, it is improper and disruptive to other mappers to use a generic comment like "general transportation updates" in the comment. Each changeset should have a unique comment, see osm.wiki/Good_changeset_comments

Hi Scott, appreciate the effort here, but this is not the way to tag neighborhoods unfortunately. Generally, neighborhoods should only appear in OSM data if they are recognized administrative boundaries at the county level. I'm not sure if Montgomery County recognizes neighborhoods this way. Absent a formal boundary, you can still add neighborhoods to OSM a number of ways.

One of the most common is to map the residential landuse and add the name of the neighborhood to the area.

Another way, which can be done in addition to the first way, is to add a node at the center of the neighborhood and use the place=neighbourhood tag. Note the British English spelling. It is recommended to use a node to tag neighborhoods when the boundaries are inexact.

Take a look at the area in Baltimore County near Mays Chapel or Timonium for some examples. Or, look at administrative neighborhoods in Baltimore City. Feel free to send any questions.

-elliott

This changeset comment has nothing to do with changing the tagging for US National Parks. What's going on here?

A crossing could certainly be upgraded from marked to signals based on on-the-ground survey or street view. The developer of Street Complete is on Slack and based on a discussion about this subject, said he would improving the tagging recommendations accordingly.

Peter, hope you're well! MDOT SHA is working on a project to map crosswalks around the state using OpenStreetMap data! Very exciting!! I see you've added some crossings here. When doing so, can you mark them as marked or unmarked? This helps us determine if the crossing is a crosswalk or an opportunity for a future crosswalk. Check out my challenge too: https://maproulette.org/browse/challenges/21065

Hi Will, I was doing some crosswalk analysis and came across the non-standard crossing=controlled tag here. I assume that was just an error (meant to be uncontrolled?) I updated it to `marked`. Cheers

Hi there. This intersection has been vastly reconfigured just this year by MDOT SHA, the government agency responsible for the road, for which I work. I just fixed this intersection up based on the latest configuration including the addition of turn lanes.

Please do not at segregated turn lanes where there is no physical separation, as is the case here. These "slip" lanes should only be separated if there is a physical barrier separating them. Paint does not count.

Thanks for adding these! Please add some more if you can--very helpful for pedestrian routing.

Ah, yes, this is broken. Admin Boundaries are tricky. They represent where the town limit is. Garrett Park is a town (https://www.garrettparkmd.gov/) so it has a boundary. Those boundaries should not be altered unless the town does some annexation or something like that. I will fix this boundary with the latest boundary data. In general, don't mess with any boundary unless you know what the implications are. Feel free to reach out if you need help with or around them.

Specificially admin boundaries should be set in stone because, well, they are, by law! They are in the place they are and it takes laws and a signature from the governor to move them.

Census boundaries on the other hand are fungible, and change every 10 years with the census. I've been working on updating them around the state since the current boundaries in the map are from 2008. Those I tend to snap to roads and rivers, because their exact boundary is not set by law, more of a guideline.

I am working in the vicinity of Brookville too

I'm with you here. Trying to disconnect the woods from the streets is tough but having them snapped makes editing the roads harder.