Lee County Buildings Import

Lee County Buildings Import is an import of building footprints dataset covering Lee County, Florida. The import is currently as of 11/15/2020 at the planning stage.

Goals

Add in all building footprints in Lee County, FL unless existing OSM data has a more accurate shape.

Schedule

Upon approval from imports@openstreetmap.org, the import shall begin.

Import Data

Background

This is a import of approximately 310k buildings in Lee County, FL.

Data source site: https://www.esri.com/arcgis-blog/products/arcgis-living-atlas/mapping/community-maps-data-sharing/

Type of license: This work is licensed under a Creative Commons by Attribution (CC BY 4.0) license.

With respect to the Esri Community Maps dataset, Esri and the Esri Community Maps Contributors agree to the following:

1. Attribution by OpenStreetMap and its users through https://wiki.openstreetmap.org/wiki/Contributors is sufficient to provide attribution to Esri Community Maps Contributors in a "reasonable manner" in accordance with Section 3(a)(1) of the CC BY 4.0 license.

2. Esri waives Section 2(a)(5)(B) of the CC BY 4.0 license as to OpenStreetMap and its users with the understanding that the Open Database License 1.0 requires open access or parallel distribution of OpenStreetMap data.

OSM Data Files

The actual shapefile that will be used for this import can be found here: https://drive.google.com/file/d/1d4H5E7opjkXKzS63QaCUyQB-Tav6zTUW/view?usp=sharing

Import Type

This is a community based import using JOSM. No scripts/automation will be needed.

Data Preparation

Data Reduction & Simplification

The data is already pre-processed into OSM tagging format, for example building=yes.

OBJECTID field was dropped from the data in ArcMap to reduce size and is not a standard OSM data field.

Source Tagging Plans

source=esri_LeeCounty_FL , this tag is already placed on each building footprint by Esri.

Changeset Tags

#osmus-tasks-228

Data Transformation

The data layer was exported to .shp format using the ArcMap Data -> Export Data function (JOSM can open .shp files with the OpenData plugin). The OBJECTID field was dropped using the attribute table in ArcMap to reduce shapefile size as OSM does not use this field.

Data Transformation Results

Finished shapefile can be seen here: https://drive.google.com/file/d/1d4H5E7opjkXKzS63QaCUyQB-Tav6zTUW/view?usp=sharing

Data Merge Workflow

Team Approach

The work is split up into tasking manager squares/cells.

References

Using JSOM, each volunteer will begin to work through the data in each tasking cell along with:

• Local knowledge
• Best available imagery
• Existing OSM data

Workflow

• Open JOSM and the OSM US Task Manager project 228.
• Click on the task tab above and claim a task cell 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)

Conflation

Identify your approach to conflation here.

QA

• Validation tools in the Tasking Manager will be used as each tasking cell is completed.
• Slack channel #local-florida on the OSM Slack for questions and discussion, as well as assisting others with performing this import.

See also

The email to the Imports mailing list was sent on 2020-11-15 and can be found in the archives of the mailing list. [1][2]