2012.1 Map update

The reason you are missing some junctions views in 2012.10 that were in the previous update is not because your unit is running out of memory; it's because Garmin removed them from the maps because they plan on replacing them later with photoreal junction views. Now, it could be a couple of map updates before that happens, you never know, but be assured that the loss of some junction views has nothing to do with the amount of memory left in you gps.

Thanks, I will keep my fingers crossed. Are the photoreal views bigger in file size than the old views.

I would imagine that the photoreal junction views are larger in file size, considering how much bigger the JCV file folder got after this last update. If a future map update is too large, I would try updating only certain parts of the country you travel in, and I know there is a way you can do that, but I don't know how.

Exact same thing happened to me when installing new update and now the GPS gives me rather confusing routes. Definitely something has gone wrong.

It downloaded and installed fine. didn't check out routes yet.

I've found that it's much easier to to install everything on an external SD card. I've been using an 8 GB card for a while now on a 1490t and as long as I put everything on the card, it installs perfectly.

Successfully downloaded and installed, no errors. Seems to work fine. No email from Garmin received yet, though I did get one last time. Have not bothered to update firmware yet, still running v4.9.

This is an "official" answer from the Garmin support website posted on May 23rd to the question of why you may be missing Junction Views after the last update:

Garmin City Navigator mapping data has begun using a combination of sources for Junction View (JCV) information in an effort to bring the richest mapping content available. You may notice that locations which previously had JCV information no longer have this information, and likewise areas that didn’t have JCV in the past are now included. This is because the sources we use to collect this information along with the criteria that we use to select the included intersections are gradually changing and we are always evaluating the best locations for this information. If you believe any of your mapping information to be incorrect, please report the error on the following webpage:
https://my.garmin.com/mapErrors/report.faces

Sounds to me like these photoreal junction views may actually not be a product of Navteq (unlike the old junction views). I thought they were. I wonder what other "sources" Garmin uses for these photoreal junction views? It's also interesting (but not surprising) that their criteria for deciding where they include Junction View is always changing.

The link to the Garmin support webpage where I found this statement: https://support.garmin.com/support/searchSupport/case.faces?caseId={fbf90030-8581-11e0-cbc1-000000000000}

Very interesting. Thanks for the info.

Getting ready to see if my new nuvi 2450LM has the latest map.

When reading the directions it said to check:
save to device
save to device and computer
save to computer.

What do you think is the best way to do this?

I always save to device and computer. That way I get Mapsource with current map installed on computer. But if you don't need or use Mapsource, you could save to device only.

So in case your map does not completely fit on your device,you can use Mapinstall to install the remaining maps onto an SDHC or microSDHC card.

It's out already.

Just got my new 2450LM and did my first Map update.
Did the Device and computer like you said. I use Mapsource a lot.

Thanks!

I just wish they'd get the numbering consistent and understandable. The chip industry (and some foods) have a date code of YYWW (or YYYYWW) where YY (or YYYY) is the year and WW is the week, so somethign made in the first week of december of 2019 would be 1051 (or 210151). A map file could have a version of 2011.26 for June of 2011.

I surmise that either intellignece is not company policy, or that there is a Not Invented Here problem.

I typoed my date code...
> something made in the first week of december
> of 2010 would be 1051 (or 210151).
>
> I surmise that either intelligence is not
> company policy, or that there is a Not
> Invented Here problem (i.e. if we didn't
> invent it then it's not worth using).

I sort of like the idea of getting updates back to representing the actual month of publication like 2012.01, 2012.04 for january and april.

Just got a 1450LMT today. Had 2011 maps on it and I just downloaded and updated to 2012.1. Took forever to download, but seems to installed without a hitch.

I'm finding the latest map update has resulted in new routing. The streets were there before, but the unit has decided to go different ways. I wonder if they cnanged some of the algorythyms.

I don't quite understand why folks are hung up on the map release numbering scheme and think Garmin is trying to confuse us. I personaly don't find it confusing at all.

Maps are updated 4 times a year at best. Garmin is simply numbering them by fiscal year quarters and they are on a mid-year calender. July being Q1-2012, thus 2012.1 And, they did us a favor by marketing/offering them a few weeks in an advance.

Other schemes might be preferable to some but Garmin has just adopted a very common busines practice.

I was really impressed when I drove route 140 into Yosemite National Park this week using the new map. Impressed because there is a detour across the Merced River for half a mile due to a major rockslide that has taken months to fix and the latest map had this taken into account! Still happy with my nuvi 760

My 780 update went well...it took forever (left it overnight to finish), but all looks good...not that I see any real differences though.

So I am up for the next one ASAP

I have noticed that sometimes I can run the identical trip and my Garmin will use different routes. The only reason I can think of of is it may take into account the time of day a given destination is traveled.

That would certainly make some sense regarding traffic. Do you find a lot of variance in the routing?

Up until this update, I only had speed limits in the USA, now it seems someone has had time to add the speed limits to (at least the major) Canadian highways. The conversion is correct, when I am driving in the states it shows me the kph equivalent to 55mph 65 mph etc.

Since Garmin is bringing out a PND with Google search, I wonder if the photoreal junction views are the same as in Google maps PC?

Thanks for this information. I was experiencing this issue.

The Nuvi display is correct. The conversion is:

1 kph = 0.621371192 mph

so 100KPH would convert to 62.137MPH which the Nuvi displays as 63.

I have a need to switch between KPH and MPH so I can confirm that when the Nuvi is showing 63MPH it will also display 100KPH in metric mode.

So, it turns out that those of you who downloaded 2012.10 a week after the release date did not get the full junction view file (which was originally around 358 MB) because garmin removed all of the junction views due to the amount of calls and complaints they were getting about certain units not having enough internal memory. I found this out due to the fact that I just exchanged my unit a week ago and noticed that when I re-downloaded 2012.10 to the replacement unit that all of the new junction views that were put in were no longer there and that the new junction view file was only about 46 MB. I then called garmin customer support and they told me that due to amount of problems the large junction view file was causing, they decided to remove most of the views, and hopefully replace them in a future map update. So for those of who still have the original 2012.10 map update with the new photoreal junction views, I would recommend you not update your maps for a while unless the junction views don't matter to you. Classic Garmin.

Just back it up, and then replace it after an update if needed.

Oh my! What a terrible decision. It seems that they could design a map update to offer specific jcv file sizes based on the model number or even based on the free memory on a given unit being updated. Shame on Garmin for doing this--and more shame that it's taken until now for them to 'fess up (and that was done only in response to rame1012's correspondence with them).

So, it's a case of "you snooze, you lose." I'm glad I updated early and have the large file on my nuvi 855.

To me, this is also a very important reason to skip the thought of using Garmin's new auto-updater since a manual update on Day 1-2 of a new map release is most likely to be completed before an auto-update in case a similar situation arrives in the future.

Although, as you say, we may not want to be the first of the jcv-ed nuvi owners to update to the next map. Let someone else determine the next map's jcv file size. I'd really hate to see all the brand new Junction Views in northern Arizona disappear for ever or until.....?

Do we know a jcv from the current or an older map will work with a future map release?

I hope you're right since I have a backup of the current large file that can be used next time. In fact, I'll likely do a extra backup right before doing the next map update.

I guess I might as well volunteer to be a guinea pig for the next couple of updates, due to the fact that I've already lost all of the junction views anyway. But for future reference, how would I back up the map update? I already choose the option to download the map update to the computer AND Gps, but where do I find the map update on my computer after I download the map update?

I don't think that file is tagged with a unit ID or is locked. Maybe Rick can shed some light on that.

Backup your entire GPS and you'll have everything

http://www.poi-factory.com/node/30394

Good idea.
How do we tell Garmin?

JCV files only work with the map update they were created for.

You could use either the newer 45MB JCV file or the 358MB original with the 2012.10 map.

HOWEVER, you will not be able to use a 2012.10 JCV file with the 2012.20 map update when it is released.

Thanks. I sorta expected and feared that to be the case. This is possibly going to create a big conundrum for me when the next map update comes out for my 855 if the jcv continues to be the smaller version.

Thanks WAASup for the info. It looks like we'll all have to suffer the small JCV's from now on. Grrr!

Why oh why can't Garmin figure out a way to install the full JCV file on an SD card for us 14xx GPS users ... it would seem like a very simple to do ... heck, I could even program that logic "if not enough memory, prompt user to imput SD card. if SD present, install full JCV file."

Come on Garmin ... this would be a better solution than arbitrarily deciding to "CRIPPLE" our GPS's with some bastardized version of a JCV file.

This update is really strange...Texas, New Mexico, Arizona, and part of California is now labeled as Mexico. Florida is labled as Cuba, and the rest of the US says The United Socialist States of America.

God help us!

The impression I get is that Garmin has decided to release JCV files which is "series" dependent. In other words, if you have a 7x5 models you'll get a certain file, if you have a 1xxx you may get a different file, a 3xxx model will get you yet another file.

The decision about file size, it seems, does not depend on whether you have very low available storage space on your Nuvi or more space than you know what to do with. For example, it appears that on a Nuvi 775 with both NA and Europe maps, and 3GB of free space, you'll get a jcv file which would fit on a 755 or 765 which has half the storage space.

I'm not 100% sure this is whats happening but it really looks like it. I don't have particular problem with Garmin attempting to adjust JCV to insure that the maps will fit on the device. What I don't like is that it appears they maybe deciding on JCV file size based on Nuvi "series" and not on actual internal storage size for "each" model

It should go by internal memory, not the series.

However... if they go by the series, then the 7x0 is a different series than the 7x5's, right?

Garmin needs consistency on how it defines 'series', not a blanket statement on what the beginning number is.

This would make sense if they did this, but I don't think they're doing that just yet, considering my nuvi 765t has 4 gigs of internal memory and I still got the smaller junction view file. Maybe they'll start doing it this way with the next map update.

Maybe they class all 7xx models together. As I said, this looks like what they are doing although I have no possitive proof.

Agree, with some minor thought, they should be able to come up with a better plan than a "series" based decision table.

Why doesn't Garmin just give their customers the OPPORTUNITY to load the largest JCV file on an SD card if the internal memory is too small?

Getting the samller JCV's seems very strange. Have you by any chance used a lot of the extra space with additional maps and there is not enough room. I ask because we have 2 755s and when I downloadded the CNNA 2012.1 NT from Garmin both units were updated with the large JCV files(about 367.5 meg).

have the large junction view file, before I exchanged my 765t and had to re-download 2012.10. I was told by a Garmin representative that they removed most of the junction views a week after the release (without notifying anyone) due to the amount of complaints they were getting from owners of other models that didn't have a larger internal memory. So therefore, they took out most of the new junction views for ALL models, not just those models that had smaller internal memories, simply because they didn't feel like dealing with the problem. I was told that they hope to replace the removed junction views in a future map update, but who knows if that will ever really happen?

I wonder if it is a problem with the new "Photo real" sites. I have the large file on my unit and have noticed the change in some of the JV's near me that are now much more detailed. It could be a problem where the unit habngs because the processor isn't hefty enough to display the view and give directions as well.