- mkgmap-dev - The mkgmap lists

Shuttle-Train
by Chris-Hein Lunkhusen 31 Mar '10

31 Mar '10

Hi, The german island Sylt can only be reached (for cars) on the shuttle train (www.syltshuttle.de) So for now our maps can't route to sylt, because we don't route over railway=rail (even if it's tagged with motorcar=yes). If I look to my Nüvi with Garmin City-Navigator Map, the way looks different than a normal rail-line, so garmin seems to have a special data type for this kind of connection. So, how to handle this? Should we add a rule to the default style to route cars over railway=rail if it is tagged additionaly with motorcar=yes ? Chris

5 8

Generate coastline - can we keep the coastline way?
by Toby Speight 31 Mar '10

31 Mar '10

When --generate-coastline=multipolygon fails, I'm left with a map that has no distinction between land and sea. However, if I don't use --generate-coastline, I at least get a line (from my style/lines). Is there any good reason why generating coastline prevents the line rules from being applied to the coastline ways? It's not a problem when I actually get sea tiles, but it's a serious nuisance when small islands have completely disappeared!

5 11

Re: [mkgmap-dev] problems with display of streetname labels
by Minko 29 Mar '10

29 Mar '10

To add a note to my former question: I found out that if I don't fill in the extended labels from the lines/ways in the TYP file, the display of street names on the mentioned GPS units are ok. If I put some of them on invisible, all the streetnames disappear. I also put the question on the ati.land.cz discussion list.

1 1

Incorrect multipolygon warnings?
by Charlie Ferrero 28 Mar '10

28 Mar '10

Hi, Whilst processing Italy, I've been getting a lot of mp warnings like: 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: Polygon 4611686018427439638 intersects itself. It is splitted into 2 polygons. 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: The polygon is composed of 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: - http://www.openstreetmap.org/browse/way/36433060 I can't see anything wrong with this mp and the JOSM validator does not pick up on anything. Is this an error with mkgmap's MP code or am I missing something? Here's another: 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: Polygon 4611686018427439886 intersects itself. It is splitted into 2 polygons. 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: The polygon is composed of 2010/03/27 13:57:27 WARNING (MultiPolygonRelation): 63242013.osm.gz: - http://www.openstreetmap.org/browse/way/36434237 -- Charlie

3 5

Boundary Lines
by Chris-Hein Lunkhusen 28 Mar '10

28 Mar '10

Hi, I see in Mapsource many boundary lines which are not existing in the OSM data. See attached screen shot. Are these lines coming from the multipolygon processing? Data is from the geofabrik germany extract. Chris

3 4

expression test !=
by Torsten Leistikow 28 Mar '10

28 Mar '10

Moin, in the Wiki the != test is described as follows: highway!=motorway This will be true when the highway tag exists, but it does NOT have the value motorway. >From my understanding this should read like highway!=motorway This will be true when the highway tag exists, but it does NOT have the value motorway, or when there is no highway tag at all. Shall I correct the description in the Wiki or must I correct my understanding of the != test? Gruss Torsten

3 2

[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