Blog
Browse Geocoding Tutorials, Guides & Updates
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...
One static map image per open house, with every stop labelled
Every Sunday tour sheet is the same story. An agent exports a list of open houses from the MLS, pastes it into a Word template, and either leaves the map blank or screenshots something from a consumer maps app — an act that ranges from legally grey to outright prohibited by the platform's terms of service. The buyer unfolds it on the passenger seat, reads "11:00am – 47 Elm Street, then 12:30pm – 8...
| Jun 02, 2026
Read One static map image per open house, with eve...
Territory carving for a 200-person SDR org in a weekend
Every RevOps team eventually faces the same crunch: a reorg lands on Thursday, 200 SDRs need clean territory assignments by Monday, and the CRM is a spreadsheet held together with VLOOKUP and good intentions. The data that drives territory carving — account addresses, employee counts, deal-stage distributions — has never been geocoded. Nobody knows which accounts actually sit in which postal geogr...
| Jun 01, 2026
Read Territory carving for a 200-person SDR org in...
Drive-time isochrones for ambulance coverage gap analysis
Every EMS director knows the eight-minute benchmark. It is not a law in most jurisdictions — it is a clinical observation baked into decades of cardiac-arrest outcome data, and it is the number that appears in every city council budget presentation about why a new station needs funding. What most EMS directors do not have is a repeatable, programmatic way to answer the follow-up question: how man...
| May 31, 2026
Read Drive-time isochrones for ambulance coverage...
HIPAA-safe patient address pipeline with no_record and Divisions
Geocoding patient addresses sounds like a one-afternoon integration. You have addresses. The API takes addresses. It returns coordinates. Ship it. It is not a one-afternoon integration. HIPAA's minimum-necessary rule applies to every system that touches protected health information, including a geocoding vendor. The moment a patient's home address transits your geocoding provider's infrastructure,...
| May 30, 2026
Read HIPAA-safe patient address pipeline with no_r...
Auto-assigning service tickets to the nearest technician
Most field-service dispatch tools still rely on a human reading a map. A ticket comes in, a dispatcher eyeballs a board, picks the technician who looks closest, and rings their radio. That works up to about forty concurrent technicians and a quiet afternoon. It does not work at scale, and it breaks entirely when the dispatcher goes to lunch. This post replaces the human-with-a-map with a two-call...
| May 29, 2026
Read Auto-assigning service tickets to the nearest...