Test slides to explain a strategy for opening civic data through GeoGit

1. GeoGitOpening a
Channel to our
Public Data

2. Git: distribute code

3. Early days of Git (2005)

4. GitHub: let’s do Git right

5. GitHub: view and edit source

6. GitHub: see changes

7. GitHub: suggest changes
These changes are called pull requests

8. GitHub takes on maps (2013)
Supports GeoJSON and TopoJSON

9. Limitations of GitHub maps

10. New visions for data

11. GeoGit thinks in geo

12. GeoGit accepts four formats
Shapefiles
SpatiaLite / SQLite
PostGIS / PostgreSQL
OSM / XML
In the long run we
can add EsriJSON,
but for now it’s
easier to convert
EsriJSON > OSM XML

13. GeoGit tracks changes

14. Open Data Today
One-Time Download
and Converting
Data Goes Stale
City’s Official
Data

15. Opening Data with GeoGit
Awesome Mash-UpsCity’s Official Data
GeoGit Sync
Updates to match city
Download in many formats
Answers “what changed since my download?”

16. Restaurant Example
I have a site like Yelp
I need to know restaurant openings & closings!
But my database is different from yours
Reviews, photos
I want to keep, but hide closed restaurants
Solution: ask GeoGit, apply changes my way

17. IRL: Permits Example
Building Permits service updates often, automatically
Setting up GeoGit to check for changes each hour
Downloads EsriJSON, converts to OSM
Imports, adds, and commits with GeoGit
Build maps that list and visualize changes

18. More Information
GeoGit ( geogit.org )
vimeo.com/67308286
GitHub ( github.com )
github.com/blog/1528
digital.cityofchicago.org/index.php/chicago-on-github/
Git
en.wikipedia.org/wiki/Git_(software)