OSRM unable to route to the center of Riga (the capital of Latvia) at `24.114803,56.945972`
Issue
For some reason OSRM routing breaks if the starting or destination is 24.114803,56.945972, which happens to be the coordinates of the center of Riga - https://map.project-osrm.org/?z=18¢er=56.945773%2C24.115216&loc=56.878999%2C23.961182&loc=56.945963%2C24.114802&hl=en&alt=0&srv=0
Moving the destination just a bit in any direction somehow fixes the issue
Steps to reproduce
$ curlie 'https://routing.openstreetmap.de/routed-car/match/v1/driving/24.178497,56.809717;24.114812,56.946963'
HTTP/2 400
server: nginx/1.22.1
date: Mon, 20 Oct 2025 12:54:03 GMT
content-type: application/json; charset=UTF-8
content-length: 57
access-control-allow-origin: *
access-control-allow-methods: GET
access-control-allow-headers: X-Requested-With, Content-Type
content-disposition: inline; filename="response.json"
{
"message": "Could not match the trace.",
"code": "NoMatch"
}
Please provide the steps required to reproduce your problem.
osrm-backendversion being used - latest- OSM extract that was processed - both latest that is deployed to the demo and
s3://osm-planet-eu-central-1/planet/pbf/2025/planet-251013.osm.pbf - Processing commands (e.g. CH vs MLD processing) - MLD
- Server queries -
'https://routing.openstreetmap.de/routed-car/match/v1/driving/24.178497,56.809717;24.114812,56.946963'
If you're reporting an issue with https://map.project-osrm.org, please provide a link to the problematic request.
Specifications
Please provide details of your development environment.
- Library/dependency versions
- Operating system
- Hardware
That is the city I come from! Is the issue maybe that the historical center of Riga is closed for traffic and you call a car URL?
Is the issue maybe that the historical center of Riga is closed for traffic and you call a car URL?
OSRM should find closest road then. If you open the link in issue description and move the pin a bit in different directions, you'll see that there is a small area (a few dozen square meters) where OSRM fails to route to.
Maybe you need to increase the radius param in the URL and not use the default (5m ?)
Maybe you need to increase the radius param in the URL and not use the default (5m ?)
It's unlimited
Any other suggestions how to make that point in Riga routable?
In the first screenshot, the point is likely snapped to this way. What happens may be related to a turn restriction as that way is part of relation 11066295 tagged with "restriction:no_left_turn".