[mkgmap-dev] test files to figure out Garmin encodings?

Mon May 18 13:34:09 BST 2009

You can download a legend/sample map from my site:
http://openmtbmap.org
Go to Download and then choose openmtbmap legend. You can download the 
legend in osm format (that download also includes my POI style-file 
part) so you can run your style-files on it.
It's missing areas (because you can do more or less whatever you want, 
as long as you define it in a typfile).
If you compile Qlandkarte GT from source or move the legend to your GPS 
you can see all lines, in Mapsource lines for sac:scale and tracktype 
are not shown (Mapsource only shows 0x00 to 0x2a). We desperatly would 
need extended types (this is independant of the NT format) to show all 
lines in Mapsource too.

I have implemented so far nearly all POI I know off. All highway types 
and tracktype, sac:scale, mtb:scale and many areas.

If you wan't to upstream the POI into mkgmap go ahead, but I think you 
would have to replace the old POI file because it's too complex to 
simply add. The only thing to watch out is, that my style-file defines 
bicyclerental and bicycleshop as carrental and carshop in the search 
function. All other searches work (As far as I can tell) perfectly. You 
will need to include a typfile to your maps however to display many of 
the POI with an icon instead of simply a point, because Garmin did not 
implement icons for everything.

POI style-file is attached (you can find it in the OSM legend download too).

Greg Troxel wrote:
> It seems there is a table of a lot of Garmin codepoints, and I wonder if
> havinga test file that has a POI with each possible codepoint, and
> similarly for roads, would help determine the behavior/meanings for the
> rest of them.  Perhaps things are 100% figured out, but it feels like
> not.
>
>
> The basic idea is to take a lat/lon to start (to make the map 'near'
> someone working on this) and then to have a grid of points spaced 50m,
> roughly square, that has each possible codepoint in some range known to
> exist.  Then a second grid with a N-S road and then every 50m E-W roads
> of every type on the left and on the right some normal road with every
> access combination.  They could be be labeled with names that have the
> codepoint, and eventually the meaning, drawing from the database of
> meaning/codepoint mappings.
>
> Once this was written other people could more easily experiment to add
> knowledge.
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090518/0cfa92cd/attachment.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: points
Url: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20090518/0cfa92cd/attachment.pl 