
Hi all, please note the new option --wanted-admin-level in r423. For details see http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&path=%2F&rev=4... and the discussion about duplicate cities: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2015q2/023603.html Gerd

HI Gerd, in Brazil we identified a problem using this new version of the splitter. In Mkgmap we employ the --latin1 option because we use non-ascii character in our language With mkgmap r3598 and splitter r421 the city of São Paulo (node http://www.openstreetmap.org/node/3509363965 ) is indexed normally, but with the mkgmap r3598 and splitter r423 not. This city node of São Paulo is admin_center, a member of the relation = boundary, admin_level = 4 of São Paulo (relation http://www.openstreetmap.org/relation/298204 ). Both (state and city) has the same name and non-ascii character "~" in the first word of the name (São). After numerous tests identified the splitter r423 does not recognize non-ascii characters when used in the first word of the name of the place. When used in other word name than the first, he acknowledges. Any suggestion? Marcio From: Gerd Petermann Sent: Friday, May 22, 2015 4:34 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: [mkgmap-dev] splitter r423 Hi all, please note the new option --wanted-admin-level in r423. For details see http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&path=%2F&rev=4... and the discussion about duplicate cities: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2015q2/023603.html Gerd

Hi Marcio, I am sure that splitter doesn't change the name. I assume that the problem is somewhere else, but I have no idea where. I suggest to use the echotags action to find out which OSM element has the wrong name . Gerd thundercel wrote
HI Gerd, in Brazil we identified a problem using this new version of the splitter.
In Mkgmap we employ the --latin1 option because we use non-ascii character in our language
With mkgmap r3598 and splitter r421 the city of São Paulo (node http://www.openstreetmap.org/node/3509363965 ) is indexed normally, but with the mkgmap r3598 and splitter r423 not.
This city node of São Paulo is admin_center, a member of the relation = boundary, admin_level = 4 of São Paulo (relation http://www.openstreetmap.org/relation/298204 ). Both (state and city) has the same name and non-ascii character "~" in the first word of the name (São).
After numerous tests identified the splitter r423 does not recognize non-ascii characters when used in the first word of the name of the place. When used in other word name than the first, he acknowledges.
Any suggestion?
Marcio
From: Gerd Petermann Sent: Friday, May 22, 2015 4:34 AM To:
mkgmap-dev@.org
Subject: [mkgmap-dev] splitter r423
Hi all,
please note the new option --wanted-admin-level in r423. For details see http://www.mkgmap.org.uk/websvn/revision.php?repname=splitter&path=%2F&rev=4...
and the discussion about duplicate cities:
http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2015q2/023603.html
Gerd
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-r423-tp5845521p5845741.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

Thanks Gerd, I'll do it Marcio -----Mensagem Original----- From: GerdP Sent: Sunday, May 24, 2015 5:27 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] splitter r423 Hi Marcio, I am sure that splitter doesn't change the name. I assume that the problem is somewhere else, but I have no idea where. I suggest to use the echotags action to find out which OSM element has the wrong name . Gerd
participants (3)
-
Gerd Petermann
-
GerdP
-
thundercel@gpsinfo.com.br