[Imports] Baltimore city buildings import

Richard Welty rwelty at averillpark.net
Thu Apr 11 17:20:34 UTC 2013

do you have any prospect of getting address data? it's strongly recommended
to conflate address data with building foot prints before importation. 
the workload
to import the two data sets separately is dramatically higher than the 
case where
you can pull them together into one import.

you may want to take this up on the mailing list for the US imports 
we also hold a google hangout every other week to discuss these sorts of 

On 4/11/13 1:08 PM, Elliott Plack wrote:
> Hello group. I submitted this idea to the group 7-15-12 but never got any
> response. Here it is again (copied from what I just posted in talk-us):
> I've been putting this one off for a while, because of the magnitude of the
> dataset. I am importing Baltimore city building footprint data one
> neighborhood at a time. Running an intersect of this layer against the
> neighborhood layer breaks it down into bite size chunks that are easier to
> work with. I've gotten the necessary permission from the city, and talked
> about it with local users at the editathon, as well as over email or in
> person.
> Here is the data:
> https://data.baltimorecity.gov/Geographic/Building-Footprint-Shape/deus-s85f
> Here is the workflow:
> Open data in GIS program
> Open neighborhood boundaries (same website) in same GIS program
> Intersect, select single neighborhood worth of buildings
> Save as individual shapefile
> Launch JOSM
> Bring in shapefile
> Download data (as new layer)
> Compare every existing feature to new ones (can take a while)
> Look for traced buildings that use non-ortho imagery (shifted)
> Copy any tags from existing building features to building in new dataset
> (preserving others work)
> Remove machine tags from new data
> Tag as building=yes
> Copy all multipolygons to .osm data layer
> Copy all polygons to .osm data layer
> Verify tagging
> Check for errors
> Fix duplicated node errors with JOSM
> Fix building inside building errors by removing extra nodes
> Final check by turning new data on/off and looking for overlaps
> Upload with special EP_Import account
> http://www.openstreetmap.org/user/ElliottPlack
> _______________________________________________
> Imports mailing list
> Imports at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/imports

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20130411/69a61cab/attachment.html>

More information about the Imports mailing list