-
Notifications
You must be signed in to change notification settings - Fork 3
Data guidelines
| Term | Status |
|---|---|
| basisOfRecord | Required |
| occurrenceID | Required |
| organismID | Required |
| eventDate | Required |
| decimalLatitude & decimalLongitude | Required |
| geodeticDatum | Required |
| scientificName | Required |
| eventID | Strongly recommended |
| samplingProtocol | Strongly recommended |
| kingdom | Strongly recommended |
| taxonRank | Strongly recommended |
| coordinateUncertaintyInMeters | Share if available |
A single record in the Occurrence Core will designate basisOfRecord:HumanObservation to delineate the point in time that the animal was in hand. Future detections of the animal by stations will be designated basisOfRecord:MachineObservation. This is one of the primary ways (combined with organismID) a user would know that the multiple observations are actually multiple detections of the same animal.
EventDate: Must be ISO-8601 compliant, without omitting any known values, with precision preferably up to the second or millisecond. Timezone is required. Time ranges should be represented by full datetimes with time zone in both halves of the range.
GeodeticDatum: EPSG:4326 recommended
eventID = urn:<institutionCode>:<project shortcode>:<datacenter-specific-ID>
datacenter-specific-ID=station-instrument-serial-deployment# is OTN’s method
samplingProtocol must contain a doi or url to published protocol - no free text- or could link to sensorML with a single record that designates the tagging of the animal as basisOfRecord:HumanObservation to delineate the point in time that the animal was in hand. Future detections of the animal by stations will be designated basisOfRecord:MachineObservation.
coordinateUncertaintyInMeters important to include - yes but never have that information, no way to make an educated guess about the upper limit because of the environmental variables affecting the range. Measurements are done on individual studies but it’s pretty much impossible to do for multiple studies.
| Term | Status |
|---|---|
| eventID | Required |
| eventDate | Required |
| decimalLatitude & decimalLongitude | Required |
| geodeticDatum | Required |
| locationID | Strongly Recommended |
| maximumDepthInMeters & minimumDepthInMeters | Strongly Recommended |
| footprintWKT | Share if available |
| modified | Share if available |
Recommendation is to have a reduced (minimum number required) number of events- not necessarily creating one to one relationships between occurrences and events
eventDate would be a range in the case of acoustic telemetry
| Term | Status |
|---|---|
| occurrenceID | Required |
| measurementType | Required |
| measurementValue | Required |
| eventID | Strongly Recommended |
| measurementUnit | Strongly Recommended |
| measurementMethod | Strongly Recommended |
| measurementTypeID | Strongly Recommended |
| measurementMethodID | Strongly Recommended |
| measurementUnitID | Strongly Recommended |
| measurementAccuracy | Share if available |
| measurementDeterminedDate | Share if available |
| measurementDeterminedBy | Share if available |
| measurementRemarks | Share if available |
| measurementValueID | Share if available |
When the basisOfRecord = HumanObservation occurrence IDs would include measurements like: length, weight, sex, alternative organism ids (color ring codes, wing tag codes, floy tag IDs).
When the basisOfRecord = MachineObservation occurrence IDs would include measurements like: temperature, depth, etc.
For event IDs associated with attached equipment, measurements might include: release id, hardware ids, sensor slope, sensor intercept, sensor type, sensor unit, transmitter id, tag id.
MOF Units and measurement types should be referenced in NERC if possible.
transmitter_id Combination of code map and ping ID (e.g. A69-9002-12345)
tag_id Unique tag ID. Dual sensor tags have different transmitter IDs but the same tag ID
release_id Unique tag release ID. A given tag ID may be associated with several release IDs if it has been re-deployed.
Decision: Release is an event with an associated occurrence(BOR:HumanObservation) and that will have the mof release_id and any other hardware ids.
If its a sensor tag and you have the tag spec sheet then you would have sensor slope, intercept, type, and unit in mof.