In other threads, you Guru's have mentioned that some routing errors can be the result of a map database error.
The road has a "missing" section. So it seems like the road does not continue - the program tries to route you around the "missing" section of the road.
With your help, I have come to learn that Garmin Mobile PC uses the same map database as the Garmin Nuvi, and Microsoft Streets and Trips. (database by Navteq).
Here is a paved road called "Live Oak Ridge Rd" in California as viewed in Garmin Mobile PC (newest version 5.00.70g) with newest map updated last week
You will see the left side of the road has a THIN LINE compared to the right side of "Live Oak Ridge Rd", and Mobile PC will not allow me to create a route that travels across the thin section.
When I try to "shape" the route with that feature of Garmin Mobil PC, I can create as many "points" and add them to the route as I want - but the program still puts a "U-turn" in the route and sends me on a long loop to get to my final destination. I ended up adding about 10 points along that thin section of road, and it never allowed me to simply drive down that road.
When I am home in California, I often travel this route to a family member's house. My Nuvi prefers a different route, but when it sees I am taking these back roads, it will re-calc and allow me to simply drive that road with proper turn instructions.
When I am running Streets & Trips 2010 it will suggest a different route, but I can easily "drag" the route onto this road without errors (image attached).
- why does Garmin Mobil PC have this issue, yet Nuvi & Streets-Trips do not?
- is there a "work around" remedy to create routes when this stuff occurs?
For anyone interested in looking at this section of road on your map software, you can enter any street number between 700 to 900 on "Live Oak Ridge Rd" in zip code 93444 Nipomo, California. It runs between Pomeroy road on the left, and Hetrick on the right.
The road has a "missing" section. So it seems like the road does not continue - the program tries to route you around the "missing" section of the road.
With your help, I have come to learn that Garmin Mobile PC uses the same map database as the Garmin Nuvi, and Microsoft Streets and Trips. (database by Navteq).
Here is a paved road called "Live Oak Ridge Rd" in California as viewed in Garmin Mobile PC (newest version 5.00.70g) with newest map updated last week
You will see the left side of the road has a THIN LINE compared to the right side of "Live Oak Ridge Rd", and Mobile PC will not allow me to create a route that travels across the thin section.
When I try to "shape" the route with that feature of Garmin Mobil PC, I can create as many "points" and add them to the route as I want - but the program still puts a "U-turn" in the route and sends me on a long loop to get to my final destination. I ended up adding about 10 points along that thin section of road, and it never allowed me to simply drive down that road.
When I am home in California, I often travel this route to a family member's house. My Nuvi prefers a different route, but when it sees I am taking these back roads, it will re-calc and allow me to simply drive that road with proper turn instructions.
When I am running Streets & Trips 2010 it will suggest a different route, but I can easily "drag" the route onto this road without errors (image attached).
- why does Garmin Mobil PC have this issue, yet Nuvi & Streets-Trips do not?
- is there a "work around" remedy to create routes when this stuff occurs?
For anyone interested in looking at this section of road on your map software, you can enter any street number between 700 to 900 on "Live Oak Ridge Rd" in zip code 93444 Nipomo, California. It runs between Pomeroy road on the left, and Hetrick on the right.
Here's the "shaped route" with Mobile PC.
At first you think that the added points along the "thin" section of road are going to let you drive down that road.
But the route includes a detour "loop" to the road below it, and the turn-by-turn directions include a U-Turn
At first you think that the added points along the "thin" section of road are going to let you drive down that road.
But the route includes a detour "loop" to the road below it, and the turn-by-turn directions include a U-Turn
Here's the route when driving. Both applications are running with their own GPS receiver.
Left side = Streets & Trips, Right side = Mobile PC (doing the "loop" to avoid part of road it apparantly thinks is missing).
This Mobile PC route does not have the "U-turn" because I did not try to shape the route. Simply started over and asked it to go to the destination.
Left side = Streets & Trips, Right side = Mobile PC (doing the "loop" to avoid part of road it apparantly thinks is missing).
This Mobile PC route does not have the "U-turn" because I did not try to shape the route. Simply started over and asked it to go to the destination.
I can see what the problem is using MapSource and CNNA NT 2010.4. Apparently, per your testing, S&T is right and Garmin is wrong about the status of that stretch of the road. I don't know why your Nuvi would route across it nor how you could fix it in Mobile PC; maybe allow unpaved roads.
Terry
Terry
I also note several other roads in that area that look like trails in MapSource and roads in S&T. Check Feijoa Pl, Cherokee Pl, Golf Ball Rd, Calle Fresa, Hetrick Ave and Amber Way for example.
Terry
Terry
Thanks - and yeah that fixed it.
Here's some photos of what the "avoidances" were prior to changes.
Once I allowed it to drive on unpaved roads, it routed me correctly without detour. Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)
Most of those "unpaved" roads you mention are paved, with $500,000 houses on them (even with todays economy...)
Here's some photos of what the "avoidances" were prior to changes.
Once I allowed it to drive on unpaved roads, it routed me correctly without detour. Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)
Most of those "unpaved" roads you mention are paved, with $500,000 houses on them (even with todays economy...)
Do you know how long ago they were paved? It takes a while for the changes to filter through Navteq but it is strange that S&T does not indicate any difference as it uses the same database.
Terry
Terry
Quote:
... "Live Oak Ridge Rd" in zip code 93444 Nipomo, California. It runs between Pomeroy road on the left, and Hetrick on the right.
Here's an image from Delorme that shows a normal paved road across the full run of that "Live Oak Ridge Rd".
Here's what is strange, about a mile north of that region there is a stretch of Hetrick ave that becomes a dirt road that looks like a mine field (virtually impassable) and every GPS I have encountered will route people through hell getting across that road. Delorme used to route me through it, my old Magellan GPS, my Garmin Nuvi, and now Garmin Mobile PC and Streets & Trips. Here's an image of Delorme routing you through shock absorber hell
Glad you guys got it figured out. I fired up Mapsource and City Navigator NA 2010.4 and Mapsource routed straight across it with no problem
So I fired up Mobile PC 6.00.70 and it also routed straight across it. without a problem.
I checked my settings in Mobile PC and the only thing I have set to avoid is U-Turns. My settings in Mapsource are to avoid U-Turns and Seasonal Road Closures.
...ken...
So I fired up Mobile PC 6.00.70 and it also routed straight across it. without a problem.
I checked my settings in Mobile PC and the only thing I have set to avoid is U-Turns. My settings in Mapsource are to avoid U-Turns and Seasonal Road Closures.
...ken...
Hi Ken, with those settings my Mobile PC is OK. It was the "avoid unpaved roads" that caused the grief. (despite the fact the road has been paved for at least 10 years that I know of).
This one road isn't that big of a deal (although I drive it at least twice a week). The main thing is I am trying to learn these tools - because when I have to run out of town and inspect a bunch of damaged houses I won't have time to learn the software.
-----------------------------------
Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)?
-----------------------------------
I am thinking there is a typo there... cuz version 6 isn't available. I think we are both using the "new" 5.00.70
There was a recent thread with title:
Changes made from version 5.00.60 to 5.00.70:
This one road isn't that big of a deal (although I drive it at least twice a week). The main thing is I am trying to learn these tools - because when I have to run out of town and inspect a bunch of damaged houses I won't have time to learn the software.
-----------------------------------
Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)?
-----------------------------------
Quote:
...So I fired up Mobile PC 6.00.70 and it also routed straight across it. without a problem.
There was a recent thread with title:
Changes made from version 5.00.60 to 5.00.70:
Ooops. I've been spending a lot of time with the new Mapsource beta version the past couple of days. It's 6.16.02, so I must have 6.xx.xx burned into my brain at the moment. Sorry, you're right about the typo.
...ken...
...ken...
Quote:
-----------------------------------
Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)?
-----------------------------------
Is this a "broken road" (database error) or is there another variable here (the database agrees that a road is present, but that it is unpaved)?
-----------------------------------
If you are concerned you should report it to Navteq at their Map Reporter. Those sorts of errors will not usually get corrected unless someone reports them. The Map Reporter makes it pretty easy to report errors like this and it's worth taking a few minutes to do it.
...ken...
Thanks for the link, and that is a great resource.
I tried to report this "road or road feature" issue but couldn't get past the 2nd screen. It says to zoom in on the map, when I do that I end up in the middle of the ocean... no matter how I try to click on the site address or any other navigation, it goes nowhere.
Do I need to register to use this site? (it didn't provide any "notice" that this was the issue...)
I tried to report this "road or road feature" issue but couldn't get past the 2nd screen. It says to zoom in on the map, when I do that I end up in the middle of the ocean... no matter how I try to click on the site address or any other navigation, it goes nowhere.
Do I need to register to use this site? (it didn't provide any "notice" that this was the issue...)
Never mind, I clicked on "classic view" and the features worked. I was able to report it.
Their map on website also has an issue with this road "stopping". In fact when you click on the missing section, it provides address of the nearby roads because it acts like that part of the road isn't there...
Their map on website also has an issue with this road "stopping". In fact when you click on the missing section, it provides address of the nearby roads because it acts like that part of the road isn't there...
Use the Find & Report tab and enter Live Oak Ridge Rd 93444.
Terry
Terry
OK, I went back to their site and walked through this again, and hit the same impasse (perhaps my IE 7 browser or something is not compatible, or anti-virus software, who knows). I have to use the "classic" view, because with this default page I cannot get the instructions to work (zoom into map) yet with the classic view it went immediately to the street.
Anyway I am glad to learn about this "report an error" thing, I had no idea without help from you folks.
Anyway I am glad to learn about this "report an error" thing, I had no idea without help from you folks.
Catch-22. If webmasters leave their sites compatible with IE7 and earlier they won't work properly with IE8. If they update them to be fully compatible with IE8 they won't work properly with older versions.
It's good to know that Navteq has provided an option so both versions will work properly, even though it's a lot more work for them.
You can thank Microsoft for the problem.
...ken...
It's good to know that Navteq has provided an option so both versions will work properly, even though it's a lot more work for them.
You can thank Microsoft for the problem.
...ken...
I use IE7 and it works fine. It does complain I don't have the correct Java plug in but I ignored that.
Terry
Terry