Why is Mapquest so sucky?

[Ghoulish Delight]

As Alex said, it's not a conscious decision, it's a programmatic quirk.

The way these route-calculating algorithms work (in very simplified terms) is that every road, every turn, every transition is assigned a weight that indicates a relative "cost" of taking that route over another. Assigning that weight is a complex process, and that's what Mapquest pays those providers for. So for whatever reason, in the data the Mapquest buys, those transition lanes carry a lower "cost" of travel than the freeway-proper.

Knowing that transition well, as I drive it nearly every day, it could be that the average speed along the transition road is faster than the average freeway speed. Or it could be that it might cut out a few dozen yards of driving distance. Or some other combination of the many factors that go into those value assignments.

The thing is, the exercise of driving-route-optimization is a highly complex and nigh unsolvable problem in the world of computer programming. There is actually no way to solve perfectly without requiring an amount of processing power that grows exponentially with the number of routing options. So these programs are forced to take shortcuts and make assumptions. They're pretty good at it, but there will inevitably be some holes in the logic. Google maps is sure to have its share somewhere. Though of course gmap's on-the-fly route changing features make them a little easier to account for when they do happen.

[RStar]

Originally Posted by blueerica

OT: Keep reading the thread title is "Why is Mapquest so sticky?"

Just sayin'...

I read the same think when I came back to it....and I wrote the dang thing!

Originally Posted by Ghoulish Delight

As Alex said, it's not a conscious decision, it's a programmatic quirk.

The way these route-calculating algorithms work (in very simplified terms) is that every road, every turn, every transition is assigned a weight that indicates a relative "cost" of taking that route over another. Assigning that weight is a complex process, and that's what Mapquest pays those providers for. So for whatever reason, in the data the Mapquest buys, those transition lanes carry a lower "cost" of travel than the freeway-proper.

Knowing that transition well, as I drive it nearly every day, it could be that the average speed along the transition road is faster than the average freeway speed. Or it could be that it might cut out a few dozen yards of driving distance. Or some other combination of the many factors that go into those value assignments.

The thing is, the exercise of driving-route-optimization is a highly complex and nigh unsolvable problem in the world of computer programming. There is actually no way to solve perfectly without requiring an amount of processing power that grows exponentially with the number of routing options. So these programs are forced to take shortcuts and make assumptions. They're pretty good at it, but there will inevitably be some holes in the logic. Google maps is sure to have its share somewhere. Though of course gmap's on-the-fly route changing features make them a little easier to account for when they do happen.

Knowing where you live I thought you'd have some insight on the local part. Because of all the work on the 22 I have been driving from Brookhurst up Chapman all the way past the 55 to our Dr.s office. Now that the work is done I thought I'd try the freeway.

Great info on how this works. It seems like the quirks happen for me more often than not....

[Kevy Baby]

Originally Posted by RStar

Great info on how this works. It seems like the quirks happen for me more often than not....

In my experience, Mapquest seems to have these weird quirks more than Google Maps

[RStar]

Originally Posted by Kevy Baby

In my experience, Mapquest seems to have these weird quirks more than Google Maps

But at least with google maps you can manipulate the the trip to change it to meet your needs.

Anyway, I suggest checking a map like Thomas guide to verify the directions before leaving.