Bug 307087 - Routing doesn't obey bollard
Summary: Routing doesn't obey bollard
Status: RESOLVED UPSTREAM
Alias: None
Product: marble
Classification: Applications
Component: data (other bugs)
Version First Reported In: 1.4 (KDE 4.9)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-20 07:54 UTC by p
Modified: 2012-09-20 08:21 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description p 2012-09-20 07:54:25 UTC
If you calculate a route for a car then the route can go through a bollard, by foot or bicycle that is fine but of course not for a car.
Comment 1 Dennis Nienhüser 2012-09-20 08:21:32 UTC
This is possibly a valid request, but out of Marble's scope: The route is not calculated directly by Marble, but by a backend which we can't fix directly. Can you please report the problem at the respective routing backend? This could be
- OpenRouteService, http://openrouteservice.org/contact.php
- Monav, http://code.google.com/p/monav/issues/list
- MapQuest, http://www.mapquest.com/
- Yours, http://wiki.openstreetmap.org/wiki/YOURS

Use the Configure button in the routing tab in Marble to deactivate some routing backends if you're unsure which one returned the current route.

Please include the location of the bollard to ensure that people can check it is correctly mapped.