Set a drive time to each place that matters. The overlap is your search area — then look at what's for sale inside it.
Shapes follow real road networks from openrouteservice, not circles.
Your filters carry across. The counts above are open houses only — homes holding one in the next two weeks. The MLS search covers every active listing, so it will show many more.
Up to four places. Each one draws the area you can reach in that drive time.
Almost nobody moving here actually asks how long the drive is. They ask whether it is too far — whether they will still accept thirty-five minutes in February, in the fourth week of doing it. This map draws the area you can genuinely reach in the time you set, on the real road network rather than as a circle.
The guide below puts that shape next to what Kansas City commutes measurably are, so the slider has something to be judged against.
Kansas City commutes are short by national standards, and knowing that changes what the slider means. Across the Kansas City, MO-KS metro area the mean travel time to work is 23.2 minutes, against 26.4 minutes for the United States (US Census Bureau, American Community Survey 2020–2024 5-year estimates, table DP03).
Of the 935,301 metro residents who commute — a figure that excludes the 16.9% who work from home — 69.9% arrive in under 30 minutes, 9.5% take 45 minutes or more, and 3.9% take an hour or more (ACS 2020–2024 5-year, table B08303).
So “under thirty minutes” is the ordinary case here, not a prize. If your shortlist is quietly asking you to accept forty-five, you are choosing something roughly one commuter in ten does — which may be entirely worth it, but it should be a decision rather than a drift.
The shapes are real openrouteservice isochrones, computed on the OpenStreetMap road network, in five-minute steps from 10 to 40 minutes around 27 prebuilt anchors (index generated 27 July 2026), plus any address you type, which is routed live.
They are free-flow. The router does not model rush hour, weather, a closed lane, or the eight minutes you spend finding parking. Read the polygon for the shape of what is reachable and the census figures above for the duration people actually live with — those are reported by the people making the trip, so the congestion is already inside them.
Shape is where this map earns its place, because a twenty-minute area is nothing like a circle. Highways stretch it into spokes; the Missouri and Kansas rivers, and the few bridges across them, pinch it hard. Two addresses the same straight-line distance from downtown can sit twenty minutes apart because one has to queue for a bridge and the other does not.
Enter the trips that repeat every week, not the ones that happen twice a year: both workplaces, the hospital you would actually use, the airport if you fly monthly. You can add up to four. Each draws its own area, and the hatched overlap is the only part of the map where every one of your constraints holds at once.
Set each drive time to the number you would still accept on the worst morning rather than the best one. If the overlap then vanishes, that is a real answer and the map says so plainly instead of showing you a quiet compromise: one anchor has to move, one drive time has to widen, or the two of you are optimising for different cities.
The count box is live listings inside the union of your areas; the second box appears only when something sits inside every area at once. Both open the same filtered MLS search, so the number you see and the search you launch always agree.
Anything about the places themselves. It draws travel time and only travel time — no score, no grade, no ranking, and nothing about who lives anywhere. A short drive is not an endorsement and a long one is not a warning.
Two further limits. An anchor is a single point, so a large campus with several entrances is approximated by one of them; and the polygons are simplified before they are drawn, so the edge is honest to a few hundred feet rather than to a driveway.
For the people who live there, the drive is not long: the mean travel time to work for Overland Park residents is 19.7 minutes, and 80.3% of them get to work in under 30 minutes, against 69.9% metro-wide (ACS 2020–2024 5-year, tables DP03 and B08303). Read that carefully, though — it measures the trip to wherever those residents actually work, and a great many Johnson County jobs are in Johnson County. If your job is specifically downtown, set Downtown KC as the anchor and see where the 25- and 30-minute edges fall, because the north and south ends of Overland Park are not the same trip.
There is no correct answer, but there is a reference distribution to decide against. Of metro residents who commute, 69.9% arrive in under 30 minutes, 9.5% take 45 minutes or more, and 3.9% take an hour or more (ACS 2020–2024 5-year, table B08303). A 45-minute commute here is not impossible; it is unusual. The useful test is not the average day but the worst one, so set the slider to the time you would still accept in February, at five in the afternoon, in the fourth week of doing it.
Less than the size of the metro suggests, measured by outcome rather than by anecdote: the mean travel time to work across the Kansas City metro is 23.2 minutes against 26.4 minutes nationally (ACS 2020–2024 5-year, table DP03). That figure is observed, so whatever congestion exists is already counted in it. Be clear about what this map does not do, though. The isochrones come from openrouteservice, which routes free-flow with no live traffic and no time of day. The polygon shows the shape of what is reachable; the census figures show what the trip actually costs.
The map answers that geographically for your specific address: set Downtown KC as the anchor, move the slider to 30, and the band that appears north of the river is the answer. For context, here is the share of residents in Northland cities whose commute to work takes under 30 minutes — North Kansas City 88.7%, Gladstone 73.4%, Parkville 71.9%, Liberty 69.5%, Excelsior Springs 67.2%, Kearney 64.6%, Platte City 60.8%, Smithville 55.6% (ACS 2020–2024 5-year, table B08303). Those are trips to wherever people work rather than to downtown, and they are travel-time facts about journeys, not descriptions of the places.
No, and it is better to say so than to imply otherwise. The isochrones are openrouteservice driving-car isochrones on the OpenStreetMap road network, computed free-flow: no live traffic, no time of day, no incidents. In practice the boundary is a good-conditions boundary, and the peak-hour version of it sits somewhere inside. Use the shape to decide which direction to search, check the duration against observed census commute times, and then drive the route once at the hour you would actually be driving it before you sign anything.
Yes. The first option in every place selector is “A specific address…”, which geocodes what you type and routes a fresh set of isochrones around it, so it behaves exactly like the 27 built-in anchors. That matters more than it sounds. The presets cover the places a stranger might commute to, but “thirty minutes from my mother’s house” or “twenty minutes from an office park nobody outside the company has heard of” is at least as common a question, and it is usually the one that actually decides where people search.
This is the question the map exists for. Add both workplaces, set each drive time to what that person will genuinely tolerate rather than what sounds reasonable, and look at the hatched area. It is the exact intersection of the two drive-time areas, not an approximation, so anything inside it satisfies both constraints at once. If nothing is inside it, the map tells you that outright. At that point the decision is which constraint gives: one drive time widens, one anchor changes, or one of you drives further than the other.
Not for the commute. The line is not a barrier and a great many people cross it twice a day, which is why this map ignores it entirely. It does have real consequences, but they are financial rather than temporal. Missouri assesses residential property at 19% of market value and Kansas at 11.5%, and once each district’s levies are applied the statutory rate runs from about 1.26% in Johnson County, Kansas to 1.83% in Wyandotte County, Kansas, with the Missouri counties in between (tax year 2025 certified levies, as of 1 November 2025). Search by drive time first, then price both sides.
Sources · Commute figures: US Census Bureau, American Community Survey 2020–2024 5-year estimates, tables DP03 and B08303, Kansas City MO-KS Metro Area and named places; retrieved 11 August 2026. Drive-time areas: openrouteservice driving-car isochrones on OpenStreetMap data, index generated 27 July 2026. Property tax: tax year 2025 certified county levies, as of 1 November 2025.