Gotcha! My guess by the sound of it could be a sliding gate, although I think the most common tag is just the more general barrier=gate. It sounds like then that gate would be restricting access along a driveway or parking aisle on the 1018 Arnold site, which haven't been added to the map yet, so I can see why a mobile editor like Every Door would instead place the node on the nearest available way, which would be the main road.

I've already been making some parking lot and driveway additions in the area from aerial imagery - how about I remove the gate on Arnold Street, add in some parking aisles and parking lots on the private property, and if you like you can add the gate back in at its exact location on the ground?

Hi, this is a pedestrian-only type of gate that'd usually be found on a footpath between farm fields (barrier=kissing_gate). Having a gate of any kind on a major street like this that would disallow vehicle traffic seems unlikely unless there's been some substantial construction. Are you sure this node shouldn't be on a nearby footpath or somewhere on private property?

I've made comments on a few of your changesets recently so to be clear I'm not singling you out for anything, I've just been doing a lot of mapping around here recently and want to bring up possible fixes when I see something.

Thanks for the response and addressing this!

Hi, according to the City of Greensboro website this park is just closed for construction: https://www.greensboro-nc.gov/Home/Components/FacilityDirectory/FacilityDirectory/425/5540

If that's the case it would be appropriate to retag the way with "landuse=construction", rather than "was:leisure=park". The "was:*=*" key was:=** is intended to mark features that no longer exist. In this case, the park still exists and is temporarily closed for construction.

The construction tags can also be combined with "check_date=*" and "opening_date=*" to the extent that information is available, to help other mappers update the way as construction progresses and eventually restore the "leisure=park" tags as normal once it's fully reopened.

Thanks for the quick response! Looks good to me. That tag will just make it clear to other mappers that it's really demolished while still shown on most aerial imagery. The feature can be removed entirely once most aerial imagery services are up to date to show it gone.

It looks like all the identifying tags for this way way/208115794 were removed as part of this change, like amenity=parking and parking=multi-storey. Was this intentional to reflect a building demolition? If so the way should be tagged with demolished:building=*. Otherwise, the identifying tags should be restored.

Hi, sharing some feedback on these additions. "Commerce City North" as it's described is a named place encompassing a large area with many different land uses. I can see it's defined as a subarea of Commerce City but does not have separate administrative borders of its own. As such it's proper to use a point marker with place=suburb as I've added here: node/13365862822

Landuse=residential should generally be used to show a smaller area of land that is entirely or predominantly used for residences (and currently in use - not only zoned or planned for future development). There's more work to be done correcting the landuse areas labeled "Reunion" - it should be a place=neighbourhood marker.

See changes in changeset/175736566
Refer to landuse=residential
and place=suburb