Bookmark this page:
- Mapsource-fastest-route
- 05-12-2008
  Re: Mapsource fastest route
| Jack Erbes | 05-12-2008 |
  Re: Mapsource fastest route
| Dave Friedenber... | 05-12-2008 |
 Re: Mapsource fastest route
| Thibaud Taudin ... | 05-12-2008 |
  Re: Mapsource fastest route
| Dave Friedenber... | 05-12-2008 |
 Re: Mapsource fastest route
| Thibaud Taudin ... | 05-12-2008 |
| Re: Mapsource fastest route
| ben brugman | 05-12-2008 |
| Re: Mapsource fastest route
| Jack Erbes | 05-13-2008 |
| Re: Mapsource fastest route
| ben brugman | 05-13-2008 |
If you were Registered and logged in, you could reply and use other advanced thread options
When I plan a certain route in Mapsource using City Navigator CN 2008
Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
But when I introduce a waypoint C between A and B that is outside the
route Mapsource found from A to B it results in a shorter and faster
route: 1489 km in 14:42 hours.
My preferences are: preferred highways, no route exclusions, fastest route.
How can? Is this normal? In that case you can't rely anymore on the
'fastest route' found by Mapsource.
Thibaud
Thibaud Taudin Chabot wrote:
It is done by an algorithm in software, I suppose there is something in
the logic can cause what would appear to be an error from a human view.
The GPS receiver is just seeing and choosing from a collection of
vectors. The vectors have attributes that probably rank the roads as
far as their type and speed limits.
If the route passing via point C adds some roads of a lower category to
the route, and those are more direct and also have the same or nearly
the speed limits as the major roads, it could explain the shorter and
quicker route. The algorithm is probably choosing the higher category
of roads and not considering that a lower category road with the same
speed limit is a better choice.
The GPS receivers algorithms are not smart as far as having any
knowledge of local conditions or traffic loadings, it is all about the
theoretical travel times based on the road attributes and your settings.
Jack
--
Jack Erbes in Ellsworth, Maine, USA - jackerbes at adelphia dot net
(also receiving email at jacker at midmaine.com)
Jack Erbes wrote:
> Thibaud Taudin Chabot wrote:
>> When I plan a certain route in Mapsource using City Navigator CN 2008
>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>> But when I introduce a waypoint C between A and B that is outside the
>> route Mapsource found from A to B it results in a shorter and faster
>> route: 1489 km in 14:42 hours.
>> My preferences are: preferred highways, no route exclusions, fastest route.
>> How can? Is this normal? In that case you can't rely anymore on the
>> 'fastest route' found by Mapsource.
>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>> But when I introduce a waypoint C between A and B that is outside the
>> route Mapsource found from A to B it results in a shorter and faster
>> route: 1489 km in 14:42 hours.
>> My preferences are: preferred highways, no route exclusions, fastest route.
>> How can? Is this normal? In that case you can't rely anymore on the
>> 'fastest route' found by Mapsource.
>
> It is done by an algorithm in software, I suppose there is something in
> the logic can cause what would appear to be an error from a human view.
>
> The GPS receiver is just seeing and choosing from a collection of
> vectors. The vectors have attributes that probably rank the roads as
> far as their type and speed limits.
>
> If the route passing via point C adds some roads of a lower category to
> the route, and those are more direct and also have the same or nearly
> the speed limits as the major roads, it could explain the shorter and
> quicker route. The algorithm is probably choosing the higher category
> of roads and not considering that a lower category road with the same
> speed limit is a better choice.
>
> The GPS receivers algorithms are not smart as far as having any
> knowledge of local conditions or traffic loadings, it is all about the
> theoretical travel times based on the road attributes and your settings.
>
> Jack
>
I agree with Jack's analysis of your routing question. I've run into
> It is done by an algorithm in software, I suppose there is something in
> the logic can cause what would appear to be an error from a human view.
>
> The GPS receiver is just seeing and choosing from a collection of
> vectors. The vectors have attributes that probably rank the roads as
> far as their type and speed limits.
>
> If the route passing via point C adds some roads of a lower category to
> the route, and those are more direct and also have the same or nearly
> the speed limits as the major roads, it could explain the shorter and
> quicker route. The algorithm is probably choosing the higher category
> of roads and not considering that a lower category road with the same
> speed limit is a better choice.
>
> The GPS receivers algorithms are not smart as far as having any
> knowledge of local conditions or traffic loadings, it is all about the
> theoretical travel times based on the road attributes and your settings.
>
> Jack
>
similar problems with some routes in Southern California. In my case,
the problem was caused by having the Road Selection preference in
Mapsource set all the way to the right to "Prefer Highways." When I
moved the Road Selection slider two places to the left of Prefer
Highways, Mapsource gave me the shortest and fastest route. Try
experimenting with different Road Selection preferences and see if you
get better routes.
Dave Friedenberg schreef:
> Jack Erbes wrote:
>> Thibaud Taudin Chabot wrote:
>>> When I plan a certain route in Mapsource using City Navigator CN 2008
>>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>>> But when I introduce a waypoint C between A and B that is outside the
>>> route Mapsource found from A to B it results in a shorter and faster
>>> route: 1489 km in 14:42 hours.
>>> My preferences are: preferred highways, no route exclusions, fastest
>>> route.
>>> How can? Is this normal? In that case you can't rely anymore on the
>>> 'fastest route' found by Mapsource.
>>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>>> But when I introduce a waypoint C between A and B that is outside the
>>> route Mapsource found from A to B it results in a shorter and faster
>>> route: 1489 km in 14:42 hours.
>>> My preferences are: preferred highways, no route exclusions, fastest
>>> route.
>>> How can? Is this normal? In that case you can't rely anymore on the
>>> 'fastest route' found by Mapsource.
>> It is done by an algorithm in software, I suppose there is something in
>> the logic can cause what would appear to be an error from a human view.
>> The GPS receiver is just seeing and choosing from a collection of
>> vectors. The vectors have attributes that probably rank the roads as
>> far as their type and speed limits.
>> If the route passing via point C adds some roads of a lower category to
>> the route, and those are more direct and also have the same or nearly
>> the speed limits as the major roads, it could explain the shorter and
>> quicker route. The algorithm is probably choosing the higher category
>> of roads and not considering that a lower category road with the same
>> speed limit is a better choice.
>> The GPS receivers algorithms are not smart as far as having any
>> knowledge of local conditions or traffic loadings, it is all about the
>> theoretical travel times based on the road attributes and your settings.
>> Jack
>> the logic can cause what would appear to be an error from a human view.
>> The GPS receiver is just seeing and choosing from a collection of
>> vectors. The vectors have attributes that probably rank the roads as
>> far as their type and speed limits.
>> If the route passing via point C adds some roads of a lower category to
>> the route, and those are more direct and also have the same or nearly
>> the speed limits as the major roads, it could explain the shorter and
>> quicker route. The algorithm is probably choosing the higher category
>> of roads and not considering that a lower category road with the same
>> speed limit is a better choice.
>> The GPS receivers algorithms are not smart as far as having any
>> knowledge of local conditions or traffic loadings, it is all about the
>> theoretical travel times based on the road attributes and your settings.
>> Jack
> I agree with Jack's analysis of your routing question. I've run into
> similar problems with some routes in Southern California. In my case,
> the problem was caused by having the Road Selection preference in
> Mapsource set all the way to the right to "Prefer Highways." When I
> moved the Road Selection slider two places to the left of Prefer
> Highways, Mapsource gave me the shortest and fastest route. Try
> experimenting with different Road Selection preferences and see if you
> get better routes.
The routes that are used after introducing point C have a higher
> similar problems with some routes in Southern California. In my case,
> the problem was caused by having the Road Selection preference in
> Mapsource set all the way to the right to "Prefer Highways." When I
> moved the Road Selection slider two places to the left of Prefer
> Highways, Mapsource gave me the shortest and fastest route. Try
> experimenting with different Road Selection preferences and see if you
> get better routes.
speedlimit (no speedlimit at all: Germany) then the routes used from A
to B (without C. So the effect you mention can not be the reason.
Thibaud
Thibaud Taudin Chabot wrote:
> Dave Friedenberg schreef:
>> Jack Erbes wrote:
>>> Thibaud Taudin Chabot wrote:
>>>> When I plan a certain route in Mapsource using City Navigator CN 2008
>>>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>>>> But when I introduce a waypoint C between A and B that is outside the
>>>> route Mapsource found from A to B it results in a shorter and faster
>>>> route: 1489 km in 14:42 hours.
>>>> My preferences are: preferred highways, no route exclusions, fastest
>>>> route.
>>>> How can? Is this normal? In that case you can't rely anymore on the
>>>> 'fastest route' found by Mapsource.
>>> It is done by an algorithm in software, I suppose there is something in
>>> the logic can cause what would appear to be an error from a human view.
>>> The GPS receiver is just seeing and choosing from a collection of
>>> vectors. The vectors have attributes that probably rank the roads as
>>> far as their type and speed limits.
>>> If the route passing via point C adds some roads of a lower category to
>>> the route, and those are more direct and also have the same or nearly
>>> the speed limits as the major roads, it could explain the shorter and
>>> quicker route. The algorithm is probably choosing the higher category
>>> of roads and not considering that a lower category road with the same
>>> speed limit is a better choice.
>>> The GPS receivers algorithms are not smart as far as having any
>>> knowledge of local conditions or traffic loadings, it is all about the
>>> theoretical travel times based on the road attributes and your settings.
>>> Jack
>>>> When I plan a certain route in Mapsource using City Navigator CN 2008
>>>> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
>>>> But when I introduce a waypoint C between A and B that is outside the
>>>> route Mapsource found from A to B it results in a shorter and faster
>>>> route: 1489 km in 14:42 hours.
>>>> My preferences are: preferred highways, no route exclusions, fastest
>>>> route.
>>>> How can? Is this normal? In that case you can't rely anymore on the
>>>> 'fastest route' found by Mapsource.
>>> It is done by an algorithm in software, I suppose there is something in
>>> the logic can cause what would appear to be an error from a human view.
>>> The GPS receiver is just seeing and choosing from a collection of
>>> vectors. The vectors have attributes that probably rank the roads as
>>> far as their type and speed limits.
>>> If the route passing via point C adds some roads of a lower category to
>>> the route, and those are more direct and also have the same or nearly
>>> the speed limits as the major roads, it could explain the shorter and
>>> quicker route. The algorithm is probably choosing the higher category
>>> of roads and not considering that a lower category road with the same
>>> speed limit is a better choice.
>>> The GPS receivers algorithms are not smart as far as having any
>>> knowledge of local conditions or traffic loadings, it is all about the
>>> theoretical travel times based on the road attributes and your settings.
>>> Jack
>> I agree with Jack's analysis of your routing question. I've run into
>> similar problems with some routes in Southern California. In my case,
>> the problem was caused by having the Road Selection preference in
>> Mapsource set all the way to the right to "Prefer Highways." When I
>> moved the Road Selection slider two places to the left of Prefer
>> Highways, Mapsource gave me the shortest and fastest route. Try
>> experimenting with different Road Selection preferences and see if you
>> get better routes.
>> similar problems with some routes in Southern California. In my case,
>> the problem was caused by having the Road Selection preference in
>> Mapsource set all the way to the right to "Prefer Highways." When I
>> moved the Road Selection slider two places to the left of Prefer
>> Highways, Mapsource gave me the shortest and fastest route. Try
>> experimenting with different Road Selection preferences and see if you
>> get better routes.
> The routes that are used after introducing point C have a higher
> speedlimit (no speedlimit at all: Germany) then the routes used from A
> to B (without C. So the effect you mention can not be the reason.
> Thibaud
Thibaud,
> speedlimit (no speedlimit at all: Germany) then the routes used from A
> to B (without C. So the effect you mention can not be the reason.
> Thibaud
Sorry that I didn't make my suggestion clearer. What I was suggesting
was that you experiment with different road selection preferences when
you use Mapsource to create a route between your points A and B. Do not
use your point C. See if one road selection preference setting gives you
a route similar to what you got when you used point C as a waypoint. In
my case, when I used Mapsource to create a route between A and B, I got
a different route with each road selection preference I tried.
Dave
- Mapsource
- Garmin GPS
- 2008-04-14
- Is there a way to get my Nuvi 850 to take a different route to the expressway?
- Garmin GPS
- 2009-01-20
- WTB new Nuvi / Route planning ?'s
- Garmin GPS
- 2008-12-10
- routing - fastest vs logical / direct
- Garmin GPS
- 2008-04-01
- c330 - adding route.
- Garmin GPS
- 2007-08-05
- wierd mapsource phenomena
- Satellite Navigation
- 2005-11-22
- GPS vs MapSource routing
- Garmin GPS
- 2007-04-25
- Switching Route
- Garmin GPS
- 2006-09-10
> Europe from A to B Mapsources finds a route of 1508 km in 15:10 hours.
> But when I introduce a waypoint C between A and B that is outside the
> route Mapsource found from A to B it results in a shorter and faster
> route: 1489 km in 14:42 hours.
> My preferences are: preferred highways, no route exclusions, fastest route.
> How can? Is this normal? In that case you can't rely anymore on the
> 'fastest route' found by Mapsource.