Route Surface & Road Type Finder
Route a drive and inspect surface and road-type tags on nearby OpenStreetMap ways. Counts may include roads off the route and are not distances or percentages.
By Aryan Khan, Founder & Editor · Updated October 2026
Nearby mapped roads can have different surface tags from the actual route. Verify the route and current conditions before travel.
How to use Route Surface & Road Type Finder
Enter a start and destination, then inspect nearby map tags as preliminary context:
The tool routes a drive and counts OpenStreetMap ways within 30 metres of up to 20 sampled route points. Nearby ways can be off the route; counts are not distance shares. Elevation gain is sampled when available.
- 1Add start, stops and destination.
- 2Press “Analyse surface & terrain”.
- 3Read the surface and road-type counts with the climb.
What people use Route Surface & Road Type Finder for
1. Gravel and adventure riding
Nearby surface tags can flag possible unpaved roads, but cannot establish which surfaces a route follows. For elevation context see the Route Elevation Gain Calculator.
2. Loaded touring
Mapped surface tags may be incomplete or out of date. Check current route conditions with local sources before touring.
3. Vehicle suitability
Counts of nearby ways do not establish whether a route is suitable or accessible for a vehicle. Check local restrictions and conditions.
4. Route comparison
Compare nearby mapped tags cautiously: counts are neither route length nor proof of the surface on the selected road.
Worked examples
A gravel-tagged way within 30 metres of a sampled point may be a parallel road. Its presence in the count does not prove the routed road is gravel.
Ways without an OpenStreetMap surface tag are counted as not recorded. Missing data should not be treated as a paved or unpaved classification.
Surface types you will meet
Examples of OpenStreetMap surface and road-type tags that may appear among nearby ways.
| Recorded as | Means | Wheels' verdict |
|---|---|---|
| Asphalt / paved | Sealed surface | Everything rolls |
| Gravel | Loose stone, graded | Road bikes crawl, gravel bikes feast |
| Dirt / ground | Unsealed earth | Weather decides |
| Track | Farm or forest track | Adventure territory |
| Cobblestone / sett | Stone blocks | Historic centres, slow and loud |
| Unknown | Not recorded in OSM | Treat as a question, not a promise |
Counts cover nearby returned ways, not the length or percentage of the route. Data can be incomplete or outdated.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Route Surface & Road Type Finder:
- Place route endpoints on roads, not rooftops. Routing engines snap points to the nearest drivable way, and a point in a river or a courtyard can snap somewhere surprising — nudging the pin to the nearest street makes results stable and explainable.
- When optimising many stops, keep the true origin first and let the engine order the rest; then sanity-check the result visually. Optimizers minimise distance, not your time windows — hard appointments still belong in manual order.
Limits & appropriate use
Routing's limits live in three places: data vintage, access reality and time modelling. The network is OpenStreetMap's current picture — new interchanges lag, private gates may be missing, seasonal ferries keep their own calendars. Access rules reflect mapped law, not today's roadworks. And durations are free-flow physics: speed limits and road classes without your city's sociology, so peak hours, weather and parking belong in your buffer, not in the engine's promise. The tools label all three limits on every result, because an unlabelled estimate is a trap.
What the stack does brilliantly is the reproducible core: the same stops, mode and engine give the same route to everyone, everywhere, which makes it a superb baseline for comparison, screening and planning. Escalation is domain-specific and well understood — professional dispatch adds live traffic and driver hours; logistics tenders add contracted networks; navigation products add certified maps. A free browser tool that hands you a clean, exportable baseline with its assumptions printed is not competing with those; it is feeding them.
- Live congestion and ETAs → traffic-aware commercial routing.
- Driver-hours and windows → transport-management systems.
- Certified navigation → licensed map products with update guarantees.
Data & methodology
Driving routing; Overpass returns up to 400 highway ways within 30 metres of up to 20 route samples. Way counts can include roads off the route and are not distance shares. Elevation is sampled from Open-Meteo when available.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- Free-flow time
- Travel time from speed limits and road classes, without congestion.
- Travelling-salesman ordering
- Reordering stops to minimise total route distance.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Routing & Travel Time. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- Driving routing; Overpass returns up to 400 highway ways within 30 metres of up to 20 route samples. Way counts can include roads off the route and are not distance shares. Elevation is sampled from Open-Meteo when available.
- Before relying on the answer
- Check the stop order, travel mode and whether the result is a network route or a simplified estimate. Repeat the calculation after changing any of these inputs.
- What the result cannot establish
- Road access, congestion and closures can change. An estimated duration is not a live arrival-time commitment.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
What if a road has no surface recorded?
It is counted as “not recorded”, never guessed — in many rural areas most ways carry no surface tag, and the report shows that honestly.
How is the sampling done?
Twenty points are spread along the routed path; OpenStreetMap ways within about 100 ft (30 m) of each point are tallied.
Does the route include live traffic?
Unless the tool explicitly says otherwise, travel times are planning estimates and should not be treated as live-traffic predictions.
Why is road distance longer than straight-line distance?
Roads must follow the available network, terrain, bridges and restrictions, while straight-line distance measures the geometric minimum between two points.
Can route results change over time?
Yes. Road-network data, access restrictions and routing datasets can change, so recheck important journeys close to travel time.
Why is road distance longer than straight-line?
The route sampled is the road route — surfaces belong to roads, not to crow lines.
Does it show elevation too?
When the elevation service is available, it estimates gain from sampled elevations along the route. Sampling may miss changes between points.
Can it force a gravel-only or paved-only route?
No. It uses a driving route and does not constrain routing by surface.
Can it tell me a road is closed?
No — surfaces and types, not closures. A mapped gravel road may still be gated; local signs outrank data.
Why does my route show 100% unknown?
The tool reports counts, not percentages. Returned ways without a surface tag are shown as not recorded.
Cobblestone counts as paved?
The tool displays the recorded surface value rather than assigning it to a paved or unpaved category.
Related tools and resources
Climb is the Route Elevation Gain Calculator; the flown preview is the Route Flyover Preview; and loops to analyse start in the Running Route Loop Generator.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our routes & travel time hub
Route Surface & Road Type Finder sits in the routes & travel time cluster, alongside 62 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Radius vs. Drive Time vs. Straight-Line Distance: Which Map Should You Use? — A practical guide to choosing between a radius circle, road travel-time map and straight-line distance so your result matches the real question you are trying to answer.