- mkgmap-dev - The mkgmap lists

[PATCH v1] Rename internal mkgmap tag from display_name to mkgmap:display_name
by WanMil 28 Dec '12

28 Dec '12

The style uses a tag display_name. This is an internal mkgmap tag and should therefore be name mkgmap:display_name. Attached patch changes this but still accepts the old display_name (issuing a warning). WanMil

1 0

Minor process-destination issue
by Chris66 28 Dec '12

28 Dec '12

Hi, Many destinations are entered with several cities, for example destination=Bonn;Rodenkirchen My Nüvi is displaying only the first entry: "Rechts abfahren nach A 555 (Bonn" The right ")" is missing also in this case. Bug or feature ? Some times ago there was a patch concerning the ";" handling, don't know if this patch was ever committed. The user should be able to decide via style file to display only the first entry or all entries. Do we have a style-function for this? item( ${destination}, 1 ) -> Bonn item( ${destination}, 2 ) -> Rodenkirchen Chris

4 7

splitter r273 with --precomp-sea parameter
by GerdP 28 Dec '12

28 Dec '12

Hi all, I've committed r273 in the problem-list branch. Besides some cosmetic changes I've implemented a first try to estimate the nodes that mkgmap adds because of the --precomp-sea parameter. If you specify the same parameter in splitter, it will read the precompiled sea files after reading the normal input files. The data is used like this: The density map that is created while reading the normal input covers a bounding box, splitter then reads all sea data that falls into this bounding box and counts the nodes in a 2nd density map. In a final step, it merges the two density maps so that only those areas with 0 nodes in the normal file are changed. Note that this happens before any kind of trimming occurs. The --precomp-sea parameter is ignored when --split-file is given. This should fix remaining problems reported eg. by toc-rox: http://gis.19327.n5.nabble.com/Norway-not-buildable-with-the-no-trim-option… Please let me know if it works as expected. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r273-with-precomp-sea-parameter-tp5… Sent from the Mkgmap Development mailing list archive at Nabble.com.

4 7

splitter-r269 - problems with osm-data and srtm-data
by Henning Scholland 27 Dec '12

27 Dec '12

Hi, I've got some problems with actual splitter and a combined input of osm and srtm-data. I merged them with osmconvert, so I think they are not mixed(--mixed gave the same result as without --mixed). I use splitter with an polygon-file of New Zealand [1] and max-nodes=1000000, which is no problem if I use only osm-data as input. Splitter generates thefollowing density-map [2] and then ends with the message: Failed to calculate areas. Sorry. Cannot split the file without creating huge, almost empty, tiles. Please specify a bounding polygon with --polygon-file parameter. Tiles should get smaller with srtm data, so my guess would bethat the tiles, which covers parts of the sea could be problematic.If you need further information, let me know. Henning [1] http://www.aighes.de/data/NewZealand.poly [2] http://www.aighes.de/data/densities-out.zip

3 6

nsis
by Henning Scholland 27 Dec '12

27 Dec '12

Hi, is there a possibility to change template of nsis without compiling mkgmap by myself? Henning

2 1

Address search issue: just a few cities available with r2423
by Enrico Liboni 27 Dec '12

27 Dec '12

Hi, today I upgraded mkgmap from r2307 to r2423 and downloaded fresh pbfs and bounds before regenerating my maps: the gmapsupp file is created correctly but address search does not work as expected. When searching for an address, if I select Italy and try to type a city only a dozen are available - typing "R" prompts me with just "Rovereto" (a minor city in the north) while Rome or anything else is not in. I reverted to r2307 and address search works fine, so this seems not related to the pbfs/bounds I downloaded. I've a Garmin Nuvi 510 and the command line I'using from Linux is: java -Xmx2000M -jar ./mkgmap/mkgmap.jar --family-name="OSM Ita and Alps" --description="OSM 2012-12-26" --route --remove-short-arcs --add-pois-to-areas --index --gmapsupp --output-dir="./data/" ./data/6*osm.pbf Any clue? Anything I can try to better debug the issue? One note: with r2423 when I set the address country, the country name appear as "Italia" while with r2307 I see "Italy", however I'm not setting language anywhere (and both my OS and garmin are in english). Thanks! gspeed

2 1

Commit: r2426: Remove option --createboundsfilename with separate boundary preprocessor.
by svn commit 26 Dec '12

26 Dec '12

Version 2426 was committed by wanmil on 2012-12-26 21:13:09 +0000 (Wed, 26 Dec 2012) Remove option --createboundsfilename with separate boundary preprocessor. The new boundary preprocessor can be started with java -cp mkgmap.jar uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreprocessor <inputfile> <boundsdirectory>

1 0

[PATCH] make tdbfile (fully) the default and remove --tdb-v3
by Steve Ratcliffe 26 Dec '12

26 Dec '12

Hi The tdbfile option is currently the default, except when there is only one input file. The attached patch removes that quirk and also removes the --tdb-v3 option. The version 3 is useless for routing and only ever existed because it took a long time to work out version 4. Also fix an obscure crash when you specify files that don't exist, that got exposed by the rest of the patch. ..Steve

2 3

Commit: r2425: Remove obsolete naming of streets by the attributes of the first point
by svn commit 26 Dec '12

26 Dec '12

Version 2425 was committed by wanmil on 2012-12-26 13:07:04 +0000 (Wed, 26 Dec 2012) Remove obsolete naming of streets by the attributes of the first point Streets could have been named by the first point if the street that had the tag 'X_name' set where X was the highway type of the street. This is not used.

1 0

Commit: r2424: Remove obsolete handling of mkgmap:gtype
by svn commit 26 Dec '12

26 Dec '12

Version 2424 was committed by wanmil on 2012-12-26 12:54:32 +0000 (Wed, 26 Dec 2012) Remove obsolete handling of mkgmap:gtype This special tag could have been used to assign a garmin type to an element without using the style file. This is not used any more and should be replaced by rules in the style files in case it is still used.

1 0