Hi Andrzej, Thanks for the quick response. As it happens, I already had the show-profiles option in my configuration, but I was using just a gmapsupp.img file and I have now realised that the elevation data is available if I use the separate tile files and set the registry to install the map. Is there any way to get that data included in a gmapsupp.img file, or an extra file to distribute with a gmapsupp.img file? I'm trying to avoid having to use both the combined img file and all the components as well. Cheers, Mike
Hi Mike option --show-profiles sets a flag in TDB file, which is a part of installation for PC. I'm not aware of any similar flag in img for device. Original topo maps from Garmin include DEM data, which are used for computing profiles. This could be the reason, why BaseCamp doesn't support contours in img. -- Best regards, Andrzej
I would be interested as well to know if/how it is possible to include DEM data directly in the gmapsupp file... On Mon, Dec 29, 2014 at 11:59 PM, Andrzej Popowski <popej@poczta.onet.pl> wrote:
Hi Mike
option --show-profiles sets a flag in TDB file, which is a part of installation for PC. I'm not aware of any similar flag in img for device.
Original topo maps from Garmin include DEM data, which are used for computing profiles. This could be the reason, why BaseCamp doesn't support contours in img.
-- Best regards, Andrzej
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
For countries with foreign letters like Greece I want to show the int_name first. For other countries I want to show the int_name in brackets. If no int_name or other good name is found, I want to show the transliterated name. Here is my code: 'name:de'=* { add mkgmap_int_name='${name:de}' } int_name=* { add mkgmap_int_name='${int_name}' } 'name:en'=* { add mkgmap_int_name='${name:en}' } 'name:fr'=* { add mkgmap_int_name='${name:fr}' } 'name:es'=* { add mkgmap_int_name='${name:es}' } mkgmap_int_name!=* { add mkgmap_int_name='${name|ascii:}' } # Error: Expecting }, instead saw | mkgmap_int_name=${name} { delete mkgmap_int_name } place=* { set mkgmap_place_name=no } place=* & mkgmap_int_name=* & mkgmap:country=GRE { set name='${mkgmap_int_name} (${name})'; set mkgmap_place_name=yes } place=* & mkgmap_int_name=* & mkgmap_place_name=no { set name='${name} (${mkgmap_int_name})'; set mkgmap_place_name=yes } According to the error message it seems, that |ascii: is not recognized. Is this syntax wrong? I found it via google but not in documentation, maybe it’s not yet working. I hope somebody has a working solution for my usecase. Walter
Hi Walter, I can't find any code that would implement the filter :ascii, but I seem to remember that I saw it in an email. Maybe as an proposion? Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sat, 10 Jan 2015 02:08:41 +0100 Subject: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
For countries with foreign letters like Greece I want to show the int_name first. For other countries I want to show the int_name in brackets. If no int_name or other good name is found, I want to show the transliterated name.
Here is my code:
'name:de'=* { add mkgmap_int_name='${name:de}' } int_name=* { add mkgmap_int_name='${int_name}' } 'name:en'=* { add mkgmap_int_name='${name:en}' } 'name:fr'=* { add mkgmap_int_name='${name:fr}' } 'name:es'=* { add mkgmap_int_name='${name:es}' } mkgmap_int_name!=* { add mkgmap_int_name='${name|ascii:}' } # Error: Expecting }, instead saw | mkgmap_int_name=${name} { delete mkgmap_int_name }
place=* { set mkgmap_place_name=no } place=* & mkgmap_int_name=* & mkgmap:country=GRE { set name='${mkgmap_int_name} (${name})'; set mkgmap_place_name=yes } place=* & mkgmap_int_name=* & mkgmap_place_name=no { set name='${name} (${mkgmap_int_name})'; set mkgmap_place_name=yes }
According to the error message it seems, that |ascii: is not recognized. Is this syntax wrong? I found it via google but not in documentation, maybe it’s not yet working.
I hope somebody has a working solution for my usecase.
Walter
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, here I found a mail from Steve Ratcliffe where this syntax was working. name:int!=* & name=* {set name='${name|ascii:} ${name}' http://gis.19327.n5.nabble.com/Command-to-transliterate-Characters-Cyrillic-... Do you know any other solution how to use the transliterated name? I only know the way to change the char code, but in that case the original name cannot be combined with the transliterated name. Walter From: Gerd Petermann Sent: Saturday, January 10, 2015 5:01 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi Walter, I can't find any code that would implement the filter :ascii, but I seem to remember that I saw it in an email. Maybe as an proposion? Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sat, 10 Jan 2015 02:08:41 +0100 Subject: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
For countries with foreign letters like Greece I want to show the int_name first. For other countries I want to show the int_name in brackets. If no int_name or other good name is found, I want to show the transliterated name.
Here is my code:
'name:de'=* { add mkgmap_int_name='${name:de}' } int_name=* { add mkgmap_int_name='${int_name}' } 'name:en'=* { add mkgmap_int_name='${name:en}' } 'name:fr'=* { add mkgmap_int_name='${name:fr}' } 'name:es'=* { add mkgmap_int_name='${name:es}' } mkgmap_int_name!=* { add mkgmap_int_name='${name|ascii:}' } # Error: Expecting }, instead saw | mkgmap_int_name=${name} { delete mkgmap_int_name }
place=* { set mkgmap_place_name=no } place=* & mkgmap_int_name=* & mkgmap:country=GRE { set name='${mkgmap_int_name} (${name})'; set mkgmap_place_name=yes } place=* & mkgmap_int_name=* & mkgmap_place_name=no { set name='${name} (${mkgmap_int_name})'; set mkgmap_place_name=yes }
According to the error message it seems, that |ascii: is not recognized. Is this syntax wrong? I found it via google but not in documentation, maybe it’s not yet working.
I hope somebody has a working solution for my usecase.
Walter
_______________________________________________ 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
Hi Walter, I see. Seems that the patch transliterate_filter.patch was never committed. @Steve: Maybe you forgot about it because Felix never confirmed that it works for him? Gerd From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sun, 11 Jan 2015 00:25:25 +0100 Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi Gerd, here I found a mail from Steve Ratcliffe where this syntax was working. name:int!=* & name=* {set name='${name|ascii:} ${name}' http://gis.19327.n5.nabble.com/Command-to-transliterate-Characters-Cyrillic-... Do you know any other solution how to use the transliterated name? I only know the way to change the char code, but in that case the original name cannot be combined with the transliterated name. Walter From: Gerd Petermann Sent: Saturday, January 10, 2015 5:01 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi Walter, I can't find any code that would implement the filter :ascii, but I seem to remember that I saw it in an email. Maybe as an proposion? Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sat, 10 Jan 2015 02:08:41 +0100 Subject: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
For countries with foreign letters like Greece I want to show the int_name first. For other countries I want to show the int_name in brackets. If no int_name or other good name is found, I want to show the transliterated name.
Here is my code:
'name:de'=* { add mkgmap_int_name='${name:de}' } int_name=* { add mkgmap_int_name='${int_name}' } 'name:en'=* { add mkgmap_int_name='${name:en}' } 'name:fr'=* { add mkgmap_int_name='${name:fr}' } 'name:es'=* { add mkgmap_int_name='${name:es}' } mkgmap_int_name!=* { add mkgmap_int_name='${name|ascii:}' } # Error: Expecting }, instead saw | mkgmap_int_name=${name} { delete mkgmap_int_name }
place=* { set mkgmap_place_name=no }
place=* & mkgmap_int_name=* & mkgmap:country=GRE { set name='${mkgmap_int_name} (${name})'; set mkgmap_place_name=yes } place=* & mkgmap_int_name=* & mkgmap_place_name=no { set name='${name} (${mkgmap_int_name})'; set mkgmap_place_name=yes }
According to the error message it seems, that |ascii: is not recognized. Is this syntax wrong? I found it via google but not in documentation, maybe it’s not yet working.
I hope somebody has a working solution for my usecase.
Walter
_______________________________________________
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 _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On 11/01/15 06:34, Gerd Petermann wrote:
I see. Seems that the patch transliterate_filter.patch was never committed.
@Steve: Maybe you forgot about it because Felix never confirmed that it works for him?
Yes that's right. I think it works but didn't seem to for anyone else ;( If it is useful I can add a test or two and commit it. ..Steve
sorry - for not confirming back then (or I think I did confirm, but maybe in a different thread). I'm still using the patch without problems. I had and will have for the next weeks some time constraints - but will be more active on the mailing list from Feb onwards again. I still think it's useful BTW. (main gripe being that some new units like edge 1000, GPS Maps 64 series and some new Nuvis don't work with mkgmap unicode maps and report maps locked. I would guess Andrzej is the expert on this - but what I remember he also saw no easy (without completely reprogramming mkgmap) solution to get around the prob. Felix On 11 January 2015 at 17:39, Steve Ratcliffe <steve@parabola.me.uk> wrote:
On 11/01/15 06:34, Gerd Petermann wrote:
I see. Seems that the patch transliterate_filter.patch was never committed.
@Steve: Maybe you forgot about it because Felix never confirmed that it works for him?
Yes that's right. I think it works but didn't seem to for anyone else ;( If it is useful I can add a test or two and commit it.
..Steve
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org Floragasse 9/11 1040 Wien Austria - Österreich
On Mon, Jan 12, 2015 at 10:06:00PM +0000, Steve Ratcliffe wrote:
Hi
{ add mkgmap_int_name='${name|ascii:}' }
This is now included in r3409. There is no longer any need for the ':', so you can just write ${name|ascii}
Side note: In src/uk/me/parabola/imgfmt/app/labelenc/ there are two implementations of the Transliterator interface: SparseTransliterator and TableTransliterator. I see no references to Greek or Cyrillic in any file in the whole directory. I guess we might try to do something (Pinyin?) as Chinese transliteration, if the Java framework does not already do that for us. I wonder if the mkgmap transliteration is compatible with the international standards, such as ISO 843 (Greek) and ISO 9 (Cyrillic). Also national standards exist for Cyrillic transliteration. Quoting a message by Χάρης Καραχριστιανίδης on the OsmAnd mailing list: https://groups.google.com/forum/#!topic/osmand/7PTV_nOhNUw "According to this link https://wiki.openstreetmap.org/wiki/Multilingual_names#Greece ISO 843:1999 should be followed for trancription of Greek Names. So for example Βύρωνος ( don't know if you can read Greek letters) should be Vyronos and not Buronos. As I can see almost all Greek streets are wrongly transcribed." Marko
Hi Steve, your new translit feature is working great. For country=GRC e.g. I can show the int, english, german or french name first, and the original name in bracket, or other way round. For the place Ροσινιόλ he could not find any int_name or name:xx so the transliterated name Rosiniol will be used, but - and that is new - the original name ist still shown and not lost. Great feature, makes a map with cyrilic or arabic char. much more readable. I am woundering, why not more users had asked for it, but I'm so happy you have implemented it. Thanks a lot Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles? Walter -----Ursprüngliche Nachricht----- From: Steve Ratcliffe Sent: Monday, January 12, 2015 11:06 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi
{ add mkgmap_int_name='${name|ascii:}' }
This is now included in r3409. There is no longer any need for the ':', so you can just write ${name|ascii} ..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
On Tue, Jan 13, 2015 at 10:01:04PM +0100, Walter Schlögl wrote:
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
By "ANSI" or "Ansi", Microsoft used to refer to their (or IBM's) proprietary Code Page 1252 encoding, which is a superset of ISO 8859-1 aka ISO Latin 1. To add some confusion, some software is referring to cp1252 as latin1. That said, an early version of ISO 8859-1 might have been an ANSI standard. It was used already in the 1980s on the Commodore Amiga, and on Digital computers and terminals (DEC Multilingual Character Set). As far as I know, there is no restriction of how files can be written in contemporary operating systems. Even on Windows, it is normal nowadays to use UTF-8 in file contents. Some Windows software could be happier if the file begins with a Byte Order Mark (BOM), but I do not think it is necessary. Given that OSM has always used the UTF-8 encoding, it would seem easiest to use UTF-8 in the log file output. Marko
Hi Walter, It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8 and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8 ..Steve
Hi Walter, reg. UTF8 in logs: When I read your post my first question was: Is he talking about the log that is written to stderr/stdout or the one that is enabled with java -Dlog.config ... -jar mkgmap.jar ... I think the latter works fine, the first two look ugly when they write to a windows console. They also look fine when you pipe them to files like this java -Dlog.config ... -jar mkgmap.jar ... > mkgmap.stdout 2>mkgmap.stderr Gerd
Date: Wed, 14 Jan 2015 09:15:50 +0000 From: steve@parabola.me.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8
and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8
..Steve _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Steve and Gerd, yes, you got me right. I was talking about stderr output where echo messages are printed. I have tried the following (under Windows): %JavaPath% -Xmx6144m -ea -jar -Dlog.config=%OptionsPath%\logging_properties.txt %ToolPath%\mkgmap\mkgmap.jar -c %OptionsPath%\%mkgmap_options% --mapname=%mapid% --overview-mapname=%overview_mapname% --family-id=%family_id% --product-id=%product_id% --gmapsupp %mkgmap_filename% %StylesPath%\%StylesFile% 2>>%LogfileName% content of logging_properties.txt is: java.util.logging.FileHandler.encoding=UTF-8 java.util.logging.ConsoleHandler.encoding=UTF-8 I am still getting outputs of echo "name='${name}'” as: ‘??????? ??????’ if the char set is not part of 1252 (e.g. for greek letters) I think I did not fully understand your hint with the logging properties. Walter From: Gerd Petermann Sent: Wednesday, January 14, 2015 11:03 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi Walter, reg. UTF8 in logs: When I read your post my first question was: Is he talking about the log that is written to stderr/stdout or the one that is enabled with java -Dlog.config ... -jar mkgmap.jar ... I think the latter works fine, the first two look ugly when they write to a windows console. They also look fine when you pipe them to files like this java -Dlog.config ... -jar mkgmap.jar ... > mkgmap.stdout 2>mkgmap.stderr Gerd
Date: Wed, 14 Jan 2015 09:15:50 +0000 From: steve@parabola.me.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8
and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8
..Steve _______________________________________________ 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
Are you sure that your console can display UTF-8 characters? A web search turned up this discussion. http://stackoverflow.com/questions/388490/unicode-characters-in-windows-comm... I am not sure which if any of the solutions described may apply to your situation. Bill On 01/14/2015 10:26 AM, Walter Schlögl wrote:
Hi Steve and Gerd, yes, you got me right. I was talking about stderr output where echo messages are printed. I have tried the following (under Windows): %JavaPath% -Xmx6144m -ea -jar *-Dlog.config=%OptionsPath%\logging_properties.txt* %ToolPath%\mkgmap\mkgmap.jar -c %OptionsPath%\%mkgmap_options% --mapname=%mapid% --overview-mapname=%overview_mapname% --family-id=%family_id% --product-id=%product_id% --gmapsupp %mkgmap_filename% %StylesPath%\%StylesFile% *2>>%LogfileName%* content of logging_properties.txt is: java.util.logging.FileHandler.encoding=UTF-8 java.util.logging.ConsoleHandler.encoding=UTF-8 I am still getting outputs of echo "name='${name}'” as: ‘??????? ??????’ if the char set is not part of 1252 (e.g. for greek letters) I think I did not fully understand your hint with the logging properties. Walter *From:* Gerd Petermann <mailto:gpetermann_muenchen@hotmail.com> *Sent:* Wednesday, January 14, 2015 11:03 AM *To:* mkgmap-dev@lists.mkgmap.org.uk <mailto:mkgmap-dev@lists.mkgmap.org.uk> *Subject:* Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists Hi Walter,
reg. UTF8 in logs: When I read your post my first question was: Is he talking about the log that is written to stderr/stdout or the one that is enabled with java -Dlog.config ... -jar mkgmap.jar ...
I think the latter works fine, the first two look ugly when they write to a windows console. They also look fine when you pipe them to files like this java -Dlog.config ... -jar mkgmap.jar ... > mkgmap.stdout 2>mkgmap.stderr
Gerd
Date: Wed, 14 Jan 2015 09:15:50 +0000 From: steve@parabola.me.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8
and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8
..Steve _______________________________________________ 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
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Walter, reg. logging.properties: This feature allows to enable detailed logging to a separate file. A sample is contained in the source: mkgmap\resources\logging.properties Another sample see http://wiki.openstreetmap.org/wiki/Mkgmap/dev I am not sure if stderr/stdout can be configured. Gerd Walter Schlögl wrote
Hi Steve and Gerd,
yes, you got me right. I was talking about stderr output where echo messages are printed.
I have tried the following (under Windows):
%JavaPath% -Xmx6144m -ea -jar -Dlog.config=%OptionsPath%\logging_properties.txt %ToolPath%\mkgmap\mkgmap.jar -c %OptionsPath%\%mkgmap_options% --mapname=%mapid% --overview-mapname=%overview_mapname% --family-id=%family_id% --product-id=%product_id% --gmapsupp %mkgmap_filename% %StylesPath%\%StylesFile% 2>>%LogfileName%
content of logging_properties.txt is:
java.util.logging.FileHandler.encoding=UTF-8 java.util.logging.ConsoleHandler.encoding=UTF-8
I am still getting outputs of echo "name='${name}'” as: ‘??????? ??????’ if the char set is not part of 1252 (e.g. for greek letters)
I think I did not fully understand your hint with the logging properties.
Walter
From: Gerd Petermann Sent: Wednesday, January 14, 2015 11:03 AM To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
reg. UTF8 in logs: When I read your post my first question was: Is he talking about the log that is written to stderr/stdout or the one that is enabled with java -Dlog.config ... -jar mkgmap.jar ...
I think the latter works fine, the first two look ugly when they write to a windows console. They also look fine when you pipe them to files like this java -Dlog.config ... -jar mkgmap.jar ... > mkgmap.stdout 2>mkgmap.stderr
Gerd
Date: Wed, 14 Jan 2015 09:15:50 +0000 From:
steve@.me
To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8
and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-------------------------------------------------------------------------------- _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830037.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Bill and Gerd, I think you are right, UTF-8 is not possible in stderr output. It was just an idea for logging but no real nead for creating correct maps. Thanks for your inputs and hints. Walter -----Ursprüngliche Nachricht----- From: GerdP Sent: Wednesday, January 14, 2015 8:55 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] how to use utf-8 in stderr output Hi Walter, reg. logging.properties: This feature allows to enable detailed logging to a separate file. A sample is contained in the source: mkgmap\resources\logging.properties Another sample see http://wiki.openstreetmap.org/wiki/Mkgmap/dev I am not sure if stderr/stdout can be configured. Gerd Walter Schlögl wrote
Hi Steve and Gerd,
yes, you got me right. I was talking about stderr output where echo messages are printed.
I have tried the following (under Windows):
%JavaPath% -Xmx6144m -ea -jar -Dlog.config=%OptionsPath%\logging_properties.txt %ToolPath%\mkgmap\mkgmap.jar -c %OptionsPath%\%mkgmap_options% --mapname=%mapid% --overview-mapname=%overview_mapname% --family-id=%family_id% --product-id=%product_id% --gmapsupp %mkgmap_filename% %StylesPath%\%StylesFile% 2>>%LogfileName%
content of logging_properties.txt is:
java.util.logging.FileHandler.encoding=UTF-8 java.util.logging.ConsoleHandler.encoding=UTF-8
I am still getting outputs of echo "name='${name}'” as: ‘??????? ??????’ if the char set is not part of 1252 (e.g. for greek letters)
I think I did not fully understand your hint with the logging properties.
Walter
From: Gerd Petermann Sent: Wednesday, January 14, 2015 11:03 AM To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
reg. UTF8 in logs: When I read your post my first question was: Is he talking about the log that is written to stderr/stdout or the one that is enabled with java -Dlog.config ... -jar mkgmap.jar ...
I think the latter works fine, the first two look ugly when they write to a windows console. They also look fine when you pipe them to files like this java -Dlog.config ... -jar mkgmap.jar ... > mkgmap.stdout 2>mkgmap.stderr
Gerd
Date: Wed, 14 Jan 2015 09:15:50 +0000 From:
steve@.me
To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] Solution to show transliterated name if no other ascii name exists
Hi Walter,
It's great to hear that it is working well for you. It was just a few lines of code, perhaps no one asked before because they imagined it would be more difficult.
Do you know, if the logfile can only be written in ANSI coding, or if there is a way to use unicode for logfiles?
I don't know for sure, but make sure you have this included in your log.config file. java.util.logging.FileHandler.encoding=UTF-8
and try adding this too: java.util.logging.ConsoleHandler.encoding=UTF-8
..Steve _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-------------------------------------------------------------------------------- _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830037.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, I know I’m nasty with all my questions... Is there a way to reference to the used code-page from points file? The usecase is like that. Check, if name contains any char that cannot be shown with the selected code-page. If no, just show the name as it is. If yes, show the int_name or name:ascii only. This happens when the code-page is selected according to one specific country, but other countries on the same map would require different char-sets, and names are shown as ???? ??????. (Of course now with transliterated name additionally) In that case showing the question mark is just not nice and could be avoided. Walter
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
Hi Walter, you are right. POIs have address fields that are usually filled by mkgmap and that is what you see. Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices). WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi WanMil, thanks, so I know now that my device can show address info but no additional label info. I am trying to add specific information to the field that is normaly used for address. Is there any direct way via command or any indirect way via overrulement of special fields? I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter. Walter -----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address Hi Walter, you are right. POIs have address fields that are usually filled by mkgmap and that is what you see. Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices). WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ 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
Hi Walter, I think the POI info is filled in StyledConverter. This source snippet shows the corresponding tags: private static final short countryTagKey = TagDict.getInstance().xlate("mkgmap:country"); private static final short regionTagKey = TagDict.getInstance().xlate("mkgmap:region"); private static final short cityTagKey = TagDict.getInstance().xlate("mkgmap:city"); private static final short postal_codeTagKey = TagDict.getInstance().xlate("mkgmap:postal_code"); private static final short streetTagKey = TagDict.getInstance().xlate("mkgmap:street"); private static final short housenumberTagKey = TagDict.getInstance().xlate("mkgmap:housenumber"); private static final short phoneTagKey = TagDict.getInstance().xlate("mkgmap:phone"); Be aware that some values like mkgmap:street and mkgmap:housenumber are used for the --housenumbers option as well, and others are used for the indexes. I think the only tag that can be used for other purposes is mkgmap:phone. Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sat, 17 Jan 2015 00:24:11 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi WanMil,
thanks, so I know now that my device can show address info but no additional label info.
I am trying to add specific information to the field that is normaly used for address.
Is there any direct way via command or any indirect way via overrulement of special fields?
I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter.
Walter
-----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
you are right. POIs have address fields that are usually filled by mkgmap and that is what you see.
Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices).
WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ 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
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd, thanks for this hint, I have played around with it and was successfull in most of the cases. Here my working solutions: ok 1) If there is opening_hours set, show this info before the phone number. opening_hours=* { set mkgmap:phone=' (${opening_hours}) ${mkgmap:phone|def:}' } ok 2) If there is a website, show this info after the phone number. website=* { set mkgmap:phone='${mkgmap:phone|def:} ${website}' } In one example I was not successfull. I am generating 1-point POIs for all points where only the addr tags are set, but no other tags available. This will show all the housenumbers in low resolution. As addr info I would like to get the full addr incl. street, postcode and so on. I tried with different solutions but nothing worked, I am getting the name-tag filled but not the addr-field. Here my code: addr:housenumber=* | addr:unit=* | addr:door=* { name '${addr:unit}/${addr:door}' | '${addr:housenumber}/${addr:unit}' | '${addr:door}' | '${addr:unit}' | '${addr:housenumber}'; set addr:postcode='${addr:street|def:} ${addr:housenumber|def:} ${addr:postcode|def:} ${addr:city|def:} ${addr:country|def:}' } [0x1e04 resolution 24] The first part is working fine, I can see the housenumber or unit + door on all buildings and also as point if there is no building. The second part is not working, the postcode tag is not written into the addr-field. Is there any restriction with the addr-field of the POI-info if no other tags are available than the addr:xxx tags? Walter From: Gerd Petermann Sent: Saturday, January 17, 2015 7:40 AM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] difference between addlabel and poi-address Hi Walter, I think the POI info is filled in StyledConverter. This source snippet shows the corresponding tags: private static final short countryTagKey = TagDict.getInstance().xlate("mkgmap:country"); private static final short regionTagKey = TagDict.getInstance().xlate("mkgmap:region"); private static final short cityTagKey = TagDict.getInstance().xlate("mkgmap:city"); private static final short postal_codeTagKey = TagDict.getInstance().xlate("mkgmap:postal_code"); private static final short streetTagKey = TagDict.getInstance().xlate("mkgmap:street"); private static final short housenumberTagKey = TagDict.getInstance().xlate("mkgmap:housenumber"); private static final short phoneTagKey = TagDict.getInstance().xlate("mkgmap:phone"); Be aware that some values like mkgmap:street and mkgmap:housenumber are used for the --housenumbers option as well, and others are used for the indexes. I think the only tag that can be used for other purposes is mkgmap:phone. Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sat, 17 Jan 2015 00:24:11 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi WanMil,
thanks, so I know now that my device can show address info but no additional label info.
I am trying to add specific information to the field that is normaly used for address.
Is there any direct way via command or any indirect way via overrulement of special fields?
I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter.
Walter
-----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
you are right. POIs have address fields that are usually filled by mkgmap and that is what you see.
Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices).
WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ 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
_______________________________________________ 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
Hi Walter, setting addr:postcode has no effect on POIs as long as you don't use that info to set also mkgmap:postal_code. Gerd Walter Schlögl wrote
Hi Gerd,
thanks for this hint, I have played around with it and was successfull in most of the cases.
Here my working solutions:
ok 1) If there is opening_hours set, show this info before the phone number.
opening_hours=* { set mkgmap:phone=' (${opening_hours}) ${mkgmap:phone|def:}' }
ok 2) If there is a website, show this info after the phone number.
website=* { set mkgmap:phone='${mkgmap:phone|def:} ${website}' }
In one example I was not successfull. I am generating 1-point POIs for all points where only the addr tags are set, but no other tags available. This will show all the housenumbers in low resolution. As addr info I would like to get the full addr incl. street, postcode and so on. I tried with different solutions but nothing worked, I am getting the name-tag filled but not the addr-field.
Here my code:
addr:housenumber=* | addr:unit=* | addr:door=* { name '${addr:unit}/${addr:door}' | '${addr:housenumber}/${addr:unit}' | '${addr:door}' | '${addr:unit}' | '${addr:housenumber}'; set addr:postcode='${addr:street|def:} ${addr:housenumber|def:} ${addr:postcode|def:} ${addr:city|def:} ${addr:country|def:}' } [0x1e04 resolution 24]
The first part is working fine, I can see the housenumber or unit + door on all buildings and also as point if there is no building. The second part is not working, the postcode tag is not written into the addr-field.
Is there any restriction with the addr-field of the POI-info if no other tags are available than the addr:xxx tags?
Walter
From: Gerd Petermann Sent: Saturday, January 17, 2015 7:40 AM To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
I think the POI info is filled in StyledConverter. This source snippet shows the corresponding tags: private static final short countryTagKey = TagDict.getInstance().xlate("mkgmap:country"); private static final short regionTagKey = TagDict.getInstance().xlate("mkgmap:region"); private static final short cityTagKey = TagDict.getInstance().xlate("mkgmap:city"); private static final short postal_codeTagKey = TagDict.getInstance().xlate("mkgmap:postal_code"); private static final short streetTagKey = TagDict.getInstance().xlate("mkgmap:street"); private static final short housenumberTagKey = TagDict.getInstance().xlate("mkgmap:housenumber"); private static final short phoneTagKey = TagDict.getInstance().xlate("mkgmap:phone");
Be aware that some values like mkgmap:street and mkgmap:housenumber are used for the --housenumbers option as well, and others are used for the indexes. I think the only tag that can be used for other purposes is mkgmap:phone.
Gerd
From:
Walter.Schloegl-Resch@
To:
mkgmap-dev@.org
Date: Sat, 17 Jan 2015 00:24:11 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi WanMil,
thanks, so I know now that my device can show address info but no additional label info.
I am trying to add specific information to the field that is normaly used for address.
Is there any direct way via command or any indirect way via overrulement of special fields?
I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter.
Walter
-----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
you are right. POIs have address fields that are usually filled by mkgmap and that is what you see.
Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices).
WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-------------------------------------------------------------------------------- _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830423.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, I have tried with { set mkgmap:postal_code=... } but it's also not working. Since all POIs are getting the address automatically, I do not understand why the pure address POI is not getting it in the same way. With this code (and the option --poi-address): addr:housenumber=* { name '${addr:housenumber}' } [0x1e04 resolution 24] I would expect, that 0x1e04 is a POI with the name equal to housenumber (e.g. 19) and an address field filled with "Street 19, 1234 City" Setting some special mkgmap fields with the address manually would be just a workaround, if the address is not working for pure address POIs. Otherwise it would be better, if I could find the original error that I'm making. Walter -----Ursprüngliche Nachricht----- From: GerdP Sent: Sunday, January 18, 2015 1:05 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] difference between addlabel and poi-address Hi Walter, setting addr:postcode has no effect on POIs as long as you don't use that info to set also mkgmap:postal_code. Gerd Walter Schlögl wrote
Hi Gerd,
thanks for this hint, I have played around with it and was successfull in most of the cases.
Here my working solutions:
ok 1) If there is opening_hours set, show this info before the phone number.
opening_hours=* { set mkgmap:phone=' (${opening_hours}) ${mkgmap:phone|def:}' }
ok 2) If there is a website, show this info after the phone number.
website=* { set mkgmap:phone='${mkgmap:phone|def:} ${website}' }
In one example I was not successfull. I am generating 1-point POIs for all points where only the addr tags are set, but no other tags available. This will show all the housenumbers in low resolution. As addr info I would like to get the full addr incl. street, postcode and so on. I tried with different solutions but nothing worked, I am getting the name-tag filled but not the addr-field.
Here my code:
addr:housenumber=* | addr:unit=* | addr:door=* { name '${addr:unit}/${addr:door}' | '${addr:housenumber}/${addr:unit}' | '${addr:door}' | '${addr:unit}' | '${addr:housenumber}'; set addr:postcode='${addr:street|def:} ${addr:housenumber|def:} ${addr:postcode|def:} ${addr:city|def:} ${addr:country|def:}' } [0x1e04 resolution 24]
The first part is working fine, I can see the housenumber or unit + door on all buildings and also as point if there is no building. The second part is not working, the postcode tag is not written into the addr-field.
Is there any restriction with the addr-field of the POI-info if no other tags are available than the addr:xxx tags?
Walter
From: Gerd Petermann Sent: Saturday, January 17, 2015 7:40 AM To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
I think the POI info is filled in StyledConverter. This source snippet shows the corresponding tags: private static final short countryTagKey = TagDict.getInstance().xlate("mkgmap:country"); private static final short regionTagKey = TagDict.getInstance().xlate("mkgmap:region"); private static final short cityTagKey = TagDict.getInstance().xlate("mkgmap:city"); private static final short postal_codeTagKey = TagDict.getInstance().xlate("mkgmap:postal_code"); private static final short streetTagKey = TagDict.getInstance().xlate("mkgmap:street"); private static final short housenumberTagKey = TagDict.getInstance().xlate("mkgmap:housenumber"); private static final short phoneTagKey = TagDict.getInstance().xlate("mkgmap:phone");
Be aware that some values like mkgmap:street and mkgmap:housenumber are used for the --housenumbers option as well, and others are used for the indexes. I think the only tag that can be used for other purposes is mkgmap:phone.
Gerd
From:
Walter.Schloegl-Resch@
To:
mkgmap-dev@.org
Date: Sat, 17 Jan 2015 00:24:11 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi WanMil,
thanks, so I know now that my device can show address info but no additional label info.
I am trying to add specific information to the field that is normaly used for address.
Is there any direct way via command or any indirect way via overrulement of special fields?
I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter.
Walter
-----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
you are right. POIs have address fields that are usually filled by mkgmap and that is what you see.
Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices).
WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-------------------------------------------------------------------------------- _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830423.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Walter, I see that mkgmap fills the address info, and it also seems to write it, but MapSource seems to ignore it. I have no experience with this. Maybe this happens because of the big number of POIs? Gerd
From: Walter.Schloegl-Resch@aon.at To: mkgmap-dev@lists.mkgmap.org.uk Date: Sun, 18 Jan 2015 15:21:35 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Gerd,
I have tried with { set mkgmap:postal_code=... } but it's also not working.
Since all POIs are getting the address automatically, I do not understand why the pure address POI is not getting it in the same way.
With this code (and the option --poi-address):
addr:housenumber=* { name '${addr:housenumber}' } [0x1e04 resolution 24]
I would expect, that 0x1e04 is a POI with the name equal to housenumber (e.g. 19) and an address field filled with "Street 19, 1234 City"
Setting some special mkgmap fields with the address manually would be just a workaround, if the address is not working for pure address POIs.
Otherwise it would be better, if I could find the original error that I'm making.
Walter
-----Ursprüngliche Nachricht----- From: GerdP Sent: Sunday, January 18, 2015 1:05 PM To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
setting addr:postcode has no effect on POIs as long as you don't use that info to set also mkgmap:postal_code.
Gerd
Walter Schlögl wrote
Hi Gerd,
thanks for this hint, I have played around with it and was successfull in most of the cases.
Here my working solutions:
ok 1) If there is opening_hours set, show this info before the phone number.
opening_hours=* { set mkgmap:phone=' (${opening_hours}) ${mkgmap:phone|def:}' }
ok 2) If there is a website, show this info after the phone number.
website=* { set mkgmap:phone='${mkgmap:phone|def:} ${website}' }
In one example I was not successfull. I am generating 1-point POIs for all points where only the addr tags are set, but no other tags available. This will show all the housenumbers in low resolution. As addr info I would like to get the full addr incl. street, postcode and so on. I tried with different solutions but nothing worked, I am getting the name-tag filled but not the addr-field.
Here my code:
addr:housenumber=* | addr:unit=* | addr:door=* { name '${addr:unit}/${addr:door}' | '${addr:housenumber}/${addr:unit}' | '${addr:door}' | '${addr:unit}' | '${addr:housenumber}'; set addr:postcode='${addr:street|def:} ${addr:housenumber|def:} ${addr:postcode|def:} ${addr:city|def:} ${addr:country|def:}' } [0x1e04 resolution 24]
The first part is working fine, I can see the housenumber or unit + door on all buildings and also as point if there is no building. The second part is not working, the postcode tag is not written into the addr-field.
Is there any restriction with the addr-field of the POI-info if no other tags are available than the addr:xxx tags?
Walter
From: Gerd Petermann Sent: Saturday, January 17, 2015 7:40 AM To:
mkgmap-dev@.org
Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
I think the POI info is filled in StyledConverter. This source snippet shows the corresponding tags: private static final short countryTagKey = TagDict.getInstance().xlate("mkgmap:country"); private static final short regionTagKey = TagDict.getInstance().xlate("mkgmap:region"); private static final short cityTagKey = TagDict.getInstance().xlate("mkgmap:city"); private static final short postal_codeTagKey = TagDict.getInstance().xlate("mkgmap:postal_code"); private static final short streetTagKey = TagDict.getInstance().xlate("mkgmap:street"); private static final short housenumberTagKey = TagDict.getInstance().xlate("mkgmap:housenumber"); private static final short phoneTagKey = TagDict.getInstance().xlate("mkgmap:phone");
Be aware that some values like mkgmap:street and mkgmap:housenumber are used for the --housenumbers option as well, and others are used for the indexes. I think the only tag that can be used for other purposes is mkgmap:phone.
Gerd
From:
Walter.Schloegl-Resch@
To:
mkgmap-dev@.org
Date: Sat, 17 Jan 2015 00:24:11 +0100 Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi WanMil,
thanks, so I know now that my device can show address info but no additional label info.
I am trying to add specific information to the field that is normaly used for address.
Is there any direct way via command or any indirect way via overrulement of special fields?
I found one exampe 4.5 on page 29 of the Style rules docu, but this is only showing how to overrule the postcode parameter.
Walter
-----Ursprüngliche Nachricht----- From: WanMil Sent: Friday, January 16, 2015 10:16 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address
Hi Walter,
you are right. POIs have address fields that are usually filled by mkgmap and that is what you see.
Each POI also have 4 label fields but usually only the first label is shown (but that might also differ between differnent devices).
WanMil
I’m not sure but I think I am mixing 2 things up. When I enable poi-address I can see the address field of the POI filled with the address on my Oregon device. When I set no-poi-address and try to fill the address field individually by using addlabel, and do not see these labels in the POI address field. Maybe addlabel is filling total different fields not available on my Oregon. Can anybody approve my assumption? Is it right, that the Oregan is not displaying the 4 addlabel fields? Walter
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-------------------------------------------------------------------------------- _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/elevation-data-tp5828381p5830423.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ 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
Gerd wrote:
I see that mkgmap fills the address info, and it also seems to write it, but MapSource seems to ignore it. I have no experience with this. Maybe this happens because of the big number of POIs?
Yes, not all pois are capable of showing address data, please check this extensive spreadsheet from Charlie Ferrero: http://www.cferrero.net/maps/downloads/garmin_feature_list.xls His website might be a little out of date but still contains a lot of useful info for garmin map makers: http://www.cferrero.net/maps/maps_index.html
Hi Minko and Gerd, yes you are right, this is a restriction of the Garmin POIs. This spreadsheet was a good tip, I did not know it yet. Unfortunately there is no POI group with text display, not supressing the address info. I have tried it with a trick, using 2 POIs, one with text display and another with address info. The Garmin device is showing a memory full message and the hole map is not shown. So I'm leaving it as it is without any more tries. Just one small clarification about the address field. If I set --poi-address than the address field is filled by mkgmap and I can manipulate the content using the trick with mkgmap:phone. If I set --no-poi-address than the address field is left blank by mkgmap and I also cannot fill it with any command via the style file. I hope I understood this correct. At last I would like to report one optical issue in --poi-address generation: There is a line break between street and postcode, but no line break between city and phone. e.g. Street Nr postcode, city+49 123 4567 It would be much nicer, to display the address field with one more line break. Street Nr postcode, city +49 123 4567 If someone is spending the effort in changing this, maybe a small enhancement could also be done. Would it make sense to add unit (maybe even door, if available) to housenumber? addr:housenumber/addr:unit/addr:door Walter -----Ursprüngliche Nachricht----- From: Minko Sent: Sunday, January 18, 2015 5:07 PM To: Development list for mkgmap Subject: Re: [mkgmap-dev] difference between addlabel and poi-address Gerd wrote:
I see that mkgmap fills the address info, and it also seems to write it, but MapSource seems to ignore it. I have no experience with this. Maybe this happens because of the big number of POIs?
Yes, not all pois are capable of showing address data, please check this extensive spreadsheet from Charlie Ferrero: http://www.cferrero.net/maps/downloads/garmin_feature_list.xls His website might be a little out of date but still contains a lot of useful info for garmin map makers: http://www.cferrero.net/maps/maps_index.html _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Walter,
Just one small clarification about the address field.
If I set --poi-address than the address field is filled by mkgmap and I can manipulate the content using the trick with mkgmap:phone.
If I set --no-poi-address than the address field is left blank by mkgmap and I also cannot fill it with any command via the style file.
I hope I understood this correct. yes, just one hint: --poi-address is the default
At last I would like to report one optical issue in --poi-address generation: There is a line break between street and postcode, but no line break between city and phone.
e.g. Street Nr postcode, city+49 123 4567
It would be much nicer, to display the address field with one more line break. Street Nr postcode, city +49 123 4567
If someone is spending the effort in changing this, maybe a small enhancement could also be done.
The formatting is done by the Garmin software, not by mkgmap. It just fills individual fields and we have a few flags for the whole tile to say how to format them. These flags are configured in resources/LocatorConfig.xml , e.g. Island (and Germany) have streetBeforeHousenumber="true" postalcodeBeforeCity="true"
Would it make sense to add unit (maybe even door, if available) to housenumber? addr:housenumber/addr:unit/addr:door
Well, the current code for the --housenumbers option will treat a housenumber like "3/5/3" like "3", so I think you can do that in the style. Gerd
participants (12)
-
Andrzej Popowski -
Bill -
Enrico Liboni -
Felix Hartmann -
Gerd Petermann -
GerdP
-
Marko Mäkelä -
Mike Baggaley -
Minko -
Steve Ratcliffe -
Walter Schlögl -
WanMil