so.... this mean "MapID" is not "Map ID" ? :)Quote:
Originally Posted by Kanopus [Only registered and activated users can see links. Click Here To Register...]
like we all know many years....
Printable View
so.... this mean "MapID" is not "Map ID" ? :)Quote:
Originally Posted by Kanopus [Only registered and activated users can see links. Click Here To Register...]
like we all know many years....
Like all recent Garmin's creations, not the same as we used to know ;)
Quote:
Originally Posted by Kanopus [Only registered and activated users can see links. Click Here To Register...]
i thinks all users not know it is not same and not mean same.... ;)
another one is only nickname to other thing.... :error:
Think, for instance, of CN Russia NT (Navicom):Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
2013.10 - FID/PID: 2618/1 > mapID: 17643383 (10D3777)
2013.20 - FID/PID: 2688/1 > mapID: 17652435 (10D5AD3)
2013.30 - FID/PID: 2753/1 > mapID: 17815387 (10FD75B)
2013.40 - FID/PID: 2794/1 > mapID: 17823074 (10FF562)
Can anybody find a rule (formula) for this? :question:
For MPC maps formula is
in hex: MID = 800h * FID + 606000h
MID = 2048 * FID+6316032.
You can check it for example with BG routing .img
2048 x 1204 + 6316032=8781824Code:I0860000 GMP 1A00h 661751
GMP: TRE RGN LBL NET NOD
map 860000 (8781824)
PID 1, FID 1204, region 1,1
date 02.02.2013 18:06:29
priority 24, parameters 1 4 23 5, locked
N: 42.931180, S: 42.619529, W: 23.498340, E: 24.498396
Custom MPC Map
Copyright 1995-2013 by GARMIN Corporation.
This doesnt work for CN maps.
It's an open fact with MPC. What's the formula for CN? :eam:Quote:
Originally Posted by catymag [Only registered and activated users can see links. Click Here To Register...]
It seems that for CN maps the mapID depends on the version number (or Product number) too, for example:
City Navigator Taiwan NT
2012.10 (v12.10, Pr: D287507AG030) - FID/PID: 2611/1 > mapID: 5321545 (513349)
2012.11 (v12.11, Pr: D287507BG030) - FID/PID: 2611/1 > mapID: 5323598 (513B4E)
"VenID" is not Vendor ID, it's Version ID. At least for Cyclops, it changes by releases (Sept is 12 while Oct is 13) It's not the month number, it's the release number.
One snapshot/release
Another snapshot/releaseCode:0 2017/Sep/28 14:00:11 2496, 9, 5, 12 006-D0701-00 Australia+New Zealand_safetycam.gpi
0 2017/Sep/22 14:00:09 2496, 9, 4, 12 006-D0700-00 BelgiumLuxembourg_safetycam.gpi
0 2017/Sep/28 14:00:16 2496, 9, 14, 12 006-D2072-00 Eastern Europe_safetycam.gpi
0 2017/Sep/21 14:00:12 2496, 9, 3, 12 006-D0697-00 France_safetycam.gpi
0 2017/Sep/28 14:00:13 2496, 9, 8, 12 006-D1297-00 Germany + Austria_safetycam.gpi
0 2017/Sep/20 14:00:14 2496, 9, 26, 12 006-D2224-00 Greece_safetycam.gpi
0 2017/Sep/23 14:00:03 2496, 9, 7, 12 006-D0760-00 Italy + Slovenia_safetycam.gpi
0 2017/Sep/22 14:00:09 2496, 9, 2, 12 006-D0699-00 Netherlands_safetycam.gpi
0 2017/Sep/28 14:00:10 2496, 9, 10, 12 006-D0913-00 Nordics_safetycam.gpi
0 2017/Sep/22 14:00:11 2496, 9, 6, 12 006-D0759-00 Portugal + Spain _safetycam.gpi
0 2017/Sep/27 14:00:13 2496, 9, 28, 12 006-D2393-00 Russia_safetycam.gpi
0 2017/Sep/20 14:00:06 2496, 9, 1, 12 006-D0698-00 UKIreland safetycam.gpi
0 2017/Sep/27 14:00:15 2496, 9, 27, 12 006-D2356-00 US+Canada_safetycam.gpi
FID=2496 seems to be identifying Cyclops and PID=9 is one product that Cyclops produced. Region ID (same for same file in each release) is the country/region the alerts are for and the last number is Version ID.Code:0 2017/Oct/14 14:00:19 2496, 9, 5, 13 006-D0701-00 Australia+New Zealand_safetycam.gpi
0 2017/Sep/22 14:00:09 2496, 9, 4, 12 006-D0700-00 BelgiumLuxembourg_safetycam.gpi
0 2017/Oct/14 14:00:21 2496, 9, 14, 13 006-D2072-00 Eastern Europe_safetycam.gpi
0 2017/Oct/10 14:00:07 2496, 9, 3, 13 006-D0697-00 France_safetycam.gpi
0 2017/Oct/10 14:00:10 2496, 9, 8, 13 006-D1297-00 Germany + Austria_safetycam.gpi
0 2017/Oct/09 14:00:15 2496, 9, 26, 13 006-D2224-00 Greece_safetycam.gpi
0 2017/Oct/04 14:00:15 2496, 9, 7, 13 006-D0760-00 Italy + Slovenia_safetycam.gpi
0 2017/Sep/22 14:00:09 2496, 9, 2, 12 006-D0699-00 Netherlands_safetycam.gpi
0 2017/Sep/28 14:00:10 2496, 9, 10, 12 006-D0913-00 Nordics_safetycam.gpi
0 2017/Sep/22 14:00:11 2496, 9, 6, 12 006-D0759-00 Portugal + Spain _safetycam.gpi
0 2017/Oct/10 14:00:16 2496, 9, 28, 13 006-D2393-00 Russia_safetycam.gpi
0 2017/Oct/11 14:00:21 2496, 9, 1, 13 006-D0698-00 UKIreland safetycam.gpi
0 2017/Sep/27 14:00:15 2496, 9, 27, 12 006-D2356-00 US+Canada_safetycam.gpi
Yes, Vendor ID/VenID is a total and complete misnomer. It arose back when the understanding of this was less clear. It was syzygy who I think coined it as a possible identification "maybe it's a Vendor ID" or such-like was what he ruminated. Jetmouse used it in the unl code generator and the usage stuck. Whether it's a Subregion or Version ID seems product dependent. However, "A rose by any other name ...."
So for a map, does VID reflect the change count between the releases (mostly per year)? That is, does it start at 0 for beginning of the year and increment for each new releases?
