Blog
Browse Geocoding Tutorials, Guides & Updates
Mass appraisal geocoding: placing every parcel correctly
A county assessor's office runs a mass appraisal cycle once a year — sometimes more often if the local tax authority is under political pressure to revalue quickly. The input is the parcel roll: hundreds of thousands of rows, each with a situs address, an APN, a legal description, and an assessed value. The output is that same roll with verified coordinates, administrative division labels (county,...
| Jun 16, 2026
Read Mass appraisal geocoding: placing every parce...
Where your hotel guests come from: address catchment analysis
Your property management system has recorded the home address of every guest who checked in for the last three years. That data is sitting in a reservation table, used for nothing except mailing confirmation letters. This post shows how to turn it into something useful: a geocoded, boundary-joined catchment map that tells your revenue management team exactly where demand comes from, how far gues...
| Jun 15, 2026
Read Where your hotel guests come from: address ca...
What's near every hotel: travel content at scale
Every hotel listing on every OTA says some version of the same thing: "centrally located," "steps from major attractions," "close to public transport." Almost none of them prove it with data. The listing that says "walking distance to the Eiffel Tower" is relying on a copywriter's memory of where the Eiffel Tower actually is, written once when the property was first listed and never audited since....
| Jun 14, 2026
Read What's near every hotel: travel content at sc...
Shared team accounts: batch geocoding for the whole company
Most companies end up with three or four separate geocoding logins before anyone notices. The operations team signed up first because they had a delivery file to clean up. The sales team created their own account a quarter later because they did not know operations already had one. Someone in the data team ran a one-off enrichment on a personal login and expensed it. Now there are several monthly...
| Jun 13, 2026
Read Shared team accounts: batch geocoding for the...
Replacing flood zone PDFs with a 50 ms API call
The Flood Insurance Rate Map — a FIRM — is a regulatory artifact. It is also, for most underwriting teams, a genuine operational bottleneck. An analyst opens a browser, types an address into a lookup portal, downloads a PDF panel, finds the right panel among fifteen that overlap the property, reads the zone designation, and transcribes it into the policy system. On a good day that is three minutes...
| Jun 11, 2026
Read Replacing flood zone PDFs with a 50 ms API ca...
Sync vs async batch geocoding: a 1 M-row decision tree
Most geocoding integrations start synchronous. A driver app resolves one stop address before rendering the map pin. A customer-facing order tracker converts a depot address on page load. These are fine. The sync path is simple, debuggable, and — for one address at a time — entirely appropriate. The trouble arrives the day a logistics operations team uploads a shipment manifest with 900,000 rows an...
| Jun 09, 2026
Read Sync vs async batch geocoding: a 1 M-row deci...
Embedding a geocoding API in your SaaS without becoming an SRE
Most B2B SaaS products reach a point where they need geocoding. A CRM wants to normalise customer addresses. A field-service scheduler needs to turn a postcode into coordinates. A compliance tool needs to attach a jurisdiction to every account record. The feature is small enough that a single engineer owns the integration — and that engineer typically has no SRE support, no dedicated infra rotatio...
| Jun 07, 2026
Read Embedding a geocoding API in your SaaS withou...
Looking up county, district, and school zone from an address
A constituent files a service request online. Your system records the address. But which county is responsible for the road? Which school district answers the permit application? Which council ward gets the political credit for fixing the pothole? Which special tax district issues the assessment? In most civic platforms, the answer to each of these questions comes from a different lookup in a diff...
| Jun 06, 2026
Read Looking up county, district, and school zone...
Your nearest-store widget needs three APIs, not one
Every retail engineering team builds the nearest-store widget the same way: geocode the user's postcode, compute straight-line distances to every store in the database, return the top five. Costs half a sprint. Ships on time. Works fine in a demo. Then someone in Manchester gets routed to a store that is technically 1.8 km away but requires crossing a motorway interchange, a railway embankment, an...
| Jun 05, 2026
Read Your nearest-store widget needs three APIs, n...
Solar site screening: 10,000 candidate roofs in an afternoon
A solar development team running a prospecting campaign has a familiar problem. The business development side hands over a spreadsheet of 10,000 addresses — residential parcels, commercial rooftops, municipal buildings — and asks which ones are worth sending a field surveyor to. The addresses came from county parcel records, utility interconnection queues, and a bought list of large flat-roof comm...
| Jun 03, 2026
Read Solar site screening: 10,000 candidate roofs...