[Geocoding] Neighborhood boundaries polygon data

[Diana Shkolnikov]

On Tue, Apr 28, 2015 at 02:11:35PM -0500, Marcelo de Moraes Serpa wrote:

> Hi list!
>
> I’m wondering if OpenStreetMap provides the shapefiles or geojson for neighbourhoods around the world, specifically the polygon boundaries for them? So far, the most reliable places I’ve found for this data were, in order of

>reliability: google maps (not open source and the data isn’t available), maponics (commercial API), quattroshapes (from foursquare, open source).
>
>Quattroshapes is not bad, and has quite a few neighborhoods polygons for major cities around the world, however I’d still like to know if OpenStreetMap also provides this data? If so, where could I fetch it from?
>
> Thanks!
>
> — Marcelo


Hey Marcelo,

I've been working on an admin boundary extraction tool for OSM. The
goal is to make these geojson files available for download via
mapzen.com similarly to metro extracts
(https://mapzen.com/metro-extracts). We aren't there just yet, but the
extraction tool is in npm and you can easily make your own extract of
whatever region you need.

https://github.com/pelias/fences-cli

npm install -g fences

touch regions.json

{
  "regions": [
    {
     "name": "USA",
      "box": {
        "left": -124.848974,
        "bottom": 24.396308
        "right": -66.885444,
        "top": 49.384358
      }
    }
  ]
}

fences create planet-latest.pbf regions.json /tmp/fences-results/

What you get in /tmp/fences-results/ are geojson files with polygons
that have "boundary"="administrative" and "admin_level"=*. There
should be the full planet set of results as well a directory for each
region you've defined in the regions.json file.

There is a github issue to add "place"="neighborhood" as well, but
they aren't currently being extracted. You can easily just make the
addition in the code though, if you need them quickly.


Cheers,

Diana
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/geocoding/attachments/20150430/6ebf6840/attachment.html>