Add tags, observation fields, threatened (status), description choice(s) to populate Collection Projects

I believe it would be beneficial to allow tags, fields, threatened (status), and description choice(s) for populating projects. I am suggesting expanding the Collection Project filters to include choices that exist in Observation searches.

Users wishing to participate in a particular Project could also add specific known qualifiers such as a tag to an observation. This would cause that observation to be included in the Project as long as other filters (or none) are met.

Pre-existing noted factors such as leucistic, albino, infected, parasite, injured, marine, seaweed, UV, net, rust, gall, red, blue, banded, radio collar, unusual, cryptobiotic/cryptogamic and etc. could be used to build a Collection Project. As well, with this feature build in “and / or / excluding”.

Hi @bobmcd, I’m thinking maybe you meant “populate” instead of “propagate” in your request title and description?


I’d like to add licensing for project’s filters to promote open data in biodiversity studies.


I definitely agree with this feature request! A colleague is looking to create an iNat project for camera trap images, and part of the purpose would be to discover new iNat users with camera traps to add to a British Columbia-Alberta camera trap network. Without the ability to filter by tag it seems like her only option is to create a traditional project and manually find people with camera trap images and request them to add their observations.

1 Like

I’m not sure I see the value from tags or description choices since that would likely result in including random irrelevant observations, but for sure I’d appreciate being able to use observation fields.
A couple other threads that seem to have requested them (not feature requests though):,


I agree that tags and description would not be particularly useful, but fields and conservation status might.


I think including “tags” is useful. When I hit the “explore” button, I can filter observations that have a particular word:

In this case, I want to see observations that have the word: “atropello” which means roadkill in Spanish.

Its easier for people that are not very familiar with iNaturalist and want to collaborate with roadkill pictures to just type “atropello” in the notes section when they are uploading their pictures in the app. We will start teaching park rangers how to upload roadkill pictures in iNat and its easier for us to teach with this method. People often get confused when I ask them to include their observations in my traditional project.

What I end up doing is manually search every now and then and include observations with tags into our project.


I am looking for similar functionality in collection projects, basically the ability for a user to have certain of their observations be included in a Collection project. I have created a few collection projects that limit the collection to specific user ids. But I don’t really want every observation made be a user, I want the ones that the user wants to include in the collection.

I know this can be done with traditional projects and maybe that’s the best choice, but it seems like it would be helpful to add another query parameter to collection projects that would support this.

Do you mean like entering the observation IDs manually as a filter for the Collection project?

Here’s my Use Case for Observation Fields in Collection Projects.

It would be valuable to automatically collect all the Interactions supported by a species, without requiring direct Observation of the species itself. For example: I can search for all the Observations where an insect visited the flowers of a specific species of milkweed. But I can’t search for “Interaction->Visited flower of: Asclepias” where “Asclepias” is recognized as a higher-level taxon in the search. I have to specify each milkweed species. If I could create a Collection Project with all these Observations Field+Value combinations, they would be available in one place automatically.

To @upupa-epops point regarding tags or description choices, I guess it would be better if there is the ability within the collection project to also be able to remove unsuitable observations.

[projectY] = SELECT ALL FROM [projectX] WHERE [custom field]>=a

Allow selection of observations for projectY from projectX by conditions applied to custom fields. For example select observations from where (trunk circumference) окружность>=300

project is a set of observations (table)
observation is a set of fields (row)
so it would be reasonable to select observations for project by any field: whether it genus or location or any tag or custom field value.