Thread: Need Info about USA/CANADA Maps 2017.Q1

If you select device LOSTNFOUND->CIRRUS, you see NA* 2017.Q2 with pricing
1 year (up to 4 updates) $89.95
single update $69.95

* Looks like NNG only consider Canada and USA as North America, *sic* Mexico is not part of North America nor South America continent, it's a continent by itself.

Spoiler: pic

[Only registered and activated users can see links. ]

This is the total download for the US 2017 maps I posted about earlier.

Spoiler: LINK

[Only registered and activated users can see links. ]

EDIT: They are password protected. Sorry, but I didn't know. I'll try to get it.

PW: camaro69

Originally Posted by jtrosky

I do have a bunch of "official" SD cards from Rosen DS-GM1010-P11 (WinCe) head-units (running Primo 2.0), so I think I can use those to buy updated maps, but the problem is that the app is "bound" to those specific SD cards - and they are only 4GB - so I don't think they are big enough to buy current maps (they contain maps from 2011/2012).\

It depends on which package you're getting. The "NA 2017.Q2" (with only Canada and USA) mentioned in my post is only 1816 MB (according to NNG). Buildings are a separate buy, but I don't think they are very big.

It's the .fds files, you don't need them because nothing can use them right now. You can also get rid of .ftr if you're not using truck restriction.
I don't know the exact "Rosen" system you're using, I just select HD version for Mustang and I see size is same

Spoiler: .

[Only registered and activated users can see links. ]

They sure *look* like TomTom 2017.03 maps to me! :-) Both Primo 2.4 (405512) and iGo View show them as TomTom 2017.03 maps.

I also compared them to TomTom 2015.09 maps (I happened to have those still) and they are *definitely* different - different file sizes and everything...

Here is the Primo 2.4 map versions screen (I only updated the Pennsylvania maps):

Spoiler: pic

Could the dates in the files be altered? Sure... I'll have to check for a recent road change - will report back.. If they are really from 2015, that road change definitely wouldn't be there...

Not sure how to be 100% sure they are not copies of some other map. One thing that does look strange to me is that in iGoView, all of the maps say "File description: Israel Map" at the top... :-) Hard to believe that NNG would make that mistake...

EDIT: That recent road change *is* in these maps, so they are definitely newer than 2015...

Sent from my Hi10 pro using Tapatalk

Good to know they are 2017.03, when comparing USA_New_York.fbl originally posted from [Only registered and activated users can see links. ] (with CRC32 of 9E28A8F3) it is different from this post of USA_New_York.fbl (with CRC32 of 13970D5D) So I would say chas521 original post was not 2017 (maybe copied wrong) but this latest post is 2017. Now can we get rest of files: .poi, .fda, .ftr, .fpa, .fsp, etc...???

Originally Posted by jtrosky

Could the dates in the files be altered?

Yes, if you know how.

Originally Posted by jtrosky

One thing that does look strange to me is that in iGoView, all of the maps say "File description: Israel Map" at the top... :-) Hard to believe that NNG would make that mistake...

NNG didn't make the mistake, iGOView did. Here is why

Spoiler: .

This post requires you to click the "LIKE this post" button and hit F5 to read this content.

Originally Posted by jtrosky

...that in iGoView, all of the maps say "File description: Israel Map" at the top... :-) Hard to believe that NNG would make that mistake...

That is just description by (old) software for a looong time....
All fbl files are defined like Israel map
all other files that come in same folder are map
POI are described like POI Australia_WhereiS_21, New_Zealand_WhereiS_10, etc...

It comes from a time when there were not many map editions, who knows, it is possible that they lead the origin from from the publications of that time and keeped it that way, maybe it is related to some of the contracts.
Main program and its database are not supplemented and modified for a long time...
And an internal marking of nng has an impact, since all files (ftr, fpa...) are detected as fbl - probably designed to make the program easier to handle with them - ie as a supplement to the main fbl file...
While someone from nng does (not) confirm this, we can only guess