Most often, these are related to closed roads, roads you’d like to ride but aren’t being mapped down, or other unexpected routing dilemmas. Whilst it seems trivial, mapping the globe and its roads is a massive, collaborative effort. The road data we use comes from OpenStreetMap (OSM) - they tell us which roads we can route users down, what the surface of roads are, etc. If you’re coming across one of these common issues, don't worry, these can be resolved easily with some quick fixes to the street details in OpenStreetMap.
Understanding Routing Errors
Beeline relies on OpenStreetMap (OSM) for all its road data, including closures, accessibility, and road tags. If you're experiencing unexpected routing, it could be due to the data on OSM.
Common Issues resolved through OpenStreetMap data
Being Routed Down a Closed Road
Sometimes, our map might not show a road closure, even if you know it's there. This can happen because:
Road closures/ reopenings can have a delay in being reported and tagged on OpenStreetMap. It will only be relayed in the Beeline app once confirmed in OpenStreetMap, so if you aren’t being routed down a road you feel you should - find the road and tag it as such or tell us, and we can get it corrected.
We don't always pick up conditional closures from OpenStreetMap (think of a road only closed during specific hours, like "9 AM to 12 PM on Saturdays").
OpenStreetMap isn't designed for very quick, short-term closures, like a road closed just for one day of work.
While we do get some road closure updates from HERE (which is part of our Beeline Plus traffic features), please understand that we won't have information on every single road closure.
What to do:
Find and fix the road on OpenStreetMap. Jump to the “Contribute to OpenStreetMap yourself!” section below to learn how.
OR
Please get in touch with us. Provide as much detail as possible about the closure, including:
Coordinates or a precise location (e.g., street names, nearby landmarks)
The approximate length of the closure
Any information about when the closure is expected to end (if known)
How we'll help: Our team will investigate the information and work to get the map data updated - please know that we are not always able to update the information, but we will try.
Incorrect Road Information
If you notice a road has incorrect speed limits, one-way restrictions, or other details that are wrong, this is also due to inaccurate information on OpenStreetMap.
What to do:
Find and fix the road on OpenStreetMap. Jump to the “Contribute to OpenStreetMap yourself!” section below to learn how.
OR
Please get in touch with us. Provide as much detail as possible about the closure, including:
Coordinates or a precise location (e.g., street names, nearby landmarks)
The approximate length of the closure
Any information about when the closure is expected to end (if known)
How we'll help: We'll be happy to investigate and update the map data if possible.
Roads Not Showing Properly on the Map/Device
This is a less common issue, but something that we would want to get sorted for you.
What to do:
Update your app: First, ensure your Beeline app is running on the latest version. App updates often include bug fixes and improvements.
Contact us: If the problem persists, we need to see what you're experiencing. Please take a screenshot of what you see in the app or a picture of what you see on your Beeline device, then get in touch with our support team. This will help us investigate efficiently.
Contribute to OpenStreetMap yourself!
Did you know that many of these map data issues, from incorrect speed limits to missing roads, can often be adjusted by users like you? OpenStreetMap is a community-driven project, and you can contribute to making the maps better for everyone.
We have a support article on ‘How to contribute speed limits on OpenStreetMap’ and plan to release more step-by-step guides soon on how you can easily make other adjustments. Please do keep an eye out for these!