Changes between Initial Version and Version 1 of Ticket #1000, comment 5


Ignore:
Timestamp:
07/20/12 12:08:59 (8 years ago)
Author:
mvglasow (2)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1000, comment 5

    initial v1  
    33 * If I remember that correctly, recalculating will be faster than the initial route calculation because only a short piece - from your current location to your destination - needs to be recalculated.
    44 * The case described above is primarily caused by an inaccurate position. Improving resilience would provide some relief here. One way would be to extend "snap to roads" to give preference to the road that the vehicle was last seen on - because cars seldom jump the guard-rail. As a further refinement, we can also give a higher preference to roads that are on the route - from behavior I have seen on some commercial sat-navs, I believe they work this way.
    5  * When off the route, displaying turn instructions is not really trivial. What might work: keep displaying the original route as a line on the map. (We can recalculate in the background and in cases like the one you describe, stop recalculation as soon as the vehicle hits the original route again.) We could then display the turn instruction for the neatest turn on the route.
     5 * When off the route, displaying turn instructions is not really trivial. What might work: keep displaying the original route as a line on the map. (We can recalculate in the background and in cases like the one you describe, stop recalculation as soon as the vehicle hits the original route again.) We could then display the turn instruction for the nearest turn on the route.