[Loadstone] Why loadstone doesn't consider ways?

Shawn Kirkpatrick shawn at loadstone-gps.com
Wed Sep 22 05:43:30 BST 2010

What you're describing is not the results of how loadstone is receiving the 
gps signals but is the result of the order of waypoints not being important 
in a route. Loadstone just calculates what checkpoint you're currently 
heading towards regardless if that's the next in the route or not. We plan 
to put in ordered checkpoints in a future release.
Streets aren't stored for a couple reasons. The first is the limited 
database engine on the phone. This is really limiting what we can do at the 
moment. Also, street data isn't always available for a given area. It's also 
possible that you're not in an area with streets so in that case having 
street line data wouldn't help and would limit the system if it were 
confined to only streets.
At some point we hope to replace the database engine with something better 
and hopefully make some kind of use of street line segments if available.
Even with the current limitations loadstone is still quite capable of 
letting you follow a route if it's planned propperly. If your route does a 
lot of doubling back on itself then you may have to be a bit selective about 
what points are checked along it. It's also not a good idea to have points 
too close together or you're probably going to get false announcements.
Sometimes in a city you'll notice the heading will tend to spin at walking 
speeds, especially with the new more sensative receivers. This will also 
have an effect on what checkpoint loadstone thinks you're heading towards. 
The best fix for this problem is to move faster or maybe turn on software 
speed or heading and see if that helps.

On Tue, 21 Sep 2010, Peter Wendorff wrote:

> Hi.
> To avoid conflicting interpretations, let me state: loadstone is a great 
> tool!
> Nevertheless my current tests for routes in dense areas in the city with much 
> ways and at places, where a route can turn around and go parallel to another 
> part of the same route for longer distances.
> If that's the case and the route file does not contain intermediate points, 
> loadstone fails at navigating along the route.
> Navit, a free (car+) navigation software and most commercial software(?) 
> takes more effort on tracking the gps signals, interpreting it more 
> sophisticated. It interpolates small differences, stores the last direction 
> interpreted as secure due to measured speed and so on.
> Neccessary to do that is to store the ways itself in the map data, no point 
> cloudes like loadstone uses.
> I would like to know why loadstone goes the simple dotted way instead of the 
> lined one.
> Is it the limited ressources availlable at most mobile phones?
> Is it, because nobody thought about it when loadstone development started?
> Is it, because nobody imagined complete map data like openstreetmap to be 
> availlable?
> I ask this question because I wonder, why there are more free navigation 
> systems going the same way as loadstone.
> I interpret the results of my test, that the other way around could provide 
> more precision to navigation tasks without the need of highly sophisticated 
> hardware like DGPS or other additional stuff.
> regards
> Peter
> _______________________________________________
> Loadstone mailing list
> Loadstone at loadstone-gps.com
> http://www.loadstone-gps.com/mailman/listinfo/loadstone

More information about the Loadstone mailing list