
Mark Burton escribió:
Patch version 5 (based on r974) - exits are now findable!
After many hours of experimentation, the exits are now findable.
One oddity, on my etrex, when I find exits it always shows me exits defined on the base map in preference to the OSM map. If I then use the menu option to change map to the OSM map, it shows the exits on the OSM map. There's some priority mechanism in force there that doesn't seem to apply when searching for non-exits. In my example map, I only have two exits defined for the M53 but the basemap has a lot more, could it be that it's using the basemap because it has more exits defined for that road? Testers, please see if it will use the OSM map in preference to the base map by default. After a lot of warnings regarding problems with exits, I get error below: GRAVE (MapBuilder): Can't create exit 5 5 (OSM id 357448458) on unknown highway M-40 Exception in thread "main" java.lang.AssertionError: Too many POIS in division at uk.me.parabola.imgfmt.app.lbl.PlacesFile.createPOIIndex(PlacesFile.java:285) at uk.me.parabola.imgfmt.app.lbl.LBLFile.createPOIIndex(LBLFile.java:149) at uk.me.parabola.mkgmap.build.MapBuilder.processPoints(MapBuilder.java:701) at uk.me.parabola.mkgmap.build.MapBuilder.makeSubdivision(MapBuilder.java:579) at uk.me.parabola.mkgmap.build.MapBuilder.makeMapAreas(MapBuilder.java:515) at uk.me.parabola.mkgmap.build.MapBuilder.makeMap(MapBuilder.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:90) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:56) at uk.me.parabola.mkgmap.main.Main.processFilename(Main.java:150) at uk.me.parabola.mkgmap.CommandArgs$Filename.processArg(CommandArgs.java:329) at uk.me.parabola.mkgmap.CommandArgs.readArgs(CommandArgs.java:119) at uk.me.parabola.mkgmap.main.Main.main(Main.java:91) Is there any chance to get the map generated? Regards Carlos