[Patch v1] allow --route with highest resolution < 24

Hi, the attached small patch allows to create a routable map with level 0 not being at resolution 24. I did not test routing very much, but at least MapSource doesn't crash. A compiled binary based on r2478 is here: http://files.mkgmap.org.uk/download/158/mkgmap.jar Gerd

Hi Gerd, I have compiled a map with your mkgmap version and routing seems to work correctly in Mapsource. I got initial crash in BaseCamp, but this could be due to its cache. Subsequent run was correct. In BaseCamp there is a problem similar to the one, I have described in NET tread. When I mark a waypoint on higher layer, it appears in different position than curosr, see screen shoot. -- Best regards, Andrzej

Hi Andrzej, please try with --no-merge-lines. Does that change something? Gerd popej wrote
Hi Gerd,
I have compiled a map with your mkgmap version and routing seems to work correctly in Mapsource. I got initial crash in BaseCamp, but this could be due to its cache. Subsequent run was correct.
In BaseCamp there is a problem similar to the one, I have described in NET tread. When I mark a waypoint on higher layer, it appears in different position than curosr, see screen shoot.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
crnet2.png (7K) <http://gis.19327.n5.nabble.com/attachment/5781260/0/crnet2.png>
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-allow-route-with-highest-resolution-... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Andrzej, okay, so that seems to prove that it was not a good idea to merge roads in this way as it produces somehow invalid NET data. Just to make sure: You did not use the reduce_net_v1.patch ? Gerd popej wrote
Hi Gerd,
please try with --no-merge-lines. Does that change something?
With this option map works correctly, I can't spot problems with position marked away of cursor.
-- Best regards, Andrzej _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-allow-route-with-highest-resolution-... Sent from the Mkgmap Development mailing list archive at Nabble.com.

Hi Gerd,
Just to make sure: You did not use the reduce_net_v1.patch ?
Good question. Actually I have made a mistake and used standard 2748 release for second test. Now I have repeated with your binary and --no-merge-lines. This works correctly, there is routing and good position of waypoints. To get all variations I compiled map with standard release and without --no-merge-lines. This version got 2 problems: routing crashes and waypoints are set off cursor, both problems visible in Mapsource. Unexpected outcome from my mistake is information that --no-merge-lines influences routing for level 0:23. -- Best regards, Andrzej
participants (3)
-
Andrzej Popowski
-
Gerd Petermann
-
GerdP