PanEuropean said:
OK It will be interesting to see what happens if and when you try it.
Richard
Glitches in Garmin V8 - open letter to Garmin
- Thread starter Wapping
- Start date
OK It will be interesting to see what happens if and when you try it.
Richard
Invicta Moto
Registered user
Greg Masters said:
I was going to ask where Garmin get the mapping from! I have yet to move to V8 from V7 on my Quest to see if my house/street is finally on the maps.
Despite being 7 years old doesn't feature in V7 although it does show up on Streetmap.co.uk that also uses Ordnance Survey....
Maybe I'll getlucky then if I go to V8?
Invicta Moto said:
My house was.
markie_wales
Registered user
Invicta Moto said:
Paul
if you go to the Garmin site, you can view V8 on line - worth checking out.
Mark
PanEuropean
Registered user
Invicta Moto said:
Garmin purchases their continent-wide mapping (e.g. City Navigator North America, City Navigator Europe) from Navteq, who are the world's largest compiler of electronic vector maps. Navteq gets their data from a variety of sources, primarily by purchasing it from the governments of the countries that are included in the product.
It's very important to recognize that Garmin does not make maps, and they are really not in the business of selling maps. Garmin is a hardware and software company, not a cartography company. It's sort of like the relationship that Dell and IBM have with software companies - IBM and Dell make computers, they don't make Windows or the programs we use on the computers. The same concept applies to Garmin - they make the GPSRs, and write the software that allows the GPSR to operate, but they don't make maps.
Michael
I remember the good 'ole days, ya never had this much with a map....... 
BTBR
BTBR
Michael,
News in from a friend of mine who is suffering the same problem:
Hi Richard
I’m delighted something seems to be happening. I can think of four specific examples (two in the UK and two in France) where I have the printed route, Garmin route and possibly film with Garmin’s announcement recorded.
I’ll collate and forward.
John
News in from a friend of mine who is suffering the same problem:
Hi Richard
I’m delighted something seems to be happening. I can think of four specific examples (two in the UK and two in France) where I have the printed route, Garmin route and possibly film with Garmin’s announcement recorded.
I’ll collate and forward.
John
Der Lustenauer
Guest
I would see the analogy slightly different, or is it the same?PanEuropean said:
Garmin is
• The computer manufacturer (as in Dell)
• The operating system manufacturer (as in Windows)
• The program manufacturer (just as in Adobe manufactures Photoshop)
the cartography people deliver the photo just as in the analogy to Photoshop.
Garmin sells maps made out of the cartography data (the photo) which can then (only?) be read by Garmin's software on their devices or on PC's.
They also might incorporate music players in their devices soon which would make my IPod redundant.
I am happy with all of the above, don't understand me wrong!
PanEuropean
Registered user
I agree with what you say - it was kind of tough for me to construct an analogy, and I think you have done just as good (or bad 
) a job as I did.
The point I was trying to stress to everyone is that Garmin doesn't have anything to do with the collection of map data. That's entirely Navteq. The only thing that Garmin does with map data is to compile the Navteq information into a format that Garmin GPSRs can read.
To be fair to Navteq, though, when you consider the immense amount of detail that they have to collect and compile, they are pretty darn good at it. Obviously, we notice the glitches, not the trouble-free parts. But, when you think about it, probably 99.999% is accurate and trouble-free. Heck, I don't even think the local phone book achieves that kind of accuracy, and that's a much simpler database than streets, roads, and POIs.
Michael
) a job as I did.The point I was trying to stress to everyone is that Garmin doesn't have anything to do with the collection of map data. That's entirely Navteq. The only thing that Garmin does with map data is to compile the Navteq information into a format that Garmin GPSRs can read.
To be fair to Navteq, though, when you consider the immense amount of detail that they have to collect and compile, they are pretty darn good at it. Obviously, we notice the glitches, not the trouble-free parts. But, when you think about it, probably 99.999% is accurate and trouble-free. Heck, I don't even think the local phone book achieves that kind of accuracy, and that's a much simpler database than streets, roads, and POIs.
Michael
If you want another anomaly, I've noted this one on an SP3, 2610 and Nav 2 from CN EU v5 to v8 and they all do it!
The anomaly is that you go from a local country road across the wrong way lane and onto the one you'll take, all with no instructions. Maybe its like the earlier examples where the GPSR / PC doesn't "see" the junction?
The directions onthe PC match the GPS's BTW.
The anomaly is that you go from a local country road across the wrong way lane and onto the one you'll take, all with no instructions. Maybe its like the earlier examples where the GPSR / PC doesn't "see" the junction?
The directions onthe PC match the GPS's BTW.
cookiemonster
Guest
Hi
Funnily enough, I'm just back from a fairly lengthy european trip which was the first time I've used my GPS to any real extent. I've a Quest running CN v8.0
I was going to put a post on here asking about some of the problems I'd encountered, namely the "roundabout" issue (being routed back and forth between two motorway junction roundabouts) and the "random exit" problem - whereby I'd be prompted to come off a main road onto a side road even although the route was straight ahead. I didnt keep any details as i'd assumed that it was all user error, being new this stuff.
I found, as someone else has mentioned, that I had to double check the pop-up display each time after the voice prompt, as sometimes "turn left" could mean "stay on the main road which has a left turn", rather than actually taking the road to the left, and a few other quirks. The "quirks" I could live with after some getting used to it all, but the "glitches" really were a bit of a pain at times.
That said I maybe had 5 or 6 "glitches" in 2154 miles across France, Spain & Belgium; crossing countries on farm tracks, forest trails and gravel roads. It just couldn't be done without the GPS. It really is a superb bit of kit.
jon
Funnily enough, I'm just back from a fairly lengthy european trip which was the first time I've used my GPS to any real extent. I've a Quest running CN v8.0
I was going to put a post on here asking about some of the problems I'd encountered, namely the "roundabout" issue (being routed back and forth between two motorway junction roundabouts) and the "random exit" problem - whereby I'd be prompted to come off a main road onto a side road even although the route was straight ahead. I didnt keep any details as i'd assumed that it was all user error, being new this stuff.
I found, as someone else has mentioned, that I had to double check the pop-up display each time after the voice prompt, as sometimes "turn left" could mean "stay on the main road which has a left turn", rather than actually taking the road to the left, and a few other quirks. The "quirks" I could live with after some getting used to it all, but the "glitches" really were a bit of a pain at times.
That said I maybe had 5 or 6 "glitches" in 2154 miles across France, Spain & Belgium; crossing countries on farm tracks, forest trails and gravel roads. It just couldn't be done without the GPS. It really is a superb bit of kit.
jon
denester
Guest
Shut down AO-Hell 9.0, better still delete; it ferks up everything else, it may have nothing to do with your problem but I'd feel better knowing it was gone 
I haven't seen any further posts regarding these anomalies - was anything resolved about this issue with Garmin? It sounded like the Engineers were looking at it....
PanEuropean
Registered user
The software engineers did take a very close look at it.
The gist of the response I got back from software engineering was this: Try to avoid putting intermediate waypoints directly on top of an intersection, or directly on top of a roundabout. If the intersection or roundabout is sufficiently complex, it is possible that MapSource may try to route you to a specific spot in that intersection/roundabout without you being aware that is what is happening.
My guess is that they are going to look at it further and probably do something to resolve it with the next revision of MapSource.
I'm going to guess (my personal guess here) that the problem is this: Way back when cartography was pretty simple and roundabouts and intersections consisted of nothing more than two roads crossing each other, you could put your intermediate waypoint wherever you wanted - it didn't matter. Now, though, the amount of detail that is contained the cartography (detail that you don't see on the screen) is fuggin' awesome - this is why the GPSR is smart enough to be able to tell you what lane to get into at an intersection, or to 'turn left, then keep left' or 'enter roundabout, then keep right' when you are navigating through a complex intersection. So, if you drop an intermediate waypoint on top of a sufficiently complex intersection - one that has more detail to it than you can actually see - the route that results might have more 'precision' to it than you really want.
Moral of the story: Try to drop enroute waypoints just after intersections or roundabouts. Extra bonus you get for doing this: When you navigate the route, the GPSR will focus all its attention on giving you proper guidance through the roundabout/intersection, and once you are through it, it will then mention that the intermediate waypoint is coming up on your left/right, as the case may be. You won't have the GPSR blabbing about an intermediate waypoint at the very same time you are trying to figure out whether to turn right, turn left, go straight, or dodge the truck that looks like it is going to run the red light.
Michael
The gist of the response I got back from software engineering was this: Try to avoid putting intermediate waypoints directly on top of an intersection, or directly on top of a roundabout. If the intersection or roundabout is sufficiently complex, it is possible that MapSource may try to route you to a specific spot in that intersection/roundabout without you being aware that is what is happening.
My guess is that they are going to look at it further and probably do something to resolve it with the next revision of MapSource.
I'm going to guess (my personal guess here) that the problem is this: Way back when cartography was pretty simple and roundabouts and intersections consisted of nothing more than two roads crossing each other, you could put your intermediate waypoint wherever you wanted - it didn't matter. Now, though, the amount of detail that is contained the cartography (detail that you don't see on the screen) is fuggin' awesome - this is why the GPSR is smart enough to be able to tell you what lane to get into at an intersection, or to 'turn left, then keep left' or 'enter roundabout, then keep right' when you are navigating through a complex intersection. So, if you drop an intermediate waypoint on top of a sufficiently complex intersection - one that has more detail to it than you can actually see - the route that results might have more 'precision' to it than you really want.
Moral of the story: Try to drop enroute waypoints just after intersections or roundabouts. Extra bonus you get for doing this: When you navigate the route, the GPSR will focus all its attention on giving you proper guidance through the roundabout/intersection, and once you are through it, it will then mention that the intermediate waypoint is coming up on your left/right, as the case may be. You won't have the GPSR blabbing about an intermediate waypoint at the very same time you are trying to figure out whether to turn right, turn left, go straight, or dodge the truck that looks like it is going to run the red light.
Michael
PanEuropean said:The software engineers did take a very close look at it.
The gist of the response I got back from software engineering was this: Try to avoid putting intermediate waypoints directly on top of an intersection, or directly on top of a roundabout. If the intersection or roundabout is sufficiently complex, it is possible that MapSource may try to route you to a specific spot in that intersection/roundabout without you being aware that is what is happening.
My guess is that they are going to look at it further and probably do something to resolve it with the next revision of MapSource.
I'm going to guess (my personal guess here) that the problem is this: Way back when cartography was pretty simple and roundabouts and intersections consisted of nothing more than two roads crossing each other, you could put your intermediate waypoint wherever you wanted - it didn't matter. Now, though, the amount of detail that is contained the cartography (detail that you don't see on the screen) is fuggin' awesome - this is why the GPSR is smart enough to be able to tell you what lane to get into at an intersection, or to 'turn left, then keep left' or 'enter roundabout, then keep right' when you are navigating through a complex intersection. So, if you drop an intermediate waypoint on top of a sufficiently complex intersection - one that has more detail to it than you can actually see - the route that results might have more 'precision' to it than you really want.
Moral of the story: Try to drop enroute waypoints just after intersections or roundabouts. Extra bonus you get for doing this: When you navigate the route, the GPSR will focus all its attention on giving you proper guidance through the roundabout/intersection, and once you are through it, it will then mention that the intermediate waypoint is coming up on your left/right, as the case may be. You won't have the GPSR blabbing about an intermediate waypoint at the very same time you are trying to figure out whether to turn right, turn left, go straight, or dodge the truck that looks like it is going to run the red light.
Michael
Thanks for the info and advice Michael...
skellum said:
Ditto.
Similar threads
