Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Page 1 of 2 12 LastLast
Results 1 to 10 of 13
  1. #1
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,407
    Rep Power
    1435

    Default Why is 'Suppmap1' in Nuvi 1xxx Inventory? & Why are some maps unselectable named as 'gmapoem'?

    Recently, in the course of attempting to assist another member who has an identical unit to mine (US purchased Nuvi 1300, with modded splash to enable LA, JCV & SLI) i had reason to examine my own Inventory to compare it with his.

    From the hidden Diagnostics Menu of my 1300 US:

    Inventory

    Boot BLK B0972-00 5.80 nuvi 1300 Boot Black Software Pass
    X-Loader B0972-00 5.80 nuvi 1300 X-Loader Software Pass
    System B0972-00 5.80 nuvi 1300 System Software Pass
    Basemap ?????-?? 0.00 Worldwide Autoroute Basemap 6FC01800
    Suppmap Erased
    Suppmap1 Erased
    PROM 1 D0783-13 20.12 CN North America NT2012.20 LBD9A8300
    PROM 2 Erased
    Dlr DB Erased
    Unknown D1074-00 9.00 Time Zone Map 9.00 03CBC600
    JCV D3153-03 2.00 Junction View (JCV) 91A81917
    Splash D1340-50 2.00 nuvi narrow+wide,TTS,TRF,LA,JPass
    Demo Erased
    FTL D0398-00 2.10 FTL Image
    Audio D0376-00 2.00 English_Australian_Karen 73980200
    Rmt SW B0360-00 3.30 MSN Direct Software 0535D7CA
    Rmt SW B0901-00 2.90 GMT3G RDS-TMC Receiver 00440300
    GTM20 B0482-01 5.50 GMT25 RDS-TMC Receiver 003F5C00
    OEM Cnfq 0.00 Consumer default

    I was struck by the inclusion of 'Suppmap1' as well as 'Suppmap' in the Inventory. i know 'Suppmap' is for 'gmapsupp.img' in SD/Garmin and i thought 'Suppmap1' may once have been reserved for gmapsupp.img in the unit itself, either in .system of 1xxx or in Garmin folder like in some other Garmin units. But of course Suppmap1 isn't reserved for gmapsupp in the unit's Garmin folder, 'coz no maps of any name will work there in 1xxx nuvis. And neither of those names will work in the .system folder of 1xxx series, the only recognised names being gmapprom.img, gmapprom1.img and gmapoem.img. The later may or may not be deselectable as i had heard and later confirmed.

    In spite of this knowledge, i loaded a couple of small free maps (Rarotonga & Laos Cambodia Vietnam) into .system as gmapsupp.img & gmapsup2.img just for fun. Nothing changed, neither worked, not showing in Map/Info on the nuvi and Suppmap & Suppmap1 still showing as 'Erased' in the Inventory. As i expected, no surprise there. But why is 'Suppmap1' there in the Inventory anyway? Is it some over-looked hangover from some long-ago software predecessor of the 1xxx line? In the SD/Garmin folder, the little Rarotonga map as 'gmapsupp.img' showed up of course as 'Suppmap' in the inventory:
    Basemap ?????-?? 0.00 Worldwide Autoroute Basemap 6FC01800
    Suppmap ?????-?? 0.00 Rarotonga 0.00 006CFBB1
    suppmap1 Erased
    PROM 1 D0783-13 20.12 CN North America NT2012.20 LBD9A8300
    PROM 2 Erased
    Dlr DB Erased

    When i renamed the little free maps as 'gmapoem.img & gmapprom1.img' in .system, as expected they worked and Laos etc as gmapoem.img was selectable and this was the Inventory for the maps:
    Basemap ?????-?? 0.00 Worldwide Autoroute Basemap 6FC01800
    Suppmap Erased
    suppmap1 Erased
    PROM 1 D0783-13 20.12 CN North America NT2012.20 LBD9A8300
    PROM 2 ?????-?? 0.00 Rarotonga 0.00 006CFBB1
    Dlr DB ?????-?? 0.00 Laos Cambodia Vietnam 2010 R5D663279
    Unknown D1074-00 9.00 Time Zone Map 9.00 03CBC600

    When i reversed the naming, Raratonga as gmapoem.ing worked, but was not de-selectable as it did not appear in Map/Info, just a space showing at the top where it should be, and this was the map Inventory then:
    Basemap ?????-?? 0.00 Worldwide Autoroute Basemap 6FC01800
    Suppmap Erased
    suppmap1 Erased
    PROM 1 D0783-13 20.12 CN North America NT2012.20 LBD9A8300
    PROM 2 ?????-?? 0.00 Laos Cambodia Vietnam 2010 R5D663279
    Dlr DB ?????-?? 0.00 Rarotonga 0.00 006CFBB1
    Unknown D1074-00 9.00 Time Zone Map 9.00 03CBC600

    So what i had heard was confirmed, some maps are selectable as gmapoem.img and some are not. I've also heard that some maps won't work at all as gmapoem.img. Anyone know why?

    OK, so who cares? Because we can stuff as many >4GB anyname images in the sd's Map folder as we like, right? So what if there may be some other naming convention possible for an extra map in the .system folder... who's gonna use it anyway.. not me. But WHY the Heck is 'Suppmap1' there????

    I bet more than one of you knows the answer to both questions......

  2.    Advertissements


  3. #2
    Important User

    Ballebar's Avatar
    Join Date
    Jul 2009
    Location
    Off the Grid ...
    Posts
    983
    Rep Power
    968

    Default Suppmap1 = gmapsup2.img or different storage location, internal vs. memory card?

    Maybe the nüvi 1300 uses some default legacy garbage in the firmware that is just empty placeholders from the past?
    Looks that way if you have tried gmapsup2.img and also internal vs. memory card storage.

    Some of the terms from a GarminDevice.xml file:
    • PreProgrammedMaps
      1. gmapprom.img
      2. gmapprom1.img
    • SupplementalMaps
      1. gmapsupp.img
      2. gmapsup2.img
    • BaseMaps
      • gmapbmap.img
    • TimeZoneMaps
      • gmaptz.img
    • PreProgrammed3DMaps
      1. gmap3d.img
      2. gmap3d1.img
    • Supplemental3DMaps
      • [GPS or memory card]:\Map\any_name.img
    • PreProgrammedDEMMaps
      • gmapdem.img
    • SupplementalDEMMaps
      • gmapdem1.img


    OEM data in gmapoem.img is usually some very small files with branded data for dealer POIs.
    Some examples of gmapoem.img files from Garmin or branded Garmin units:
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]
    [Only registered and activated users can see links. ]

    There's similar gmapoem.img files for branded versions of units sold by Tesco, Dixons, Carrefour, Géant, Hyundai etc.

    More about the map files here:
    [Only registered and activated users can see links. ]



    This post suggests that Suppmap1 is the internal gmapsupp.img and that Suppmap is the gmapsupp.img stored on a memory card. That's for nüvi 7x0 & 7x5.

    Quote Originally Posted by catymag View Post
    Multi maps on Nuvi 7x0/7x5

    original poster hulio (thanks)



    Nuvi internal (diagnostic utility) OS map naming
    -----------------------------------------------------------
    7x0/7x5

    1. PROM1 = gmapprom.img
    2. PROM2 = gmapprom1.img
    3. Suppmap1 = gmapsupp.img (nuvi drive only)
    4. Suppmap = gmapsupp.img (SD Card drive only)
    5. Dir DB = gmapoem.img
    6. Basemap = gmapbmap.img

    7x5 only

    7. TZMap = gmaptz.img
    8. 3DMap 1 = gmap3d.img
    +9. 3DMap 2 = gmap3d1.img

    About the 4 GiB barrier!

    Well, you can put as many <= 4 GiB map files as you want in the Map directory of your memory card. As long as there's room for all the files anyway.
    The problem is other constraints like how many map tiles your unit supports and the most severe constraint about the number of map families it can support.
    If I store all TOPO Norway Adventure in one gmapsupp.img then I have 20 map families there. That's NOT readable by any Garmin unit I've tested including the Garmin Montana 650t. Normally it works with 16 or 17 MapIDs as the total for all maps but not with 20.
    Don't post thanking posts. Use the "Like"button instead.





    [Only registered and activated users can see links. ]

    NOTICE! Due to other activities I'm now having a very low attention to questions and requests here at GPSPower.

  4. #3
    GPSPower Helper

    dasilvarsa's Avatar
    Join Date
    Feb 2011
    Location
    Global
    Posts
    1,160
    Rep Power
    351

    Default

    @neil
    I have garmap2011.3 in unit map folder gmapsupp.img and it shows up in invenyory as.
    Suppmap1 ?????-?? 0.00 Garmap2011.3East 0.00 09fa526e.

  5. #4
    Master
    Join Date
    Feb 2011
    Location
    Sofia
    Age
    31
    Posts
    919
    Rep Power
    213

    Default

    @ Neil

    About the >4GB image...

    I think I have read that there is a limitation of the size of an image. (OM of cgpsmapper? can't remember now) It is not possible an image to be more than 4GB. But I am not sure as I think this is also dependable on the type of the image (non NT or NT image). Also this is dependable for a model - for example GM XT, nuvi 300 don't support images more than 2GB.

    About the selectability of gmappoem maps...

    Think this is also dependable on the type of image (non NT or NT). Maybe there could be some additional information in the header that determines should an image be selectable or static. But who really cares despite developers?
    Last edited by ddabcd277; 5th February 2012 at 12:15.

  6. #5
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,407
    Rep Power
    1435

    Default

    @dasilvarsa
    Well, well, well.... aren't you a smart little meerkat? I just chucked Philippines Roadguide into the nuvi map folder named gmapsupp.img and now my Inventory for maps is:
    Basemap ?????-?? 0.00 Worldwide Autoroute Basemap 6FC01800
    Suppmap Erased
    suppmap1 ?????-?? Roadguide.ph 2.01 Contributors 51725900
    PROM 1 D0783-13 20.12 CN North America NT2012.20 LBD9A8300
    PROM 2 ?????-?? 0.00 Laos Cambodia Vietnam 2010 R5D663279
    Dlr DB ?????-?? 0.00 Rarotonga 0.00 006CFBB1
    Unknown D1074-00 9.00 Time Zone Map 9.00 03CBC600
    So that's what it's for, gmapsupp.img in the Map folder!!.... wow, just like having a hip pocket in your undies isn't it? Useless as 'you-know-whats' on a bull. What genius at garmin dreamed that one up..."I know, we'll reserve the 1xxx path to Suppmap1 for gmapsupp.img in the internal Map folder. That'll come in handy, won't it? ....Man, my hand is HUGE, dude.. where's the Pringles?" And here's me thinking it must be for some specialty maps like DEM or 3D images supported by some nuvis or some other obscure but practical use. Hah!

    Oh well, thanks every one else for your imput...a nice quick response from some of my favourites on Noeman.

    PS: Really i suppose who cares about the selectable/non-selectable gmapoem thing. It really doesn't matter at all hey ddabcd277?.
    Last edited by Neil; 5th February 2012 at 13:42. Reason: PS

  7. #6
    Master
    Join Date
    Feb 2011
    Location
    Sofia
    Age
    31
    Posts
    919
    Rep Power
    213

    Default

    @ Neli

    So many question so little answers. "I know one thing, that I know nothing".

  8. #7
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,407
    Rep Power
    1435

    Default

    @Ballebar
    Thanks for your answer. As usually informative, thoughtful and nicely crafted answer. I resisted responding to it last night (it's almost 8am here now) as i felt it deserved a much more considered answer than my somewhat flippant one above. A lot of that info i was aware of, ie the file naming protocol and paths for some other nuvis like 7x0/7x5, which makes sense for the legacy units with such original naming constraints and is therefore quite understandable. But suppmap1 for gmapsupp.img in the Nuvi's Map folder makes absolutely no sense and apparently cannot be explained away as "some over-looked hangover from some long-ago software predecessor of the 1xxx line?" (my musing) or "Maybe the nüvi 1300 uses some default legacy garbage in the firmware that is just empty placeholders from the past?" (your similar conjecture). So what was Garmin up to? Was it just neccessary for them to leave suppmap1 there because they constructed the 1xxx firmware from some other existing fw as a base? Therefore it was easier/better to have it linked to 'something' than dead? I suppose that makes sense, kind of. But why to to gmapsupp.img in the internal Map folder, when at least to gmapsupp.img in .system or even to gmapsup2.img in sd/Garmin may serve some purpose. I suppose it was just easier because of some fw constraints not understandable by a layman like me. But i'm sure you could figure it out if you could be bothered, however it's simply not worth the effort so please don't try on my account.

    I was also only vaguely aware of the use of Dlr DB/gmapoem.img for oem branded images and that as such it cannot be deselected. I'm also of the (perhaps incorrect) impression that Garmin sometimes uses gmapoem.img for preloaded 'normal' maps, and that they also are not deselectable and don't show in Maps/Info, is that so? However, that's not what i was on about with my original question, which was on using 'foreign' maps not normally intended for oem use. It has been answered by ddabcd277 probably as to do with the NT/nonNT type and/or some info in the header which makes sense to me. That explanation of header info would also explain way some are not even recognised as gmapoem.img at all as i had heard.

    My >4GB file size comment was a bit of a 'throwaway line' really. I was also vaguely aware of the map tile number/map family number limit constraints. I'm quite aware of the [Only registered and activated users can see links. ], but honestly thought it was 4 gigabytes (GB) less 1 byte. I notice you used 4 GiB (gibibyte). A typo? No, you don't do typos.. so it really is a 4 gibibytes less 1 byte limit?

  9. #8
    Garmin/GPS Systems GMod.

    Neil's Avatar
    Join Date
    Aug 2011
    Location
    Oz.
    Posts
    7,407
    Rep Power
    1435

    Default

    Sorry to bump my own thread. Consecutive posts by other people i generally find to be quite annoying, so my apologies for doing this. I had forgotten to mention something which really i could have done as an edit to either post #5 or 7. After replying to post #4 by dasilvarsa i rechecked my .xml and found this in it:
    <Name>SupplementalMaps</Name>
    - <File>
    - <Specification>
    <Identifier>IMG</Identifier>
    </Specification>
    - <Location>
    <Path>Map</Path>
    <BaseName>gmapsupp</BaseName>
    <FileExtension>img</FileExtension>
    </Location>
    <TransferDirection>InputOutput</TransferDirection>
    </File>
    </DataType>
    - <DataType>
    <Name>NMaps</Name>
    - <File>
    - <Specification>
    <Identifier>IMG</Identifier>
    </Specification>
    - <Location>
    <Path>Map</Path>
    <FileExtension>img</FileExtension>
    </Location>
    <TransferDirection>InputOutput</TransferDirection>
    I had last looked at the .xml not long before my initial post but somehow again managed to miss the fact that the path for 'suppmap1' is to 'Map'. I've looked at that .xml so many times. i can't believe that i didn't see and absorb the implication at some point, and it's right above the 'NMaps' path to 'Map'. I've always taken NMaps to be an abbreviation of 'AnyName Maps' which it means in a practical sense anyway, because there is no basename entry between the Path and File Extension entries. I hadn't bothered about adding the above info as an edit because i really expected a volley of replies pointing out that the path for 'suppmap1' as 'gmapsupp' was to 'Map' in GarminDevice.xml. Perhaps most people were aware of it and just thought it too trivial to comment on, but to me it was a revelation. So maybe i was being too tough on the garmin software engineers, because it must be that the Supplemental Maps path to the Map folder was done intentionally to pave the way for NMaps in later fw revisions?

    But now the reason for the bump.. i have always been confused by gigabytes & gibibytes, binary and decimal values, and the fact that harddrive manufacturers and Microsoft differed in their descriptions of what is a GB (gigabyte), or for that matter the value of a megabyte or a terabyte. So ok, i knew that when valuing a gigabyte anyway, MS would 'discount' the HD maker's value to about 93% or so roughly (1 over 1.074 or thereabouts). So i thought i'd revisit this trying, if possible, to clear this confusion up for myself. I wish i hadn't. Trying to get my head around things like 10^9, 2^30, 2^32, 1000^3, 1024^3 as values for a gigabyte and/or a gibibyte, depending on how it best suits the case of the particular claimant have now made my head spin, and that's pre-braced with a stiff expresso. I mean, reduced to simple figures they all just look like rifle numbers or NY telphone numbers to me anyway. So, BB, it was you who actually opened this particularly nasty can of worms for me. Can you clear it up without confusing me further? Keep in mind that i have had NO formal computor training, am of pensionable age and regularly deplete my meager stock of remaining brain cells thru excess consumption of fine West Aust. Shiraz. So please, you or anybody else, reply like you're explaining it to the village idiot. What is the FAT32 file size limitation, 4 GB minus 1 byte, or 4 Gib - 1, are they really the same values anyway, and what does the Heck does it really mean in actual bytes? To most people, that is. Keep it simple Sam. Hmmm?
    Last edited by Neil; 8th February 2012 at 10:53. Reason: can't type, can't spell.

  10. #9
    Important User

    Ballebar's Avatar
    Join Date
    Jul 2009
    Location
    Off the Grid ...
    Posts
    983
    Rep Power
    968

    Default

    2^10 vs. 10^3
    Historically most people defines 1 kilobyte as 2^10=1024 bytes, 1 megabyte as 1024 kilobytes, 1 gigabyte as 1024 megabytes and so on. That's the definition that was used in the beginning of calculating bits and bytes in computers and PCs.
    Storage manufacturers have hijacked the term and by political and technical lobbying got the SI definition of decimal counting for kb, MB, GB, TB etc. to be commercially accepted. They claim that k stands for 10^3=1000, M for 10^6=1000000, G for 10^9=1000000000 and that it allows them to use the decimal definition of prefixes for bytes. That even despite the de facto standard for computer science had been binary 1024 calculated prefixes for decades.

    When we where using kB and MB it didn't matter so much if it was decimal or binary definition behind the symbols. But we loose approx. 2.34% for each step in the k -> M -> G -> T -> P ...
    1 kB is ~97.66% of 1 KiB
    1 MB is ~95.37% of 1 MiB
    1 GB is ~93.13% of 1 GiB
    1 TB is ~90.95% of 1 TiB
    1 PB is ~88.82% of 1 PiB
    ...
    ...
    So with TB and PB we have lost close to 10% or more from what many of us actually expected from binary calculated units.

    Gigabytes vs. gibibytes class action suit nears end
    Code:
    Please Login or Register to see the links
    Microsoft still uses the term gigabyte (GB) as calculating 1024 MB or 1024*1024 kB or 1024*1024*1024 bytes. I'm also using 1 GB as 1024 MB in normal everyday life but tries to be as accurate as possible here in the Noeman forum. So here at Noeman I'm trying to use KiB, MiB, GiB when appropriate. Most file host forums also shows MB but uses binary calculation such as it should be displayed as MiB instead.

    We could even complicate it further by using the original definition of a byte - one data word used for CPU calculation or data storage. That means 1 byte = 4 bits in a 4-bit CPU world, 1 byte = 8 bits in a 8-bit CPU environment and so on. In my Windows 7 64-bit OS that would mean 1 byte = 64 bits.
    Code:
    Please Login or Register to see the links

    2^32
    If you have a FAT32 file system it means the address space is 32-bits. Calculating from address 0 (zero) and up to 2^32-1. The -1 comes from that you start with address 0. That's the maximum unsigned 32-bit integer that could be used in linear addressing. This is equal to 4 GiB - 1.
    Code:
    Please Login or Register to see the links

    Some (un)usefull historical data
    In the old DOS days with 16-bit application there was a lot of tools like DOS Phar Lap Extender to break the OS limit of 16-bit addressing. By using such extenders they could write 32-bit applications to run in a 16-bit OS.
    Code:
    Please Login or Register to see the links

    About the total numbers of map families (MapIDs) that can be used at the same time in a Garmin unit.
    I haven't tried to measure this by science and taking the time to test my Garmin units. If I load my 32 GB Samsung Class 10 microSDHC card with 4 City Navigator NT, 7 TOPO maps and 6 BC g2 the result is that some maps is not seen by the unit.
    Perhaps Mapperoni would be kind and share his more exhaustive evaluations of that subject. I think Mapperoni tested the capacity of a GPSmap 62 unit with TOPO Norway Adventure. There's a total of 20 maps in that series and all have a different MapID.

  11. #10
    VIP Master

    Join Date
    May 2009
    Location
    Maryland
    Posts
    356
    Rep Power
    11

    Default

    I thought the limits put on the map size ( Especially for units like the Montana 650 ) was based on how many "Tiles" were in am image and not the actual size of the image file.

    I can't recall exactly what the tile limit was, but it was somewhere around 2025 tiles I thought for official Garmin maps.

    For "custom" maps, the tile limit on the Montana used to be 100, but has recently been increased to a 500 tile limit for "Custom" maps on the Montana.

    It will also depend on whihc GPS unit you are using and which Firmware/Software version.

    If That Topo Norway Advenbture has more than the allowed number of tiles than the GPS will not work.

    If there are 20 Map "Families", there well may be over the allowed number of tiles... I don't know.

    There may be a way to movfe some of the tiles into another map image file and turn both the img files on using the Montana and they "may" both show up as one "may" overlay the other.

    BTW.... I'm not an expert. Like many here... I'm still learning.

 

 
Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.