Howard County Import
This is the second draft...
About
This is a project to import public domain data from Howard County (Maryland) GIS division.
Contributors
Interested OpenStreetMap editors are welcome to join our import. These users are working primarily on this project:
- ElliottPlack as EP_Imports
- RoadGeek_MD99 as RG-MD99_imports
Intention
Here is a short list of the intended results for the map
- Import the building footprints county-wide
- Import the address points and blend with the buildings where there is a one to one correspondence.
- Review street centerlines for missing streets and street names.
- Review other layers of interest including, schools, fire stations, parks, cemeteries, food establishments, farms, golf courses, libraries, liquor licenses, etc.
Standards
- Community involvement
- Accuracy
- Documentation
- Respect existing edits
- There may be data that represents real world changes since this GIS data was published.
- Attribution
- Though in the public domain, we should still reference the creator.
Background
All data being imported is coming from Howard County open data portal: https://data.howardcountymd.gov
Data source site: https://data.howardcountymd.gov
Type of license: Public Domain, and written confirmation (https://www.dropbox.com/sh/uddd00skp1o225y/AADhFD1nf18F1BRPeYq_zEyia?dl=0&preview=RE+Howard+County+Buildings+%26+Addresses+on+OpenStreetMap.pdf)
ODbL Compliance verified: Yes
Timeline
This project started in September 2016, with analysis and coding. Import is expected to begin by late 2016.
Test Area
Buildings in Howard County inside Eldridge postal code 21075.
Workflow
QGIS will be used on the county shapefiles to de-project, as well as mix case and normalize the street names. Then buildings which contain only one point address were merged, and joined via unique IDs to remove those address points that are now duplicated. Currently, this process is being done by hand, but a Python script may be developed. A script was written to then take the resulting shapefiles (buildings and address points) and create an OSM (XML) file, which JOSM can load.
The actual import will be done in JOSM, partitioned by ZIP code boundaries. JOSM Validation will be used to check for automated errors. Additional error checking will be performed using OSM Inspector with Address and Geometry tabs.
Tagging Plans
building = yes (default or house when in large residential areas)
addr:housenumber = <Number>
addr:street = <Unabbreviated Mixed-Case Street Name>
addr:city = <City>
addr:postal = <ZIP Code>