iNaturalist 2019 Team Retreat Follow-Up

Hi Everyone,

The iNaturalist team gathers for a yearly retreat to discuss our priorities for the coming year, and we met in a very wet and stormy Bolinas, California last week for this purpose. We also worked on a jigsaw puzzle and caught up on some reading during downtime.

Here is a un-ordered (except for the first item), non-exhaustive list of what we plan to focus on over the next year. Please keep in mind that some things may take longer than expected or might just not get done this year, other issues and priorities might pop-up, and that any big changes likely won’t occur until after the City Nature Challenge, which ends on May 5th, 2019.

Looking it over, a major theme is “improving core functionality,” making what iNat already does work better and more efficiently without adding a ton of big new features. The idea is to really strengthen what iNaturalist does right now so that we can add new functionality in the future.

  • Revamped notifications system and dashboard - This will have to be a revision from the ground up so it will take some time, but we acknowledge that this is part of the site which needs a big update. I’ve started a topic in General where you all can share any thoughts you have about notifications. Note that new Feature Requests about notifications won’t be approved, please share your thoughts in the General topic.
  • Implementing an embedded translation feature for comments and descriptions, similar to what’s found on Twitter and Facebook.
  • Create a tool to help users split and merge their observations
  • Releasing a significant update to Seek in the next few months.
  • Rewriting the Explore/Observations Search page and adding more filters.
  • Adding a user-to-user trust system. For example, I could trust kueda and he would be able to see true locations of my observations.
  • Investigate ways to capture comments and ID remarks that are useful for making identifications and including them on the taxon page and in identification tools.
  • Bring up the iOS app to feature parity with the Android app.
  • Re-design/re-organize the Account Settings page. It’s pretty messy at the moment and if more settings are desired, it would be best to make that page more manageable.
  • Continue to improve the Computer Vision model and the use of geospatial data in suggestions.
  • Continue to upgrade infrastructure and make the site more efficient behind the scenes as the community scales.

Those are the broad end-user related updates we’re looking to tackle over the next year or so. And of course we’ll be working to grow and improve the community (especially identifiers) as always, with some new members of the international iNaturalist Network on the horizon.

And there will be smaller improvements, bug fixes, etc. throughout the year. We’ll be going through Feature Requests as much as we can.

We do want to thank everyone in the iNat community for all of your support and contributions, iNat would really be nothing without its users giving their time and energy to make it a positive place.

— Tony

The iNat team (from left to right; photo by Abhas): Abhas Misraraj, Ken-ichi Ueda, Carrie Seltzer, Amanda Bullington, Patrick Leary, Alex Shepard, Tony Iwane, Scott Loarie


Awesome! This sounds like a great direction to go following the explosive growth of last year (and possibly this coming spring). The notifications update will be really helpful for us high volume users. The trust system may allow for more cases where people can use collection projects rather than the older project types. (though i think the older project type remains important for some uses). In-site translation would be awesome. I don’t merge and split stuff much other than copying observations but i know a lot of people want that feature. I am looking forward to seeing what you did with Seek! I don’t use it much since i’d just use regular iNat instead, but i think it’s a great option for kids, etc. Too bad our 3 year old is still a little too young but it won’t be long… Really excited about the capturing of ID features too! And improvement of the computer vision too. Heck all of it. I hope you consider including captive species (or plants at least) in the algorithm since new users who rely a lot on the algorithm tend to observe those a lot.


If I want to split an observation I make a copy and I am always happy that the pictures are copied too. After that a remove from each observation the obsolete photos. What should this ‘split observations tool’ do?

1 Like

Investigate ways to capture comments and ID remarks that are useful for making identifications and including them on the taxon page and in identification tools.

Nice. I’m looking forward to this. There are a lot of useful ID tips flowing through comments and it would be fantastic to be able to capture this knowledge on taxon pages (or something like that). We’ll probably need to be able to connect single comments to several taxon pages as they’re often about how to tell one taxon apart from another.


It’s for cases where the user - generally a newer user - has multiple photos of different species in one observation and separate observations should be made out of each photo.


This will certainly be useful for paper wasps. Though on the other side, would there be a feasible way to get certain tips removed from a taxon page (or otherwise vote a “tip” to be non-factual)? There have been a number of cases where rather incorrect notes had previously been used, and it really would be great not to have to see these pop up here.


What I have found most useful is when someone includes in their comments a link to a journal post that goes into great detail how to differentiate between species. Here is a recent one getting us straight on Phyla species in Texas: ([


4 posts were split to a new topic: Train the vision model on cultivated plants

Thank you for all the great work you are doing to maintain and evolving the platform!

It would be great the get the possibility to choose the language of the mobile app within the app, or choose the language in which common names are displayed from within the apps settings menu.


This would be really great. I often ask folks for specific help so I can learn for the next time. It would be easy to check some little box to say that there is ID guidance within the observation for others to find. Or build it some other way. I’d love to have this resource.


You have hit all my “want” buttons:) Such a good plan to strengthen the core before adding feathers, if I may mix my metaphors. Thanks.


Would it be possible that splits/merges could also be ‘suggested’ by another user (similar to the ID process?) - e.g:

  • User X (potentially new) uploads 9 photos in one observation - 6 are a duck, 2 are a wasp, 1 is a dog
  • User Y looks at this, sees the issue, and selects the photos that should be split into two new observations
  • User X gets a notification, and a card appears on the original observation in the timeline - ‘Y thinks that this should be split into multiple’ (with the actual stepped changes detailed in the body of the card), and an ‘Agree’ or ‘Disagree’ button
    • Click ‘agree’, two new obs are created and new user avoids a deep dive into iNat mechanics on first go (and User Y avoids having to try and explain where to click and what to do via the comments section)
    • Click ‘disagree’ and User X can explain with a comment that we’re not looking at ducks, wasps, dogs, but actually the grass that they’re standing on or whatever

(plus similar for merge)


We’ll definitely consider that approach but I can’t make any promises. Cool idea, though!


very cool idea!