Blog
Browse Geocoding Tutorials, Guides & Updates
Bank branch catchment and CRA reporting with batch geocoding
Community Reinvestment Act reporting demands a precise answer to a deceptively simple question: which census tract does each loan application belong to? The examiner will spot-check your HMDA LAR. The geocoding quality on file needs to hold up to scrutiny. Get the county wrong on a borderline address and you have a tract assignment error; get the tract wrong and you have a reporting error. Do that...
| Jun 20, 2026
Read Bank branch catchment and CRA reporting with...
Verifying vacation rental locations before they go live
A guest books a beachfront cottage. The listing says "oceanfront, 50 metres to the sand." The pin on the map sits in the middle of a roundabout 400 metres inland. They arrive at night, cannot find the property, and by morning the host has a one-star review and the platform has a chargeback dispute open. This is not a rare edge case. Any platform that lets hosts type their own address and drag thei...
| Jun 19, 2026
Read Verifying vacation rental locations before th...
Run geocoding for every client under one team plan
Agencies do not have a geocoding problem. They have five geocoding problems, one per active client, running simultaneously, billed to three different stakeholders, executed by a team of four analysts who share a Slack channel and a deadline but not a clear picture of who has spent how many credits this month. The standard workaround is a proliferation of accounts: each analyst signs up separately,...
| Jun 18, 2026
Read Run geocoding for every client under one team...
Mapping your insurance book exposure by zone
Most carriers can tell you their aggregate exposure by state in thirty seconds. Fewer can tell you what percentage of their book sits inside a named wind corridor, within two kilometres of a mapped wildfire buffer, or below 5 m elevation in a coastal county. The reason is almost never a shortage of risk models — it is that translating a million policy addresses into zone assignments is harder than...
| Jun 17, 2026
Read Mapping your insurance book exposure by zone
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...