[mkgmap-dev] [PATCH v2] Fix Nuvi routing regression (rebloat Table A)
From Mark Burton markb at ordern.com on Thu Nov 26 10:49:18 GMT 2009
Hi Marko, Thanks for the report. > My Edge 705 calculates a 22.7 km route to Pasila railway station > just fine, except that it now seems to favor smaller roads with more > intersections. What do you think, would it be worthwhile to have > some middle ground for Table A? Not one entry per arc nor one entry > per way, but an entry per a configureable number or distance of arcs, > perhaps? Not sure about that but I do think that this warrants some more work to try and understand exactly what the constraint is. It's interesting that it doesn't appear to have any effect on mapsource (or the etrex, as far as I can tell). I don't favour making it configurable because then the map makers would need to say what units their maps are compatible with. Far simpler to take the hit on map size (and possibly routing performance) until we know what's really happening. > > I will ask the Nüvi user to try out the same map. Thanks, I reckon it will be OK for them now. Cheers, Mark
- Previous message: [mkgmap-dev] [PATCH v2] Fix Nuvi routing regression (rebloat Table A)
- Next message: [mkgmap-dev] [PATCH v2] Fix Nuvi routing regression (rebloat Table A)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list