Self hosted GIS with open geo data - Real-world experience
summary
A company builds a self‑hosted GIS on OpenStreetMap using ORS + Pelias on Kubernetes and ships a facade API for geocoding and driving‑time queries, completing a pilot in weeks and full rollout in months; results show about 50% cost reduction in Google Maps API spend while running QA and prod copies that cost ~5–10% of monthly savings and leaving Google Maps as a 5% fallback. Pain points: updates take hours, data quality varies by country, no real‑time traffic.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:56Business context
- 3:24Self-hosted GIS need
- 4:28Results and savings
- 6:15Technical stack
- 9:04Implementation timeline
- 11:32Challenges
- 14:22When self-hosted GIS works best
- 15:26Conclusion and Q&A
related talks
50m–Mom, can we have G**gle Maps? –We have G**gle Maps at home
22mCloud Native GIS - The value of development velocity in GIS
02h 44mBuilding Geographical APIs with Open Data, PostgreSQL & PostGIS
30mGeospatial analysis made easy with PostGIS and Geoalchemy
46mGetting Down To Earth: Geospatial Analysis With Rails
40mGIS capability of PostgreSql using POSTGIS & OSM DATA
21mThe Open Source Geospatial Community, PostGIS, & Postgres
48mOne and a half year with Heroku-like PaaS