Scythebill 20.3 is out, and the big new feature is something I've been working on quietly for awhile - itinerary planning! There's also a more reliable way to transfer files to Android (or the iOS beta), and lots of smaller improvements and fixes. As always, download here, and let me know if you have any problems, either on Facebook or by email.
One note, though: this may be the last version of Scythebill that will include the IOC taxonomy. Its last release was in May, and its last "big" release is more than a year old now. It's not going to receive further updates, and I'd rather simplify as eBird and AviList convergence nears completion.
Itinerary planning
Scythebill's got a brand new feature to help you plan your trips - whether you're building a new itinerary for yourself, or want to prepare a list of targets for a set itinerary, this can help you out! It relies heavily on eBird data, especially as prepared by another open-source birding software provider - OpenBirding. My thanks for all their work!
To start, select a country or state in Browse by location or on the Lifers map (in Special Reports) and click the new "Plan itinerary…" button:
Itinerary stops go into a list in the center, where they can be renamed, reordered, removed, or combined. And the list for each stop isn't just "present" or absent - it's also categorized based on frequency, from "common" and "uncommon" down to "scarce' and "rare".
And if you're wondering when to go, just click "When to go..." at the top and a wealth of additional information emerges:
... and even an eBird-style per-species barchart!
Once you've got your itinerary set, save it as a spreadsheet. The spreadsheet has both the itinerary and the species list in two tabs. You can reopen it later with Open itinerary... in the File menu. And if you share it with another Scythebill user, they can open it and see how the same itinerary works for their target species!
There's so much here that I've made a demo video.
Some quick points of caution: all of this is based on what other birders have reported to eBird. Sparsely "eBirded" locations will have less accurate data. eBird "Sensitive Species" will not show up in itineraries at all. And the existence of a hotspot doesn't guarantee that the spot is publicly accessible or even safe to visit - you'll need to use your own judgement before visiting a site.
Encrypted cloud transfer for "Send to phone"
The "send to phone" feature for the Android (and iOS beta) app sends your sightings straight across your local network. That fails on networks that keep devices apart, such as many hotel, office and guest Wi-Fi networks. The dialog now has a "Use encrypted cloud transfer" button. The file will be uploaded to a server Scythebill runs - but only after end-to-end encryption is applied. The "key" for decrypting is in the QR code, and not sent to Scythebill's servers; I cannot read the file contents in any way. It's also deleted immediately after your phone receives it (and in 2 hours if that doesn't work).
Smaller changes
- All requests to eBird, Google, and the new OpenBirding APIs now are routed through an intermediate Scythebill server. This should have no effect on your usage, but means (in particular) that your IP addresses and other information never gets to eBird or Google.
- eBird taxonomy families and orders now have common names in Spanish, French, German, Brazilian Portuguese, and Dutch. Some of these names are invented (though derived from proper translations of species), so if I've gotten any wrong, let me know!
- A bug where editing visit details showed stale report information (making it look like data was lost, though it wasn't) has been fixed.
- A few small import fixes have been made - in particular, Scythebill now supports importing with dates containing four-letter month abbreviations like "Sept".
- Species entry was broken for locations with hierarchies of county/state/country in an unexpected order.
- Species entry is more graceful when resized for a tall screen.
Am I correct in assuming that when the next Avilist update arrives you will be replacing IOC support with Avilist support and that we will still have two taxonomies supported? I understand that Clements intention is to synchronise at species level this update but subspecies synchronisation is a way off, timescale in years not months. I do wonder what has been gained by effectively replacing IOC with Avilist but that is a different question to be discussed elsewhere
ReplyDeleteI am not planning on supporting two taxonomies at this time, just the one. We'll see how far off the subspecies lists are in this update before finalizing that decision, but it is a lot of work to have two lists if the species-level taxonomy is identical or nearly so.
Delete