neil wrote:Geocat wrote:Certainly the user's location and purpose can change the perspective but from where I sit the appearances are not good.
That's it in a nutshell, it is a personal perspective, and from your location, which as a general rule cannot be applied to the whole of North America or 'just anywhere'.
Ok, then let's talk in generalities. I just completed a 500-mile interstate trip and compared RouteBuddy with Google Map at various locations. I found that RouteBuddy has:
* less current roads,
* fewer features (parks, hospitals, malls, etc.) shown on the base map,
* no labels on the features even at high zoom,
* fewer major roads highlighted (although RB uses more colors for what it has),
* less useful road labels (some rotated, some highways without number designation),
* poor labeling of roads at moderate zoom levels,
* fewer and less current POIs with less information.
You should be able to see these deficiencies throughout the west coast. They are not specific to my city. I checked some other cities in the country and found the same pattern.
neil wrote:Geocat wrote:You can appreciate that data over 2 years old are not going to satisfy many customers and it is little consolation that other areas may have more recent data--if even 18 months can be considered recent!
As explained before, anything newer is a bit of a rarity from any raw data supplier to GPS manufacturer or otherwise.
In my 10-year experience of buying 7 different NAVTEQ updates for car, handheld and computer nav systems the data were always around one year old. Your Tele Atlas data is over 2 years old--that is unreasonable in my book. I have heard that Tele Atlas is behind NAVTEQ in the U.S. and my sample confirms that.
neil wrote:Given a choice I'd rather see with my eyes what's available as a POI, of course telephone numbers may make a difference to some but directory enquiries are still available via your cell phone.
So why even use RouteBuddy to look up POIs?! My phone even has Google Map with traffic.
neil wrote:How about you send me a .kml file centered on the location you mention, then I can check it out for myself.
I'm not sure what you want in a kml file (I rarely use them) but the center coord for the comparison maps above is roughly N 44°03.45', W 121°21.16'. I don't remember where I did the one-mile restaurant search but it was probably around 44°03.745', W 121°19.485'.
neil wrote:However this posting on our NAM map set is entering realms of pedantry where, if we had time, we could pick holes in any data - West Coast or not. Neither do I plan to start dissing competitors products but ask readers to add up all the features RouteBuddy has on offer against what's offered from other developers. The results sure speak for themselves.
The local detail I point out is characteristic of large-scale deficiencies in the maps and POIs that limit RouteBuddy's usefulness. Some of its features are nice but if I can't depend on the data then features don't matter. I would never think of trusting a 3-year-old paper map or phone book in the fast-growing west coast, nor have I been able to trust RouteBuddy because of too much obsolete data. I'm surprised you dismiss it so easily because half of any mapping system is the data.
neil wrote:Geocat wrote:As for managing data, I can't trust RouteBuddy yet because of crashes and erratic behavior.
We've narrowed down most of what causes RouteBuddy to misbehave from support tickets and bug reports. RouteBuddy as a complex mapping application has to do a lot of work (because of the high definition maps we offer) and problems on the host machine can cause hiccups. I think I've listed these elsewhere on the forum but are happy to list them again if requested.
I don't see any functional difference in the definition of the maps. They all look pretty much the same on a laptop screen to me, with the major visual difference being single- versus double-line roads. I don't doubt that RouteBuddy has a theroretical advantage but the main way the definition affects me is the large, cumbersome map file.