Map A Radius From An Address

You're standing in a parking lot, phone in hand, trying to figure out if that coffee shop across the street is actually within walking distance of your meeting. Or maybe you're a real estate agent trying to show a client every school within three miles of a listing. Or you're planning a road trip and need to know which national parks fall inside a four-hour drive from your cousin's house in Denver.

All of these problems have the same solution: mapping a radius from an address.

It sounds simple. Draw a circle on a map. Done. But anyone who's actually tried to do this — really do it, not just eyeball it — knows the devil lives in the details. Worth adding: the tool you pick matters. Now, the projection matters. Whether you're measuring "as the crow flies" versus actual drive time changes everything.

Let's walk through it properly.

What Is Radius Mapping

At its core, radius mapping is exactly what it sounds like: you pick a center point — an address, a coordinate, a landmark — and you draw a circle around it at a specified distance. Even so, everything inside that circle falls within your radius. Everything outside doesn't.

But there are two fundamentally different ways to define "distance," and confusing them is the single biggest mistake people make.

Straight-line distance (often called "as-the-crow-flies" or Euclidean distance) draws a perfect circle on a flat map. It ignores roads, rivers, mountains, one-way streets, and traffic. It's the geometric radius. If you set a 5-mile radius from downtown Seattle, you'll capture parts of Bainbridge Island across the water — even though driving there takes an hour and a ferry ride.

Drive-time distance (isochrone mapping) calculates how far you can actually travel along the road network in a given amount of time. A 15-minute drive-time radius from that same downtown Seattle point looks nothing like a circle. It stretches along highways and bottlenecks at bridges. It's lumpy, asymmetrical, and infinitely more useful for most real-world decisions.

Some tools also offer walking-radius or cycling-radius variants, which follow pedestrian paths and bike lanes instead of car roads. The shape changes again.

The term "radius" technically only applies to the straight-line version. Purists will tell you an isochrone isn't a radius at all. Here's the thing — they're right. But in common usage, people say "radius" for all of it. I'll use the term loosely here — just know which one you actually need.

Why It Matters

You'd be surprised how many decisions hinge on getting this right.

A restaurant owner picking a second location needs to know how many potential customers live within a 10-minute drive — not a 10-mile circle that includes a lake and a highway with no exits. A parent choosing a daycare needs walking distance, not straight-line distance that cuts through a freeway. A field sales manager assigning territories needs drive-time polygons that don't overlap and leave gaps.

Get it wrong, and you're not just looking at a slightly off map. You're making business decisions on bad data. You're telling a client "it's a 10-minute walk" when it's actually 25 because the sidewalk ends. You're excluding a whole neighborhood from your delivery zone because the river bends weirdly.

The stakes are usually higher than people realize.

How to Actually Do It

There's no single "best" tool. The right choice depends on what you're trying to accomplish, how technical you are, and whether you need to do this once or five hundred times.

Free browser-based tools for quick one-offs

If you need a radius map right now and you'll never need another one, start here.

Google Maps — the one everyone already has — can measure straight-line distance. Right-click your starting point, select "Measure distance," click your endpoint. It gives you a line, not a circle. To get a circle, you have to drop multiple points around the perimeter manually. Tedious. But it works in a pinch.

MapDevelopers' Radius Tool (mapdevelopers.com/draw-circle-tool) — paste an address, set a radius in miles or kilometers, get a circle. You can export a KML for Google Earth. Clean, free, no login. The circle renders on a Google Maps base layer.

FreeMapTools Radius Around Point (freemaptools.com/radius-around-point.htm) — similar idea, more options. You can add multiple radii, change colors, get the coordinates of the circle's perimeter points. Useful if you need to plug those coordinates into something else.

TravelTime's free radius map (traveltime.com/radius-map) — this one's different. It does drive-time isochrones for free, up to a point. Enter an address, pick "driving" or "public transport," set minutes. The resulting shape is an isochrone, not a circle. Much more useful for real-world planning. The free tier has limits on exports and API calls, but for a one-off visual? Solid.

When you need drive-time polygons (isochrones)

Straight-line circles are easy. Drive-time shapes are hard because they require a routing engine — a graph of the entire road network with speeds, turn restrictions, one-ways, traffic patterns.

Continue exploring with our guides on acid and base combine to form and the direction of the current in an alternating current circuit.

TravelTime API — the gold standard for this. They've built a global isochrone engine that returns polygons in seconds. You send a coordinate, a travel mode (drive, walk, transit, bike), and a time limit. You get back a GeoJSON polygon. Expensive at scale, but the free tier handles plenty for testing.

Mapbox Isochrone API — similar concept, built on OpenStreetMap data. Good developer experience. Pricing is per-request. The polygons sometimes look a little jagged at the edges compared to TravelTime, but for most use cases it's indistinguishable.

OpenRouteService (ORS) — open-source, self-hostable if you have the infrastructure. Uses OSM data. The hosted free tier is generous (2,000 requests/day). Great if you want to avoid vendor lock-in or need to run this behind a firewall. The isochrone quality depends on OSM completeness in your area — rural regions can be spotty.

Valhalla — Mapzen's open-source routing engine. Powers a lot of the above. You can run it yourself. The isochrone service is fast and supports multimodal routing (drive to park-and-ride, then transit). Steeper learning curve.

When you need to do this at scale

"At scale" means different things. Hundreds of radii? Even so, thousands? Millions?

QGIS + plugins — if you're comfortable with desktop GIS, the "Travel Time" plugin or "ORS Tools" plugin lets you batch-generate isochrones from a CSV of addresses. Free, powerful, runs locally. Learning curve is real but the flexibility is unmatched. You can style, overlay, intersect with census data, join to your own datasets — whatever you need.

Python + GeoPandas + OSMnx / Valhalla / ORS — for developers who want scriptable, reproducible pipelines. OSMnx can download street networks and compute straight-line buffers natively. For drive-time, you'll call an API (ORS, Valhalla, TravelTime) or run a local Valhalla instance. This is how

This is how you build a pipeline that can handle thousands of locations without breaking a sweat. The key is to decouple your data ingestion from your computation. Now, pull the street network once, cache it, and then reuse it across hundreds of requests. For most teams, the sweet spot is a simple Python script that reads a CSV of origin points, calls an API like ORS or Valhalla for each, and writes the results to a GeoPackage or PostGIS table. If you're working with real-time dashboards, consider caching isochrones in a spatial database and only recompute when the underlying road network changes.

Batch processing at scale — if you're running this for a city or region rather than a handful of addresses, you can download the full OSM extract for your area and compute drive-time polygons locally. Valhalla's isochrone command accepts a network file and generates a polygon for every node in seconds. The trade-off is storage: a full OSM extract for a mid-sized metro area can be several gigabytes. But once you have it, you can run isochrone queries against it without any API calls at all.

Geospatial libraries — GeoPandas and Shapely make it straightforward to join isochrone polygons to other layers, like census tracts, parcel boundaries, or points of interest. You can clip isochrones to a study area, union overlapping polygons, or even compute the intersection of multiple travel modes to find optimal multi-modal routes. The geopandas + shapely combo is the backbone of most custom isochrone workflows.

Cloud and serverless options — if you don't want to manage infrastructure, services like AWS Lambda, Google Cloud Functions, or Azure Functions can handle isochrone requests on demand. You set a trigger (e.g., a scheduled job or an API call), the function computes the polygon, and stores it in a database. This scales elastically and costs roughly nothing for light workloads. The downside is that you'll pay for compute time, and the latency per request is higher than a self-hosted Valhalla instance.

Choosing the right approach

The right tool depends on your use case:

• Quick visual check — TravelTime API or Mapbox Isochrone API. One API call, one polygon, done.
• Prototyping and testing — Valhalla or ORS. Free, open-source, and you can run it locally.
• Batch processing for a city — QGIS + plugins or Python + GeoPandas + OSMnx. Reproducible, flexible, and no vendor lock-in.
• Production at scale — Self-hosted Valhalla or ORS behind a firewall, or a serverless pipeline with caching.

The bottom line

Isochrones are one of the most practical tools in a planner's or analyst's toolkit. They turn a simple "how far" question into a rich spatial analysis. Still, the tools range from a single API call to a full local pipeline, and the free tiers are generous enough to start without commitment. Whether you're building a city-wide isochrone map or just checking drive times for a single address, the right approach is available — you just need to match it to your scale and your infrastructure.

In the next installment, we'll explore how to visualize and share these polygons, including best practices for styling isochrones for public-facing maps and integrating them into web applications.