What per-product billing gets wrong about how APIs are used
Real applications mix geocoding, IP lookups, and time zone calls in a single request path. Billing them as separate products ignores how they are used together.
Notes on geocoding, IP data, and building on the My Geocode API.
Real applications mix geocoding, IP lookups, and time zone calls in a single request path. Billing them as separate products ignores how they are used together.
OpenCage built its name on simple onboarding and blended open data. Here is what a migration to a compatible drop-in host looks like in practice.
A sales operations team had eleven thousand customer addresses in a spreadsheet and no way to see them as a map, until a single batch geocoding run changed that.
Thousands of phones on the same carrier network can share one public IP address. That single fact explains most of the accuracy limits on mobile geolocation.
Turn any pair of coordinates into a time zone name, current UTC offset, and abbreviation with one API call, ready for your own date library.
Requests built for Bing Maps REST Services now work against our host unchanged, matching the same parameters and response fields exactly.
Time zone lookups run on a public, actively maintained data source. Charging a separate premium for that lookup does not reflect a real added cost.
Mapbox Geocoding returns GeoJSON, which shapes a lot of downstream code. Here is what changes and what does not when you switch providers.
Get the postal code back from an address that is missing one, using the same forward geocoding call you already have in your checkout or signup form.
A software company stopped guessing what time it was for a customer and started reading it directly off the support ticket, using nothing but the customer's IP address.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom