Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Aug 13, 2015 2:15am

the other openstreetmap churches post

Scott Murray wrote the other day asking about getting Church data out of OpenStreetMap:

What is the easiest way to extract a list of a specific type of features from OSM for a particular area? For example, say I want all of the churches ( feature type: building / church ) in London, and the name, lat, and lon for each. Ideally all of this would end up in a simple CSV. This would be a one-time extract, and I don’t need to update it again later.

It was a pretty quick process, so I wrote it up for him and asked his permission to re-post here. I figured others might run into the same need. Today, Steven Vance in Chicago posted a response to a near-identical question with a different approach. There are many ways to skin this cat, and possibly not enough guides on this kind of retail data extraction from OpenStreetMap.

This is what I sent to Scott:

Since you’re asking for a major urban area, I would expect that London is part of the Mapzen metro extracts.

I downloaded a copy of the London OSM2PGSQL SHP data, because I know that it tends to be a closer (and often messier) representation of what’s in the OSM source database. If I was looking for roads or something else that I felt confident was already a defined and separate layer, I would download the IMPOSM SHP data. If I was looking for something outside a covered city, then I’d need to go digging in the Planet and I would be sad (edit: I’d follow Steven’s advice).

Next I looked on the OSM wiki to see how churches are tagged. The suggested tag is amenity = place_of_worship.

Then I used ogr2ogr, a tool in the GDAL family, to quickly peel out all the tag matches. I could do this interactively in QGIS as well, but I find the command line to be a speedier way to get what I want. ogr2ogr can be a pain in the butt to install, but I’ve found that it’s something of a secret hidden easter egg in Postgres.app, so if you install that you can find ogr2ogr hidden inside.

Here’s the conversion to get the OSM ID and the name for all places of worship:

ogr2ogr \
    -select 'osm_id, name' \
    -where "amenity = 'place_of_worship’” \
    london_england_osm_point-amenity-place_of_worship.shp \

At this point I opened the shapefile in QGIS to see what’s there, and saw this this:

That looks right, so I convert it to a CSV preserving the geometry in (Y, X) fields, also using ogr2ogr:

ogr2ogr \
    -f CSV -lco GEOMETRY=AS_YX \
    london_england_osm_point-amenity-place_of_worship.csv \

Here is the result.

Comments (3)

  1. The problem that my tutorial doesn't address is converting one of the output methods of Overpass into a CSV with latitude and longitude fields. It outputs a KML (but that doesn't continued lat/long as attributes) and GeoJSON (which is an associative array so cannot be converted to CSV easily). The alternative to using ogr2ogr to adding the lat/long fields to a CSV is to use QGIS and the "Add/Update Geometry Column" function that will add latitude and longitude fields in whatever units the projection specifies. The GeoJSON from Overpass would be in 4326 so QGIS will add the expected lat/long fields.

    Posted by Steven Vance on Thursday, August 13 2015 10:19am EDT

  2. Right. Those formats will be pretty easy to convert using the same ogr2ogr process, or a re-save from QGIS.

    Posted by Michal Migurski on Saturday, August 15 2015 2:03pm EDT

  3. Overpass has direct CSV output. It's a little buried in the documentation though: http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Output_Format_.28out.29 I think there are also more and more places of worship that are modeled as buildings, so it would be good to include a way query (and relation to, for completeness sake). Here's a lightly edited Overpass Turbo Wizard query, setting csv output and requesting the center of geometries instead of the full geometry: http://overpass-turbo.eu/s/aZV (to use such a query outside of Turbo, the "{{geocodeArea: Cook County, Illinois}}" can be replaced with a reference to the OSM object)

    Posted by Max Erickson on Monday, August 17 2015 2:37pm EDT

Sorry, no new comments on old posts.

February 2017
Su M Tu W Th F Sa

Recent Entries

  1. things I’ve recently learned about legislative redistricting
  2. oh no
  3. landsat satellite imagery is easy to use
  4. openstreetmap: robots, crisis, and craft mappers
  5. quoted in the news
  6. dockering address data
  7. blog all dog-eared pages: the best and the brightest
  8. five-minute geocoder for openaddresses
  9. notes on debian packaging for ubuntu
  10. guyana trip report
  11. openaddresses population comparison
  12. blog all oft-played tracks VII
  13. week 1,984: back to the map
  14. bike eleven: trek roadie
  15. code like you don’t have the time
  16. projecting elevation data
  17. the bike rack burrito n’ beer box
  18. a historical map for moving bodies, moving culture
  19. the other openstreetmap churches post
  20. platforminess, smartness, and meaningfulness