| Versions |
 |
|
| Author |
Topic  |
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 17 juin 2005 : 17:55:33
|
Most of the time I have no need for using any setting other than Quickest. When the Quickest setting is used iGuidance generates in my experience very very good routes.
But occasionally I do find myself in need of avoiding highways. Is Local supposed to help me with that? (It often doesn't in my area)
Sometimes I don't care about how quickly I will get to my destination, but it is more important that the route be the shortest. The Shortest setting doesn't often generate the route of the shortest distance either.
I admit I don't know what the Major setting is really for. I personally would like to see iGuidance one day replacing Major and Local with just simple Highways Disable/Enable, just like the current Toll Roads Disable/Enable option.
SHORTEST
The following pictures show iGuidance 2.1.1 versus MS Streets & Trips 2005 both set to calculate the shortest route:
Start: 2601 Finch Ave West, Toronto, Ontario, Canada Destination: 1601 Finch Ave East, Toronto, Ontario, Canada


Marvin Hlavac - Toronto, Canada |
Edited by - Marvin Hlavac on 27 juin 2005 17:52:39
|
|
|
Ads
|
|
|
Squaredancer
284 Posts |
Posted - 17 juin 2005 : 18:59:18
|
quote: [i]Quoted from an earlier INAV response......FYI: "shortest" means the route which gives you the "shortest" distance, and it does only that.
In the "shortest" distance route option, iGuidance will provide a route where mathematically calculated to have the "shortest" miles/ft/yd, but it may be on a surface street or residential street where you have to drive at much much less speed and w/ many stop lights and stop signs.
Hmmmm.....I wonder what kind of math they are using????? |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 17 juin 2005 : 19:32:39
|
It should work exactly the way iNav described it, but either there is some bug there or it is just simply designed by programmers to take into consideration time value, not just distance value :(
I do wish the programmers could look into it when they have the time.
I'll post more pictures in a few days...
Marvin Hlavac - Toronto, Canada |
 |
|
|
Squaredancer
284 Posts |
Posted - 17 juin 2005 : 20:02:26
|
quote: Originally posted by Marvin Hlavac
It should work exactly the way iNav described it
I agree with you wholeheartedly, but....
quote: From an anonymous source
3. Info regarding routing issue will be posted and hopefully once for all will take care of this issue. 4. Some customers are looking for 100% PERFECT software which in real world is not just possible.
I do hope they take the information posted here more seriously than they have in the past. Customer satisfaction is what all good companies strive for.
|
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 17 juin 2005 : 20:31:02
|
Sure, but I understand that they are busy with at least a couple of other (iGuidance ralated) projects whose dedline is near. Let's cut them some slack ;-)
Marvin Hlavac - Toronto, Canada |
 |
|
|
Squaredancer
284 Posts |
Posted - 17 juin 2005 : 20:51:04
|
I'm with them till the next release. It would be a great program if they can fix the routing problem.
But....."Let's cut them some slack ;-)" I will be more than happy to cut slack to the timeline, but not on their "attitude".
|
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 18 juin 2005 : 14:33:14
|
LOCAL
The following pictures show iGuidance 2.1.1 versus MS Streets & Trips 2005 both set to calculate LOCAL route (S&T is set to prefer "Arterial" roads as opposed to highways):
Start: 1111 Sheppard Ave West, Toronto, Ontario, Canada Destination: 5555 Sheppard Ave East, Toronto, Ontario, Canada
S&T easily avoids highways by correctly routing from start to the destination (which is on the same street). But iGuidance routes us via HWY-401, which LOCAL setting should not do as far as I know.


Marvin Hlavac - Toronto, Canada |
 |
|
|
Squaredancer
284 Posts |
Posted - 18 juin 2005 : 17:42:23
|
Marv, I GOT THE SOLUTION FOR IGUIDANCE They should drop "Shortest/Major/Local" and add "SCENIC Tour"
Bob |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 18 juin 2005 : 18:04:43
|
;-) That's a good one ;-)
But one possitive thing would be achieved by eliminating "Shortest/Major/Local": I suspect a lot of new users blame iGuidance for bad routing only because they use one of the three above settings. If Quickest is used the routes are the way they should be (almost always).
Marvin Hlavac - Toronto, Canada |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 18 juin 2005 : 19:57:17
|
But if Bob <Squaredancer> desires a “scenic” route…
…here is one:
QUICKEST
It doesn’t happen very often that the iGuidance Quickest setting incorrectly calculates a route. But it does happen, I have seen it on a few occasions, and that suggests some fine-tuning is still possible.
Method: Quickest Toll Roads: Disabled
Start: 5137 Rutherford Rd, Vaughan, Ontario, Canada Destination: 3997 16th Ave, Markham, Ontario, Canada
(The start & end locations on the same street, just the name changes at one point)
iGuidance 2.1.1: Quickest – 40 minutes / 49 kilometres S&T 2005: Quickest – 29 minutes / 23 kilometres


SHORTEST
I tried to calculate the same route but now with Shortest setting.
S&T 2005 was actually suggesting (correctly) the same (shortest) route.
iGuidance 2.1.1: Shortest – 44 minutes / 47 kilometres S&T 2005: Shortest – 29 minutes / 23 kilometres


Marvin Hlavac - Toronto, Canada |
Edited by - Marvin Hlavac on 18 juin 2005 20:11:39 |
 |
|
|
JP.Frenette
10 Posts |
Posted - 18 juin 2005 : 20:41:42
|
Marvin: This is exactly what I was complaining in another post. The routing seems to insist in using highway, no matter if it's actually far from the shortest. As soon as there's a highway in the area that goes in the general direction of the planned destination, it's the way it will route you, no matter what.
On a positive note, thanks to your registery hack, the automatic rerouting performs miracle. No more endless U-turn!
Now, if iNav would provide routing that is more logical, this would be great. I love the voice navigation! Adding more stop over points would also be great. |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 18 juin 2005 : 21:10:05
|
Yes, that's exactly what it seems to be doing. Getting on a closest highway may be fine if you select Quickest, but often it is wrong when Shortest or Local is used.
P.S. The registry thing that is something we have to thank to the programmers. Them adding it there indicates they are working on the issue.
Marvin Hlavac - Toronto, Canada |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 18 juin 2005 : 21:44:35
|
Question: Could these Shortest/Major/Local routing problems be occurring only in a handful of large cities or in locations close to highways?
Marvin Hlavac - Toronto, Canada |
 |
|
|
Squaredancer
284 Posts |
Posted - 18 juin 2005 : 21:57:00
|
If it is confined to big cities, then the Wash. DC area (VA suburbs) is one of them. I've seen similar routings. AND, we do have a BUNCH of major highways.
BOB |
 |
|
|
coolGPS
65 Posts |
Posted - 19 juin 2005 : 07:27:41
|
| I just got back from a trip from Huntsville Alabama to Atlanta Georgia using Version 2.1.1 and I must say iGuidance let me down terribly on the way back. I had the usual "mapping" glitches which I am normally accustom to, but I had a real messup this time. With the setting on quickest and never touched, it sent me west on 20 instead of East for probably 20 miles (headed toward Atlanta). I was just chatting with my wife not paying attention because I have always put my faith in Cathy getting me where I need to go (huge mistake). All of the sudden, when I reached the Talladaga speedway, I new I was going the wrong way. About 2-5 miles past the speedway, cathy had me get off the exit and make a U-turn only to retrace my path headed East to Atlanta. Let's just say I am torked right now and I need to cool down. Instead of getting home at midnight, I got home at 1:00 am thanks to iGuidance. I must say that I am suprised as this has never ever happened to me using Routis 1.1. If you are going from Huntsville to Atlanta, you better heed this warning and maybe do mapquest instead. Perhaps I can try to get my exact path at a latter time (and submit issue to iNav), but right now I going to crash. I hope that V2.1.1 does not have any crazy mapping/routing problems going on. Be on the lookout. By the way, they seemed to fix the multiple city issue as expected. I am just stunned on the Routing issue I had. If this is a map issue, it is just horrible. Let's just say my wife was completely ready to throw my GPS out the window. She told me to put Routis 1.1 back on. |
 |
|
|
Marvin Hlavac
Canada
6817 Posts |
Posted - 19 juin 2005 : 09:35:46
|
I just created a route Huntsville Alabama to Atlanta Georgia, but entering just the city center as start & finish seems to generate a route that appears to be correct. But to have the two actual addresses used in the trip could possibly help the programmers...
Marvin Hlavac - Toronto, Canada |
 |
|
Topic  |
|
|
|
| This page was generated in 0,75 seconds. |
 |
|