On 08.01.2013 10:45, GerdP wrote:
toc-rox wrote
I have tested the norway map in both of my devices (Montana, Dakota) and couldn't find any problem.
Regards Klaus Thanks for testing. The problem is that - afaik - we did never exactly find out what the reason for the crash was, we just know that it is likely to occur in almost empty areas. So, the absence of a crash with your data doesn't mean the problem is solved :-( It may also be related to gps firmware.
@Felix: Are you able to reproduce the problem reported in this thread? http://gis.19327.n5.nabble.com/Serious-Bug-Mkgmap-creating-map-that-puts-new... with new splitter, no problems with the bay of biscay anymore. But I don't really understand what that bug has to do with "not enough room in osm file" problem - which is a problem about too few interaction between mkgmap and splitter.... (integrated fallback by mkgmap calling splitter and splitting the file into two parts would be best IMHO).
Please try also the removeShortArcs_v2.patch. This reduces the amount of data needed to store the coast line information in the *.img file by ~ 25%, so it reduces the likelyhood for the "There is not enough room in a single garmin map for all the input data" message. I hope that WanMils work on the new mp_cut branch will provide a much better solution for this.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Norway-not-buildable-with-the-no-trim-option-... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org