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

Thanks for the quick fix!

Hi, it looks like as part of your changeset you moved this node (node/1649972474) ~1500ft from its correct location, distorting the pedestrian path (way/775141614) and area attached to it. I assume this was inadvertent as it can happen when using the mouse to pan around if not careful. It looks like iD editor may have flagged the path as crossing other paths and buildings and you chose the option to tag it as a tunnel rather than revert the move. Please revert this change and review changes before saving in the future.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/174930469

The old MLK Center building way/1446608190 was demolished in 2023. It's since been replaced by a new building - corrected in changeset changeset/174837785

building=ger, that is

Spilled railway=* tag into name=* field, resulting in streets named "Louisa Streetrailway=abandoned". Please review edits before saving. Corrected by changeset #166839998
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/158726188

Yeah, that sounds good! Any gated communities that are residential only and have clear boundaries should be fine to have the name on the way itself.

Definitely there are a lot of places out there that don't observe the wiki as closely; like a lot of things on OSM it's hard to get every community to agree on one way of mapping things. Or, people aren't aware of the wiki, or the features are left over from before those guidelines...

Hi! Looks like we're both working on cleaning up the Midland/Odessa zoning imports. I figured I'd message to make sure we're on the same page. I would agree the neighborhood POIs that are out here seem pretty excessive. Also agree there are a ton of really odd relations that need to go. Although, my practice has been to leave the point markers for neighborhoods as is. Based on the wiki guidance for place=neighbourhood it's generally preferred that way instead of adding the name to residential areas.
The reasoning being that a neighborhood can be made up of many different landuses, and usually has loosely-defined borders. I've got no issue with culling down some of the neighborhood marker points if you've got a good source on the local neighborhoods, but would suggest not replacing them with named residential areas, or even named multipoly relations. Let me know what you think. Mainly looking at these pages:
landuse=residential#Named_residential_areas
place=neighbourhood?uselang=en#Node_or_area?

Yeah, I'm certainly one who gets annoyed seeing a massive bounding box so I hate to do it myself

My pleasure! Was just clicking around some Osmose Lvl1 issues looking for easy fixes.

Yikes, sorry about the size of this bbox. I'm still getting the hang of Osmose editor, clearly.

Hi and welcome to OSM! I noticed that as part of this changeset you added building=school to the three areas tagged as amenity=school. That building=* tag should be used only for features that are themselves a building. When added to the school grounds, that would suggest that the whole property is encased in one large building that overlaps the school buildings already on the map. I've corrected these by removing the building=* tags and wanted you to know for the future. Thanks!

Hi, these buildings and road have been demolished as of July 2024 or earlier and were removed from the map as part of changeset: changeset/154419262

Since aerial imagery has not been updated recently enough to reflect the demolition I've now marked the buildings and road as demolished:*=* to prevent future confusion. These can be removed entirely at a later time when most aerial imagery is updated to reflect current conditions. See changeset/163693122

Hi, as part of this changeset way/195029792 was retagged from landuse=retail to building=yes. It's likely this was accidental, but make sure to check the edits you make and review the warnings shown by iD before saving. Reverted with changeset/163261604

Resolved above issue in changeset/161863933

Hello, as part of this changeset Auten Road (way/787967132) was moved, as a whole, roughly 50 feet to the south - possibly result of an unintentional Move command used when the whole feature was selected. This caused some crossing ways, partially addressed by changeset#156691847 - and overall misaligned the road. Please take caution, especially with a large changeset such as this, and check the elements you've modified before saving your edits publicly.
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/156285571

Hi, this new natural=wood feature (way/1351864058) was drawn to almost exactly overlap the existing landuse=grass feature (way/1303809959). If you believe natural=wood to be a more accurate descriptor of the land cover at this location, it's recommended to re-tag the existing land cover feature, rather than add a second conflicting way on top of it.

Corrected by changeset/161576611

Hi, a couple comments:
* the new building (way/1351224883) overlaps an already-existing building. If this was intended to map a sub-part of the building with different height for 3d rendering, this part should be tagged as building:part=yes rather than building=yes.
* the name=* tag for way/1351224883 is all lowercase, which should not be used unless a given place's name is stylized as such in the real world.
* typically places should only be named on the map once to reduce clutter. In this case the apartment complex "The Ivy at Berlin Place" is already mapped and named as residential=apartments, way/15907297

For reference:
osm.wiki/Names#Good_practice
building:part=*

Welcome to OSM and thanks for adding to the map! A couple notes on this changeset:

* Typically, it is not advised to use landuse=residential to cover a large region as though it were administrative boundaries; use it only for land area predominantly used for residences. i.e. it shouldn't overlap farmland, lakes, etc. See the wiki here: landuse=residential

* This area was added to the relation for the administrative boundary Keeler Township (relation/10229316), perhaps by mistake? The area does not in reality define any part of the township boundaries.

* While Sister Lake is locally known to be the region around these lakes, it is not an incorporated community with any defined administrative boundaries. Typically in this case a point feature should be used to mark the general location of the place rather than an area boundary. In this case, a populated place marker already exists on the map: node/153496066.

I will work on correcting what needs to be corrected. Hopefully this is helpful feedback to keep in mind going forward. If you have questions or comments feel free to respond in this thread.

Hi, a node in County Highway U (way/21427494) was pulled out of alignment and snapped to water (way/800094523). Corrected in changeset/160322047
---
#REVIEWED_BAD #OSMCHA
Published using OSMCha: https://osmcha.org/changesets/159963205