I was successfully building maps for a Montana with my own style. Since the Montana died, I replaced it with a Zumo XT. It isn't working so well now. I can use my map on qmapshack and it looks as expected, but on the Zumo it appears that Garmin does not recognize some (or all) my custom type codes. Any ideas what the limitations are, or how to work with this? They've added something called 'Map Theme', which is a small xml file. I don't see a way to load my typ file, but I didn't need to do that before since I included that with the mkgmap build. Brad
Have a look at www.javawa.nl or https://www.pinns.co.uk/osm/theme_editor.html <https://www.pinns.co.uk/osm/theme_editor.html> Although themes are text files, Garmin is particularly fussy about certain text characters and a surplus of spaces. When you modify them manually you may find the theme is not recognized. To a certain extent it is a matter of trial and error when converting a typ file to a theme, ie the theme only recognizes a limited number of types. Typwiz6 can convert TYP files to themes - there may be others Themes are saved in Garmin/themes folder Good Luck Nick <https://www.javawa.nl/zumocolors.html> <https://www.javawa.nl/zumocolors.html> <https://www.javawa.nl/zumocolors.html> On 25/07/2020 15:37, brad wrote:
I was successfully building maps for a Montana with my own style. Since the Montana died, I replaced it with a Zumo XT. It isn't working so well now. I can use my map on qmapshack and it looks as expected, but on the Zumo it appears that Garmin does not recognize some (or all) my custom type codes. Any ideas what the limitations are, or how to work with this? They've added something called 'Map Theme', which is a small xml file. I don't see a way to load my typ file, but I didn't need to do that before since I included that with the mkgmap build. Brad
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
I took a look at those, thx. Unfortunately they don't really tell you what feature you're editing if you've created a map with mkgmap. typwiz is a windows program, which doesn't work for me. What I determined is that these typ codes don't work : 0x2c, 2f, 10101, 2d, 33 These work as expected: 0x2a, 0x02, 0x01, 13 The theme file has names such as MAP_PLTCL_INTL_CLR, MAP_ROAD_RESIDENTIAL_CLR and MAP_ROAD_RESIDENTIAL_CLR. Perhaps these translate to a typ code, and overwrite what is coded by mkgmap? On 7/25/20 9:14 AM, nick wrote:
Have a look at
www.javawa.nl
or
https://www.pinns.co.uk/osm/theme_editor.html
Although themes are text files, Garmin is particularly fussy about certain text characters and a surplus of spaces. When you modify them manually
you may find the theme is not recognized.
To a certain extent it is a matter of trial and error when converting a typ file to a theme, ie the theme only recognizes a limited number of types.
Typwiz6 can convert TYP files to themes - there may be others
Themes are saved in Garmin/themes folder
Good Luck
Nick
<https://www.javawa.nl/zumocolors.html>
<https://www.javawa.nl/zumocolors.html> <https://www.javawa.nl/zumocolors.html> On 25/07/2020 15:37, brad wrote:
I was successfully building maps for a Montana with my own style. Since the Montana died, I replaced it with a Zumo XT. It isn't working so well now. I can use my map on qmapshack and it looks as expected, but on the Zumo it appears that Garmin does not recognize some (or all) my custom type codes. Any ideas what the limitations are, or how to work with this? They've added something called 'Map Theme', which is a small xml file. I don't see a way to load my typ file, but I didn't need to do that before since I included that with the mkgmap build. Brad
_______________________________________________ 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
Yes delete (backup before) the map themes file, it's overriding the .typ However there is an only editor for it somewhere, forgot the location right now. On Fri, 31 Jul 2020, 05:58 brad <bradhaack@fastmail.com> wrote:
I took a look at those, thx. Unfortunately they don't really tell you what feature you're editing if you've created a map with mkgmap. typwiz is a windows program, which doesn't work for me.
What I determined is that these typ codes don't work : 0x2c, 2f, 10101, 2d, 33 These work as expected: 0x2a, 0x02, 0x01, 13
The theme file has names such as MAP_PLTCL_INTL_CLR, MAP_ROAD_RESIDENTIAL_CLR and MAP_ROAD_RESIDENTIAL_CLR. Perhaps these translate to a typ code, and overwrite what is coded by mkgmap?
On 7/25/20 9:14 AM, nick wrote:
Have a look at
www.javawa.nl
or
https://www.pinns.co.uk/osm/theme_editor.html
Although themes are text files, Garmin is particularly fussy about certain text characters and a surplus of spaces. When you modify them manually
you may find the theme is not recognized.
To a certain extent it is a matter of trial and error when converting a typ file to a theme, ie the theme only recognizes a limited number of types.
Typwiz6 can convert TYP files to themes - there may be others
Themes are saved in Garmin/themes folder
Good Luck
Nick
<https://www.javawa.nl/zumocolors.html>
<https://www.javawa.nl/zumocolors.html> <https://www.javawa.nl/zumocolors.html> On 25/07/2020 15:37, brad wrote:
I was successfully building maps for a Montana with my own style. Since the Montana died, I replaced it with a Zumo XT. It isn't working so well now. I can use my map on qmapshack and it looks as expected, but on the Zumo it appears that Garmin does not recognize some (or all) my custom type codes. Any ideas what the limitations are, or how to work with this? They've added something called 'Map Theme', which is a small xml file. I don't see a way to load my typ file, but I didn't need to do that before since I included that with the mkgmap build. Brad
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing listmkgmap-dev@lists.mkgmap.org.ukhttp://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
Even if I load a theme file with nothing in it, it doesn't seem to matter. I have worked out a set of typ codes for the roads and trails that work. Now I'm looking at points (POI), and I'm getting almost nothing on the Zumo. The only POI I'm getting is a WC using the Openfietsmap_full style & mapnik typ. Ticker Berkin posted a while back about a test map, this sounds useful, so I generated a map with this: java -jar ~/Apps/Mkgmap/mkgmap-r4565/mkgmap.jar --gmapsupp --verbose --order-by-decreasing-area test-map:all-elements ~/Apps/Mkgmap/mkgmap-r4565/examples/typ-files/sameOrder.txt But I must be missing something because that doesn't show any POI's on Qmapshack on my desktop, and the polygons are messed up. Is this feature documented anywhere? Any help is appreciated. On 7/31/20 1:08 AM, Felix Hartmann wrote:
Yes delete (backup before) the map themes file, it's overriding the .typ However there is an only editor for it somewhere, forgot the location right now.
On Fri, 31 Jul 2020, 05:58 brad <bradhaack@fastmail.com <mailto:bradhaack@fastmail.com>> wrote:
I took a look at those, thx. Unfortunately they don't really tell you what feature you're editing if you've created a map with mkgmap. typwiz is a windows program, which doesn't work for me.
What I determined is that these typ codes don't work : 0x2c, 2f, 10101, 2d, 33 These work as expected: 0x2a, 0x02, 0x01, 13
The theme file has names such as MAP_PLTCL_INTL_CLR, MAP_ROAD_RESIDENTIAL_CLR and MAP_ROAD_RESIDENTIAL_CLR. Perhaps these translate to a typ code, and overwrite what is coded by mkgmap?
On 7/25/20 9:14 AM, nick wrote:
Have a look at
www.javawa.nl <http://www.javawa.nl>
or
https://www.pinns.co.uk/osm/theme_editor.html
Although themes are text files, Garmin is particularly fussy about certain text characters and a surplus of spaces. When you modify them manually
you may find the theme is not recognized.
To a certain extent it is a matter of trial and error when converting a typ file to a theme, ie the theme only recognizes a limited number of types.
Typwiz6 can convert TYP files to themes - there may be others
Themes are saved in Garmin/themes folder
Good Luck
Nick
<https://www.javawa.nl/zumocolors.html>
<https://www.javawa.nl/zumocolors.html> <https://www.javawa.nl/zumocolors.html> On 25/07/2020 15:37, brad wrote:
I was successfully building maps for a Montana with my own style. Since the Montana died, I replaced it with a Zumo XT. It isn't working so well now. I can use my map on qmapshack and it looks as expected, but on the Zumo it appears that Garmin does not recognize some (or all) my custom type codes. Any ideas what the limitations are, or how to work with this? They've added something called 'Map Theme', which is a small xml file. I don't see a way to load my typ file, but I didn't need to do that before since I included that with the mkgmap build. Brad
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk <mailto: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 <mailto: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 <mailto: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 Brad test-map:all-elements isn't documented except in it's source: https://svn.mkgmap.org.uk/mkgmap/mkgmap/trunk/src/uk/me/parabola/mkgmap /reader/test/AllElements.java It generates a map with blocks of POI, lines and polygons, both named and unnamed. You might need to zoom in to see things. The TYP file sameOrder.txt does not supply any icons; maybe Qmapshack doesn't either - I've never used it. It does non-obvious things like using a non-standard background for half the above blocks and no background for the others, ie like a transparent map. This required setting POI_FLAG_TRANSPARENT for the test map to be displayed on the devices I tried. Maybe qmapshack has a different understanding. How are the polygons messed up? I don't know anything about zumo/themes - sorry. Ticker On Thu, 2020-08-06 at 16:10 -0600, brad wrote:
Even if I load a theme file with nothing in it, it doesn't seem to matter. I have worked out a set of typ codes for the roads and trails that work. Now I'm looking at points (POI), and I'm getting almost nothing on the Zumo. The only POI I'm getting is a WC using the Openfietsmap_full style & mapnik typ.
Ticker Berkin posted a while back about a test map, this sounds useful, so I generated a map with this: java -jar ~/Apps/Mkgmap/mkgmap-r4565/mkgmap.jar --gmapsupp --verbose --order-by-decreasing-area test-map:all-elements ~/Apps/Mkgmap/mkgmap -r4565/examples/typ-files/sameOrder.txt But I must be missing something because that doesn't show any POI's on Qmapshack on my desktop, and the polygons are messed up. Is this feature documented anywhere?
Any help is appreciated.
Hi, all! First, note the attached file is in JSON format and is inherently UTF-8. Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations. Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values. Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file. Thank you, Randolph J. Herber
Hi I'm interested to learn the source you used for language codes > &0x2F . As far as I know Garmin only uses codes up to 0x2E Regards Nick On 08/08/2020 21:42, Randolph J. Herber wrote:
Hi, all!
First, note the attached file is in JSON format and is inherently UTF-8.
Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations.
Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values.
Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file.
Thank you, Randolph J. Herber
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Dear, Sir: Apparently, I did not make myself sufficiently clear. I apologize. First, I request the codes from 0x23 to 0x2e so that I can assign the correct languages to those codes. Second, and I quote myself: "I arbitrarily assigned codes for the other languages." I see two uses for the table I provided. First, for someone that does not use a language whose code is 0x01 to 0x22 to use one of the "extra" languages to fill slot 0x00 or, in fact, any of the slots to have a more comfortable language in their Garmin receiver. Second, for some who does not not want to do a language re-assignment, to find translations from a more comfortable language to one of the Garmin "official" languages. In no way to I contradict your statement: "As far as I know Garmin only uses codes up to 0x2E." As I said before: "I request consideration: I intend no offense and corrections are welcome." Sincerely, Randolph J. Herber On 8/9/2020 4:41 AM, nick wrote:
Hi
I'm interested to learn the source you used for language codes > &0x2F .
As far as I know Garmin only uses codes up to 0x2E
Regards
Nick
On 08/08/2020 21:42, Randolph J. Herber wrote:
Hi, all!
First, note the attached file is in JSON format and is inherently UTF-8.
Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations.
Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values.
Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file.
Thank you, Randolph J. Herber
_______________________________________________ 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
I can help you with 0x23 - 2e "0x23 brazilian" "0x24 korean" "0x25 japanese" "0x26 chinese" "0x27 trad. chinese" "0x28 thai" "0x29 arabic" "0x2a belarusian" "0x2b ukrainian" "0x2c moldavian" "0x2d montenegrin" "0x2e Irish" r. Nick On 09/08/2020 13:09, Randolph J. Herber wrote:
Dear, Sir:
Apparently, I did not make myself sufficiently clear. I apologize. First, I request the codes from 0x23 to 0x2e so that I can assign the correct languages to those codes. Second, and I quote myself: "I arbitrarily assigned codes for the other languages."
I see two uses for the table I provided. First, for someone that does not use a language whose code is 0x01 to 0x22 to use one of the "extra" languages to fill slot 0x00 or, in fact, any of the slots to have a more comfortable language in their Garmin receiver. Second, for some who does not not want to do a language re-assignment, to find translations from a more comfortable language to one of the Garmin "official" languages.
In no way to I contradict your statement: "As far as I know Garmin only uses codes up to 0x2E."
As I said before: "I request consideration: I intend no offense and corrections are welcome."
Sincerely, Randolph J. Herber
On 8/9/2020 4:41 AM, nick wrote:
Hi
I'm interested to learn the source you used for language codes > &0x2F .
As far as I know Garmin only uses codes up to 0x2E
Regards
Nick
On 08/08/2020 21:42, Randolph J. Herber wrote:
Hi, all!
First, note the attached file is in JSON format and is inherently UTF-8.
Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations.
Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values.
Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file.
Thank you, Randolph J. Herber
_______________________________________________ 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, 0x23 is Brazilian Portuguese. It is similar, but not equal, to '0x0b Portuguese'. Best regards, Alexandre On 09/08/2020 09:29, nick wrote:
I can help you with 0x23 - 2e
"0x23 brazilian" "0x24 korean" "0x25 japanese" "0x26 chinese" "0x27 trad. chinese" "0x28 thai" "0x29 arabic" "0x2a belarusian" "0x2b ukrainian" "0x2c moldavian" "0x2d montenegrin" "0x2e Irish"
r.
Nick
On 09/08/2020 13:09, Randolph J. Herber wrote:
Dear, Sir:
Apparently, I did not make myself sufficiently clear. I apologize. First, I request the codes from 0x23 to 0x2e so that I can assign the correct languages to those codes. Second, and I quote myself: "I arbitrarily assigned codes for the other languages."
I see two uses for the table I provided. First, for someone that does not use a language whose code is 0x01 to 0x22 to use one of the "extra" languages to fill slot 0x00 or, in fact, any of the slots to have a more comfortable language in their Garmin receiver. Second, for some who does not not want to do a language re-assignment, to find translations from a more comfortable language to one of the Garmin "official" languages.
In no way to I contradict your statement: "As far as I know Garmin only uses codes up to 0x2E."
As I said before: "I request consideration: I intend no offense and corrections are welcome."
Sincerely, Randolph J. Herber
On 8/9/2020 4:41 AM, nick wrote:
Hi
I'm interested to learn the source you used for language codes > &0x2F .
As far as I know Garmin only uses codes up to 0x2E
Regards
Nick
On 08/08/2020 21:42, Randolph J. Herber wrote:
Hi, all!
First, note the attached file is in JSON format and is inherently UTF-8.
Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations.
Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values.
Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file.
Thank you, Randolph J. Herber
_______________________________________________ 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
Dear, Sirs: nick at Pinns, UK, pointed out that Garmin had other assigned language codes than those in the mkgmap documentation that I found and supplied me the additional codes and language pairs. I note that three of the languages Google Translate does not have. Those codes have been left unused. Brazilian is Portuguese in the sense that British and American are both English. There is a Portuguese translation in the set. Moldavian is Romanian in Cyrillic letters and there is a Romanian translation in the set. Montenegrin is not present at Google; but, both Serbian and Croatian are present in the set. These are closely related languages and may be mutually intelligible with Montenegrin. The other languages common to Garmin and Google were given their Garmin assigned codes. The remaining languages were given codes at 0x40 and above to move them away from the Garmin codes. Sincerlely, Randolph J. Herber On 8/9/2020 4:41 AM, nick wrote:
On 08/08/2020 21:42, Randolph J. Herber wrote:
Hi, all!
First, note the attached file is in JSON format and is inherently UTF-8.
Second, the file contains four sub-tables: point, line, polygon, and language. The first three should be obvious. The language sub-table contains the languages presented. I used the extant codes for the extant languages mentioned in the mkgmap web documentation. I arbitrarily assigned codes for the other languages. Altogether, one hundred three languages are presented. I used Google Translate and am paying for Google's services here. Therefore, this is work-for-hire and I may give them away. Yes, I readily admit some of translations are awkward or even incorrect. There, I request consideration: I intend no offense and corrections are welcome. I tended not to change Eurocentric terms to American terms although in some cases I added the equivalent American term. I expanded some of the phrases in hopes of improving the machine translations.
Third, I feel that all urban areas should be treated equivalently and I note Ticker Berkin's previous comments on that topic, the translations reflect my preferences. I did incorporate Ticker's most significant objection which I did find valid. Also, I feel that an logarithmic scale is appropriate in this application and that 3.2*3.2 is 10.24, which is about 10. This allows a good range of population values.
Fourth, I am working on incorporating this material into the default style and typ files, in particular the typ file.
Thank you, Randolph J. Herber
_______________________________________________ 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
Thanks Ticker That helped a lot. What I learned is that the Zumo does not like any custom types for points. I tested it with my typ file and the mapnik one. If there is something in the type file, nothing shows up on the zumo for that type code. It does show me what the garmin icons are, so I'll have to work with that. It really unfortunate, lesson learned: don't buy a zumo. Brad On 8/7/20 4:42 AM, Ticker Berkin wrote:
Hi Brad
test-map:all-elements isn't documented except in it's source:
https://svn.mkgmap.org.uk/mkgmap/mkgmap/trunk/src/uk/me/parabola/mkgmap/read...
It generates a map with blocks of POI, lines and polygons, both named and unnamed.
You might need to zoom in to see things.
The TYP file sameOrder.txt does not supply any icons; maybe Qmapshack doesn't either - I've never used it.
It does non-obvious things like using a non-standard background for half the above blocks and no background for the others, ie like a transparent map. This required setting POI_FLAG_TRANSPARENT for the test map to be displayed on the devices I tried. Maybe qmapshack has a different understanding.
How are the polygons messed up?
I don't know anything about zumo/themes - sorry.
Ticker
On Thu, 2020-08-06 at 16:10 -0600, brad wrote:
Even if I load a theme file with nothing in it, it doesn't seem to matter. I have worked out a set of typ codes for the roads and trails that work. Now I'm looking at points (POI), and I'm getting almost nothing on the Zumo. The only POI I'm getting is a WC using the Openfietsmap_full style & mapnik typ.
Ticker Berkin posted a while back about a test map, this sounds useful, so I generated a map with this: java -jar ~/Apps/Mkgmap/mkgmap-r4565/mkgmap.jar --gmapsupp --verbose --order-by-decreasing-area test-map:all-elements ~/Apps/Mkgmap/mkgmap-r4565/examples/typ-files/sameOrder.txt But I must be missing something because that doesn't show any POI's on Qmapshack on my desktop, and the polygons are messed up. Is this feature documented anywhere?
Any help is appreciated.
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Brad I don't know anything about Zumos but if it uses themes I suspect pois are kept in a gpi file, Garmin/Poi I have a Garmin Drive of some sorts and have added all my points in various gpi files. Bitmaps have to be .bmp but canbe any width or height (this applies to recent devices) More info and screen shot : https://www.pinns.co.uk/osm/gpi.html <https://www.pinns.co.uk/osm/gpi.html> Perhaps check out various Zumo forums , ie https://www.zumouserforums.co.uk/ <https://www.zumouserforums.co.uk/> r Nick On 10/08/2020 02:59, brad wrote:
Thanks Ticker That helped a lot. What I learned is that the Zumo does not like any custom types for points. I tested it with my typ file and the mapnik one. If there is something in the type file, nothing shows up on the zumo for that type code. It does show me what the garmin icons are, so I'll have to work with that. It really unfortunate, lesson learned: don't buy a zumo. Brad
On 8/7/20 4:42 AM, Ticker Berkin wrote:
Hi Brad
test-map:all-elements isn't documented except in it's source:
https://svn.mkgmap.org.uk/mkgmap/mkgmap/trunk/src/uk/me/parabola/mkgmap/read... <https://svn.mkgmap.org.uk/mkgmap/mkgmap/trunk/src/uk/me/parabola/mkgmap/reader/test/AllElements.java>
It generates a map with blocks of POI, lines and polygons, both named and unnamed.
You might need to zoom in to see things.
The TYP file sameOrder.txt does not supply any icons; maybe Qmapshack doesn't either - I've never used it.
It does non-obvious things like using a non-standard background for half the above blocks and no background for the others, ie like a transparent map. This required setting POI_FLAG_TRANSPARENT for the test map to be displayed on the devices I tried. Maybe qmapshack has a different understanding.
How are the polygons messed up?
I don't know anything about zumo/themes - sorry.
Ticker
On Thu, 2020-08-06 at 16:10 -0600, brad wrote:
Even if I load a theme file with nothing in it, it doesn't seem to matter. I have worked out a set of typ codes for the roads and trails that work. Now I'm looking at points (POI), and I'm getting almost nothing on the Zumo. The only POI I'm getting is a WC using the Openfietsmap_full style & mapnik typ.
Ticker Berkin posted a while back about a test map, this sounds useful, so I generated a map with this: java -jar ~/Apps/Mkgmap/mkgmap-r4565/mkgmap.jar --gmapsupp --verbose --order-by-decreasing-area test-map:all-elements ~/Apps/Mkgmap/mkgmap-r4565/examples/typ-files/sameOrder.txt But I must be missing something because that doesn't show any POI's on Qmapshack on my desktop, and the polygons are messed up. Is this feature documented anywhere?
Any help is appreciated.
_______________________________________________ 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
Thanks from me too. I currently have two Garmin Montanas but have always been curious about the more modern Zumo models. I can put that issue to rest now because I make my own maps with mkgmap. It's tricky enough getting everything right with a Garmin GPS that behaves "normally". My Montana works well enough to do what I want with it. On Mon, Aug 10, 2020 at 8:59 AM brad <bradhaack@fastmail.com> wrote:
Thanks Ticker That helped a lot. What I learned is that the Zumo does not like any custom types for points. I tested it with my typ file and the mapnik one. If there is something in the type file, nothing shows up on the zumo for that type code. It does show me what the garmin icons are, so I'll have to work with that. It really unfortunate, lesson learned: don't buy a zumo. Brad
On 8/7/20 4:42 AM, Ticker Berkin wrote:
Hi Brad
test-map:all-elements isn't documented except in it's source:
https://svn.mkgmap.org.uk/mkgmap/mkgmap/trunk/src/uk/me/parabola/mkgmap/read...
It generates a map with blocks of POI, lines and polygons, both named and unnamed.
You might need to zoom in to see things.
The TYP file sameOrder.txt does not supply any icons; maybe Qmapshack doesn't either - I've never used it.
It does non-obvious things like using a non-standard background for half the above blocks and no background for the others, ie like a transparent map. This required setting POI_FLAG_TRANSPARENT for the test map to be displayed on the devices I tried. Maybe qmapshack has a different understanding.
How are the polygons messed up?
I don't know anything about zumo/themes - sorry.
Ticker
On Thu, 2020-08-06 at 16:10 -0600, brad wrote:
Even if I load a theme file with nothing in it, it doesn't seem to matter. I have worked out a set of typ codes for the roads and trails that work. Now I'm looking at points (POI), and I'm getting almost nothing on the Zumo. The only POI I'm getting is a WC using the Openfietsmap_full style & mapnik typ.
Ticker Berkin posted a while back about a test map, this sounds useful, so I generated a map with this: java -jar ~/Apps/Mkgmap/mkgmap-r4565/mkgmap.jar --gmapsupp --verbose --order-by-decreasing-area test-map:all-elements ~/Apps/Mkgmap/mkgmap-r4565/examples/typ-files/sameOrder.txt But I must be missing something because that doesn't show any POI's on Qmapshack on my desktop, and the polygons are messed up. Is this feature documented anywhere?
Any help is appreciated.
_______________________________________________ mkgmap-dev mailing listmkgmap-dev@lists.mkgmap.org.ukhttp://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
-- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com
participants (7)
-
Alexandre Folle de Menezes -
brad -
Dave Swarthout -
Felix Hartmann -
nick -
Randolph J. Herber -
Ticker Berkin