- mkgmap-dev - The mkgmap lists

Testing for a literal question mark
by Dave Swarthout 19 Mar '15

19 Mar '15

How would I write a regex style rule that fires when it encounters a question mark in a name? There is a group of local mappers that have used an invented name of "Ban ?" for towns they do not know the name of. I want to set the name to something more meaningful but I can't seem to discover a way to escape the ? without crashing mkgmap. -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com

3 3

Commit: r3498: modfiy evaluation of maxspeed=* tag
by svn commit 18 Mar '15

18 Mar '15

Version mkgmap-r3498 was committed by gerd on Wed, 18 Mar 2015 modfiy evaluation of maxspeed=* tag - set mkgmap:road-speed-max instead of mkgmap:road-speed-class - evaluate also some tags like maxspeed=RU:urban based on rules documented in the wiki - use slightly different threshold values thanks to Andrzej Popowski and Bernd Weigelt

3 3

"Building" POI are not searchable resource
by Alexandre Loss 18 Mar '15

18 Mar '15

Hi Gerd, I observed in my maps that the POI of type "building" (Garmin code 0x6402) are not searchable using MapSource "Find Place-->Resource" tool. However, I'm able to find these kind POI using MapSource "Find Near Places" tool. Is this the regular behavior or is there some problem in the index? Thanks. Alexandre

2 5

comparison of relation tag and way tag
by Mike Baggaley 17 Mar '15

17 Mar '15

Hi, I have the following lines in my relations file: type=route & (route~'.*foot.*' | route~'.*hiking.*') & network~'.*[nr]wn.*' & name~".*$.*$" { set name='${name|subst:"$.*$~>"}'} type=route & (route~'.*foot.*' | route~'.*hiking.*') & network~'.*[nr]wn.*' & name=* { apply_once { set hikingroute=yes; set rn='$(rn) & ${name}' | '${name}'; } } This is working, but if for example the way has two hiking relations with names "Shropshire Way (Route 1)" and "Shropshire Way (Route 2)", the first rule changes the names of both relations to "Shropshire Way", and the second rule sets the rn tag of the way to "Shropshire Way & Shropshire Way". I would like to check whether the rn tag on the way already contains the name of the relation (or is equal to if contains can't be done), so that I end up with rn as "Shropshire Way". Can anyone tell me how this can be achieved? Thanks, Mike

2 2

roadspeed in default style
by Andrzej Popowski 16 Mar '15

16 Mar '15

Hi, one of threads reminded me about "roadspeed" include in default style. As far as I understand, Garmin maps made by mkgmap contain average road speed, which can be used for calculation of arrival time. Include "roadspeed" deals with speed limits and convert them into value, which is then treated as average speed. In my opinion this is wrong assumption. Better average speed could be estimated from road type. Speed limit should be used only to limit average speed, for example on good roads in urban area. I'm using this approach in my maps. I have attached my alternative for roadspeed. -- Best regards, Andrzej

7 42

How to search for the Second City Name
by A. Carlos 15 Mar '15

15 Mar '15

Hello list members, I have a doubt beginners Using this command: --x-split-name-index GPS or Mapsource I can search by street, by typing any part of her name. This facility also has the POI search, but the search for City not found a way to search only by the second name. Does anyone have a tip, if any, for this facility to be equal to search by street? grateful Carlos

3 3

Question on Auto-Zoom
by Michael Poesdorf 14 Mar '15

14 Mar '15

Dear developers, Are you aware of the criteria that a garmin unit (I'm using a Montana 600) is using for Auto-Zoom? There is not much information around on the internet. Some tell something about speed. Quite many tell that zoom is done to the extent to include the next turn activity. Some tell that routing has to be active (I had some auto zooming although I wasn't activly routing) Computerteddy couldn't help . I'm asking as I drive some road for quite a while/distance and the unit doesn't zoom out but sticks to the 50m-scale. Although at the beginning of this part it switches to the 200m scale for a 1 or 2 of seconds. Which would be ok for me for at least the next kilometer. So I wonder why it doesn't stick longer to it. Is there something with the style or the typ-file to be considered? Or a setting in the unit? Appreciating your comments Best regards, Michael

3 2

Re: [mkgmap-dev] Commit: r3495: Corrections for --make-opposite-cycleways option
by Mike Baggaley 13 Mar '15

13 Mar '15

Hi Gerd, you had me confused there - I thought you were going to commit the update to the style and deprecate the --make-opposite-cycleways option... Regards, Mike >From svn commit svn at mkgmap.org.uk on Thu Mar 12 07:11:53 GMT 2015 > >Version mkgmap-r3495 was committed by gerd on Thu, 12 Mar 2015 > >Corrections for --make-opposite-cycleways option > >1) remove explicit access tags like to make sure that the synthesised >cycle way allows only bicycle traffic in both directions. >With the >2) don't add the suffix " (cycleway)" to the name

2 1

Commit: r3495: Corrections for --make-opposite-cycleways option
by svn commit 12 Mar '15

12 Mar '15

Version mkgmap-r3495 was committed by gerd on Thu, 12 Mar 2015 Corrections for --make-opposite-cycleways option 1) remove explicit access tags like to make sure that the synthesised cycle way allows only bicycle traffic in both directions. With the 2) don't add the suffix " (cycleway)" to the name - Mike Baggaley

1 0

--make-opposite-cycleways option
by Mike Baggaley 10 Mar '15

10 Mar '15

Dear all, When using the --make-opposite-cycleways option, I notice that the address index adds a road name of the actual road name suffixed with " (cycleway)". For me at least, this is undesirable. Also the generated name does not conform to the OSM naming convention of not including any descriptive information in names. I therefore propose that the name of an opposite cycleway be set to the same as the original road name, and that users who want to name the opposite cycleway differently should use the style file to rename it. In looking at the code that produces the opposite cycleway, I also believe there is an error in the way it handles access tags - the code currently sets access=no, bicycle=yes and foot=no, but ignores all other access tags. Hence if (for example) the road has psv=yes on it, the generated cycleway will also have psv=yes (unless I am misunderstanding something in the handling of access tags). I therefore submit the attached patch for trial. Regards, Mike

4 26