- mkgmap-dev - The mkgmap lists

Firmware V4.00 on new Marine Devices
by RheinSkipper 20 Feb '15

20 Feb '15

Dear list Garmin recently released a major firmware update (v 4.0) for the Echomap and newest GPSmap marine series. http://newsroom.garmin.com/press-release/marine/garmin-gpsmap-and-echomap-pr oduct-lines-receive-new-features After the firmware update my current charts fail with a map format not supported error on those devices. However one of my old charts which was produced with mkgmap-r3316 in mid-2014 still works. I want to track down the problem. Can someone point me to a download-link for mkgmap-r3316 (both binaries and default style from this release) so I can try to reconstruct a map that does not produce the error? Regards Jürgen

6 19

r3468 in housenumber2 branch
by Gerd Petermann 19 Feb '15

19 Feb '15

Hi all, with r3468 I fixed the errors reported for r3466. Please try that release again. Gerd

3 2

housenumber2 branch
by Gerd Petermann 19 Feb '15

19 Feb '15

Hi all, I think r3466 is now stable enough for a first public test. It is fully compatible with trunk r3449. Improvements compared to trunk: 1) Number nodes are now supported. A number node is a special node, house number intervals start and end with a number node. In trunk, only route nodes (road junctions and end points) are used for this, in the branch we can add many more number nodes. The advantage is that we can create more (and smaller) intervals when needed. 2) The number nodes are used to support "random" house numbers (numbers with no particular order). The program simulates an address search for any of the house numbers found in OSM data. If a number is found in multiple places, the corresponding intervals are split so that wrong overlaps are removed. This should lead to good results for correct OSM data and better results for wrong data like duplicate numbers with large distances and other typical copy+paste errors. 3) An additional step is performed to improve the results of the address search. As a result, an address search should point you to a point on the road that is not more than 40m away from the closest point. The trunk version doesn't care about this and results maybe > 200m away. Performance: The img size increases by a a few KB, compile time is a bit higher, routing should work as with trunk. Use logging property uk.me.parabola.mkgmap.osmstyle.housenumber.level=INFO to get details. Todo: Support for addr:place , code review and unit tests Any feedback is welcome. Gerd

5 10

Road reference hbox not rendered 3449
by Ervin Malicdem 19 Feb '15

19 Feb '15

Hello! Road ref hbox are not rendered in 3449. It instead goes before the name of the road. No script changes. Compared between 3442 and 3449 Ervin M. *Schadow1 Expeditions* - A Filipino must not be a stranger to his own motherland. http://www.s1expeditions.com

1 0

Error on address
by Stéphane MARTIN 18 Feb '15

18 Feb '15

Hi all, With mkgmap-housenumbers2-r3459 and BANO (https://github.com/PacoTyson/bano2garmin/) I got this in the STOUT : java.lang.AssertionError: internal error id=67924872, Rue Étienne Clementel (n1),E,24,22,N,0,0 [24(0), 22(1)] [] at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.verify(ExtNumbers.java:341) at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.getNumbers(ExtNumbers.java:99) at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.dupNode(ExtNumbers.java:593) at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.tryAddNumberNode(ExtNumbers.java:470) at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.checkChainPlausibility(ExtNumbers.java:850) at uk.me.parabola.mkgmap.osmstyle.housenumber.ExtNumbers.checkChainPlausibility(ExtNumbers.java:855) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberRoad.checkIntervals(HousenumberRoad.java:152) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.buildNumberIntervals(HousenumberGenerator.java:833) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.assignHouseNumbersToRoads(HousenumberGenerator.java:654) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.matchCluster(HousenumberGenerator.java:539) at uk.me.parabola.mkgmap.osmstyle.housenumber.HousenumberGenerator.generate(HousenumberGenerator.java:486) at uk.me.parabola.mkgmap.osmstyle.StyledConverter.end(StyledConverter.java:595) at uk.me.parabola.mkgmap.reader.osm.ElementSaver.convert(ElementSaver.java:250) at uk.me.parabola.mkgmap.reader.osm.bin.OsmBinMapDataSource.load(OsmBinMapDataSource.java:67) at uk.me.parabola.mkgmap.reader.osm.OsmMapDataSource.load(OsmMapDataSource.java:130) at uk.me.parabola.mkgmap.main.MapMaker.loadFromFile(MapMaker.java:167) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:63) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:253) at uk.me.parabola.mkgmap.main.Main$1.call(Main.java:249) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) And in the logfile : 2015/02/17 09:41:08 GRAVE (ExtNumbers): 20630009.osm.pbf: internal error, house too far from forced segment in road id=67924872, Rue Étienne Clementel 24(0) http://www.openstreetmap.org/node/-19806613 mkgmap options : --max-jobs --latin1 --area-name=$COUNTRY \ --bounds=../bounds.zip \ --route \ --index --tdbfile --housenumbers \ --x-split-name-index \ --location-autofill=is_in,nearest \ --name-tag-list=name:fr,int_name,name \ --adjust-turn-headings \ --process-destination --process-exits \ --x-add-indirect-links \ --verbose \ --style-file="$WORKDIR/styles/$STYLE/" \ --list-styles --check-styles \ --family-name="$COUNTRY OSM $STYLE" \ --series-name="$COUNTRY-OSM-$STYLE" \ --mapname=$MAPNAME \ --overview-mapnumber=$MAPNAME \ --reduce-point-density=4 --reduce-point-density-polygon=8 \ --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12:2, 11:0" \ --preserve-element-order \ --add-pois-to-lines \ --add-pois-to-areas \ --report-similar-arcs \ --link-pois-to-ways \ --min-size-polygon \ --drive-on=detect --check-roundabouts --check-roundabout-flares \ --make-opposite-cycleways \ --country-name="$COUNTRY" --country-abbr="$ABBR" \ --precomp-sea="$WORKDIR/sea.zip" --generate-sea=multipolygon \ -c "mkgmap-$STYLE-$COUNTRY.cfg" \ --description="$COUNTRY OSM $STYLE" $ID*.pbf \ "$WORKDIR/styles/$STYLE/$STYLE.TYP" 2>&1 | tee "$COUNTRY.log" http://files.mkgmap.org.uk/download/252/20630009.osm.pbf Steph

3 10

Combine ovm files?
by Ralf Kleineisel 18 Feb '15

18 Feb '15

Hi, is there a way to combine several overview map work files (ovm_*.img) into a new overview map? I have a set of about 200 compiled map tiles and the corresponding ovm files. I can combine subsets of these map tiles into new gmapsupp files, but how do I make the new overview maps? Best regards Ralf

2 3

Error creating image
by demon.box 17 Feb '15

17 Feb '15

Hi, recently during the mkgmap image creation often I have this error, always the same: (...) exception_access_violation (0xc0000005) at pc=0xffffffffa3805120, pid=3164, problematic frame C 0xffffffffa3755120 (...) java version 1.8.0_31 mkgmap 3447 but the strange thing is that after the error if I restart it (without any changhes) the creation of the image ends correctly! I mean, for example: start1 = ERROR start2 = ERROR start3 = OK without any changes..!!! This is my mkgmap command: *start /low /b /wait java -enableassertions -Xmx3000m -jar ..\bin\mkgmap.jar --country-name="%country%" --family-id=%FID% --mapname=66%FID%001 --overview-mapname=66%FID%000 --series-name="OSM_%date%" --family-name="OSM_%date%" --style-file=..\bin\styles\ --style=%style% --name-tag-list=name:it,name --description="%country%" --route -c ..\bin\template_basic.args -c template.args %TypFileToAdd%* Have you any idea, what is wrong? Thanks. --enrico -- View this message in context: http://gis.19327.n5.nabble.com/Error-creating-image-tp5833599.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 2

mixed index branch merge
by Steve Ratcliffe 17 Feb '15

17 Feb '15

Hi So finally I will merge the mixed index branch. I have added a temporary option that will be required to enable it - it will be off by default as there may still be a problem with the gmapsupp version. I think it would be best to selectively enable it per country along with lists of names to avoid. This would be best done by people from or familiar with the countries in question. I'll write another message when it is done. ..Steve

9 20

help needed for graphical problem
by Gerd Petermann 12 Feb '15

12 Feb '15

Hi all, for improvements in the housenumber2 branch I have to split a road segment into two parts. Given: the two (Garmin) points p1 and p2 that build the road segment and a distance d with d < p1.distance(p2). The normal way to calculate the wanted point is to use the Coord.makeBetweenPoint() method. The problem: the simple algo in makeBetweenPoint() calculates the point without looking at the rounding for the Garmin raster, so for line segments with a small slope the calculated point might be too far away from the displayed line. The effect is that the splitted line has a rather large angle while the originial line looks - of course - perfectly straight. I am sure this problem was already solved, but up to now I did not find an algo that works without a loop to calculate a set of points and chose the best one, e.g. using the Bresenham algo. Any hints? Gerd

3 8

Commit: r3449: Merge the mixed-index branch.
by svn commit 12 Feb '15

12 Feb '15

Version mkgmap-r3449 was committed by steve on Thu, 12 Feb 2015 Merge the mixed-index branch. Each word of a street name is added to the global index. To enable the functionality you need to use the --x-split-name-index flag, since there is no logic to prevent useless parts of the name (such as 'street', 'rue', 'calle' etc) being included. In the future rules will be added so that it works by default according to the country.

1 0