Minnesota/DakotaCounty/DCGISContributes

From OpenStreetMap Wiki
Jump to navigation Jump to search

Dakota County GIS (DCGIS) has interesting in supporting editing in OSM with authoritative data that falls under its open data policy. Dakota County GIS will support editing in OSM by providing data that can be used to address issues in OSM and by editing the data themselves.

The following are how Dakota County will participate.

  1. Dakota County GIS will participate on the mailing list and OSM Slack Channel #local-mn as necessary to make this a successful venture.
  2. DCGIS will update this page and any pages linked from it with pertinent information.
  3. Provide authoritative data that falls under its open data policy making it great for inclusion in OSM (just like the building import)

Expect this page and the others to be updated as the planning process continues.

Aerial Photography - Dakota County will contribute its most current available imagery to the Editor Layer Index (ELI) for use by OSM editors. User DCJoeS has been participating and has provided access to 2017 and 2019 imagery to date.

Building and Address Import - Dakota County will support a resurrection of the 2017 Building and Address Import as Spring 2020. The wiki page has been updated with some information, more to come. The current project has been limited to areas that have yet to be imported or where significant change has taken place. This project was previously noted on the import mailing list as being done by one user on their own time, but with the support of the organization is now open to others, especially Dakota County staff. The project has been set at Intermediate, but is not restricted to that level of editor. The project is here.

Streets - Dakota County GIS maintains the authoritative street centerline dataset for Dakota County.  The dataset is used for emergency services dispatching, geocoding, general mapping and analysis.  Dakota County GIS contributes this data to a regional data collaborative.  Dakota County GIS recognizes that a full replacement of street centerlines in OSM would be disruptive to the OSM community and a time-consuming task for those involved.  Dakota County GIS will provide editing support to increase the accuracy of the existing data in other ways.

Current Contributions

  1. Staff has identified residential street segments that have no names.  Staff is adding names to those segments in a private MapRoulette challenge using the iDEditor.
  2. Import missing segments (new roads) neighborhood by neighborhood with appropriate tags using the JOSM editor.

County and City Boundaries - Analysis

There are minor difference between the existing boundary data in OSM as it relates to the municipalities of Dakota County, Mn.  Those differences may simply be related to the age of the original data imported (2008 tiger import) or edits by community members without access to the actual municipal boundary files or annexations that have occurred that are not yet represented.  The same is likely in the case of the boundary of the county itself.  Minor errors should be corrected.

The township boundaries are lacking in their entirety, except for where they coincide with a municipality.  These boundaries can be imported from the County’s municipality layer.

Jared Campbell has as diary entry that proposes a method that “ensures that tags and relations don’t have to be recreated onto a new boundary (much cleaner and easier in the long term)” using a shapefile and the JOSM editor to modify an existing boundary.  Using the shapefile as a template/base layer to snap existing nodes to without risking loss of existing tags and relations is an acceptable method for updating existing boundaries.   Jared’s diary entry also addresses adding and deleting additional nodes as needed.

https://wiki.openstreetmap.org/wiki/User:Jared.Campbell/JOSM.MergeShapefileBoundaries

Tasks

  1. Dakota County GIS staff will
    1. Edit the existing city boundaries using the County’s municipality layer AND
    2. Provide the data to an OSM community member skilled in using the municipality layer as the source to replace those boundaries in error.
    3. City names will be verified and changed if in error
  2. Dakota County GIS staff will
    1. Edit the existing county boundary using the County’s municipality layer AND
    2. Provide the data to an OSM community member skilled in using the municipality layer as the source to replace those boundaries in error.
  3. Dakota County GIS staff will
    1. Import the township boundaries using the County’s municipality layer AND
    2. Provide the data to OSM community members skilled in using the municipality layer as the source to import the township boundaries.
    3. Tag
      1. admin_level=7
      2. name= <with township name in the proper format, ie “Eureka Township”>
  4. Dakota County GIS staff will
    1. To the best of their knowledge and ability, address any issues that come to light as a result of updating these boundaries.

The boundary file is available for download from the Minnesota Geospatial Commons for anyone who would like to pursue this: https://gisdata.mn.gov/dataset/us-mn-co-dakota-bdry-munbndp

Parks - Analysis

Testing was done to compare the leisure:park and leisure:nature_reserve with the authoritative data source from Dakota County GIS and the respective parks departments at the County and its cities.  It didn’t yield any ground-breaking results.  It was expected that boundaries would not match.  Many of the parks in OSM had been digitized from aerial photography, whereas, the data from the county and city collaboration was generated from parcel boundaries.  At the time of analysis there were 413 leisure:park and leisure:nature_reserve polygons in OSM.  The County provided data has 537.

Tasks

  1. Dakota County GIS staff will provide data that could be imported/conflated with
    1. The following tags at minimum
      1. name
      2. operator
      3. leisure:park
    2. The following tags, when the information is available within the aggregated dataset from the collaborative effort
      1. addr:housenumber
      2. addr:street
      3. addr:city
      4. addr:state
      5. addr:country
      6. opening_hours:
    3. Tasking server project with - https://tasks.openstreetmap.us/project/195
      1. Appropriately sized (chunked) areas with a small number of parks to conflate/import in a few minutes time or less
      2. Instructions for the task at hand
      3. Instructions for adding 2019 Spring Aerial Photography of Dakota County for a background in JOSM

Park Trails more information coming

Campus Details more information coming about data to increase the detail of Dakota County government building and trailhead locations

Retrieved from "https://wiki.openstreetmap.org/w/index.php?title=Minnesota/DakotaCounty/DCGISContributes&oldid=1976840"