[Talk-us] [Imports-us] OSM-Colorado Mappy Hour Denver Buildings Import Discussion
miketho16 at gmail.com
Wed Jan 25 01:20:19 UTC 2017
This is very exciting to see this coming along. Let me know how I can
help. Hopefully we can use its success to convince other government bodies
in Colorado to allow us to import their data into OSM! Here are a few
re: "The Denver Regional Council of Governments (DRCOG), in partnership
with local governments and public entities, has purchased detailed
infrastructure data..." - This makes it sound like they purchased a
commercial dataset, which raises questions about licensing in my mind. I
suspect that what happened is they "contracted for the collection of
detailed infrastructure data..." In other words, it was work for hire, and
they own all rights to the data,. Therefore, as long as the right official
within DRCOG signs off, we are good (no third party vendor has any
ownership rights in the data and doesn't have to be consulted). If this is
in fact the case, someone may wish to change the wording.
"Tagging Plans", "OTHER_TAG" - does this contain any useful information we
can map to OSM tags?
re: "Building Roofprints (poly) - Stereo-compiled (3D)"
* Where applicable, are the buildings in the source data orthogonal (square
corners) - like we try to create in OSM?
* re "multi-level commercial/industrial buildings" I presume this means a
building that has multiple roof heights, not multiple levels/floors inside
the building. For example a building that has one section that is two
stories high and has a roof height of 20 feet, and another section that is
three stories high and has a roof height of 30 feet.
* re "multi-level commercial/industrial buildings" - consider relations to
group the various building parts together. 
A "parking structure" should probably be tagged:
(not sure it should get a building tag)
A "tank" should probably not be tagged as building=, but rather just
Not all "medical" buildings will be hospitals.
Nothing is said about how the features other than buildings will be
Nothing is said about how the imported data will be conflated with the
existing OSM data (I see there is a place holder).
re "Merge Colorado Office of Information Technology (OIT) state address
layer..." - does this data have a ODbL compatible license?
On Tue, Jan 24, 2017 at 4:21 PM, Russell Deffner <russdeffner at gmail.com>
> Greetings all, this is a cross-post :)
> For some of you this may be old news/reminder. Last spring the Denver
> Regional Council of Governments approached our local group, OSM-Colorado
> <https://www.meetup.com/OSM-Colorado/>, to discuss if and how a ton of
> planimetric data that they have collected and released as public domain
> could also be added to OpenStreetMap. Since then we’ve been discussing
> with the local mappers and working together with DRCOG to prepare a pilot
> import for their building dataset and we’re very close to that goal. This
> email is mainly a ‘last call’ for the local/US community to review what we
> have outlined on the wiki: http://wiki.openstreetmap.org/
> wiki/Denver_Planimetrics_Import before we send notice to the main imports
> The other thing this email is, and why I’m cross-posting, is because we’d
> love to have you come discuss the import and other OSM stuff at a Mappy
> Hour tomorrow the 25th; details: https://www.meetup.com/OSM-
> Of course if you can’t make mappy hour please email me any comments,
> thoughts, suggestions or advice; thank you!
> Russell Deffner
> russdeffner at gmail.com
> Imports-us mailing list
> Imports-us at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Talk-us