July 2014 - mkgmap-dev - The mkgmap lists

New SSL cert for svn.mkgmap.org.uk
by Steve Ratcliffe 25 Jul '14

25 Jul '14

Hi There is a new SSL certificate for svn.mkgmap.org.uk which you will have to accept if you are using svn over https. The fingerprint is: 7F:90:A1:29:99:17:03:8F:D8:6A:0E:AD:82:96:9D:C4:A0:A2:18:58 ..Steve

1 0

Why do these rules not match?
by Felix Hartmann 25 Jul '14

25 Jul '14

Only this rule is actually matching. name:int=* & name=* & (name = $name:int ) {delete name; set intnamedeleted=yes} But if I want to change it so I can filter names e.g. here: http://www.openstreetmap.org/node/369495900 In this case I want to delete name:en based on the condition that name is fully present in name:en. So I created the below rules according to the above scheme name:en=* & name=* & (name ~ '.*$name:en' ) {delete name:en; echo "Beginning name matched"} name:en=* & name=* & (name ~ '$name:en.*' ) {delete name:int; echo "end name matched"} name:en=* & name=* & (name:en ~ '.*$name' ) {delete name; echo "beginning name:int matched"} name:en=* &name=* & (name:en ~ '$name.*' ) {delete name; echo "end name:int matched"} -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

1 0

Java tuning hint
by Gerd Petermann 24 Jul '14

24 Jul '14

Hi all, today I found a hint that seems to help mkgmap: http://java-performance.info/string-intern-in-java-6-7-8/ In short, try java run time parameter -XX:StringTableSize=100003 for mkgmap. Gerd

3 10

small transliteration bug
by Michał Rogala 23 Jul '14

23 Jul '14

Hi! latin1 transliteration doesn't touch letter ó (0x00F3) - it should be converter to letter o. Could you please fix it? :) Thanks in advance. Michal Rogala

3 8

address search in Nuvi broken
by Paulo Carvalho 22 Jul '14

22 Jul '14

Hi, Michal, I compile maps fof Brazil that also has street names with latin accented characters. Here are my global mkgmap params (taken from a build batch script): SET _params_globais_mkgmap= ^ --copyright-message="(c) OpenStreetMap Contributors" ^ --country-abbr=BRA ^ --country-name=Brasil ^ --process-exits ^ --name-tag-list=int_name,name ^ --index ^ --preserve-element-order ^ --route ^ --housenumbers ^ --x-housenumbers ^ --adjust-turn-headings ^ --location-autofill=is_in,nearest ^ --remove-short-arcs ^ --latin1 ^ --generate-sea=extend-sea-sectors ^ --add-pois-to-areas ^ --add-pois-to-lines ^ --link-pois-to-ways ^ --poi-address ^ --pois-to-areas-placement=entrance=main;entrance=yes;building=entrance ^ --make-poi-index ^ --reduce-point-density=2.6 ^ --reduce-point-density-polygon=8 ^ --code-page=1252 ^ --merge-lines ^ --min-size-polygon=8 ^ --process-destination ^ --style-file=.\requisitos\cocar_style_file ^ --polygon-size-limits=24:12,18:10,16:8,12:4,10:0 My address searches are working fine with 3314. Do you use a custom style/address file (or other style files)? If so, don't forget to replace mkgmap's default files when you upgrade. This may be a cause of sudden loss of functionality after an upgrade. Mine has been extensively customized to meet my country particularities. So I always have to replace the ones that come with mkgmap every time I upgrade. Do you enable the --keeping-going parameter? If so, maybe an error is occurring in between (administrative boundary pre-processing? Map tiling?) and your IMG is incomplete. I never enable it. BTW, I tested my map compiled with 3314 on a Nuvi 255W. all the best, Paulo > From: "Michał Rogala" <michal.rogala(a)gmail.com> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Cc: > Date: Sat, 19 Jul 2014 18:49:20 +0200 > Subject: [mkgmap-dev] address search in Nuvi broken > > Hi! > > I have a strange problem with Nuvi devices. I generate one map in two > versions: > > - latin 1 > - cp1250 > > Address search for both maps works well in GPSMap 62 and similar > handhelds, as well as in MapSource and BaseCamp. Recently I've got a few > Nuvi devices for testing and it occured that on those devices address > search doesn't work - you can't choose any city (no results found). > > Problem occurs when using latin1 version - cp1250 works fine. > > After a lot of trial and error I found out that in Nuvi you need to enter > city and street name with upper-case letters (enable "caps-lock" in device). > > This is really strange and I have no idea how to resolve this situation - > adding --lower-case doesn't work. It doesn't matter if I upload map using > MapInstall or by dropping IMG file. > > I have tested two mkgmap versions: > > - mkgmap 3314 - address search broken > - mkgmap 3280 - address search works fine, although letter "ó" is not > properly transliterated into "o" - Wrociszów town should be Wrociszow > > I compile map for Poland - so maybe it has something to do with > diacritical chars and transliteration. > > > best regards > > Michal Rogala > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev >

3 4

address search in Nuvi broken
by Michał Rogala 19 Jul '14

19 Jul '14

Hi! I have a strange problem with Nuvi devices. I generate one map in two versions: - latin 1 - cp1250 Address search for both maps works well in GPSMap 62 and similar handhelds, as well as in MapSource and BaseCamp. Recently I've got a few Nuvi devices for testing and it occured that on those devices address search doesn't work - you can't choose any city (no results found). Problem occurs when using latin1 version - cp1250 works fine. After a lot of trial and error I found out that in Nuvi you need to enter city and street name with upper-case letters (enable "caps-lock" in device). This is really strange and I have no idea how to resolve this situation - adding --lower-case doesn't work. It doesn't matter if I upload map using MapInstall or by dropping IMG file. I have tested two mkgmap versions: - mkgmap 3314 - address search broken - mkgmap 3280 - address search works fine, although letter "ó" is not properly transliterated into "o" - Wrociszów town should be Wrociszow I compile map for Poland - so maybe it has something to do with diacritical chars and transliteration. best regards Michal Rogala

1 0

Commit: r3316: Add address lines for countries Slovakia and Greece
by svn commit 19 Jul '14

19 Jul '14

Version mkgmap-r3316 was committed by steve on Sat, 19 Jul 2014 Add address lines for countries Slovakia and Greece - Marek Greško

1 0

administrative boundaries for Slovakia
by Marek Greško 19 Jul '14

19 Jul '14

Hello, could you, please include following into the inc/address file of the default style. For Slovakia I am almost sure it is correct and for Greece I have high level of belief. Thanks Marek # Slovakia mkgmap:country=SVK & mkgmap:city!=* & mkgmap:admin_level6=* { set mkgmap:city='${mkgmap:admin_level6}' } mkgmap:country=SVK & mkgmap:city!=* & mkgmap:admin_level9=* { set mkgmap:city='${mkgmap:admin_level9}' } mkgmap:country=SVK & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8}' } # Greece mkgmap:country=GRE & mkgmap:city!=* & mkgmap:admin_level7=* { set mkgmap:city='${mkgmap:admin_level7}' } mkgmap:country=GRE & mkgmap:city!=* & mkgmap:admin_level8=* { set mkgmap:city='${mkgmap:admin_level8}' }

2 1

Commit: r3315: Filter some objects that are not buildings.
by svn commit 19 Jul '14

19 Jul '14

Version mkgmap-r3315 was committed by steve on Sat, 19 Jul 2014 Filter some objects that are not buildings. Tourism and graveyards are not building, neither are groyne and reinforced slope. They are removed from the catch all building rule. - Minko

1 0

building catch all
by chris66 19 Jul '14

19 Jul '14

Hi, at the end of polygons we have some catch all rule: (building=* | amenity=*) & area!=no [0x13 resolution 24] tourism=* & area!=no & waterway!=* [0x13 resolution 24] # man_made can be used on areas or lines man_made=* & area!=no & (man_made!=door & man_made!=embankment & man_made!=breakwater & man_made!=cable_line & man_made!=cutline & man_made!=cutting & man_made!=levee & man_made!=trench) [0x13 resolution 24] man_made=* & area=yes [0x13 resolution 24] This causes that following osm elements are mapped to building (0x13): tourism=camp_site (should be mapped to 0x17 or 0x19) amenity=grave_yard (should be mapped to 0x1a) So I think we should have more specific rules here instead a catch-all. Chris

4 8