Export OpenStreetMap data to CSV, JSON or Excel
OpenStreetMap holds structured data on millions of places — but it isn't published as a spreadsheet. The raw exports come as .osm XML or .pbf map files, and the usual way to query it (the Overpass API) returns map geometry in its own format, not tidy business rows. If what you actually want is a list of places in a city, one per row, with name, address and contact, you need something that does the extracting and flattening for you.
This shows how to turn OpenStreetMap into a clean CSV, JSON or Excel file for any city — no API key, no query language, and no map software.
What you get — one row per place
Every place comes back as a single flat row, ready for a spreadsheet:
- Identity: name, category, brand
- Location: latitude, longitude, street, housenumber, city, postcode, country, state — plus a ready-made full_address and a map_url
- Contact: phone, email, website
- Details: opening_hours, operator, branch
- Source: osm_id, osm_type, source_url, and the full all_tags blob if you want the raw detail
Anything OpenStreetMap hasn't mapped comes back as an empty cell — honest-null, never guessed — so what's in the file is real. (For a field-by-field breakdown, see what data you get from OpenStreetMap.)
How to export it (no API key)
Run the dataquarry OpenStreetMap Places Scraper on Apify. Give it an area, a radius around a point, or a bounding box, and pick the categories you want:
{"area":"Austin, Texas","categories":["restaurant","cafe","supermarket"]}
Run it, then download the dataset in the format you need. You'll get rows like this:
| name | category | full_address | phone | website | map_url |
|---|---|---|---|---|---|
| Whole Foods Market | supermarket | 525 N Lamar Blvd, Austin, TX 78703, USA | +1 512-476-1206 | https://www.wholefoodsmarket.com | https://www.openstreetmap.org/node/123456789 |
| Juan in a Million | restaurant | 2300 E Cesar Chavez St, Austin, TX 78702, USA | https://www.openstreetmap.org/node/987654321 |
Run the OpenStreetMap Places Scraper on Apify →
Which format should you pick?
- CSV — opens straight in Excel, Google Sheets or Numbers; best for analysts and one-off lists.
- JSON — best when you're feeding the data into code, a database, or an AI / RAG pipeline.
- Excel (
.xlsx) — a ready-to-share workbook with the columns already typed.
All three come from the same run, so you can export more than one without paying twice.
Why OpenStreetMap?
The data is open OpenStreetMap data under the ODbL, so you can use and redistribute it with attribution to © OpenStreetMap contributors — no API key, no logins, and none of the anti-bot or Terms-of-Service problems that come with scraping Google Maps or other sites. Unmapped fields stay blank instead of being invented. Pricing is pay-per-result: $3 per 1,000 rows.
FAQ
How do I export OpenStreetMap data to CSV?
Give the tool a city (or a radius, or a bounding box), run it, and download the result as CSV — one row per place, with name, address, coordinates, brand and contact. No API key and no query language.
Can I get the data as JSON or Excel instead?
Yes. The same result set exports as CSV, JSON or Excel — pick whichever fits your workflow when you download it.
How much does it cost?
Pay-per-result: $3 per 1,000 rows — you only pay for the rows you actually get.