Competing with the giants: OpenCage vs Google
summary
OpenCage runs a geocoding API built on OpenStreetMap and multiple open-source geocoders, exposing a simple REST endpoint and SDKs; it enforces flat-fee pricing with soft limits and accepts major currencies so bills never spike. Terms let customers store results and use any map. A no_record API flag disables logging and wins privacy-sensitive clients (healthcare). Infrastructure focuses on uptime and predictability rather than matching Google's full Maps platform.
AI-written summary · about
chapters (12)
- 0:00Intro
- 5:30Main differentiator
- 7:30Google
- 8:18How can we win
- 11:50Finding space
- 13:04Terms and conditions
- 15:21Privacy
- 17:55One thing well
- 20:32Competitors
- 21:59AWS
- 23:06Reliability
- 24:44Be patient
related talks
31mOGC APIs: Web API Standards for Handling and Exchanging Location Data
05mGetting to Know SimpleGeo
25mSpatially enabling Web APIs through OGC Standards
27mMapbox Search Box vs. Mapbox Geocoding
21mOpen Standards for Getting your APIs into the Geospatial Ecosystem.
46mOpen network APIs: CAMARA & Open Gateway Initiative
20mOGC API Standards: Enhancing Digital Infrastructure
27mApidays Virtual Helsinki - Geir Sjurseth, Google Cloud