Union County Ohio Data Import

This proposal covers the import of data from Union County, Ohio provided by the county on their GIS Data Downloads web page and other data provided directly from County staff. The initial phase of this data import will be building outlines; however, additional data such as addresses, roads, school districts, and township jurisdictions are also potential sources. Some data will be provided by the City of Marysville, Ohio made available at the Marysville Open Data site and from city staff. The project was started by Langdon Sanders.

Requirements

This project recognizes and aims to follow the Community Import Guidelines.

• Prerequisites
• Community Buy-in
• License Approval
• Documentation
• Import Review
• Uploading

Source

Union County provides source data in public domain as a shapefile on their GIS Data Downloads page.

License

Initial permission to use the building data for updating OpenStreetMap was granted via email from GIS staff of Union County upon request from Langdon Sanders. Per conversation with Union County GIS staff, the GIS data is provided under open records rules per the Ohio Revised Code and is permitted for use in OpenStreetMap. Contact information for Union County: 233 W. 6th Street, Marysville, Ohio 43040 by phone at 937-645-3018.

Initial request and approval

From: Shiping X <[redacted]@co.union.oh.us> Date: Mon, Jun 3, 2019 at 4:14 PM Subject: RE: New GIS Coordinator at Marysville To: Langdon Sanders <lsanders@marysvilleohio.org>

Hi Langdon,

Please use them to update map. Thank you very much,

Shiping X.

From: Langdon Sanders <lsanders@marysvilleohio.org> Sent: Monday, June 03, 2019 4:11 PM To: Shiping X <[redacted]@co.union.oh.us> Subject: Re: New GIS Coordinator at Marysville

It was nice meeting you Shiping,

I am already using those building footprint files which are very helpful. Would it be okay if I used them to update OpenStreetMap? This data is used by lots of other providers like Esri basemaps, Mapbox and Google so updating here would help with basemaps in other systems. https://www.openstreetmap.org/#map=14/40.2375/-83.3855 Thanks!

Langdon Sanders, MPA GISP

Second confirmation

From: Josh H <[redacted]@co.union.oh.us> Date: Fri, Jul 26, 2019 at 5:41 PM Subject: COGUG and building footprints To: Langdon Sanders <lsanders@marysvilleohio.org>

Hi Langdon,

Just wanted to let you know that I added the building footprints to our download page at https://www.co.union.oh.us/gis-data/. Also, I wanted . . .[unrelated].

Josh

Project Log

Step 1 - Prerequisites

1. ☑ Gain familiarity with the basics of OpenStreetMap, including editing, such as adding details of your neighbourhood.
2. ☑ Review what can go wrong with imports.
3. ☑ Identify data you'd like to import. This might be street centerlines, building outlines, waterways, addresses, etc and the data license requirements.

Step 2 - Community Buy-in

• Announced the project through the US mail-list on June 17, 2019
• Joined the OpenStreetMap Slack team , specifically the #Ohio and #imports and introduced the project
• Received on process such as using the JOSM editor along with the "open data," "To Do," and "conflation" plugins

Step 3 - License approval

1. ☑ You must obtain proper permissions and licenses to use the data in OSM from the data owner
   1. License approval granted in email and phone conversations with Union County GIS staff under Ohio Revised Code for public records.

Step 4 - Documentation

1. You must register your permissions and project by adding a line to the table at Import/Catalogue.
2. You must write a plan for your import in the OSM wiki. [In Progress]
   1. ☑ Create a wiki page outlining the details of your plan. This plan must include:
      1. ☑ how to convert the data to OSM XML,
         1. Will use open-data JOSM plug-in to import shapefile building footprints then copy features into OSM using JOSM copy and paste
         2. dividing up the work,
            1. All import processing to be completed by Langdon Sanders
         3. how to handle conflation,
            1. Will follow best practices from other projects, community advice, and the Conflation plug-in
         4. how to map GIS attributes to OSM tags,
            1. Only tag available will be `building=yes`
         5. how to potentially simplify any data,
         6. how you plan to divide up the work,
         7. revert plans,
         8. changeset size policies, and
         9. plans for quality assurance. An example for this can be found at Import/Plan Outline
3. If required by the data owners, you must add an acknowledgement to the list of Contributors.

Required to place import entry in the Import/Catalogue. [Not Complete]

Write a plan [In Progress via this wiki]

Import Review

• Subscribe to mailing list [Complete June 17, 2019]
• Post review of import [Not Complete]. Provided link to data to be imported in original email but need to request approval from imports@openstreetmap.org. [Not Complete]

Data Processing

Plan is to use the JOSM editor, load the reference building data in using the opendata plug-in, mark various sections of the county for adding and review, copy the buildings in small sections, review each building using the TODO List plugin, and upload the data to OSM in small batches. Changes will be submitted with review requested.

Conflation

Will be exploring use of the conflation plugin to determine overlap of buildings between sources.