For those working this way, I have a few questions since I haven't put time into doing much experimentation.
My main questions are past the actual map data, and more into usability. There is much to do surrounding using the map software as a tool in a variety of phases- planning, live use while driving, editing, sharing, and presenting/exporting.
I kind of leave out "routes" which are usually a string of waypoints connected as straight lines, and rarely find a use for them unless turn-by-turn directions are needed. They have some other utility, but it seems more for trips where resources and time management are higher priorities.
How can/does the tool-
Create tracks, save, load?
Create waypoints, save, load? Limitations on label length?
Add labels and symbols (non-waypoint)? Build/import custom symbols?
Save a "map?" (map is all user-added data- tracks,labels, waypoints, symbols)
Edit maps? Removing sections of tracks, merging data from other maps, selecting groups of waypoints or groups of <any map element type> to delete
Export maps to display formats (png/jpeg/tiff)
Export maps to GPX/KML, etc?
Import maps from other formats?
Ease of on-screen (touch based) controls? Drawbacks? Can you add/customize only the controls you want?
Night mode (think OziExplorer)?
Layered views (topo/sat/custom)?
Calculate altitude profiles for tracks?
I would like to consider the possibility of going away from Natl Geo TOPO! 7.5' / 24K maps, but there is a lot of functionality needed to make a shift I haven't noticed with the mobile apps. All the Android tablets out are very alluring. Maybe I can get Natl Geo to build an Android tablet app.
It is much more difficult lately to find a reasonably priced PC based tablet. At the current prices and display size/qualities, Androids don't need to be so ruggedized as losing one to elements isn't so much of a hit as a $3,000+ ruggedized PC version.