Hi Robert, Here are my though. I removed your secions I completly agree with in order to keep section where I have comments.
2010/8/13 Robert Norris <rw_nor...@hotmail.com>: > > As I mentioned in another post, being able to export to file / directly > upload a *route* into the GPS. > I may address this myself.... I remember an old discussion of myself about the missing of "route" type in viking. One solution would be to add a flag to "track" in order to decide if it is a track or a route. > ATM these services only go via roads. Most of my trips are walking, mountain > biking and road cycling (using quiet roads). > If the service supports it (Google has 'walking' but it just avoids main > roads) I would want to be control the type of route. On/off road / road types > / path / footpath / cycleways / etc. IMHO there is two way to address this aspect: - we try to imagine all possible/interesting options and we offer the way for "routing plugins" to activate these options - we offer a way for "routing plugins" to declare options to expose to user. I have the feeling that second option is better, because existing routing Web services expose really different options. For example, some of them propose "fastest" or "shortest" for car routes. Other propose "cool" or "sportive" cycleways. Other one propose "wheelchair" or not option for walking route. And future routing web service will offer certainly other options. So, I think the options for controling the route should be provided by each "routing plugin". > Anyway most of my routes are circular, generally going back to my car / or > train station after getting out into the countryside. > > One could try to auto-generate a circular route to give a route of desired > length - For a particular start point / somewhere in this area ; I want to go > for about a 5 mile walk or a 35 bike ride etc... ; I want to go via these > specified places/points (i.e points of interest - a viewpoint, a pub, a shop, > whatever) > > OK it's a bit clever but the sorts of things OSM could be able to answer, as > that's how I plan a day trip. > > Multi day trips are different, as these may not return to the beginning, > having a destination in mind - but often following a larger 'real' route, > such as walking Hadrian's Wall. > > Obviously, getting directions for car journeys is another use case. Wow!!! These features are really "evolved", I think. As first evolved features, I suggest an option with following alternatives: - one way trip: the route goes through all waypoints - one way + reverse: the route goes through all waypoints and then return via all waypoints in reverse order - one way + return: the route goes through all waypoints and return to the starting point, directly. I think all these features can be implemented with any sort of routing web service, as viking can compute the request in the right way. > It would be interesting to find out what people use Viking for. There is many different way to use viking. Some use it for hiking, others for 4x4, others for sailing, others as OSM frontend. > I think Viking needs to address things that JOSM, merkaator, tangoGPS and > others aren't - for me this means primarily the multi track storing aspect. > Hence I can plan to places where I haven't been before. Agreed. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
