March 2010 - mkgmap-dev - The mkgmap lists

[PATCH v1] MP: Join tags by intersection and not by union
by WanMil 27 Mar '10

27 Mar '10

In case multiple ways were joined to a polygon the polygon was tagged with the union set of tags of all joined ways. This algorithm is not compatible to the tag join algorithm described on the multipolygon relation definition (http://wiki.openstreetmap.org/wiki/Relation:multipolygon#Tagging) Additionally it can produce weired results. Example: MP, Tags: type=multipolygon (no more) Way 1, role=outer, Tags: boundary=administrative, highway=primary Way 2, role=outer, Tags: boundary=administrative The resulting polygon was tagged with boundary=administrative, highway=primary So a primary road was created around the complete region. The new algorithm creates a polygon with boundary=administrative only. WanMil

2 3

problems with display of streetname labels
by Minko 27 Mar '10

27 Mar '10

Hello list, I found out that on certain GPSr units (Colorado/Oregon/Dakota, Nuvi) streetname labels won't display correctly. I noticed that only SOME streetnames appear (highway=pedestrian) while other highway types remain totally absent. When I disable streetnames totally, they are still visible. If I master reset those units, and put it back on, all streetnames are visible for a while. After a few browsings across the map, most names disappear again and never show up. On other units (Etrex) I dont see those problems, the names are displayed correctly, apart from the Pedestrian streets (I can't set them off). I think the main problem lies in the TYP file: if I don't use the TYP file, the streetnames are displayed again. In my TYP file, I now suppress the labels of pedestrian streets, so now on the Etrex it works ok, but still no street names on other GPSrs. Anyone familiar with this behaviour? What can i do about it? Cheers, Minko PS I use http://ati.land.cz/gps/typdecomp/editor.cgi for my TYP files My Typ file can be downloaded at http://sites.google.com/site/openfietsmap/procedure

1 0

Question to address search
by Daniela Duerbeck 25 Mar '10

25 Mar '10

Hi! Yes, I know, that this is already buggy, but I'd like to understand, in which way ... (Or how to work around) I tried on several maps, a small one, that contains just Munich (there I could not find bugs concerning the address search), but also larger areas like upper Bavaria or Bavaria. There it seems to be dependent from where I am. A road which is nearby can be found, but not one that is farer away. A little bit it seemed to me as if just addresses can be found on large maps that are south or southeast from my current postition. Dani

5 6

bug in name command when combined with continue with_actions
by Torsten Leistikow 25 Mar '10

25 Mar '10

Moin, I want to create two symbols for a single element (tagged with key=value), and both symbols shall have different name (alpha and bravo). If my points style looks like the following key=value {name 'alpha'} [0x6005 resolution 20 continue with_actions] key=value {name 'bravo'} [0x5001 resolution 20 continue with_actions] then I will get the two symbols, but both have the name alpha. If I rewrite my style to key=value {set name="alpha"} [0x6005 resolution 20 continue with_actions] key=value {set name="bravo"} [0x5001 resolution 20 continue with_actions] then I will get the two symbols with the correct names alpha and bravo. Interestingly, if I just use the first version but without the with_actions extension key=value {name 'alpha'} [0x6005 resolution 20 continue] key=value {name 'bravo'} [0x5001 resolution 20 continue] then I will again get the two symbols with the correct names alpha and bravo. Gruss Torsten

2 4

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