Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Established patterns for modelling of species occurrence? #222

Open
ashleysommer opened this issue May 31, 2024 · 6 comments
Open

Established patterns for modelling of species occurrence? #222

ashleysommer opened this issue May 31, 2024 · 6 comments
Labels
wontfix This will not be worked on

Comments

@ashleysommer
Copy link

ashleysommer commented May 31, 2024

@nicholascar and I have some ideas for proposing one or two new classes and properties in the TERN ontology to more cleanly model species occurrences, for use in the BDR.

Before we go ahead and write up the proposal, is there any example data or real production data that shows how TERN models individual incidental species occurrence, and/or systematic survey results of species occurrence (plants or animals)?

Partially related to #59
Partially related to #69

@smguru
Copy link
Contributor

smguru commented Jun 2, 2024

Hello @ashleysommer yes we have data which is completely animal occurrence in Ecoplots https://ecoplots.tern.org.au/search?dataset=wet-tropics-vertebrate#/

Occurrence is a feature type, and we manage it using a FoI and feature type. For example, animal occurrence and plant occurrence are all related to occurrence.
We have added a survey class based on Nic's recommendation, which is another option. We call that class optional.

FYi @javiersan18 @nicholascar @junrongYu

@ashleysommer
Copy link
Author

Thanks @smguru

Our conversations in the BDR have been around modelling an occurrence as something that happens at a specific time. So in SOSA an occurrence would be a subclass of an Observation or a Sampling. In current modelling design we have a Sampling of a geometry produces a Sample (the animal specimen), then an Observation of the specimen produces the scientific_name result. We are treating the Observation as the occurrence, but we are considering switching the perspective to consider the Sampling as the "occurrence" as it happens at a time, and produces a specimen.

I suppose it comes down to the question of; is an "occurrence" an event at a time and place, or a thing with properties?

Our intention with this conversation was to propose a subclass of tern:Sampling called, called something like:

  • OccurrenceSampling
  • OccurrenceEvent
  • OccurrenceActivity

Then we could more cleanly model the species occurrence without forcing occurrence-specific properties and restrictions on a tern:Sampling.

@ashleysommer
Copy link
Author

I have diagrammed the modelling of a single record of the wet-tropics-vertebrate dataset, showing the way TERN has done their modelling, with the Feature-of-interest centric view:
TERN Occurrence model(1)

@ashleysommer
Copy link
Author

ashleysommer commented Jun 4, 2024

This is how we are currently modelling it using Sampling as the Occurrence activity:
Copy of Dingo Model

@smguru
Copy link
Contributor

smguru commented Jun 5, 2024

Hello @ashleysommer long time back we did a demo on occurrence data you can look at the example here https://github.com/ternaustralia/bdr-faealla-worked-example
you can play with the data as well.

FYI @javiersan18 @junrongYu

@smguru smguru added the wontfix This will not be worked on label Aug 27, 2024
@smguru
Copy link
Contributor

smguru commented Aug 27, 2024

@ashleysommer probably subclass is not required and I will keep this issue on freeze

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants