This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Incorrect oneway implementation/map

It seems that the route track creation is allowing to drive agains oneway streets. This is despite the fact that this completely legal for the waste majorty of oneway sections in Vienna.

This bug makes track editing close to impossible in Vienna and probably a lot other cities.

  • It seems

    It seems ...

    the route track creation is allowing to drive agains oneway streets.

    On how many roads did you find this? 1, 2 or on 30 in vienna?

    and probably a lot other cities.

    So far, I have not experienced this in any of the routes I have driven. 

  • In which city did you try this successfully. I'm talking about track creation.

    I tried many oneway streets for which I know that they are allowed to be driven both ways by bicicles.

  • I'm sorry, I don't like to talk about my neighboring cities for privacy reasons. But they are in Germany.
    As for the timeliness of the data, I was also very surprised. In our case, a completely newly built residential area with completely new streets (2 months) is perfectly integrated into the cycle map.

    As far as your streets in Vienna are concerned, perhaps you should name the streets more precisely so that other users or a GARMIN employee can understand and possibly help you.

    Somehow I don't really understand you. If it is allowed to ride with a bike against the one-way street, why is it a problem when planning the route along such streets?

  • As far as your streets in Vienna are concerned, perhaps you should name the streets more precisely so that other users or a GARMIN employee can understand and possibly help you.

    I did not find any bidirectional oneway street in Vienna that does work.

  • Somehow I don't really understand you. If it is allowed to ride with a bike against the one-way street, why is it a problem when planning the route along such streets?

    Because it plans detours on high traffic roads. The only way to overcome this is with fre hand sections. But for that I don't need a route planner at all.

    And I assume that the navigation has the same issue. I did not try yet because the address search there is so cumbersome that it is hardly useable for ad hoc navigation.

  • Do you have set to avoid High Traffic Roads? Maybe that can explain the Edge is planning detours on High Traffic Roads and has nothing to do with the "oneway - but not for bicycles" property of streets? What happens if you set NOT to avoid High Traffic Roads?

  • What is your experience? Can I expect Garmin to resolve this anytime soon?
    With this issue navigation is useless in at least in Vienna/Austria.

  • You are pointing to Garmin to solve 'your' problem, but are you sure it really is a problem? As @MaxR6 also pointed out, it should be possible - and it normally is - to plan routes for bicycle along a oneway street where bikes are allowed to ride against the oneway.
    Did you experiment with the suggestion I gave you? If you get detours on High Traffic Roads, do you still get these detours if you set to avoid High Traffic Roads?
    Can you give a pointer to the exact situation where you meet your problem - city, streetname, etc., preferrably with a link to openstreetmap.org? Which map do you use - is it the Garmin Cycle Map EU or other?

  • I don't think that it is just my problem. Neither the route creation nor the navigation works correctly for bike exceptions on one way streets in Vienna. I could not find a single correct case in Vienna. To name one example: Blumauergasse, which has an exception on the full length. The map is cycle EU 2021.20. 

  • On OpenStreetMap I have checked the Blumauergasse for possible tagging errors. No issues - it is a oneway street with cycling allowed in both directions.
    As a test I have planned some routes along the Blumauergasse in Vienna in both directions:
    1. Using the online planner http://brouter.de/brouter-web/#map=18/48.21858/16.38401/standard It uses OpenStreetMap (OSM) as map layer. Result: no issues with cycling against the main oneway direction. If you wish, you can download the planned route as a .gpx file that has to be transferred to the Edge Explore 2 (EE2) in the folder ..\Garmin\Newfiles.
    2. Using the OpenFietsMap (Alps) being installed on my PC with the Garmin program Mapsource (the program Basecamp will do too). Result: no issues with cycling against the main oneway direction. If you wish, you can download the planned route as a .gpx file that has to be transferred to the Edge Explore 2 (EE2) in the folder ..\Garmin\Newfiles.
    You can download the OpenFietsmap (Alps) from https://www.openfietsmap.nl/downloads/alps, but you have to install the map on the PC, followed by installing your area of interest from within Basecamp or Mapsource on the EE2. An easier approach is downloading the GPS version of the OpenFietsMap Europe. There is a separate download for the EU-Central area that you can copy directly to the folder ..\Garmin on the EE2 - rename the file gmapsupp.img to something like OFM-Alps-Central.img to prevent unwanted overwrites in the future.
    3. Using the Garmin Cycle Map EU 2021.20 with Basecamp. Result: routing for bicycle against the main oneway direction is refused. The exeption for bicycles is ignored and this is clearly a Garmin map error and should be reported to Garmin as soon as possible. The Garmin Cycle Map is generated from OSM data too.

    I have not tested on-device routes using the OFM_EU-Central.
    My suggestion is to install the OpenFietsMap EU-Central on your EE2 and start experimenting planning routes on the EE2 over the Blumauergasse in both directions. Don't forget to disable ALL Garmin maps on the EE2, except the worldwide Basemap. I would be very surprised if your issue still exists!