-
Notifications
You must be signed in to change notification settings - Fork 17
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
nominal time versus start time #134
Comments
Need to inquire with Gunther Haase whether this should be considered baltrad issue, this might happen in merging scripts generating polar volumes that do not store the adequate nominal time. |
From ODIM hdf5 data model: Note that all date and time information is for the nominal time of the data, ie. the time for which the data are valid. (The nominal time is not the exact acquisition time which is found elsewhere in the file.) Note that all scans belonging to the same volume must have the same nominal date and time. Some ambiguity here in what time for which the data are valid means exactly |
Certain baltrad polar volumes have nominal time in 15 minute blocks, even when polar volumes are available every 5 minutes. This leads to profiles that have duplicate nominal times (under
what/date
andwhat/time
). The starting time of the scan, as stored under/how/startdate
attribute, is different for these polar volumes.Two possible solutions:
/how/startdate
or - more in line with bioRad convention so far -(/how/startdate + /how/enddate)/2
as the profile nominal time instead. This requires a change in vol2bird.The text was updated successfully, but these errors were encountered: