M-NCPPC Planning Department

From OpenStreetMap Wiki
Jump to navigation Jump to search


This import project will include multiple data sets from the Planning Department of Prince George's County, including building outlines and address nodes.


Types of Data

  • Buildings (polygons)
    • Will be merged with address point files in order to give the buildings proper tags
    • This will be split into many pieces following the WSSC Grids in order to create manageable file sizes
    • These two actions will be done using a python script
  • Specific POI such as Libraries, Post Offices, etc. (nodes)

Additionally we might add other data such as Parks (polygons)

Data is obtained from http://gisdata.pgplanning.org/metadata/


Link to waiver as of April 2023


Discovered on May 11, 2019 an explicit license was found to be applied included thus conflicting with the original claims of this import of public domain which did not appear as of the Wayback Machine March 28, 2019. The website never clearly stated a public domain license.

The Prince George’s County Planning Department maintains an enterprise Geographic Information System (GIS). Beginning on July 1, 2015 the Planning Department implemented its GIS open data initiative which allows for the distribution of digital data to anyone in the public and private sectors.

The data, which is available at no cost, includes planimetric, property, zoning, terrain, administrative, Census, environmental, historic, infrastructure, and park facility datasets. Over 200 different datasets are available for use and distribution. Detailed information on each dataset can be found at the GIS Data Catalog.

Use Constraints
Creative Commons Attribution  https://creativecommons.org/licenses/by/4.0/. You can copy, modify, distribute, and perform analysis on the data, even for commercial purposes, all without asking permission, but please provide attribution to the Prince George's County Planning Department. The Planning Department makes no warranties about the data, and disclaims liability for all uses of the data, to the fullest extent permitted by applicable law.


  • Initial planning and testing phase
  • Communicating with the talk-us and import mailing lists
  • Imported test libraries point file and test building polygon file
  • Importing Building outlines and address Nodes

The Plan

  1. Prepare files to be imported
    • Updating Tags to match OSM standards
    • If necessary, simplify data (remove unnecessary tags)
    • Break large files into smaller sections (buildings polygon file)
    • Join buildings file with address file
    • Create and use Python scripts whenever possible to streamline process
  2. Communicate with talk-us and import mailing lists to discuss the import
  3. Do a test import with a small file (Libraries point file and one grid of Buildings polygon file) within JOSM Editor
    • Successful import of both of these files
    • Used Conflate Plugin from the JOSM Editor in order to fix duplicate points
    • Use an arcpy script to determine if a polygon exists already before importing into OSM
  4. Proceed with rest of files over a period of time


Example: Libraries Point Shape File → OSM Standards

Libraries Field Names OSM Tags
ADDRESS addr:housenumber
CITY addr:city
STATE  addr:state
ZIPCODE  addr:postcode
NAME  name
TELEPHONE (xxx-xxx-xxxx) phone (+1-xxx-xxx-xxxx)

Example: Building Outline Shape File → OSM Standards

Libraries Field Names OSM Tags
ADDRESS addr:housenumber
STREET addr:street
CITY addr:city
STATE  addr:state
ZIPCODE  addr:postcode

New Attributes that need to be added:


These field names/tags will be changed or added within the JOSM editor except the TELEPHONE field which requires extra edits within ESRI's ArcMap. Any additional fields will not be imported. I have written a script to split ADDRESS Field into two fields (House Number and Street Name). I have also written a script to convert TELEPHONE Field into the proper format.


Using JOSM's conflate plugin, I can update /clean-up potentially existing data for POI points and add more useful information (phone number, address, etc.).

For polygon data such as buildings I have created a script that will draw from existing OSM data and determine if that building overlaps existing buildings and create a shapefile of only new buildings and overlapping buildings. Then we will manually go through the intersecting buildings.

Mailing List Discussion






editor: System-users-3.svgGregoryM (Gregory_M-NCPPC_Import on osm)

editor: M-NCPPC_Import