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

Do we recommend measurementDeterminedDate for MOFs associated with occurrences #15

Open
peterdesmet opened this issue Sep 13, 2019 · 2 comments

Comments

@peterdesmet
Copy link
Member

From the Mahoney use case: if a temperature measurement F53:deployment1:measurement1 in MOF is associated with an occurrence F53:deployment1:1902295519 and that occurrence has a precise eventDate = 2014-02-11 21:35:42.000+00:00. Do we recommend to then also repeat that eventDate as the measurementDeterminedDate of the MOF record?

/cc @pieterprovoost

@pieterprovoost
Copy link

@peterdesmet From the OBIS perspective there's no need to repeat the time. When we parse and index data in OBIS attributes such as time and location are inherited from parent records unless the information in the child record is more precise.

One could argue that repeating the time is useful in case someone accesses the Darwin Core Archive directly to work with the measurements, but some matching with the occurrences will need to happen anyway in order to get the coordinates (for which there are no fields in the measurements). So I would not recommend repeating time.

@peterdesmet
Copy link
Member Author

Thanks @pieterprovoost. It will also lead to smaller data files and avoids consistency errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants