gatownsend

Hi folks,

I'm having a problem with routing using iGuidance and I was wondering if some non-iGuidance users would be willing to enter a start and destination into their software and let me know what route it calculates. I've done this route using Yahoo!, MSN, Mapquest, Mapopolis and iGuidance. The three websites and Mapopolis all gave the same route (the one I drive every day to work). iGuidance on the other hand absolutely refuses to route down one road near my house unless I put a stop-over somewhere.

The starting point would be the intersection of Shorthorn Drive and Bishop Way in Sagamore Hills, OH 44067 (it might say Northfield since that's where the post office is). The destination is 24601 Center Ridge Road, Westlake, OH 44145.

The route the websites and Mapopolis give is:

Either Bishop or Shorthorn to Acadia
Acadia to Valley View
Valley View turns into Canal
Canal to Pleasant Valley
Pleasant Valley to 77
77 to 480
480 to Clague
Clague to Center Ridge.
Distance: 25.3 miles.

iGuidance wants to route me down just about any street EXCEPT Valley View, which always results in a longer trip, even when I have "shortest" or "quickest" selected. I've tried every setting possible in iGuidance, but cannot produce this optimal route unless I put a stop-over along the route somewhere (which I don't want to do because I don't want to have to click 'ok' to continue on my route).

I was just curious to see what route other software besides Mapopolis and iGuidance came up with. Since all the websites and software I've tried use Navtech maps, I'm beginning to think this is a software problem with iGuidance. I'm going to send an email to their support department, but wanted to see if I could get results from another program or two before I do.

Thanks,

Gary

walkabt

IGuidance uses TeleAtlas maps. The other sources use NavTeq?

I have Mapopolis, I also looked at MapPoint 2002 and MapPoint.com

JakeRich

I think iGuidance uses NavTeq.

gatownsend

Originally Posted by JakeRich

I think iGuidance uses NavTeq.

iGuidance does use NavTeq.

~Gary

walkabt

You know, I knew that?! Hmm, am I thinking of PocketMap and TomTom?

JakeRich

Back to the original problem. I put the route in Maps & Streets 2004 and got the route gatownsend prefers. S&T2k4 uses NavTeq maps, too.

gatownsend

Thanks Jake,

I was hoping to hear from a Routis or Prymenav user (since I believe those are basically the same software) to see if they experienced the weird route or not, but I'm glad to get any response.

I've submitted something to iNavcorp's support and they've responded saying they'd get back to me within 24 hours. When I hear back from them I'll post what they came up with (if anything).

This morning I let it caculate the longer route, but then drove the route that the other software and websites had calculated. The reroutes iGuidance came up with were completely crazy. It absolutely wanted to route me over to route 82 every chance it got, with it's last reroute sending me 12 minutes out of my way when I had a straight shot to a closer freeway entrance. Hopefully iNav will come up with something.

Regards,

Gary

gatownsend

Well, I got a response back from iNav. It appears the v. 2.1 update has been pushed back (I thought I read it would be released in the 4th quarter)

Here's what they said:

Hi Gary:
We tested your address and found out the following:
1) Under iGuidance v1.0/v1.1, it did come up w/ the same route as the ones you got from all other maps.
2) Under iGuidance v2.0, in order to save memory for all the added 3D and graphic colors, we modified the routing algorithm by searching smaller block of data, and hence the result you noticed in certain areas.

We are currently working on a new memory management enhancement program which will increase the efficiency of memory usage to allow coast-to-coast routing with all the new graphics and 3D view. Once that's completed, we will change back to the original routing algorithm as in v1.1, and thus provide solution to the issue you experienced.

These enhancements and changes will be incorporated into our v2.1 update, which currently is scheduled for Q1/2005 release.

We apologize for the inconvenience.

Thank you.
Support Team
www.inavcorp.com