I guess I'm interested in knowing how you use navigation when you're on trips Dave. Do you build a route before heading out and follow that or do you show up in an area and use the nav to see if X road will get you through to Y location. Maybe a combination of the two? What specifically was your Garmin able to do that isn't a feature now?
Boy, that could take a while to answer!
Just briefly, and maybe I'll try and get into more detail later, but here are a couple very short answers to your questions.
No, I don't build routes. Have never built a route. Don't know how. Don't know what use a route would be to me. I like to stay fluid and make route choices on the fly most of the time.
Yes, I use the nav to see where X road goes, constantly. I'm accustomed to doing it on a dedicated GPS, with hardware buttons though. Meaning, I'm accustomed to doing it while bouncing down a rough two track, with one hand, mostly by braille and being able to accomplish the whole operation in about two seconds with only one second to actually look at the screen and get the info I want. I envision I'll have to come to a stop and focus my attention on the tablet to do the same thing using touch screen and raster maps. Which, will crimp my style! I've been on a couple trips with guys using these systems and it seems like they always have to stop and waste time just to make nav decisions that I'm accustomed to doing without slowing down or scarcely even taking my eyes off the trail.
A couple quick complaints about raster maps, which, aside from having dedicated hardware buttons (touch screen just sucks, by comparison, for vehicle nav, in my opinion...), vector maps is what I miss most about my Garmin compared to these Android tablet apps.
1. Raster maps are freaking huge and take forever to download. Vector maps are a tiny faction of the size, load dozens to hundreds of times faster (depending on the particulars) and take up only a tiny fraction of the disk space. As a simple example, I just downloaded CoPilot, a street nav program - won't be useful at all for offroad nav, but emulates typical street GPS function. Anyway... It uses vector maps and complete street maps of the USA and Canada are only about 2.6 GB. By comparison, I've been downloading several sets of topo maps for a trip to The Maze I'm leaving on later today. So far, a couple sets of raster topos for just The Maze are sitting at about 3 GB. Probably end up with about 7GB worth for just this one small area, since I want to try out some different types. I can imagine that just Utah, for the 24K topos, in raster format, must be dozens of GB.
2. Raster maps don't scale smartly. Here is an example of what I mean. The CalTopo 24K are a popular free map for BCN or Gaia. And they are great for hiking. But, they just plain suck for my purposes in vehicle nav. The road on them is just a pair of dashed lines, against varying backgrounds. Zoom in tight enough and it works fine - you can plainly see the terrain features and road path for a short distance around. But, if you want to do a quick reconnaissance of where a side road goes, so you zoom out, pretty soon, you can't see the road anymore. Those little dashed lines just keep getting smaller as you zoom out until they very quickly aren't distinguishable at all anymore. Ditto for text labels on the map.
Vector maps scale smartly. As you zoom out, the road (dirt two track, highway, whatever), doesn't get so small you can't see it. Roads (and certain other features) have a minimum pixel dimension they shrink to which is still very visible. So, as you zoom out to view a wider area, you can easily see the roads around you and where they go. In similar vein, roads are typically color coded - on my old Garmin, during daytime (it had very useful separate color schemes for day and night), dirt roads are green and paved roads are red, on a tan background. Good contrast, very easy to see all roads of all types at all times. With dedicated hardware zoom buttons, it was a two second deal, even while bouncing on rough road, to "beep" the zoom out button a few times, glance at the screen and see that yes, that green dirt side road goes through to the red highway. Information acquired. Beep the zoom in button a few times, back to the preferred zoom for driving. All in about two seconds, and all of the actual zooming done by braille without even taking my eyes off the road. Contrast that to BCN or Gaia using the CalTopo 24K's. To accomplish the same thing, I'm going to have to come to a stop first. No way I can navigate those little touch screen zoom buttons effectively while bouncing on a rough track. Then, I'm going to be limited in how far I can zoom out before map features become indistinguishable, which means I'm also going to have to pan the map - more reason I need to stop to do it. A big deal? No, not really. But, repeating this a dozen times in a day, vs. just maintaining forward progress the whole time, is a minor PITA, to be sure.
Note, BCN has a set of free raster topos that emulates scaling in a way. It's not perfect, but it's better than anything comparable I've seen in Gaia so far. They have a set of ArcGIS topos that actually download three separate sets of maps - 250K, 100K and 24K and smartly switch map layers as you zoom in or out. These "may" end up being my go to, for BCN, we'll see. They take up a TON of space though!
3. Raster maps are basically just "dumb" images. So, there are many "features" where this comes into play, but I'll just list one that is most obvious and bothers me all the time. Again using the CalTopo 24K's as an example. "Track up" is the ONLY way to fly, for vehicle nav. But, running track up with a dumb raster map, if you are going south, all the text labels on the map are upside down and backwards! Nice... Not...
There are many, many other ways the "dumb" nature of raster maps prevent features you take for granted using a GPS that uses vector maps.
Note, it's obvious that both BCN and Gaia were designed for hiking. And for use typically on a smaller phone screen. Not in vehicle, off-road nav, using a typically larger tablet screen. Aside from the raster vs. vector maps thing, I'm seeing a LOT of simple UI elements that could be changed to make these programs far easier to use, for how I personally will be using them. A simple example - the zoom in/out buttons in Gaia. They are tiny and close together. I'm sure some people master them while moving. But I just can't see my fumble fingers ever being able to use those zoom buttons worth a darn while bouncing down a rough track. By simply providing a UI option to make the buttons much larger and on opposite sides of the screen, functionality for my purposes would be significantly enhanced. I see LOTS of small things like this I wish were different.
Adding a UI style for "Offroad Vehicle" and another one for "large screen" could increase usability greatly for my purposes.
Having worked for a software development company for 25 years and actually having designed some successful (or at least profit making) programs in the long ago time, I know that good software companies typically crave this kind of feedback from users and are anxious to try and implement many requests and suggestions. As such, after I become a bit more familiar with the programs, you can bet I'll be lighting up the customer feedback inboxes at both companies.
- DAA