Lee County Buildings Import

From OpenStreetMap Wiki
Jump to navigation Jump to search


Lee County Buildings Import is an import of building footprints dataset covering Lee County, Florida. The import is currently as of 5/14/2021 in progress and has been amended as of 5/14/2021 to incorporate the efforts by Esri in Import/Lee County, Florida Buildings into this project.

Goals

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

Schedule

Import shall begin the month of May 2021.

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 (bulk upload method only) can be found here: https://drive.google.com/file/d/1d4H5E7opjkXKzS63QaCUyQB-Tav6zTUW/view?usp=sharing

For RapiD, the dataset is available within the RapiD assist menu under the "Add/Manage Datasets" tab.

Import Type

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

Data Preparation (for bulk upload method only)

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 Preparation (RapiD method)

**For the dataset used in RapiD, see Import/Lee County, Florida Buildings for more information on how Esri prepared the data for inclusion in RapiD.

Data Merge Workflow

Team Approach

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

References

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

  • Local knowledge
  • Best available imagery
  • Existing OSM data

Workflow (RapiD/easy method, any account)

  • Open the OSM US Task Manager project 228 at https://tasks.openstreetmap.us/projects/228/tasks/.
  • Pick a random tasking cell that has not been marked as done. If a tasking cell is too large, you can use the "split task" button when you click on a particular cell to split it up into four smaller cells.
  • In the editor tab, select RapiD from the dropdown list, then RapiD will open in a new tab or window upon selecting "Map selected task".
  • When RapiD opens, click the RapiD assist button, then go to the "View/Manage Datasets" tab, type "Lee" in the filter search bar and the "Lee County Buildings" dataset should be the only item that appears when search results are filtered. Select this dataset (RapiD will default to highlighting the features yellow though you can change it to any color of your pleasing).
  • Any building in the dataset that either the entire building or part of the building is within the tasking cell's boundaries will appear with yellow outlines and yellow diagonal hatching within the building's outline. Buildings in the dataset outside the tasking cell will not appear.
  • Address any issues that appear in iD's automated issue checker tool, and if the building does not have the appropiate tagging (i.e. building=yes on a single family residence), then change the building=tag accordingly (for the example mentioned earlier, building=yes -> building=house). To better keep track of what you've already done, add in 5 buildings at a time, fix tags/issues as appropiate, then move on to the next 5 buildings, etc. Apparently the tasking manager cells bypass RapiD's default 50 maximum AI feature limit so do not add too many buildings at once to avoid RapiD slowing to a crawl/crashing; try to keep it around 75-100 per changeset.
  • Upload after 75-100 buildings checked, added, and modified, and repeat the add/issue fix/change tags for each subsquent 75-100 buildings until the tasking cell is completely filled.
  • Once the cell is completely filled, mark the cell as complete/done, but do not validate it.

Workflow (bulk upload method, import accounts only)

  • 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]