Route Mapper
Driving distance in kilometres and duration as h:mm between two coordinates, with the routing profile named.
Driving distance between two points
Type the latitude and longitude of a start and of a destination, then press Run. The page asks a router for the road route between them and prints the distance in kilometres, the duration as hours and minutes, and the profile the router used. The short Berlin example below returns 1.888 km in 0:04 on the driving profile.
What leaves your machine
The route is computed on the tool server. Your four coordinates are sent to router.project-osrm.org, the OSRM project's public demo router, as the path of the request — digits, a decimal point, a comma and a semicolon, nothing else. The request also carries three fixed switches asking for the route only: no turn-by-turn steps, no alternative routes, no geometry. Those switches are constants in the tool's source, not your input, and there is no place name, no address, no key and no account. Each number is parsed and range-checked before the path is built, so a value that is not a number is refused here and never reaches the router. This page does not ask the browser for a location.
Whose numbers these are
The distance and duration are a third party's estimate: OSRM's own route over OpenStreetMap data, using its car profile. They are not a traffic-aware arrival time, and they do not know about a closed road, a ferry queue or a border crossing. The profile matters more than the numbers suggest — a lorry, a bicycle or a walking route follows different roads and different rules, and this tool only answers for a car.
Where it stops
A latitude outside -90 to 90 or a longitude outside -180 to 180 is refused, with the field named, before any request is made. When the router cannot join the two points by road it answers NoRoute, and the page reports that code rather than showing zero kilometres. The demo router is a shared public instance with no service guarantee, so a busy moment can return a rate-limit error; the page names the HTTP status it received instead of inventing a route.
Driving distance and duration between two coordinates, from the OSRM public demo server, with the profile the router used printed beside the answer.
This one is server-backed: four coordinates are sent to router.project-osrm.org, formatted as floats in the path. The profile is a car profile on OpenStreetMap data — not a lorry, a bicycle or a pedestrian.
How to use Route Mapper
Enter Start latitude and Start longitude, then End latitude and End longitude, all in decimal degrees.
Press Measure the route and read the distance in kilometres with the duration as h:mm.
Read the profile named beside the answer — a car route over OpenStreetMap data — and treat NoRoute as the router's code rather than zero kilometres.
What is sent, and where
The request goes to the OSRM demo server's driving route endpoint, keyless. Each of the four numbers is parsed to a float, bounds-checked and formatted before it becomes a path segment, so a visitor's string never reaches the path — `../`, `?` or a host name has nowhere to go. Redirects are refused and the response body is not logged.
Reading the answer
The page prints the distance in kilometres, the duration as h:mm, and the profile. A route the router cannot find is reported as the router's own NoRoute code, never as zero kilometres, because zero would read as a valid route.
Where it stops
Two points, one profile, no waypoints and no traffic model. The demo server is a shared public instance with no service guarantee, and a coordinate outside the planet is refused by the field that carries it.
What to Expect
Best for
- a rough driving distance between two points
- checking whether a route exists at all before planning
What this tool keeps
- The lookup runs on the tool server and returns one answer; this page keeps no history of routes.
What may need cleanup
- Nothing is stored here. The server's log line names the two points and the status returned, not a saved route.
Frequently asked questions
Which router answers this?
OSRM's public demo server, driving profile, on OpenStreetMap data. The page prints the profile beside the distance and duration so the basis is visible.
Why is the answer wrong for a lorry or a bike?
Because the profile is a car profile. The demo server's driving route does not model vehicle height, weight, access restrictions or bicycle paths, and the page says so rather than implying otherwise.
What happens if no route is found?
The page reports the router's NoRoute code as the answer. It never shows zero kilometres, because that would look like a valid route of no length.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.