Open mackenziemeier86 opened 3 months ago
I think if you edit process_deploymentRealtime.yml
and add
profile_time:
comment: Timestamp corresponding to the mid-point of the profile
long_name: Profile Center Time
observation_type: calculated
platform: platform
standard_name: time
_FillValue: -999999.0
it should work?
Please open the other question as a new issue to keep searching the issues trackers clear! Thanks,
When I run my profile files through the IOOS compliance checker the only issue I get is "Variable profile_time must contain attribute: _FillValue" - is there a way to add _FillValue to profile_time? I checked the files and _FillValue isn't included with profile_time.
On another note - we went through our profile .nc files and it seems that half the files captured the start/end of a profile - all the expected profiles are reflected, but every other .nc file generated has this structure with 25 sample points either from the bottom or top of the profile, but is not a continuous dive. I have added the first few EBD/DBD files along with the resulting .nc files (one is a usable profile, one has the 25 samples) and the timeseries/gridfile. Any explanation for why this is happening and how to fix it? https://github.com/mackenziemeier86/Pyglider-Test-Data-and-Output-.git