Hello,
The size of the Michigan map I generate from the CloudMade extract went down
from 63M to 59M.
On my Etrex Vista HCx,
1) Detroit area->Munising, MI: the computation time is roughly the same (27
sec average old map, 28 sec average new map) and the resulting route is
exactly the same.
2)
Mark,
As far as I can see, it works well. I haven't tested it very thoroughly,
but I don't find immediate oddities.
There's still the various routing oddities. Mapsource sometimes doesn't
find a route; my Nuvi sometimes finds weird routes (and sometimes does
it right).
Anyway, your patch makes t
Hi Felix,
> I just played around a bit in Mapsource, and couldn't notice ANY
> difference. If routing does not work somewhere without this patch, it
> will not work either with the patch. If it works without patch, it does
> so with patch too. (I installed the otherwise exact same map twice in
Mark Burton wrote:
Hi Marko,
I successfully tested it on Finland with Edge 705 firmware 2.90. The map
is slightly smaller (36 megabytes instead of 37) and routing (car and bicycle,
200 to 250 km distance) still works. It still makes a stupid detour for
the bicycle route, but I would blam
Bennie,
Du Plessis, Bennie schreef:
[...]
> Making Southern Africa in one tile I can route maximum approx 1400km.(870m)
>I can approve slightly by increasing --remove_short_arcs=50, but that
>distorts the map :(
... because you essentially remove every detail that's less than 50
meters
Reduce number of Table A entries.
Previously, Table A entries were unique for each combination of
start node,
end node and RoadDef. But no information from the start and end
nodes goes
into Table A so we can ignore the start and end nodes and all roads
within a given routi
Hi Marko,
> I successfully tested it on Finland with Edge 705 firmware 2.90. The map
> is slightly smaller (36 megabytes instead of 37) and routing (car and bicycle,
> 200 to 250 km distance) still works. It still makes a stupid detour for
> the bicycle route, but I would blame that on the Garm
Hi Mark,
On Tue, Sep 22, 2009 at 12:49:17AM +0100, Mark Burton wrote:
>
> Reduce number of Table A entries.
>
> Previously, Table A entries were unique for each combination of start
> node,
> end node and RoadDef. But no information from the start and end nodes goes
> into Table
Reduce number of Table A entries.
Previously, Table A entries were unique for each combination of start node,
end node and RoadDef. But no information from the start and end nodes goes
into Table A so we can ignore the start and end nodes and all roads
within a given routing c
