[Loadstone] Distance Calculation
charlieofalbany at hotmail.com
Fri Feb 16 22:46:46 GMT 2007
I guess it's also what you're looking for in GPS software. I think this is
why most cost so much. I saw a Magellan on QVC the other day and you can
ask it how many casinos are within 200 miles of your current location.
After you pick one it can tell you how to get there, how long it might take,
alternate routes if there's a need to detour. The phone number and address
of the location. And my head spins from all the information and what it can
I've been looking for the simple solution for my GPS needs and Loadstone has
it as of now. I need to know where I am at certain times. I know how to
----- Original Message -----
From: "Shawn Kirkpatrick" <shawn at odyssey.cm.nu>
To: "General discussion pertaining to the Loadstone GPS program"
<loadstone at loadstone-gps.com>
Sent: Friday, February 16, 2007 6:42 AM
Subject: Re: [Loadstone] Distance Calculation
> Well, that would be kind of nice but not very practical at the moment. For
> one thing, we really don't have that much detail about the streets. The
> important thing would be we just don't have that kind of computing power
> the phone. By the time the phone finished calculating the distance you'd
> probably already be there.
> On Fri, 16 Feb 2007, Hasan Karahasan wrote:
>> currently the distance between points is obviously calculated by
>> differences as linear distance. That's very important and should remain
>> it is. But it would be great to see also the approximate distance a
>> pedestrian has to go or a car has to drive for a certain route.
>> Of course this needs many points to be accurate. Think we have every
>> coordinates of the streets in a certain area, than we could calculate the
>> distance as the sum of distances between a given start point and its
>> neighbour towards the end point. Running this algorithm until we reach
>> end point should give quite realistic values for the distance. The more
>> points along a street we have, the more accurate the result will be.
>> crossings and curves would produce some source of defect unless we have
>> coordinates of the crossing itself. But I think we can neglect this
>> malfunction for the first.
>> How about implementing that?
>> Loadstone mailing list
>> Loadstone at loadstone-gps.com
> Loadstone mailing list
> Loadstone at loadstone-gps.com
More information about the Loadstone