Description of the desired feature
When downloading the .csv or .json from your OceanOps search query, you find the (SENSOR) START OR END DATEs also with the TIME information hh:mm:ss.
The description of the OceanOps format describes and also when entering these parameters in OceanOps, you can only select the DATE yyyy-mm-dd.
Often the hh:mm:ss information is T00:00:00Z but sometimes you find it for example as T13:45:03Z
How/where do the entries with the TIME other then T00:00:00Z come from?
If you provide your metainformation via file, should you add the TIME hh:mm:ss for the (SENSOR) START OR END DATEs groups? Should this be necessary?
Right now if you provide the TIME and it does not match with the entry in OceanOps, OceanOps likes to create a new sensor entry for this station.
Also if you only provide the DATE, it will not match with the OceanOps entries.
I would like some clarification.
Suggested solution
No response
Alternatives considered
No response
Additional context
No response
Description of the desired feature
When downloading the .csv or .json from your OceanOps search query, you find the (SENSOR) START OR END DATEs also with the TIME information hh:mm:ss.
The description of the OceanOps format describes and also when entering these parameters in OceanOps, you can only select the DATE yyyy-mm-dd.
Often the hh:mm:ss information is T00:00:00Z but sometimes you find it for example as T13:45:03Z
How/where do the entries with the TIME other then T00:00:00Z come from?
If you provide your metainformation via file, should you add the TIME hh:mm:ss for the (SENSOR) START OR END DATEs groups? Should this be necessary?
Right now if you provide the TIME and it does not match with the entry in OceanOps, OceanOps likes to create a new sensor entry for this station.
Also if you only provide the DATE, it will not match with the OceanOps entries.
I would like some clarification.
Suggested solution
No response
Alternatives considered
No response
Additional context
No response