My partner and I built this website with it a few years ago: https://www.owlsnearme.com/
(I realize this is a bit on-brand for me but I also use it to track pelicans https://tools.simonwillison.net/species-observation-map#%7B%... )
Fun to travel and "pokemon" some new local stuff too.
The iNaturalist app doesn‘t. It has more features, but Seek‘s former advantage „let me just the a photo and auto-identify“ is now in the iNaturalist main app, as well, so it is my default now.
Frustration shared.
I got 0/4 though on the easiest difficulty level. Feature request: a version where you have to guess the common name instead, I think that would still be fun.
The iNat API certainly has some quirks and shortcomings, but in terms of usability it's uncommonly good compared to most biodiversity platforms. I maintain the python API client[1], which is used for data visualizations, doing useful things with your own observation data (which is how I got into it), Jupyter notebooks, Discord bots, and some research/education workflows.
People who walk by the yard might tell their friends, but ordinary word-of-mouth can't be queried online. Not yet.
EDIT: We did have what turned out to be a significant invasive species observation. It was published in my SO's account with the location obscured. I looked up the species online and realized it might be a concern, so I killed it and put it in the freezer. In the meantime, the California Agricultural Inspectors got wind of it and contacted iNat to obtain the email address associated with the account. After making contact, they sent someone to pick up my specimen, and the later, 4 inspectors (yes, really, 3 inspectors and a supervisor) were sent to look for additional specimens. None were found.
Unrelated to this incident, I posted endangered species (not on our property) in my account, and iNat automatically obscures the location. Later on, I got an ~~email~~ message via iNat from the California Department of Fish and Wildlife asking for access to the precise locations, which I gladly provided.
Like all people learn is "someone does in fact live at that address and they use this app"
1. “Hide the start and end points of activities that start at SPECIFIC addresses.” 2. “Hide start and end no matter where they happen.”
Then it can be useful to add your home/work/routine locations.
If iNaturalist doesn’t have a setting like that, it’s a nice approach — especially if it’s included as part of initial onboarding flow — so it helps people without needing to remember to make visibility choices each time.
A problem I often have with Merlin is that the birds seem to know when I record them, and promptly stop singing...
[1] https://merlin.allaboutbirds.org/
[2] https://floraincongita.com/
I'm going to give Merlin a try - the app has UI to download the network for offline use.
Great app, easy interface, friendly community. Thank you iNaturalist team!
So I would take walks and try to identify any plant I didn’t know. The first day I didn’t even make it around the block. Over the course of moths I got better and could go a few miles before spotting a (native) plant I had no idea about. Now I know when most flowers bloom, what’s wdible, what’s poisonous, what’s related, and it’s fun to share with other plant people too.
Seattle is such a beautiful place to learn about plant life, since it is so temperate the city is like a world tree museum. Almost any kind of tree that doesn’t prefer desert will grow here and people over the centuries have planted many unique and exotic varieties.
Conversely, its also beneficial to report sightings of helpful bugs/birds/bats/etc. so can get an early warning when a population starts to thin out.
Tech blogs or pointers would be great
https://github.com/inaturalist/inaturalist/blob/main/app/ass...
https://github.com/inaturalist/inaturalist/blob/main/app/ass...
https://github.com/inaturalist/inaturalist/blob/main/app/ass...
For client side rendering, deck.gl is quite good, also a newer library called lonboard from DevelopmentSeed.
As it stands, I don’t really have a system in place, and I don’t want to put a lot of effort into a lossy (assets get compressed and stripped of metadata) online project.
1. Mostly use the mobile app, and take photos and upload observations directly from there. Local photo collection either isn't a priority or is backed up by their phone's cloud sync.
2. Mostly use inaturalist.org via a desktop browser, with either a standalone digital camera or mobile photos synced to desktop. Local filesystem (hopefully plus backups) is the source of truth.
I have been working on a desktop application[2] with a long-term goal of full bidirectional sync, and a secondary goal of offline usage. The current feature set is fairly modest and read-only, though, focusing on organizing local photos using data from iNat.