Map tiles vs map segments

I am coming here as a Mapsource user, but I guess Basecamp does not differ from MS as regards terminology. Until today I had thought that map tiles and map segments meant the same, they  were just two names for the elements of Garmin maps. I was aware of the map tiles/segments limit of 2048 as regards uploading a mapset fromMS (or BC) to my rusty 60csx.

But today I saw this support page https://support.garmin.com/en-US/?faq=R4ZceJN09l6Vdc60ks1j86 , which speaks about a limit of appr. 3000 mapping segments (I guess both the segments of Garmin maps and those of custom maps are included in this limit) and 500 custom map  tiles 

Checking the proposed Related page it was confirmed that segment is what I thought to be as segment/tile. But then what is tile?

Thanks for the explanation.

  • I've always called segments tiles, as do most folks. Either way it refers to the parts that make up a map. 

  • OK, thanks, but if these are synonyms, how the heck could Garmin give different limits for segments and tiles? Is it simply a mistake?

    I bolded it in my original post, maybe you overlooked it.

  • Like Sussamb, and many others, I've always used the terms (map) segments and tiles interchangably.

    The FAQ you quoted is for the GPSmap 65 not the 60CSx. Some newer Garmin "outdoor" models support a "custom map" feature (one or more JPG images in a KML file). Those are different from Garmin maps/charts. It seems Garmin used different terms for those different things. I don't recall the CSx segment/tile limit but 2,000 sounds about right. Never been an issue in my case but Topo maps and some older maps/charts have small segments/tiles making the unit limit important.

    FYI I have a 76CSx and still use it. My nuvi 1490T still works but has a loose USB connector making it unusable when using a cable (goes in/out of USB mass storage mode constantly). I also have an Oregon 600 but don't use it as much. I did buy a 2nd hand eTrex HCx as a backup to my my 76CSx (newer models don't, to my knowledge, log tracks to the SD card which means that you can't log unlimited track points vs the 10,000 limit). Also I prefer models that use standard (AA) batteries which makes their useful lifetime much longer. Garmin seems to believe (these) days in the throw-away mentality [non-replacable rechargable batteries].

    BTW I still use MapSource in preference to Basecamp. If you get a new model you'll probably have to use whatever Garmin dictates these days.

    Regards.

  • Sorry, the limit is not 2048, but 2025 segments/tiles for 60csx.

    I had planned to edit my first post, but simply forgot it.

  • Some newer Garmin "outdoor" models support a "custom map" feature (one or more JPG images in a KML file).

    Btw thanks for this explanation, which boggled my mind again. Until now I thought Garmin called “custom map” to be all those maps which are third party, sold not by Garmin.

    Either they are manifesting as standalone img’s copied into the newer devices as one map (of maybe more) used on these devices, or either just part of the mapset generated by MS/BC and uploaded into the device (or copied into its sd card) as gmapsupp.img. 

  • Both your 60CSx and my units are obsolete according to Garmin. They seem to reuse old terminology when naming new features on newer models.

    "Custom map" still, IMO, refers to non-Garmin/Garmin partner maps. That said it also refers to the newer feature. I think my Oregon 600 supports custom maps but I've never tried that feature out. Not useful to me.

    FYI newer models support more than one gmapsupp.img file. My nuvi 1490T and Oregon 600 do. On my 76CSx and eTrex HCx I keep multiple files on the microSD card and rename them (via US mass storage mode) as needed.

    I also own a 2nd hand GPS V which only supports old Garmin (non-NT) maps and only has 19MB of internal memory. BC won't even see it (being a serial port only device). That said MS works just fine to download/upload stuff.

    In my case all my "obsolete" units do the job I want and except for my 1490T are fully functional. If you know how to work with them there's no need for Garmin or 3rd party support (which you probably won't get anyway). Of course you may have to forego the latest bells'n'whistles.

  • Custom maps aren't simply all third party maps. They are a specific type of 'map' and you can read about them here support.garmin.com/.../