[mkgmap-dev] 3byte .typ file support
From Felix Hartmann extremecarver at googlemail.com on Sun Nov 2 14:16:11 GMT 2008
Well in the TYP File they are are specified type=0xXXXXX (5digits - hexadecimal), however in the map they are specified as Type=0x00 AND V2Type=0xXXXXX You can download free map samples (unlocked) from example here: http://www.garmin.com/garmin/cms/site/de/lang/de/wanderkarten (or direct link: http://www.garminonline.de/allgemein/admin/klick.php?URL=http://www.garmin-download.de/web/topo_de/garmin.exe ). Extract the resulting gmapsupp.img with gmaptool (Split files for Mapsource). Have a look at 06701072.img which is the mapfile of Garmisch Partenkirchen. Here is an extract of a 3byte map in Polish Format (mp), with some different examples (how to do this: Open a 3byte .img with Maptk --> Tools --> Analyse IMG. I find the one old POI also pretty interesting, as it shows some fields that could be used by mkgmap too. Download Maptk (Freeware) here: http://www.maptk.dnsalias.com/ I'm not sure how the DEM is incorporated into these maps (yes they do have a DEM, but I don't know how it's used). Maybe the DEM used automatically if a map is 3byte? The example given on the Spanish blog was different, because it had a distinct type. The DEM information can definitely be found in the img itself. (I exported a tile of the testmap, then again using gmaptool integrated it into mapsource, and the only thing inside that gmapsupp.img was the img and the typfile (I00002BC.typ). Notice the difference between 3byte objects (type=0x00 PLUS V2Type=5X and all others. Remember again that all 3byte objects can only be seen if used with a typfile. However exported to Polish Format, GPSMapedit ( http://www.geopainting.com/en/ ) may see them too. [IMG ID] ID=06701072 OrigID=I0664010 Name=Garmisch-Partenkirchen CodePage=1252 Copyright=GARMIN CORPORATION1995-2007 LIC_700, Germany TOPO1 ID 7002007 ATKIS Basis-DLM, DGM50 M745 - © Vermessungsverwalt POIs - © Teleatlas 's-Hertogenbosch2007 Verzeichnis der Bergnamen Bayerns - © Bayrisches L Verlauf Rothaarsteig - © Rothaarsteigverein e.V.2 Verläufe Premiumwanderwege Saarland - © Tourismus Verläufe Bergbau-Wanderrouten Ibbenbüren - © Knapp alle weiteren Wanderrouten - © Masepo GmbH2007 © Garmin Deutschland GmbH (unverkäufliche Testvers DrawPriority=24 Levels=6 Level0=24 Level1=22 Level2=20 Level3=18 Level4=17 Level5=16 Zoom0=0 Zoom1=1 Zoom2=2 Zoom3=3 Zoom4=4 Zoom5=5 [END-IMG ID] [POI] V2Type=0x11501 Type=0x00 Data0=(47.46791,11.00914) [END] [POI] Type=0x2b01 Label=LÄNGENFELDER HOF StreetDesc=LÄNGENFELDER STRAßE 6 CityName=GRAINAU RegionName=BAYERN CountryName=DEUTSCHLAND Zip=82491 Phone=+(49)-(8821)-985880 Data0=(47.47205,11.04761) [END] [POLYLINE] V2Type=0x10e16 Type=0x00 Label=KREUZWANKL-SKI-EXPRESS EndLevel=1 Data0=(47.45547,11.08216),(47.46313,11.09415) [END] [POLYLINE] V2Type=0x10f0b Type=0x00 EndLevel=1 Data0=(53.85157,11.73211),(53.85170,11.73218),(53.85232,11.73286),(53.85275,11.73237) [END] [POLYGON] V2Type=0x1100a Type=0x00 EndLevel=1 Data0=(47.47330,11.06626),(47.47351,11.06637),(47.47377,11.06594),(47.47366,11.06579),(47.47388,11.06549),(47.47375,11.06519),(47.47355,11.06519),(47.47345,11.06531),(47.47364,11.06574) [END] [POLYGON] V2Type=0x11000 Type=0x00 EndLevel=1 Data0=(47.47308,11.06426),(47.47306,11.06407),(47.47298,11.06381),(47.47270,11.06328),(47.47261,11.06295),(47.47233,11.06295),(47.47201,11.06285),(47.47169,11.06272),(47.47160,11.06285),(47.47152,11.06291),(47.47143,11.06300),(47.47134,11.06336),(47.47126,11.06370),(47.47149,11.06368),(47.47152,11.06381),(47.47152,11.06390),(47.47175,11.06385),(47.47175,11.06403),(47.47205,11.06403),(47.47203,11.06394),(47.47214,11.06396),(47.47218,11.06405),(47.47248,11.06398),(47.47248,11.06454),(47.47276,11.06478),(47.47280,11.06482),(47.47283,11.06478),(47.47293,11.06439),(47.47300,11.06431) [END] [POLYGON] Type=0x05 Data0=(47.44804,11.27283),(47.44813,11.27232),(47.44714,11.27197),(47.44703,11.27242),(47.44740,11.27259) [END] Alexander Atanasov wrote: > > Hi, > > On Sun, Nov 2, 2008 at 4:32 AM, Felix Hartmann > <extremecarver at googlemail.com> wrote: > > I found out one missing information about the 3byte .typ files. > > 3 byte typfiles are addes as v2type=XXXXX instead ov type=xx00 > > > > I'll confirm this later, but it looks like that if we use > v2type=1160d then > > garmin handhelds (with typ support) will interprete this line as Digital > > Elevation Model DEM. This could be the key to not only see contour > lines, > > but also have a DEM. See the following articles in Spanish for more > > information about it (use google translate if you don't understand > Spanish > > too well): > > That's interesting. > This so called v2types aka marine aka NT types, are found in rgn2,3,4. > But they are two bytes there. If typ file doesn't have other way > to specify them, that makes sense. > > -- > have fun, > alex > > . -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20081102/948dda97/attachment.html
- Previous message: [mkgmap-dev] 3byte .typ file support
- Next message: [mkgmap-dev] 3byte .typ file support
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list