Skip to main content

Convert Shapefiles to GeoJSON for GitHub Maps

3 min read

Summary: With GDAL installed, one ogr2ogr command turns a proprietary Shapefile into GeoJSON, which GitHub renders as an interactive map. Once public geodata lives on GitHub in an open, text-based format, anyone can fork, diff, and improve it like code.

Table of contents

With GitHub natively supporting mapping and embeds, I recently wanted to put some of the free, publicly available government data published on data.dc.gov to use. They have all sorts of great information, from bus routes to polling places, to the location of every liquor license in DC. The only problem was that the data was stored in a proprietary and complex format known as a Shapefile. The format arose when the desktop ruled supreme, and many common uses require a costly software subscription.

Luckily, a strangely named piece of open source software known as ogr2ogr can convert the data into the more modern, more open GeoJSON format that GitHub supports, and the resulting map can be automatically rendered, not to mention more easily diffed.

If you’ve got a Mac, it only takes a few seconds

  1. If you don’t already have it, install Homebrew
  2. Install gdal with the command: $ brew install gdal
  3. Grab a Shapefile (distributed as a .zip file) from the DC Data Catalog or your favorite data source and unzip it someplace convenient
  4. cd into the directory with your shiny new unzipped Shapefile
  5. Run (replacing [name] with the name of your downloaded Shapefile): $ ogr2ogr -f GeoJSON -t_srs crs:84 [name].geojson [name].shp
  6. Grab the resulting GeoJSON file and commit it to GitHub
  7. Navigate to the GeoJSON file on GitHub.com to browse your map

In addition to converting the Shapefile over to GeoJSON, the other step in there, -t_srs crs:84, ensures that by the time the data hits GitHub, it’s encoded with the right projection so it can be mapped properly. Need to convert multiple Shapefiles in bulk? Just use this bulk Shapefile to GeoJSON conversion script. Windows users? You’re covered too.

Why this is important

For one, you’re liberating public geodata that would otherwise be inaccessible to the average citizen and making it available in a dead simple point, click, zoom interface that anyone can use. For another, once you put the information on GitHub in an open, text-based format, civic hackers and subject-matter experts can begin treating that data like open source code (forking, merging, diffing, tracking changes over time), and all of a sudden we’ve opened up not just the data, but the entire collaborative ecosystem that now surrounds it.

See the finished map on GitHub

View the DC Embassies map on GitHub.

Keep reading

Ben Balter

I'm Ben Balter, and I write here about developer platforms, product and engineering leadership, open source, and showing your work. I spent over a decade building developer platforms at GitHub. For five years I was a product manager for trust and safety, shipping 500+ features and the API endpoints behind them to 50M+ developers. I also led a bottom-up rewrite of GitHub Pages and wrote the open source library behind GitHub's license detection, and my open source projects have hundreds of millions of downloads. I wrote Open and Async, the playbook for remote and distributed teams, and shipped a Model Context Protocol (MCP) server alongside it so agents can query it directly. More about the author

Follow along: Bluesky LinkedIn

Originally published June 26, 2013 View revision history

This page is open source Help improve this article on GitHub

Keyboard shortcuts

Search

  • / or ⌘ K Open search
  • ↓ or j ↑ or k Move through results
  • Enter Open the selected result
  • Esc Close search

Go to

  • g then h Home
  • g then p All posts

This page

  • y Copy link to this page
  • ? Show this list