[Loadstone] Routeplanner/Breadcrumb generator

Ari Moisio arimo at iki.fi
Wed May 21 10:24:25 BST 2008


  About the terminology. There are at least three different  methods to 
create a route, an ordered list of locations:

- Breadcrumbs: these are locations stored automatically by certain period 
of time or by some distance from each other. They are most suitable if 
someone gets lost or for very complex routes. Because some users will not 
know in advance it they will get lost this mode should be started 
automatically if user wishes so. In this case it would be better to use 
distance-based storing of locations.

  Suitable time, distance and minimun time between storing the location 
could be user adjustable.

- Manual routes: these are like breadcrumbs but user enters desired route 
points manually by walking the route instead of automatic storing.

  There could also be some automation to store a point with certain 
distance from previous point, if the heading changes or user stops for a 
longer period of time.

- Route planning: in this mode route points are added when exploring the 
surroundings. In this mode there should be an easy command to remove route 
points at the end of the planned route.

You can still escape from the Gates of hell: Use Linux!
mr. M01510

On Wed, 21 May 2008, Sandberg, Robert wrote:

> Hi folks!
> You guys decide what comes first of course, but in my own opinion a
> route saving functionality is more important than the internal GPS
> support. How many people actually have a phone with built in GPS or will
> get one soon? Whereas the route feature would benefit everyone
> immediately.
> As for terminology, I think there are 2 major differences here. On one
> hand we have route saving, where track recording  and bread crumb
> generating are the methods, and on the other hand we have route
> planning, which means using POI's that are already there, to determine
> how to get from A to B.
> In my mind, track recording and bread crumb generation boil down to the
> same thing. You go from A to B and record way points, bread crumbs, what
> ever you want to call them. I think 2 factors should decide when such an
> automatic entry is made. Distance and change of direction. Say you
> dropped a bread crumb every 100 meters. If distance were the only
> criteria, a 90 degrees turn at 50 meters would not be recorded. This
> would basically produce the hair pin effect. So you need change of
> direction in there as well. I'm not in favour of time, because you'd
> have to involve speed then as well.
> Technically these way points or bread crumbs are POI's I suppose, but
> you wouldn't want them to show in your POI database. Why not just flag
> them as bread crumbs, the way you do with check points? You could save
> them to the same database and reload saved routes at will, just like
> loading a check point file.
> Cheers,
> Robbie Sandberg
> -----Original Message-----
> From: loadstone-bounces at loadstone-gps.com
> [mailto:loadstone-bounces at loadstone-gps.com] On Behalf Of Shawn
> Kirkpatrick
> Sent: Wednesday, May 21, 2008 2:43 AM
> To: loadstone at loadstone-gps.com
> Subject: Re: [Loadstone] Routeplanner/Breadcrumb generator
> There's a lot of information here and a few similar but slightly
> different
> ideas getting intertwined. The dev team will have to figure out how
> exactly
> this stuff is going to work rather than trying to hack things in to get
> things kind of working.
> At the moment none of this is on my current todo list, I have access to
> an
> n82 for a very short time so I'm working on getting the internal gps
> support
> working while I have access to it. There's also the menu problem to get
> fixed. Once those are done then I can turn to some of this track/route
> stuff.
> One thing that would be helpful with all this would be to get our
> terminology consistant. At the moment we have references to track
> recording,
> bredcrumb generating, route planning, and various variations on these
> terms.
> We need to get some solid concepts and what exactly we want to call
> them,
> that'll make it much easier to figure out how they need to be
> implemented.
> On Wed, 21 May 2008, Rob Melchers wrote:
>> Hi all,
>> So far we have the following points:
>> - the option to overlay more databases to keep seperate recorded
> points and
>> generated tracks, but have them available at the same time.
>> Shawn will have to tell if this is possible at all.
>> - generate checkpoints files for a generated track (start to finish
> and vv)
>> including heading comments, so a user can use a generated track
> immediately.
>> This part of the routeplanner logic needs to be on the phone, it
> should be
>> possible.
>> - maybe use distances in stead of time to record tracks, so when a
> user stops
>> you don't get a whole lot of recorded points at the same place.
>> Timing is more accurate, the nmea data comes in per second. Distance
>> measurement has shown to be not accurate in all receivers. Maybe a
>> combination as in approach time is possible.
>> -  have an easy saving method so a user can combine existing points
> databases
>> and generated tracks for later use.
>> This should be the least of our problems.
>> Shawn, thoughts please.
>> Rob
> _______________________________________________
> Loadstone mailing list
> Loadstone at loadstone-gps.com
> http://www.loadstone-gps.com/mailman/listinfo/loadstone
> _______________________________________________
> Loadstone mailing list
> Loadstone at loadstone-gps.com
> http://www.loadstone-gps.com/mailman/listinfo/loadstone

More information about the Loadstone mailing list