Migration guides: a new home for switching providers
Dedicated migration guides now walk through switching an existing integration to My Geocode, provider by provider, endpoint by endpoint.
Notes on geocoding, IP data, and building on the My Geocode API.
Dedicated migration guides now walk through switching an existing integration to My Geocode, provider by provider, endpoint by endpoint.
Most time zone bugs do not come from bad data. They come from code that was never tested against the one week a year when the rules actually change.
When you already have a clean postal code and country, skip free-text parsing entirely and go straight to the postcode endpoint for a more direct match.
Bulk geocoding needs are handled differently across providers, from CSV uploads to batch API calls. Here is how the common approaches compare.
A single page now lists all seventeen compatibility hosts side by side, making it easy to see which providers can be swapped in with one key.
A timestamp from years ago needs the time zone rule that was actually in effect back then, not today's rule. Getting this wrong quietly corrupts historical data.
A publisher's newsletter open rates varied wildly by region, and the reason turned out to be simple: everyone was getting it at the same fixed hour regardless of where they lived.
An IP lookup API that still treats IPv6 as a minor edge case is quietly treating a growing share of real internet traffic as an afterthought.
Switching a live API host without an outage takes more than just updating a URL. Here is a checklist for doing it without users noticing.
Compare an IP address's location and network details against what a signup form claims, catching obvious mismatches without a dedicated fraud tool.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom