Page 2 of 2   << first < 1 2
Bookmark this page: Add 76 Cx Navigation guestion to Yahoo MyWeb Add 76 Cx Navigation guestion to Google Bookmarks Add 76 Cx Navigation guestion to Windows Live Add 76 Cx Navigation guestion to Del.icio.us Digg 76 Cx Navigation guestion! Add 76 Cx Navigation guestion to Netscape
  •  
  • Subject
  • Author
  • Date
If you were  Registered and logged in, you could reply and use other advanced thread options
Posted by Klatch on August 8, 2010, 11:54 am



> Thanks, also to Bob and Klatch.
> I'll try putting in a waypoint just before and after a sideroad etc and
> give it a run.
> Also in Setup>Routing>, I have Guidance Method=== Follow Road.
> For Follow Road Method, I have=== Faster Time.
> Then under Follow Road Options I have, Off Road Recalculation===
> Automatic. Calculation Method===Better Route (???????)
> Then Calculate Routes for==Car/Motorcycle with U-Turns and Carpool Lanes
> avoided.
> Need any changes to help the wandering off problem? Thanks. Lee.
>> Lee wrote:
>>> I am assuming it must have layed out a shorter route or something,
>>> HOWEVER,
>>> I want the unit to navigate the route I layed out, with no surprise
>>> changes.
>> As someone else said, you need to build your route with waypoints that
>> will force the GPS to design the same route when it does its
>> calculations.
>> And if you do not start from exactly the same location, or you deviate
>> from the route, expect mayhem until you rejoin the original route.
>> or buy paper maps and draw your route on them. The only way to be sure
>> :-)
> --
> www.lightningnews.com Lightning fast anonymous usenet downloads for 5$
> only !

The only thing different in my setup is guidance method = "prompted". For
my uses, sometimes I need to select "off road". Other than that, I think
the different algorithms are the main cause of the difference and the best
method to get what you want is more via points.



Posted by JF Mezei on August 8, 2010, 3:36 pm


Lee wrote:

> I'll try putting in a waypoint just before and after a sideroad etc and give
> it a run.

Put waypoints in the middle of a road segment. This tends to provide
stronger "guidance" to force the GPS to steer you through that road.

Also, if you put waypoints near intersections, it will generate many
alarms as you reach intersection (your waypoint and then the "turn left"
one, or vice versa) and can be confusing.


Posted by LightByrd on August 8, 2010, 4:55 pm


> Lee wrote:
>> I'll try putting in a waypoint just before and after a sideroad etc and
>> give
>> it a run.
> Put waypoints in the middle of a road segment. This tends to provide
> stronger "guidance" to force the GPS to steer you through that road.
> Also, if you put waypoints near intersections, it will generate many
> alarms as you reach intersection (your waypoint and then the "turn left"
> one, or vice versa) and can be confusing.


I can attest to both of your points (I have 76CSx).

1) Put as many viapoints (no more!) as necessary to have Mapsource draw &
upload the route you want.
I have a 150 mile route that uses a lot of high speed good condition rural
roads.
No matter what criteria (best, fastest, most direct, avoid this, don't avoid
that) you give either Mapsource or the device itself, it will NEVER choose
what is indeed the fastest and most direct route! Nature of the beast

2) If you do choose intersections as via points, be darn sure you zoom
Mapsource into about 100 metres/yards before you place it.
I once had a u-turn sent to me because I was 10 feet past the intersection
--
Regards,
Richard Harison



Posted by JF Mezei on August 8, 2010, 5:29 pm


LightByrd wrote:

> 2) If you do choose intersections as via points, be darn sure you zoom
> Mapsource into about 100 metres/yards before you place it.
> I once had a u-turn sent to me because I was 10 feet past the intersection

Gets worse of you put the waypoint up a one-way street. The GPS will
then make you take a convoluted route to get to that waypoint "from
behind" and then rejoin the road.

Note that I have seen situations where RoadTrip on a map tolerates this,
but the GPS didn't and wanted a convoluted route to get to that waypoint.

This is why I prever waypoints in the middle of a road segment, away
from significant intersections, unless I personally need this. (aka:
calculating distance until I reach a certain road).


Posted by LightByrd on August 8, 2010, 5:47 pm


> LightByrd wrote:
>> 2) If you do choose intersections as via points, be darn sure you zoom
>> Mapsource into about 100 metres/yards before you place it.
>> I once had a u-turn sent to me because I was 10 feet past the
>> intersection
> Gets worse of you put the waypoint up a one-way street. The GPS will
> then make you take a convoluted route to get to that waypoint "from
> behind" and then rejoin the road.
> Note that I have seen situations where RoadTrip on a map tolerates this,
> but the GPS didn't and wanted a convoluted route to get to that waypoint.
> This is why I prever waypoints in the middle of a road segment, away
> from significant intersections, unless I personally need this. (aka:
> calculating distance until I reach a certain road).


Only problem there is, as you point out, I am a "distance to next" freak,
and I interpret that as an intersection or like.
At any rate I would assume that a mid segment viapoint should be placed
AFTER an intersection involving a turn!

--
Regards,
Richard Harison



Page 2 of 2   << first < 1 2
Related Posts
  • Subject
  • Posted In
  • Date