-
Notifications
You must be signed in to change notification settings - Fork 8
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
Start and End coordinates and depths in DarwinCore #206
Comments
I don't know if there are any best practise for this maybe the OBIS folks would know. Generally, the start and end position of the trawl event could be modelled in the the dwc:footprintWKT (https://dwc.tdwg.org/terms/#dwc:footprintWKT) field, something like |
WKT does allow a third dimension, but you will have to specify what that third dimension is. In this case I think you can use
|
Maybe it makes sense to create three events - (1) start of the trawl as the first event, (2) the full trawl as the third event, and (3) the end of the trawl as the third event? And chain them together using parentEventID? |
I was unaware of WKT allowing a third dimension, but I think that's a great option for describing the transect. It seems to me that the simplest thing would be to use it to describe the entire transect as a single sample, but I wouldn't be opposed to what @dagendresen suggests, or some variation on it. |
It is also possible to use the extended Measurement or Facts extension (eMoF) for the start and end depth of the Event. Maybe these two vocabs suggested by @JoBeja can be used for
Thanks again! |
I work with datasets who are typically structured with start and end coordinates (ex: start and end positions of a trawl event)
and start and end depth values (who are not necessarly equivalent to a mininum or maximum depth of the transect) .
What would be the best practice to map these informations in the Darwin Core standard?
The text was updated successfully, but these errors were encountered: