Bees on plants in botanical gardens

Hello everybody!

Over the past years I have uploaded every now and then an occasional bee to the platform. Now I would like to become a bit more serious and I was thinking that in addition to the bee, I could annotate the flower as well. Thus, I thought I could just duplicate the bee entry and make in addition a flower entry out of it (Probably I need to add an additional flower picture as often my pictures are cropped to the bee). Like here:

Bee - https://www.inaturalist.org/observations/311643914

Flower - https://www.inaturalist.org/observations/315007032

In the ā€˜Notes’ section I refer to the other entry and I also add ā€˜Observation Fields’ (Flower visited by bee … & Interaction –> Visited flower of …)

Is it okay to do it like this or is there any better way to link bee and flower. Also, as many of my bee observations are from Botanical Gardens, I would add quite some cultivated plants (Of course I would mark them as cultivated, but still.). Is that even wanted? Should I try to proceed with this, or is it better, to just stick to the bees?

Thanks for your thoughts,

Anja!

1 Like

You are welcome to use this project. Started in South Africa, but open to all - while we wait for iNat to offer an integrated way.

https://www.inaturalist.org/projects/interactions-linked

1 Like

You can also use the field ā€œAssociated Observationā€ to link to the relevant observation. I’ve added it to your observations as an example.

2 Likes

Thanks! I joined the project and added the interactions.

2 Likes

Thanks, will do this as well.

2 Likes

Here’s one of my observations (a spider, not a bee) with the ā€œAssociated observationā€ field: https://www.inaturalist.org/observations/312841143 . How do you associate more than two observations together?

I find it useful, every once in a while, to re-read this comment by the creator of iNaturalist. From 2019 Feb 26:

4 Likes

I enjoy observing bees in botanical gardens (my local one has a section with flower beds arranged taxonomically, for educational purposes, and I have thought sometimes that this must seem like an all-you-can-eat buffet for the oligolectic bees who specialize in a particular genus or family).

I try to take a photo of the label when photographing bees on a particular plant so that I can note this in the observation (I enter the taxon name in the observation field Interaction → Visited flower of), but I don’t as a rule make separate observations for the plants. There is no rule that you cannot, but I don’t personally find it meaningful to do so. Also note that you can’t add more than one value for an observation field, so if multiple insects visited the same plant, it is difficult to link the plant to more than one observation.

You can create a set of linked observations by assigning them all the same value specific to that set (usually the number of one of the observations). This is the premise of the observation field similar observation set. However, you can’t record the type of relationship between the observations using this field.

2 Likes

I typically use the ā€œduplicateā€ feature:

  1. Combine all the pictures showing a combo of different species that I plan to duplicate for into one observation.
  2. ID for an obvious one in the first picture, adding a note in the description which one is the ID target.
  3. Upload to generate the observation record.
  4. Duplicate the observation and ID for other species in the picture(s), adding notes which one is the target for each.
  5. Edit the duplicates as needed by deleting pictures that don’t show the identified organism and adding additional pictures that show only that organism.
  6. Resort the images for all observations so ideally the identified organism is the only (or at last most obvious) target in the first picture.

This will result in all the observations being linked together on the photo pages - example: https://www.inaturalist.org/photos/56583514

3 Likes

2016 … 2019 … meanwhile we are forced to use a workaround. ā€˜Our hands are tied’

While I’ve done this, I’ve always followed the protocol of this project: Pollinator Interactions of Plants (PIP) of the NE US. Their project page states:

ā€˜We request that submissions include the following observation field: ā€œInteraction->Visited flower of:ā€ It is a required field for this project. If you’re unsure of the flower, you can put ā€˜flowering plant’ as the taxon and then post a second iNat observation of the flower. To link iNat observations between pollinator and plant, add the observation field **ā€œreference URLā€**and include the link.’

And in fact when you try to add an observation to this project, you are prompted to include that ā€œInteraction->Visited flower ofā€ observation field. Then, even when I feel that I’m able to enter the plant to species level, I try always to make a separate observation of the plant and add the ā€œreference URLā€ observation field. This seems especially important in genera where my ID may be inaccurate, e.g., where there are possible hybrids, or e.g. where IDs can get tricky (as with Solidago in our region).

The general point I’m making is that even though iNat may not be ideal for recording interactions between organisms, using an established protocol set up by a well-thought-out project goes a long way towards providing useful structure for the data.

5 Likes

If you end up using observation fields, I made a little viewer…
Garden Viewer

I keep doing re-writes of the source code so it’s not completely ready to share yet. It could be interesting for a botanical garden because they could ask visitors to do a targeted bio-blitz for wildlife activity on only certain plants. There is a configuration file (a .json) that tells it which observation field to focus on for the plant list and for wildlife activity.

2 Likes

Thanks for your thoughts. And yes, I actually agree, adding the plant as an additional observation is probably not very meaningful as all of these observations would be casual. In the end, all I want is having somehow a proper link to the visited plant species in addition to the ā€˜Notes’ section.

True that. Thanks for making me aware of the project. And yes, even though I take many of my pictures in Botanical Gardens, plants are not always labelled which makes it sometimes necessary to upload the plant as its own observation to indeed confirm species.

This is cool. :slight_smile: Is that automatically updated? I linked a view more observations that I made here in the Botanical Garden. I definitely like it as it provides a nice list of plants with its visitors for a specific Botanical Garden. Thanks!

I figured out that it is updated. :slight_smile: But these four (all linked to Common motherwort) are not included. Did you specify a start date for the viewer?

https://www.inaturalist.org/observations/288986232

https://www.inaturalist.org/observations/291158043

https://www.inaturalist.org/observations/292033116

https://www.inaturalist.org/observations/291245477

It’s project based… so the observation of the common motherwort would need to be in the ā€œTiere, Pilze und Pflanzen I’m Botanischen Garten der Universitat Tubingenā€ project. The other option would be to create a project for just the plants that are ā€œin focusā€ and add and remove plants to that project when you want them to appear in the app.

Part of the thinking is… the botanical garden could then direct visitors to specific plants via their configuration of the app. Some of the cultivated plants in a botanical garden tend to be unusual. It’s possible the unusual plants have unusual insect visitors. If each botanical garden had a handful of observers, they would quite naturally begin to on-board those users who would want their data to display in the app provided by the botanical garden project. It’s a way to nudge organizations toward helping with iNat on-boarding. What the organization gets out of it is data, visitor engagement, and the ability to direct the attention of their visitors toward specific plants.

It also helps with data normalization… because observers within each botanical garden would use consistent observation fields if they wanted their data to appear in the app for the botanical garden staff to see.

1 Like

Also… from the app’s perspective, you only need one plant observation with ā€œinteraction→flower visited byā€ populated (the app doesn’t need a plant observation for every insect visit). You could use a generic field like ā€œgarden listā€ = ā€œyesā€ for the plant if you wanted to. You can also configure it to use a tag as the plant filter… so if a botanist at the botanical garden wanted to have their own configuration with a handful of plants in focus they could tag plant observations with a unique tag that the app could be configured to look for…

I like to use the Observation field ā€˜Feeding on’, because many of my flowers have been planted by me and I don’t add them to iNat. Here an example: https://www.inaturalist.org/observations/316566679 .

Then I can click on ā€˜Feeding on’ and look at all the different insects that have been feeding on Tagetes patula on all of iNat (well, all the ones annotated with ā€˜Feeding on’)

Thanks! :slight_smile: The observations on common motehrwort are in the project ā€œTiere, Pilze und Pflanzen I’m Botanischen Garten der Universitat Tubingenā€ but still not in the viewer list. As far as I can see, all other observations are included except for all observations on this plant - which is quite curious.

I have to admit, some of the things you are trying to explain to me, I don’t get. :slight_smile: But I also don’t want to annoy you with more questions. I really have to spend a little more time on iNaturlist to figure some things out.

In any case, I love the idea of the viewer that you made, because as you say it enables you directly to figure out plants that are visited by certain insects which makes it much easier to direct people. If you want this.