[Loadstone] Thinking aloud about creating checkpoints automatically

Rob Melchers rob at loadstone-gps.com
Thu Oct 30 08:20:27 GMT 2008

No, the phone could handle it. It's a tedious process though. The problem 
is that algorithms for route planning are not always the best solutions for 
pedestrian use. Added to that is that the blind not always take the 
shortest route but the best navigatable one.


At 10/30/2008, you wrote:
>Hi Rob,
><snip It would be a bit hard to operate on the phone.
>PL] Is it because of the phone's limmited processing power?
>And, apologies for sending multiple copies of this message. I am using
>gmail's web interface and the browser got stuck.
>On 10/30/08, Rob Melchers <rob at loadstone-gps.com> wrote:
> > This is a description of the existing Routeplanner on the tools page of the
> > LS website. It would be a bit hard to operate on the phone. We are thinking
> > about a route mode based on intersections, but that's an ongoing process.
> >
> > Rob
> >
> > At 10/30/2008, you wrote:
> >>Hi all,
> >>
> >>Given that data on roads, streats etc., is hard to come by for many
> >>places, I have been trying to find a way of using existing loadstone
> >>features to implement some form of routing. Here is what I have come
> >>up with.
> >>
> >>1. The user sets a start and an end location. The start location can
> >>also be taken from the current gps position.
> >>
> >>2. Then, a list of all checkpoints between the starting and
> >>destination location is created. By between I mean a list of points
> >>from the destination to the starting location. Of course, it would be
> >>almost impossible to tell directions and since we do not have data on
> >>roads etc., we would need to create the checkpoints in a radius of the
> >>destination. The value of this radius would be the distance of the
> >>starting location to the end location.
> >>
> >>3. Great, now we have a checkpoint list. If there are a lot of points,
> >>the checkpoint list can become very large and slow down the program.
> >>the user could delete them manually or, we could use a feature that
> >>would track the route the user would travel. See the next point for
> >>details.
> >>
> >>4. Once the checkpint list has been created, a trip meter like feature
> >>could be implemented which would track what points were crossed from
> >>the starting location to the end location. If a point was not in the
> >>checkpoints list, that point would be added. This is required to take
> >>the shape of cities into account.
> >>
> >>5. Once the user has reached the destination, all the other
> >>checkpoints could be erased.
> >>
> >>6. Now, further manual adjustments like adding turning instructions
> >>etc., could be added.
> >>
> >>Anyone any thoughts?
> >>Pranav
> >>_______________________________________________
> >>Loadstone mailing list
> >>Loadstone at loadstone-gps.com
> >>http://www.loadstone-gps.com/mailman/listinfo/loadstone
> >
>Loadstone mailing list
>Loadstone at loadstone-gps.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.loadstone-gps.com/pipermail/loadstone/attachments/20081030/7464bfec/attachment-0001.htm 

More information about the Loadstone mailing list