Quasimoto
Member Since: 27 Jul 2005
Location: Middleburg, VA
Posts: 34
|
Navigation System Design Problems? | |
I had the chance to take my HSE on an extended off-road/camping excursion this weekend, and got to really try out the navigation system for the first time (having only had the truck for a week now). I probably haven't spent enough time with the manual as I should have -- only about 25 minutes -- but based on my experience using several systems by Garmin, and being in the business of hardware/software user interface design, I came across what seem to be real flaws with the nav system.
The most glaring one is the system's inability to accept just a town or city name as a destination. Frequently I don't have an exact address or POI when heading to (or want to use as a waypoint) a particular town, but it appears the system *requires* a specific address. I also can't use "City Center" as a POI coupled with a town or city name. I hope I'm wrong about this.
The other major frustration I had with the system involves its seeming inability to accept highway or route numbers when setting an "Intersection" destination. I wanted to go to the intersection of "Route 344" and "Highway 81", but no combination of inputs ("US Route 344", "Rt 344", "344", etc.) would allow me to specify intersections with numeric appellations. (I can find the intersection of "Smith Road" and "Darby Street" but not "Route 754 and Highway 3"). Again, this is something the Garmin software systems have no trouble with. Any ideas?
The last thing I was dismayed to notice -- annoying rather than really functionally limiting -- was the presentation of the Points of Interest list. When you request to "view all points of interest", a long list is presented, but it appears in what seems a random order. It starts with "All Restaurants", followed by cuisine types, followed by a random list (ie, not alphabetical nor ordered according to any logic I can understand). Anyone have any insight into this design "feature"? -QM
|
Mon Aug 01 2005 3:44am |
|