-
Notifications
You must be signed in to change notification settings - Fork 22
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
Clarify the meaning of Territory #557
Comments
Definitions of territory in the standards, documentation and implementations from WMO-No. 1192:
from the UML of the schema: A Territory is a territory specification accompanied by a timestamp indicating the time from which that territory is considered to be valid. If known, an end time may also be provided. In WIGOS, an ObservingFacility may carry multiple territories which are valid over different consecutive periods of time. If only a single territory is specified, the timestamp is optional. from the documentation in the schemas directory UI for new record in OSCAR/Surface: |
Definitions of ownership in the standards, documentation and implementations from WMO-No. 1192:
from documentation |
Details
For now, OceanOPS delivers the operating country of the platform for OSCAR.
We have understood that this should rather be the country in which the platform is operating.
Can you please clarify?
The first solution suits better the marine platforms otherwise we would enter into sensitive issues defining in which EEZ the platform is operating (e.g., disputes). That said, technically we could do it.
Anyway, we still note an issue in the case of European funded and operated platforms (e.g., https://oscar.wmo.int/surface/#/search/station/stationReportDetails/0-22000-0-6900947)
Territory is written "inapplicable", while it should be "European Union".
The platform is effectively operated and owned by the European Research Infrastructure Euro-Argo.
In addition, we envision as well future platforms operated by OceanOPS and then the country would be United Nations. To be discussed.
Requestor
@MKrieger29 and OceanOps
The text was updated successfully, but these errors were encountered: