Let's Talk Annotations

I moved the above post to this thread to keep discussion about proposed annotations changes together.

On a separate issue to flowers/fruits, the annotations for leaves appear skewed to a particular subset of deciduous plants:

Breaking Leaf Buds
Colored Leaves
Green Leaves
No Live Leaves

Until recently, I hadn’t applied ā€œBreaking Leaf Budsā€ because it didn’t seem to match the growth pattern of Australian evergreen plants. I’m happy to use it now, but I can’t be the only one confused by it. The descriptions ā€œColored Leavesā€ and ā€œGreen Leavesā€ are also unhelpful for plants that don’t normally have mature green leaves, or where the new growth may be coloured, depending on temperature:

https://inaturalist.ala.org.au/observations/288924899

A better set of descriptions might be:

New Leaf Growth
Mature Leaves
Senescing Leaves
No Live Leaves

7 Likes

There is an annotation complication there if someone can recognise there is fruit present but not whether or not it is ripe. Annotation layers might be too fiddly, but would be interesting (applying a general fruit annotation bringing up its own little sub-annotation list, say!).

There are definitely major differences phenology- and appearance-wise between unripe fruit, ripe fruit, fruits that have opened, the actual seeds, and stuff like the lingering woody fruits you get on Melaleuca for certain.

1 Like

80% of iNatters don’t know what ā€œscenescingā€ means, and an additional 10% don’t realize that colorful fall leaves are scenescing. Other than that, the leaf annotation idea is pretty good.

On the fruit front, more than once I’ve wished we could distinguish between ripe fruit and ovaries that are just past pollination, but I have my doubts about people being able to apply the distinction correctly. We’re probably doing well is the presence of fruits is accurately reported.

1 Like

I don’t see it as a complication. If people can’t tell whether fruit is ripe, but can tell that fruit is present, the few who annotate will probably select ā€œfruitā€ but not ā€œripe fruitā€, which is the intended outcome. That still leaves open the option for someone who can recognise ripe fruit to add the ā€œripe fruitā€ annotation later or downvote an incorrect annotation.

I’d be open to other wording for senescence, such as ā€œleaves changing colourā€. However, most people don’t annotate leaves anyway, and the current wording has a few people marking ā€œgreen leavesā€ for evergreen plants. What the change opens up is the chance for informed annotaters to use a core iNat function to greater effect.

Further on flowers and fruit, I think the final option would be better as:

No flowers or fruit visible

This better captures the issue of evidence for vs. against, similar to wording on ID disagreements. Recently, I’ve been mapping distributions of Box Mistletoe near my home to understand its urban ecology. I’m making no attempt to zoom in on the mistletoes, which are up high in eucalypts, to show the unripe fruit expected at this time of year. But I can’t in good faith annotate ā€œNo flowers or fruitā€, so these observations remain pending annotation.

1 Like

Maybe ā€œLife Stageā€ should be renamed ā€œObservation Life Stageā€ and continue being a single value field like it is now.

Then, a second ā€œOther Life Stagesā€ field should be added and which accepts multiple values.

ā€œOther Life Stagesā€ would be similar to ā€œEvidence of Presenceā€. I can see ā€œOther Life Stagesā€ being useful for beetles where sometimes there is an adult beetle laying eggs, or when there are larvae emerging from eggs, or when an adult beetle is emerging from its pupa, or when there are clearly pupae and the picture shows a larvae next to them.

Observations (and therefore their annotations) are for individual organisms, and staff have noted many times that observations are the fundamental unit of iNaturalist. It seems very unlikely that annotations that break that definition of the observation would be included.

1 Like

Just adding ripe fruit in addition to fruit? I would have thought it would expand into ripe and unripe fruit, though that would have backwards compatibility issues, true. Feels odd to have typed fruit annotation next to untyped fruit, which is why I like the drop down menu option becoming available when fruit is selected.

My thought is that you add ā€œripe fruitā€ as an additional stage and leave ā€œfruitā€ as a stage without further definition. As you note, it avoids backward compatibility issues. It also means people can mark ā€œfruitā€ without needing to know whether the fruit is ripe or not. Plenty of times, people will mark ā€œflowersā€ without additionally noting the equally visible ā€œflower budsā€. Incomplete annotation is less of a problem than incorrect annotation.

4 Likes

I was going to make a feature request for the addition of some plant annotations, but apparently iNat staff is ā€œnot currently accepting feature requests relating to annotationsā€, so here I am.

We really need an ā€œExpanding leavesā€ annotation for species with naked buds whose leaf primordia are not enclosed by bud scales but nevertheless expand into mature leaves. Examples are Carya cordiformis, Juglans cinerea and Filicium decipiens (which gave me the idea for this annotation as I have just finished reviewing its observations). This annotation could also apply to the leaves of species with enclosed buds that are still actively growing, up to the point where they stop growing completely.

Additionally, I think the ā€œCannot be determinedā€ annotation should be extended to the Flowers and fruits and Leaves categories, for observations where only isolated floral buds/flowers/fruits or only isolated leaves are included. Observations of a single leaf on a countertop or in someone’s hand are too common for this not to exist.

Finally please give our conifer homies some love with ā€œMale/staminate conesā€, ā€œFemale/ovulate conesā€ and ā€œSeedsā€ annotations

1 Like

I agree with you on all fronts. The current annotations are heavily skewed toward temperate deciduous plants with enclosed buds. Many tropical evergreen plants have naked buds and never lose all their leaves at once, although most do lose some of their leaves every year. I had also thought that ā€œSenescing/senescent leavesā€ would make for a much more accurate annotation than ā€œColored leavesā€. My full list:

  1. Breaking leaf buds
  2. Expanding leaves
  3. Mature leaves
  4. Senescing leaves
  5. No live leaves

As I’ve suggested, the less wordy ā€œCannot be determinedā€ that is already in use for the Sex category would stand in well for ā€œNot enough evidence to be assessedā€. Otherwise ā€œInsufficient evidenceā€ might work. Why was your feature request rejected exactly?

1 Like

To keep the conversation together on one active thread ? (Rejected as a NEW feature request - not the request as such was rejected)

1 Like

I see. Thank you

The issue is that this thread isn’t so good for reaching iNat staff and petitioning in favour of annotation changes, unlike specific feature requests

? This is the dedicated thread. And the author is tiwane. iNat staff.

2 Likes

That sounds like a very technical difference from the existing ā€œbreaking leaf buds,ā€ and I doubt if it matters much. Separating the two is basically annotating taxon rather than phenology, which isn’t what annotations are for.

That would be annotated ā€œgreen leaves,ā€ with no need to annotate anything regarding flowers. Why? Because that kind of observation is not useful to someone studying flower phenology, which is the kind of user who needs the flower annotations.

Now there, I’m with you. Many of us have asked for that.

You’re right. When I opened the thread I jumped to a late reply but Tiwane indeed created it. There is also a list of annotations under review at the top which I hadn’t noticed

1 Like

I agree that the difference is very granular and ā€œtechnicalā€. Ultimately what I struggle with is the goal of annotations and why there are limits to how specific they can be. For the sake of efficiency, simplicity and user-friendliness, I am of the opinion that there should exist as few annotations as possible, but sometimes the existing ones just don’t strike my preferred level of granularity. Also ā€œgreen leavesā€ is actually too granular for plants whose mature leaves are not green, like the ā€˜Crimson King’ cultivar of Acer platanoides.

I agree there is no need to add an annotation in the Flowers and fruits category in this scenario. I am just worried that someone will add an erroneous, incorrigible annotation later if I don’t indicate the absence of floral buds, flowers or fruits. I guess ā€œNo flowers or fruitsā€ is good enough, although it can’t be proven that the plant the leaf was collected from did not bear any of these structures at the time of collection.

Agreed. As others mentioned above, incorrect annotations are much more common and problematic than incomplete ones.

A related problem I’ve noticed is fruit that’s hanging onto the plant but is no longer viable (e.g. gray, shriveled acorns that are already dead, but didn’t absciss properly). I’d prefer they weren’t marked as fruit, and where flowers and buds are absent, the ā€œNot enough evidence to assess flower/fruitā€ would be useful to prevent future erroneous annotations as ā€œfruitingā€.

Yeah that’s not what anyone’s arguing, but we are actively slowing the research process by not curating annotations to reduce the amount of data checking that researchers need to do.

A great example of this was the Yucca Phenology Project and research article (in which they manually annotated ~9,000 observations), relying in part upon correct annotations to allow for accurate characterization of changes in phenology related to climate change, and also allude to the untapped power and limitations of iNaturalist/citizen science data generally via recommendations for improved best practices (including annotating lack of evidence for flowering/fruiting assessment as I mentioned in my first post on this):

https://www.inaturalist.org/posts/27112-using-inaturalist-to-help-solve-a-desert-southwest-phenological-mystery

ā€Most importantly, we want to use this journal post to thank all the people who have taken the time to photograph and identify Yuccas…As we show in our paper, we can actually get a fairly good idea of just where, when and to-whom those flowering anomalies happened, and we can also ask some neat follow-up questions, too. For example, did species in areas that had unusual flowering events have reduced or no flowering during normal flowering times? And while I am excited about the work we’ve done, I think there is enormous and yet-untapped potential to look at phenology trends at scale using iNaturalist data.ā€

and

ā€Despite these promising attributes, best practices for use of iNaturalist and associated citizen science data resources must still be developed to realize the full value of these data streams for assessing plant phenology trends…In particular, we scored flowers, open flowers and whole plants as present or absent. We added ā€œuncertainā€ as a scoring category, because initial examination revealed cases where image quality was poor or the state otherwise difficult to observe.ā€

one more:

ā€œiNaturalist records often can be used to report absence, which is particularly useful for modeling climatic drivers of phenology. Definitive absence requires scoring if a whole plant is visible in the photograph, which we strongly recommend capturing.ā€

3 Likes