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 Now if I could just figure out how to post to the imports@ ----- http://about.me/elliottp | http://www.openstreetmap.org/user/ElliottPlack -- View this message in context: http://gis.19327.n5.nabble.com/Import-Baltimore-City-buildings-tp5756665.html Sent from the USA mailing list archive at Nabble.com. _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us