1 / 21

Open Source GIS

Open Source GIS. How we use free tools to do cool things. Martin Catala Donald Hayward. Why Open Source?. Why Open Source?. Error 999999. Why Open Source?. "Free Open Source Software" (FOSS) Free ($0) Free (-dom) Control Flexibility Quality (more eyes, more contributors) Innovation.

larissa-peterson
Download Presentation

Open Source GIS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Open Source GIS How we use free tools to do cool things Martin Catala Donald Hayward

  2. Why Open Source?

  3. Why Open Source? Error 999999

  4. Why Open Source? • "Free Open Source Software" (FOSS) • Free ($0) • Free (-dom) • Control • Flexibility • Quality (more eyes, more contributors) • Innovation

  5. Why Open Source? • "Plays nice" with others • Open Standards mean you can keep ESRI but still get benefits from FOSS • SHP, WMS, WFS, KML, GeoJSON, etc. • Enterprise-grade software and support • Open Source GIS tools are not just toys anymore (Boundless)

  6. Why Open Source? • It's more fun • Fewer don'ts and can'ts • If you can dream it, you can build it • The cool kids are doing it

  7. Why Open Source? • Still skeptical? ESRI isn't. • Python (ArcPy) • https://github.com/Esri

  8. How we use Open Source

  9. Our (abbreviated) Toolbox: • PostGIS (a spatial database system) • QGIS (a desktop GIS application) • OpenStreetMap • GeoServer (c.f. ArcServer) • Python (GDAL, Mapnik, cluster computing) • OpenTripPlanner (Analyst Engine) • OpenLayers, Leaflet, D3.js (Web Mapping)

  10. Transit Livability Explorer

  11. Transit Livability Explorer Made with: • OpenLayers (web map) • PostGIS (backend, analysis) • QGIS (analysis, data management) • ArcMap (analysis)

  12. Transit Livability Explorer Analysis • Multi-step, often changing hands several times (ArcGIS -> PostGIS -> QGIS -> etc.) • Large-scale operations scripted with ArcPy, PostGIS SQL, or GDAL Python on USF Research Cluster

  13. Transit Livability Explorer Click to select: • OpenLayers translates the click into (x,y) • A web API queries an indexed PostGIS table for features intersecting the clicked coordinates

  14. Transit Livability Explorer Simplified GeoJSON Features with PostGIS: SELECT ST_AsGeoJSON( ST_Simplify( geom, 100 ) ) FROM `table`;

  15. MPO Advisory Council Map

  16. MPO Advisory Council Map • Project constraints: • Dynamic web map • Must work on all major browsers (even IE) • Quick update when boundaries change • No server-side processing • No cloud "add-ins"

  17. MPO Advisory Council Map First Attempt: • GeoJSON on OpenLayers/Leaflet/GMaps • Several layers with many features and high-resolution boundaries • Worked fine on my computer • Client's browser crashed

  18. MPO Advisory Council Map Then we tried... • Simplifying geometries • Better, but old version of IE still choked • Rendering static images • ArcGIS screwed up the georeferencing export

  19. MPO Advisory Council Map Finally... • Re-discovered Mapnik • Python-based mapping library • Custom-made slippy tiles • Accepts Shapefiles as input • Generates 100,000+ map tiles in a few minutes.

  20. Summary • Open Source is cheap • Open Source is practical • Open Source is cool

  21. Questions?

More Related