Tampa, Florida Building Import

Imports and automated edits should only be carried out by those with experience and understanding of the way the OpenStreetMap community creates maps, and only with careful planning and consultation with the local community.
See Import/Guidelines and Automated Edits code of conduct for more information. Imports/automated edits which do not follow these guidelines might be reverted!

About

This page is intended to document plans for an upcoming import of Microsoft Building Footprint Data supplied under ODbL by Microsoft.

We plan to follow the import checklist, but our general high level plan is this:

• Identify data to import
• Translate, tag, and otherwise tenderize the data
• Invite community members to help manually import the outlines
• Divvy up the work using the HOT Tasking Manager
• Do the work: Import/merge the data
• QA the data
• Beverage of choice & on to the next task

The intent is to begin this effort as soon as possible to aid in whatever way we can with the Irma Hurricane destruction in Florida.

Import Data

Background

The building outlines were made available by Microsoft. See Microsoft Building Footprint Data for details

Import Type

This is a community building based effort.

There are currently no plans to script or automate this import.

Data Preparation

Tagging Plans

No source tags will be added.

Changeset Tag

Tag in import-related changesets: #osmus-project-x #hurricaneharvey

Data Transformation

The source files will need to be converted to OSM XML. Shpfiles will be processed in Postgresql to expand street addresses. Two slighly different approaches are being proposed. A PostGIS approach github and a Python approach [1].

We have used Paul Norman's org2osm to convert from Postgresql to an OSM XML for this. The translation script is:

def filterTags(attrs):
    if not attrs: 
        return

    tags = {}
    tags['building'] = 'yes'
    if 'HEIGHT' in attrs and attrs['HEIGHT'] != '':
        tags['height'] = attrs['HEIGHT']    

    return tags

Data Merge Workflow

Team Approach

The work for this effort will be divided up into sections, with each section constituting a census block. Census Blocks will be used by the US Tasking Manager.

References

Using the JSOM, each volunteer will begin to work through the data for that district.

• Local knowledge
• Best available imagery
• Existing OSM data

Workflow

• Open JOSM and the OSM US Task Manager project 118
• Click on the task tab above and claim a task on the map to the right by clicking on an area you'd like to work in
• Click the "JOSM" button, this will open the area in JOSM and load up existing OSM data
• Click the ".osm" button, this will open new building outline data in a separate layer
• Select the new building layer and validate the layer, fix all issues
• Copy all geometry from building layer and paste it into the existing OSM data layer, Ctrl-c, Ctrl-Alt-v.
• Run validation on the existing OSM data layer that now contains new data, resolve all issues emanating from collisions between existing and new data (see merge rules).
• Do a sanity check on data:
• Merge with existing buildings.
  • To merge with a building outline, use the Replace Geometry (Ctrl+Sift+G) by selection the existing building outline and the new address node. Note: Only merge building outline with an address node if the building outline contains just one address node.
• Change visible storage tanks from building=yes to man_made=storage_tank
• Upload data to OSM
• Go back to the Tasking Manager and mark the task as done (but not as validated)
  

Dedicated Import Account

Users will be expected to obtain an unique import account, for example, user Foo might pick Foo_Import.

QA

Validation

• Use of validation tools in the Tasking Manager process
• Use Slack for questions and to help others during the import.