This repository has been archived by the owner on Apr 22, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
openstreetmap polygons
Diana Shkolnikov edited this page Feb 20, 2015
·
2 revisions
The admin polygons hiding inside OSM files look very promising. Don't just take our word for it.
<iframe src="//player.vimeo.com/video/91893151" width="500" height="281" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>OpenStreetMap Data in Production + Labeling OSM Streets with Foursquare and Mapreduce - David Blackman from OpenStreetMap US on Vimeo.
So the goal is to make this data accessible and begin using it in our import pipeline, given that data quality is not a major barrier. If the quality is not sufficient (though we think it's already pretty excellent), exposing the data to the community will hopefully encourage improvements to it.
| Story | Estimate | Priority | Status | Notes |
|---|---|---|---|---|
| Implement polygon extraction | 3 | 0 | done |
|
| Make it faster | 2 | 0 | done |
|
| Split output into admin_level files | 1 | 0 | done |
#2 |
| Chef-ify extraction process and setup recurring runs (identify list of supported extracts) | 1 | 0 | done |
|
| Create simple website for download of extracted data | 3 | 1 | ||
| Normalize the data: find common set of tags and add areas with non-standard/incomplete tags to error output | 2 | 1 | ||
| Write blog post | 2 | 1 | ||
| Fork admin-lookup and populate with osm polygons instead of quattroshapes | 2 | 2 |