Tools for ID-A-Thons

Watching the iNaturalist ambassador webinar on identifying today prompted me to release several tools that I have been using to run ID-A-Thons for our Flora of Oregon: Vascular Plants project. All of the tools below are available at https://mickley.github.io/iNat-Tools/ along with their code. I hope that they are helpful to all of you interested in running ID-A-Thons and other identification-related projects!

Progress Bar

The ID progress bar widget lets you set up a progress bar to track the number of identifications made over a given time period. It’s flexible and can be filtered to show identifications for observations in a place, taxon, taxonomic rank, by a group of users, etc. You can optionally add a second comparison bar for a different time period. This can be embedded as an iframe widget into a journal post.

Leaderboard

The ID leaderboard widget shows a leaderboard of the number of identifications by user for a given time period. Like the progress bar above, it can be filtered by place, taxon, taxonomic, rank, group of users, etc, and can be embedded as an iframe widget in a journal post.

For some idea of how these two widgets can be used, see our journal post from our last ID-A-Thon.

Species Count Tool

This tool is designed to show a list of species for a given filter along with the number of observations for each species. It’s similar to what you would find if you clicked the species tab on iNaturalist in the Explore view or on a project. However, those views only show the top 200 species. This tool can show an unlimited number, and by default it will show species with the fewest observations first. For example, this link shows all of the species in the Flora of Oregon: Vascular Plants project that have only been observed once. Clicking on a photo will open up that taxon in the Identify tool on inaturalist. Clicking on the species name takes you to that taxon page. You can also click the Identify All Taxa button to load all the displayed taxa in the Identify tool.

Finding species with few observations for a particular place, project, or taxon is very helpful if you’re looking to identify or curate observations. It lets you easily find observations that might be out of range, incorrectly identified, captive/cultivated (but not marked as such), and rare or otherwise interesting. It can also help an observer find and target species that are in need of more observations to be included in the vision model.

25 Likes

Astoundingly, nearly half of those identifications have been done by just 10 people!

https://www.inaturalist.org/posts/80156-identifying-on-inaturalist-finding-your-niche-to-contribute

Congratulations to the 10 superidentifiers including @sedgequeen and @oxalismtp on their home patch - and to you for the tools and the journal posts !!

5 Likes

i don’t think this is true for GET /identifications and its sibling endpoints

@pisum yes, it’s whatever each endpoint supports. Perhaps that’s right.

@DianaStuder: We really need more identifiers, at least for Oregon plants. That’s been one of the reasons to hold ID-A-Thons: get more folks involved.

2 Likes

My goal is small. All the biodiversity. Across the continent of Africa. I tackle what I can, to move the IDs … one step … further. Your 2 that I mentioned also help out in Africa. Very curious to see how iNat unfolds the ID-A-Thon.

2 Likes

I run a plant ID-a-thon for New England and New York every February; the 2026 marathon will be our fifth. Your tools are great, thank you! One of the things that has helped us enormously is that the New England Botanical Society invited its members to help out, via their regular email announcements. Maybe your local botanical group could help out, too?

(Our fifth annual ID-a-thon!! We better think up some fun ways to celebrate, come February.)

8 Likes

most general users aren’t going to know what the API supports, only what you tell them your thing supports. since you’re actively promoting your stuff, it seems like it’s your responsibility to clarify what the API is actually capable of and modify your claims as needed before other folks spend a lot of time trying to use your thing in ways that it can’t actually handle.

2 Likes

How have I missed that? That’s my stomping ground…

2 Likes

@lynnharper: Thanks, we actually studied yours when we started ours. And yes, the Native Plant Society of Oregon is very involved.

I’ll be really interested to see how a staff-run ID-a-thon differs from those put on by volunteers. Maybe they will make themselves new nifty tools.

3 Likes

I will try my best to remember to invite you. If I remember correctly, it’s the third weekend of February.

1 Like

And we should study yours!

is it associated with the cooperative plant id project, or is it different?

It’s different. It’s just a 48-hour marathon, not an ongoing project.

1 Like

I’d be up with for helping during your ID a thon. how do I get involved?

Sometime in early January I’ll set up the project. We’re not supposed to advertise projects on the forum (I already feel guilty for talking about it so much!), so probably the best thing you can do is follow me and see what projects I’m administering? Or put a note in your calendar to message me in early 2026 - that would work.

2 Likes

Will do. And don’t worry, my lips are sealed!

1 Like

If anyone wants a spider person to assist with their events, I’m always willing and excited!

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.