Talk:OSM Map On Garmin/POI Types
Embed icon images?
I wondered whether it would be worth adding screen-captures of the actual icons in use? I have done this for many POIs on my GPSMap76Csx, but haven't put them online incase there is some Garmin copyright on them? For a starting point, a lot of the icons are listed here: http://freegeographytools.com/2008/garmin-gps-unit-waypoint-icons-table
Also, is there a more user-friendly way of displaying this info? It's pretty hard to read and if I were to add another column for the 76Csx it would get even worse. csdf 14:55, 5 October 2009 (UTC)
- I didn't add screen-captures because of the possible copyright issues. Of course one could describe the icons with text (which is done for some icons). But as for most maps the standard symbols are overridden with custom icons anyway it doesn't matter much. If you find a more user-friendly way for the display I would be very much interested. I haven't found a better way yet. What I would like to keep is the comparison between the different units, so they shouldn't be split into separate pages. The table could be split along its length, but that wouldn't help for usability, only for file size when editing. Radfahrer 06:43, 6 October 2009 (UTC)
Remove distinction between type and sub-type?
Is it helpful to distinguish between type and sub-type? In the mkgmap style file you have to refer to the whole type code anyway, so for beginners it would be easier if we just listed the full type code. --csdf 10:23, 9 November 2009 (UTC)
- I'd think that it is helpful, because it structures the list a little bit. If you're looking for a certain code you can first scan for the type, then look for the subtype. Further it is easier to express ranges this way. Would there be a benefit if we used the full type code? This stuff here is not really for beginners anyway. Radfahrer 22:58, 9 November 2009 (UTC)
- Fair enough. I classify myself as a pseudo-beginner, and I know that without any background in hex, the difference between type and sub-type had me scratching my head for a bit. Ultimately, I would have thought the main object of this list is so that someone can say "I want to display a ski symbol - what's the code I should use?". But perhaps people are using it for other things too.--csdf 09:36, 12 November 2009 (UTC)
- If you just want to display a certain symbol you might want to look into TYP files, because with them you are able to create your own icons. What this list deals with is the more complex issue of the assignment of the POI codes to the POI categories on each device. This is fixed and device specific (and sometimes even software version specific). All currently available lists of Garmin POIs do not differentiate between devices. But for the beginner it might be easier to use just one of the available lists (for example the garmin_feature_list.csv that is supplied with mkgmap). In the end this work here should enable us to create a list of save codes that work the same on all devices. Radfahrer 21:34, 13 December 2009 (UTC)
- TYP files are fine if you want to define custom icons. But when I started, I just wanted to know what symbol a certain Garmin type code corresponded to under the default (no-TYP) situation. So the table imho actually has two uses:
- Explain what categories a given Garmin type falls into (what you are using it for)
- Explain what default symbol appears for a given Garmin type on a given GPS device (what I was using it for)
- The garmin_feature_list.csv file doesn't help with the second use, really (i.e. it doesn't help you understand what the default symbol looks like).--csdf 11:36, 14 December 2009 (UTC)
- TYP files are fine if you want to define custom icons. But when I started, I just wanted to know what symbol a certain Garmin type code corresponded to under the default (no-TYP) situation. So the table imho actually has two uses:
- If you just want to display a certain symbol you might want to look into TYP files, because with them you are able to create your own icons. What this list deals with is the more complex issue of the assignment of the POI codes to the POI categories on each device. This is fixed and device specific (and sometimes even software version specific). All currently available lists of Garmin POIs do not differentiate between devices. But for the beginner it might be easier to use just one of the available lists (for example the garmin_feature_list.csv that is supplied with mkgmap). In the end this work here should enable us to create a list of save codes that work the same on all devices. Radfahrer 21:34, 13 December 2009 (UTC)
- Fair enough. I classify myself as a pseudo-beginner, and I know that without any background in hex, the difference between type and sub-type had me scratching my head for a bit. Ultimately, I would have thought the main object of this list is so that someone can say "I want to display a ski symbol - what's the code I should use?". But perhaps people are using it for other things too.--csdf 09:36, 12 November 2009 (UTC)