November 2013 - mkgmap-dev - The mkgmap lists

One node - two index entries?
by Bernhard Hiller 10 Nov '13

10 Nov '13

Background: Often hotels have a restaurant also, the combination of amenity=restaurant and tourism=hotel on one node (or area) is quite common. Now the hotel should be in "Lodging - Hotel", and the restaurant somewhere in "Food and Drink". Hence my question is: is it possible to get one node into the index twice in different categories? I tried following rules: tourism=hotel & amenty!=* { name '${name|def:}(${stars}*)${operator|def:}' | '${name} ${operator}' | '${name}' | '${operator}' } [0x2b01 level 2] tourism=hotel & amenty=* { name '${name|def:}(${stars}*)${operator|def:}' | '${name} ${operator}' | '${name}' | '${operator}' } [0x2b01 level 2 continue] ... amenity=restaurant [0x2a00 level 0] On my Oregon 600, only the hotel is indexed, but not the restaurant. Is that currently possible with some different rules / order of rules, or not yet possible, or even not possible at all?

2 2

Commit: r2815: merge the reduce-limits branch
by svn commit 09 Nov '13

09 Nov '13

Version mkgmap-r2815 was committed by gerd on Fri, 08 Nov 2013 merge the reduce-limits branch

3 3

Multiple relations
by Anna Leuchter 09 Nov '13

09 Nov '13

Ciao Enrico, RELATIONS file ... type=route & route=bicycle { apply { set bike_relation=yes; } } type=route & (route=foot | route=hiking) { apply { set hike_relation=yes; } } ... LINES file ... highway=track & bike_relation=yes [0x01 road_class=0 road_speed=0 resolution 24 continue ] highway=track & hike_relation=yes [0x02 road_class=0 road_speed=0 resolution 24 continue ] ... You can set a tag in RELATIONS file if the way element belongs to a route. And if there are 2 matches 2 tags will be set. These tags you can than use in LINES file to create the garmin objects. regards Gert

3 2

Multiple relations
by Anna Leuchter 08 Nov '13

08 Nov '13

Hi Enrico, >How can you see the image attached MapSource display tha name of the highway >(not the name of the route relation) if there is one or the label >"Sconosciuto" if there isn't. >I would delete (I don't want to see it). It is possibile? sorry, but may be i don't understand you. 1. deleting a tag if you want to delete a tag use "delete { key123 }" see style manual 4.3.4 page 11. 2. using route relation names RELATIONS file type=route & route=bicycle { apply { set bike_relation=yes; set br_name='${name}'; } } LINES file ... highway=track & bike_relation=yes { name '${name}' | '${br_name}' | 'Sconosciuto' } [0x01 road_class=0 road_speed=0 resolution 24 continue ] ... In this case, the name of element would be used if it exist and if it not exists, the relation name would be used. If both doesn't exist, name will be set to "Sconosciuto" regards Gert

2 1

Commit: r2814: Test tag value against tag value.
by svn commit 07 Nov '13

07 Nov '13

Version mkgmap-r2814 was committed by steve on Thu, 07 Nov 2013 Test tag value against tag value. A new syntax is added to allow you to compare the value of two different tags. Example: name = $name:en { ... } matches if the english name is the same as the plain name.

1 0

reduce_limits branch
by Gerd Petermann 07 Nov '13

07 Nov '13

Hi all, I've committed r2799. This reverts some experimental code. I think the program is now ready for productional use. It is fully compatible with trunk. Please try it! Improvements: 1) Smoothing filters are more efficient, this reduces img size by ~ 3% Please check if you see changes in parallel lines, e.g. SRTM data. If so, please let me know if this version is better or worse. 2) Roads with many (>250) points are no longer split into parts as long as they are not also very long or have a large bounding box . This reduces NOD size a little bit. I don't know if it improves routing, but GPSMapEdit loads the map a bit faster (10% seen with tile from Australia) Gerd

2 2

[Patch v2] higher precision in coordinates
by Gerd Petermann 07 Nov '13

07 Nov '13

Hi, attached is v2 of the patch. It still only solves problems related to routing, but I see many possible improvemets with more coding. I think we should create a branch for it, but I first like to finish work on the reduce_limits branch, which in turn is more useful in combination with the mergeroads branch. Gerd

3 5

Commit: r2800: Combine the two examples sections.
by svn commit 05 Nov '13

05 Nov '13

Version mkgmap-r2800 was committed by steve on Tue, 05 Nov 2013 Combine the two examples sections. Both the sections containing examples are combined and placed at the end of the chapter.

1 0

Multiple relations
by demon.box 05 Nov '13

05 Nov '13

Hi, there is a way in the style to display every route relations on the same highway segment on separate lines? I mean, on a highway segment that have more than one route relation I would see (on MapSource or BaseCamp) something like this: Route number 1 Route number 2 ecc. Thanks very much. --enrico -- View this message in context: http://gis.19327.n5.nabble.com/Multiple-relations-tp5784094.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

Numerical comparison of two tags
by Bernhard Hiller 03 Nov '13

03 Nov '13

I'd like to set maxspeed to the minimum of maxspeed, maxspeed:forward, and maxspeed:backward. In my lines file, I use: |maxspeed:forward=*& maxspeed!=* { set maxspeed='${maxspeed:forward}' } maxspeed:forward=*& (maxspeed:forward<maxspeed) { set maxspeed='${maxspeed:forward}' } maxspeed:backward=*& maxspeed!=* { set maxspeed='${maxspeed:backward}' } maxspeed:backward=*& (maxspeed:backward<maxspeed) { set maxspeed='${maxspeed:backward}' }| That works only if exactly one tag is set. But when both forward and backward are available, I get the value of forward even if backward is less. An example is wayhttp://www.openstreetmap.org/browse/way/70594951. I played with additional / different rules, and my conclusion is that it is NOT POSSIBLE to compare the values of two tags with each other. For example, I tried: |highway=*& maxspeed!=* { set maxspeed=999 } maxspeed:forward=*& (maxspeed:forward<maxspeed) { set maxspeed='${maxspeed:forward}' } maxspeed:backward=*& (maxspeed:backward<maxspeed) { set maxspeed='${maxspeed:backward}' }| And you can guess the result: maxspeed=999, for that way with maxspeed:forward=60 and maxspeed:backward=40. Is my conclusion correct? And, if so, will there be a patch?

4 11