Property-level risk scoring at portfolio scale
Anchor addresses, layer terrain and elevation, assess access from emergency services. Bulk-process portfolios in one call.
Risk underwriting needs spatial features for every address in a portfolio: precise coordinates, elevation and grade for flood and landslide priors, distance and reach to emergency services, and admin hierarchy for regulatory aggregation. The bulk shape of the problem makes it ideal for batch processing.
batch_geocode anchors up to 1,000 addresses per call with confidence scores and typed errors on failures. get_elevation returns per-point heights plus a summary block. get_isochrone computes drive-time reach from the nearest fire station, hospital, or coast guard. reverse_geocode hangs admin metadata off raw coordinates for portfolio aggregation by region.
Outputs are deterministic and versioned, so an underwriting model can pin to a specific data snapshot for reproducibility across audit cycles.
What this looks like in practice
Common shapes mapped to the tools you'd reach for.
Portfolio anchoring
Run a portfolio CSV through batch_geocode. Successful rows return coordinates and confidence; failed rows return typed errors. Re-run failures after manual cleanup or parse_address normalisation.
Flood and elevation priors
For each anchored property, query get_elevation. Combine height and grade with proximity to coastline or river to derive a flood-risk band feature for the underwriting model.
Emergency-service access
Compute drive-time isochrones from each fire station and hospital. Tag every property with the time-to-nearest-service, useful for pricing and capital allocation models.
The Footstep tools that fit this shape
A focused subset of the catalogue. Click any card for the full reference.
batch_geocodeGeocode up to 1,000 addresses in a single call.
get_elevationElevation values for coordinates or paths, with summary statistics.
get_isochroneEverywhere reachable within a time or distance budget. Returns a polygon boundary.
reverse_geocodeConvert coordinates to an address. Find what's at a lat/lng.
get_matrixTravel times and distances between every origin and destination pair.
Other use cases
Search, rescue, and crisis response
Score where a missing person is most likely to be found. Direct ground teams to the highest-density hexes first.
Read →Logistics and autonomous fleets
Multi-stop optimisation, OD matrices, and corridor search for the agents and backends that move things.
Read →Environmental and field operations
Terrain profiles, reachability polygons, and GPS map matching for ESG reporting, conservation, and field research.
Read →Real estate and property
Geocode listings, model commute reach, score nearby amenities, and overlay terrain risk. The toolkit behind agent-led property search.
Read →Travel and itinerary planning
Find places, route between them, fit them into a time budget, and surface what's on the way. The geospatial layer behind agentic trip planners.
Read →Customer-input cleanup
Fix typos, expand abbreviations, validate before geocoding. The reliable pre-step for agents handling user-typed addresses.
Read →Field service and dispatch
Optimise visit order, score reachable jobs from each tech, clean GPS into proof-of-visit records.
Read →Healthcare access and equity
Compute drive-time and walk-time access to facilities, model coverage gaps, place ambulances with travel-time matrices.
Read →Sales and territory planning
Build OD matrices between reps and accounts, draw catchments around offices, normalise lead addresses at scale.
Read →Outdoor and fitness apps
Plan walking, hiking, and cycling routes with explicit difficulty. Snap noisy GPS into clean traces with surface and grade per edge.
Read →Public-sector planning
Model who can reach what, where the gaps are, how transit changes the answer. Reachability and matrix tools for civic planning.
Read →