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@gmail.com> To: Development list for mkgmap <mkgmap-dev@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@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi! I dont' use --keep-going. My styles are totally custom. Problem is probably related with characters used in central and eastern Europe. You can try to compile: http://download.geofabrik.de/europe/poland-latest.osm.pbf and see if address search works for you (without --code-page). Recent changes to mkgmap included a lot of code related to text/unicode processing so that may be the case. I will make some other tests to find out which commit broke this :) best regards Michal Rogala 2014-07-20 14:56 GMT+02:00 Paulo Carvalho <paulo.r.m.carvalho@gmail.com>:
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@gmail.com> To: Development list for mkgmap <mkgmap-dev@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@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
So, after a lot of trial and error it seems that this bug is not related to differences between commits. I supposed that --latin1 switch is implicit, but if my options omit this parameter address search doesn't work. If I use --latin1 explicitly, everything works fine. This problem only occurs on Nuvi. GPSMap is not affected. best regards Michal Rogala 2014-07-21 10:50 GMT+02:00 Michał Rogala <michal.rogala@gmail.com>:
Hi!
I dont' use --keep-going. My styles are totally custom. Problem is probably related with characters used in central and eastern Europe. You can try to compile:
http://download.geofabrik.de/europe/poland-latest.osm.pbf
and see if address search works for you (without --code-page). Recent changes to mkgmap included a lot of code related to text/unicode processing so that may be the case. I will make some other tests to find out which commit broke this :)
best regards
Michal Rogala
2014-07-20 14:56 GMT+02:00 Paulo Carvalho <paulo.r.m.carvalho@gmail.com>:
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@gmail.com> To: Development list for mkgmap <mkgmap-dev@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@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 21/07/14 13:48, Michał Rogala wrote:
So, after a lot of trial and error it seems that this bug is not related to differences between commits. I supposed that --latin1 switch is implicit, but if my options omit this parameter address search doesn't work. If I use --latin1 explicitly, everything works fine.
Yes, latin1 is not the default, although we did decide that it should be some time ago, so I shall go ahead and do it.
This problem only occurs on Nuvi. GPSMap is not affected.
Without --latin1, the labels are stored in a compressed 6 bit format that is upper case only. I did wonder if it would work with the index, but it seems to for mapsource so I allowed it. It is quite plausible that it doesn't work with some devices though. ..Steve
Ok, thanks for explanation :) best regards Michal Rogala 2014-07-22 11:12 GMT+02:00 Steve Ratcliffe <steve@parabola.me.uk>:
On 21/07/14 13:48, Michał Rogala wrote:
So, after a lot of trial and error it seems that this bug is not related to differences between commits. I supposed that --latin1 switch is implicit, but if my options omit this parameter address search doesn't work. If I use --latin1 explicitly, everything works fine.
Yes, latin1 is not the default, although we did decide that it should be some time ago, so I shall go ahead and do it.
This problem only occurs on Nuvi. GPSMap is not affected.
Without --latin1, the labels are stored in a compressed 6 bit format that is upper case only. I did wonder if it would work with the index, but it seems to for mapsource so I allowed it. It is quite plausible that it doesn't work with some devices though.
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (3)
-
Michał Rogala -
Paulo Carvalho -
Steve Ratcliffe