IMHO, routing is complex and is out of scope of viking.
In the other hand, viking can provide a GUI for routing tools. Perhaps can we design an interface to plug routing tools (online web tools or offline command line process). For example, :
- viking helps the user to design the waypoints of itsroute (begining, end, and intermediate)
- viking activates the tool to compute the route
- viking retrieve and display the route
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes, routing is complex, and viking should not intend to do the routing itself. there exist several free projects which may be used as external tool.
I see two usecases:
1)
viking helps to design start, intermediate and final points for a 'longer' route, calls an external tool (may be online or local), reimports the resulting track (using gpx this should be easily possible -o r not?)
2) 'continuous' mode: when designing a route in viking (i.e. setting a new trackpoint at the end of a route), the routing interface could route from the resent to the new trackpoint (if user activated autorouting).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately there is no option to remove / blank out the now not relevant Milestone value. Instead I've created a new 'Never' Milestone.
I thought setting this to won't fix, would have closed the discussion - so I've now marked that manually as well.
Note that notionally off-line routing could be achieved by running OSRM locally on your machine. However Viking would need to be able to read the JSON output, now that the GPX output has been recently discontinued in December 2015. Also see discussion here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMHO, routing is complex and is out of scope of viking.
In the other hand, viking can provide a GUI for routing tools. Perhaps can we design an interface to plug routing tools (online web tools or offline command line process). For example, :
- viking helps the user to design the waypoints of itsroute (begining, end, and intermediate)
- viking activates the tool to compute the route
- viking retrieve and display the route
yes, routing is complex, and viking should not intend to do the routing itself. there exist several free projects which may be used as external tool.
I see two usecases:
1)
viking helps to design start, intermediate and final points for a 'longer' route, calls an external tool (may be online or local), reimports the resulting track (using gpx this should be easily possible -o r not?)
2) 'continuous' mode: when designing a route in viking (i.e. setting a new trackpoint at the end of a route), the routing interface could route from the resent to the new trackpoint (if user activated autorouting).
Improved Online Routing will be included in release v1.5.
Agreed: Offline routing is out of scope for Viking and hence closing this request as clearly no one is going to implement this any time soon.
should the milestone on this change if its not going to get done?
Unfortunately there is no option to remove / blank out the now not relevant Milestone value. Instead I've created a new 'Never' Milestone.
I thought setting this to won't fix, would have closed the discussion - so I've now marked that manually as well.
Note that notionally off-line routing could be achieved by running OSRM locally on your machine. However Viking would need to be able to read the JSON output, now that the GPX output has been recently discontinued in December 2015. Also see discussion here.