FYI, here is what those 3D buildings are supposed to look like: https://osmbuildings.org/?lat=39.72460&lon=-104.98584&zoom=18.4&tilt=30 (this is that KDVR building). The geometry looks good, but needs to have tagging fixed.

See corrections here: changeset/67366250

In this case, most of the "split into multiple buildings" are more a case of a malformed multi-part building than they are a case of incorrect geometry. Let me look into a good way of making these compliant with current 3D building standards.

Changes implemented in the following changeset. Most of these are just errors - I need to watch a little closer when merging in an area that has so much existing mapping, and so much active change.

changeset/67365553

The one area I haven't changed yet is the "split" buildings - the issue here is that the geometry is intended to work with a multi-part 3D building, but is not up to the old or current OSM standard for 3D buildings. My understanding is that the old convention was multiple "building=yes" combined in to a multipolygon, the new standard is a single building outline with all building tags, and then components tagged "building:part=yes" with geometry tags only, no address tags.

Let me do a little research on the best way to make these DRCOG geometries compliant with the building:part method - I don't want to lose the good geometry, but I also don't want to leave them rendering the way they are now.

Thanks for the detailed notes on this and the other changeset. I tried to preserve hand mapped edits while importing, but it seems I missed a few. I’m out of town at the moment, but will go over both sets next week.

I got a lot of those during validation last night, Geofabrik just hasn't caught up yet. It is clear we need to do more work on pre-processing the addresses, and working out good workflows for dealing with corrections as we go.

Hi David and Chacha - in my experience so far with the addresses in the DRCOG import, the "N " prefix is always wrong, but the "E " prefix is sometimes correct, and sometimes not... I retain it when the street name in OSM includes East already (in this neighborhood this seems common for the numbered streets, but rare for the named streets). For cases that seem uncertain, checking the street signs using Mapillary or Bing Streetside data has been helpful.