Tell IPv4 and IPv6 visitors apart in your logs
Read the version field on an IP lookup to know whether a visitor connected over IPv4 or IPv6, and why the distinction matters for logs and quota.
Step by step: geocode an address list, geolocate visitors, build an elevation profile, find the time zone of a point.
Read the version field on an IP lookup to know whether a visitor connected over IPv4 or IPv6, and why the distinction matters for logs and quota.
Use a visitor's IP address to set a sensible default country, tax rate, and currency before they type a single character into your form.
Look up a visitor's approximate location from their IP address entirely on your server, with no JavaScript tag or browser script involved.
Send a list of points along a route and get the elevation at each one back in a single request, ready to chart without further lookups.
Show timestamps in a visitor's local time instead of raw UTC, using their coordinates and a single time zone lookup with the right timestamp.
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.
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.
Wire up address suggestions as a customer types, cutting down on typos and abandoned checkout forms without a mapping library or extra scripts.
Send a list of latitude and longitude pairs to the reverse endpoint in one call and get back an address for each one, in order, without extra overhead.
Turn a spreadsheet export into a single POST request and get back one geocoded result per row, without writing a request loop or paying for extra calls.
Only Guides, as it is published.
Subscribe to Guides