Conceptual Modelling

This module is implemented within the 1 ha plot at 1, 2, 3 or 4 100 m transects consisting of 100, 1 m x 1 m consecutive quadrats. In each quadrat, the absence of signs is recorded, or the presence of each sign type along with the attributed species (minimum data requirement). The number of each sign type by attributed species can be recorded.

The feature of interest is fauna sign, and the feature type is fauna evidence . All observations are recorded for each site during a site visit. Weather conditions are recorded as observations too, and the feature type is weather.

Mapping Diagram

This diagram includes parameters used during the survey and their relationships.

Survey Data Mapping

https://dev.core-api.paratoo.tern.org.au/documentation/#/Sign-based-active-plot-search-survey/post%2Fsign-based-active-plot-search-surveys provides example survey data:

{
  "data": {
    "surveyId": "string",
    "plot_visit": 0,
    "survey_type": "S",  ##TBC
    "survey_intent": "O",
    "nearby_track_transect_survey": true, ##TBC
    "target_species": [
      {
        "lut": "Goat",
        "other_species": "string"
      }
    ],
    "observer_details": [
      {
        "observer_name": "string",
        "role": "S"
      }
    ],
    "weather": {
      "precipitation": "NO",
      "precipitation_duration": "I",
      "wind_description": "C",
      "cloud_cover": "SU",
      "temperature": 0,
      "moon_phase": "NM"
    },
    "tracking_surface_info": "string", ##TBC
    "site_info_collection": true,  ##TBC
    "createdBy": 0,
    "updatedBy": 0
  }
}

Surveys are mapped as Procedure in TERN Ontology. Protocol used is Method, and linked with Procedure via tern:hasMethod.

Reconnaissance and survey set-up are before conducting surveys, and parameters entered in this process are mapped as Attribute of survey Input.

TERN has Ontology for people and organisations https://linkeddata.tern.org.au/viewers/tern-org-ontology. Observer is mapped as Agent. Role is Attribute of Agent. Agent has property schema:name, and it’s the observer name.

Mapping parameters into TERN Ontology

Parameter in example data	Properties or classes in TERN Ontology

Parameter in example data	Properties or classes in TERN Ontology
surveyId	The URL of `tern:Procedure` class
plot_visit	The class `tern:SiteVisit`
survey_intent	The attribute of class `tern:Input`, fauna survey intent type
target_species	The attribute of class `tern:Input`, target species
observer_details	The class `prov:Agent`
observer_name	The property of `prov:Agent`, schema:name
Role	The attribute of `prov:Agent`, observer role
weather	The class `tern:ObservationCollection` with a collection of weather observations
precipitation	The class `tern:Observation`with observable property precipitation type
precipitation_duration	The class `tern:Observation`with observable property precipitation duration
wind description	The class `tern:Observation`with observable property wind description
cloud_cover	The class `tern:Observation`with observable property cloud cover
temperature	The class `tern:Observation`with observable property air temperature
moon_phase	The class `tern:Observation`with observable property moon phase
createdBy	The class `prov:Agent`
updatedBy	The class `prov:Agent`

Mapping example

If the survey data is:

{
  "data": {
    "surveyId": "survey001",
    "plot_visit": site-visit-001,
    "survey_intent": "one-off measure",
    "target_species": [
      {
        "lut": "Goat",
        "other_species": "Cat"
      }
    ],
    "observer_details": [
      {
        "observer_name": "Luke Green",
        "role": "Experienced surveyor"
      }
    ],
    "weather": {
      "precipitation": "NO",
      "precipitation_duration": "I",
      "wind_description": "C",
      "cloud_cover": "SU",
      "temperature": 15,
      "moon_phase": "NM"
    },
    "createdBy": "Luke Green",
    "updatedBy": "Luke Green"
  }
}

How is Survey represented? https://w3id.org/tern/ontologies/tern/Procedure

<http://example.com/survey/001> a tern:Procedure ; -------------------------------------------- #surveyId
        tern:hasMethod <http://example.com/url-of-within-plot-belt-transect-protocol> ; ------- #method URI in controlled vocabualries
        tern:hasInput <http://example.com/survey001/input-variables> ;
        prov:wasAssociatedWith <http://example.com/person/luke-green> . ----------------------- #observer / people who created or updated the record

<http://example.com/survey001/input-variables> a tern:Input ;
        tern:hasAttribute <http://example.com/survey001/input-variables/survey-intent> ; ------ #survey_intent
        tern:hasAttribute <http://example.com/survey001/input-variables/target-species> . ----- #target_species

How is attribute value represented? https://w3id.org/tern/ontologies/tern/Attribute

How is plot visit represented? https://w3id.org/tern/ontologies/tern/SiteVisit

How is observation represented? https://w3id.org/tern/ontologies/tern/Observation

How is person represented? https://w3id.org/tern/ontologies/org/Person

Project: PlotX

Protocol Mapping: Signs-based Fauna Survey - Within-plot Belt Transect