The routing part will not recognize existing barriers on roads. While the OSM data contain information about potential barriers (e.g. barrier=block, motorcar=no), in several cases I have tried the route found will go across them, regardless of the selected transport means. This is quite a big problem, since such a route becomes unusable. Reproducible: Always Steps to Reproduce: 1. Select Openstreetmap Map View. Find a place where data contain a road barrier. Eg. look for "maly 0krouhlik" road 2. Switch to Routing tab. For places A and B, choose sites on either sides of the barrier. Select profile Car (fastest, or shortest) 3. Click Get directions. Actual Results: The route which is found crosses the barrier. Expected Results: The resulting route should make a by-pass around the barrier.
Which routing backend are you using? Use the "settings" button in the Routing tab and check which backends are enabled. Some support barriers, some ignore them.
OpenRouteService and Yours appear to lead both to the described behaviour, if checked individually. The other routing backends do not seem to work- do not provide any route at this moment.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
The bug seems to persist still in the version 2.2.20 of Marble. That is, I tried to find a car route at the place indicated, either with the profile "car (fastest)" or "car (shortest)". The only results I got were routes provided by Yours. For "car (shortest)", actually I sometimes did get a reasonable route avoiding the barrier when one of the points A, B was dragged on the map by the mouse. However, the summary at the drop-down box shows the direct distance between the depart and arrival (less than 200 m), not the actual length of the route (1 km or so). In other cases, the route went across the barrier "Car (fastest)" always yields a straight route going across the barrier. In either case, the direction list remains empty.
Thanks for the update!