OSM data problems

I have used Kurviger route planning and navigation for couple of months. Have no complaints for the app, but OSM data used by this app is absolutely useless. Too many errors and misinformation. I did try to correct them, but it seems I need about 120 working hours just to correct a few regions in Quebec, Canada. We ride a lot here and the OSM data is very bad. Is there a way to use Google data or any other? Instead of a route 2 in Ontario in most sections it shows train trucks. In other region of Quebec it kept taking me out of main route and pushing into side streets of a village and bringing me back to the route, but instead of taking me into, it crosses the route and turns and comes back and crosses again!
If the OSM is the only option I think I will another app of my route planning.

1 Like

Could you share some of the problematic routes that you tried to plan? In Kurviger, just go to “…” menu, then “Share” and post the short link here. Some of the described problems might be caused by using too much avoidances, but I also agree that OSM is not on the same level in all parts of the world.

Currently OSM ist the only option in Kurviger, I do not know if developers are considering other sources for the future.

2 Likes

The problem is not one or two routes. Any route created in Quebec or Ontario (haven’t tried in other provinces) has this type of problem.
I have to put in hundreds of waypoints to keep the route on the proper road.
The first time I did report the issue was on route 2 in Ontario. The route wouldn’t stay on Rte 2 road. When checked on OSM, most of the the Rte 2 was marked as railroad!
I tried to correct that, but gave up after 1 hour. Too many sections were wrong.

1 Like

Maybe you could still share a couple of exemolary routes where your expectations were not met, so we can figure out what exactly is going on.

I am from Europe an although it might be a well known in Canada, I could not figure out what is the “Route 2” that you referred to in the first post.