Add real-life use cases to documentation and tools/ #371
Description
While the TUI allows to get used to GeoToad's most important features, it's incomplete when it comes to special use.
I've been using the command-line approach for years, and wrapped a number of scripts around the main geotoad invocation - also to provide a maximum of information both to my geocaching partners during trip planning, and to my various devices.
I don't upload solutions to GC's servers but keep them in a text file on my disk, so merging that is another detail to share.
Some examples might show how
- multiple output formats are created in one go, and which one fits which device
- to keep a list of cache finds (and found counts) that can be easily parsed
- to optionally exclude found caches (based on such a list, to avoid an extra, possibly long query)
- to postprocess individual queries to merge them with solutions and partially found stations
- to provide the full dataset by merging multiple query results, keeping the most recent info for each cache
- to create "paper" maps for those who prefer to plan at the kitchen table (which is bigger than any tablet)
- to get hold of spoiler images for offline use
etc.
Since GeoToad is written in Ruby, and I'm a scripter, most things have been done in Ruby and Bash, and many of them haven't been optimized or beautified (I prefer to be outside as much as possible, at the cost of extra coding sessions).
What do you think? What are you missing badly, but not badly enough yet to have asked for it? Is there something you'd like to share yourself? Step forward ;)