- mkgmap-dev - The mkgmap lists

nodes on boundary
by Carsten Schwede 25 Mar '10

25 Mar '10

Hi there, last I have read here on the mailing list about the tag for routing over the tile boundary. <tag k='mkgmap:on-boundary' v='1' /> Since we dont use splitter for cutting the planet my question is on which nodes must this tag be? A sample: Tile1 # Tile2 # C # | A-----#-------B # | # | # D # tile boundary Our cutting creates the tiles so, that node A and the way between A and B i in the Tile 1. The nodes B, C, D and the way between them are in the Tile 2. Must the node B have the special on-boundary tag in both tiles, or only in the tile 1? -- Best wishes Computerteddy

4 6

debugging ferries
by Chris-Hein Lunkhusen 25 Mar '10

25 Mar '10

Hi, I tested the ferry routing with mkgmap default style and found that my Nüvi was not able to route me to Borkum. When I set a via point on the ferry route it works ok, but without this via point mapsource does "direct line routing". MS screenshot: <http://up.picr.de/4006248.png> There is no tile-boundary in between. Chris

3 4

Commit: r1620: Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.
by svn commit 24 Mar '10

24 Mar '10

Version 1620 was commited by markb on 2010-03-22 21:24:01 +0000 (Mon, 22 Mar 2010) Can now explicitly tag boundary nodes with mkgmap:on-boundary=1.

3 3

Commit: r1624: Revert "Add --min-line-size and --min-polygon-size options."
by svn commit 24 Mar '10

24 Mar '10

Version 1624 was commited by markb on 2010-03-23 21:52:40 +0000 (Tue, 23 Mar 2010) Revert "Add --min-line-size and --min-polygon-size options." Let's just pretend this never happened.

3 2

Commit: r1621: Add --min-line-size and --min-polygon-size options.
by svn commit 23 Mar '10

23 Mar '10

Version 1621 was commited by markb on 2010-03-23 09:07:10 +0000 (Tue, 23 Mar 2010) Add --min-line-size and --min-polygon-size options. Allow the user to specify the minimum size of line and polygon features. Features smaller than that at a given zoom level are dropped. The defaults are 1 for lines and 8 for polygons. Based on a patch supplied by Felix Hartmann.

3 5

Commit: r1623: Squash spaces in label strings.
by svn commit 23 Mar '10

23 Mar '10

Version 1623 was commited by markb on 2010-03-23 20:15:14 +0000 (Tue, 23 Mar 2010) Squash spaces in label strings.

1 0

Commit: r1622: Compile regexps used in stripGarminCodes() to reduce mkgmap's carbon footprint.
by svn commit 23 Mar '10

23 Mar '10

Version 1622 was commited by markb on 2010-03-23 20:15:10 +0000 (Tue, 23 Mar 2010) Compile regexps used in stripGarminCodes() to reduce mkgmap's carbon footprint.

1 0

Using multiple TYP files
by Toby Speight 23 Mar '10

23 Mar '10

I'm having trouble combining IMG files with different product and family IDs into a single gmapsupp.img. I can create single-family images with no problem, but trying to create a multiple-family image thusly: /-------- | $(MKGMAP) --gmapsupp \ | --family-id=1672 --product-id=1672 1672*.img 1672.TYP \ | --family-id=6324 --product-id=6324 6324*.img 6324.TYP \-------- results in all the image files getting the 6324 IDs, and so the 1672* files appear in the wrong style. It also means that I can't selectively show or hide the two families. How best to combine the two?

7 13

[PATCH v1] squash spaces in labels
by Mark Burton 23 Mar '10

23 Mar '10

This patch squashes spaces in label strings so that "High Street" becomes "High Street". Is there any reason why we would want to preserve multiple spaces? Mark

1 0

Minimum size patch installed
by Mark Burton 23 Mar '10

23 Mar '10

The patch to support different min sizes for lines and polys has now be committed. I added a couple of options so that the default values (1 and 8 as per the original patch) can be changed if required. Mark

1 0