That is good to know.

I beg your pardon - I don't wish to appear flippant, but..

Whenever I look for "reviews" for any given product, I look for the BAD ones first, THEN the good ones. Most often, the "bad" ones are some unreasonable expectation or some petty complaint, and you have to weed through those for the REAL BAD complaints. "Product broke in a month" or, in this case, "does really annoying things X and Y" are good to know.

By that token, I would like to hear cases where TeleAtlas data was just plain bad. I know they exist. Right now, NO MAP DATA will be 100% correct in every case - as I said, roads change VERY FREQUENTLY here, and so it's definitely a concern. I'm more concerned with who has more correct data.

Not that I would get to pick, in any case.. <sigh>
And for that, I definitely sympathize.

One other complaint I had with the Lexus (NAVTEQ).. Roads - particularly highways - were inconsistently named. For example, it would find "HWY 55" but it would only find "NC HWY 54" and not "HWY 54." It was not the same. SO FAR, the TeleAtlas is consistent here AND more flexible, i.e. I can find "HWY 54" OR "NC HWY 54". With the NAVTEQ it was its way, or well.. The highway. It also searched only on simple matches, not in proximity. It was also very bad at telling what towns were "near," but certainly I'll chalk that up more to implementation than bad data. In the end, for a manufacturer's integrated system, it all matters.

So far, I'm very satisfied. I think the Lexus system had a slight edge in usability and (yeah, again) in its ability - without traffic data - to accurately predict ETA, although, strangely, it would not "adapt." If it WOULD have been 30 minutes but I drove like a maniac, it would be off. With the X5's system, it WILL adapt and as I get closer, it will be more accurate.. But it's the ridiculous initial (or far away) time that bothers me. It could say I'm half a mile from home and it will take five minutes! Irritating.