Re: [mkgmap-dev] max-speed and arbitrary values
On Thu, 4 Jun 2009, Carlos Dávila wrote: Marco Certelli escribió: I think I can confirm what said here. My nuvi 255 seems to learn the speed I drive on each road (with impact on routing decision next time I drive the same area). I think nuvi 300 doesn't have this behaviour. I have driven many times my road to work and it continues calculating about twice the time it really takes me from home to work (about 50 km trip). Using city navigator for the same route, time calculation is correct. That is really strange. What's your firmware version? -Wolfgang ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Re: [mkgmap-dev] [PATCH v1] quick distance calculation
On Tue, 19 May 2009, Mark Burton wrote: Well, that's a good question. As distance() mostly gets called to determine which of a bunch of points is nearest, it probably doesn't matter at all that the result is slightly wrong. Really? In that case you could as well change the metric from Euclidean to something more simple like the Manhattan metric: dist = abs(lat2-lat1) + costab[lat1] * abs(lon2-lon1) where costab is a table lookup for cos(). This will still find a point that is close, but it is not guaranteed to be the same as with the Euclidean metric. Would that matter? -Wolfgang ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
