You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.
Maybe I'm missing something, but is there no way to have (time,feature_id) axis order in a timeSeries feature type NetCDF-DSG file? I can only get the point featureType to work in THREDDS or toolsUI if I have (feature_id,time) I would prefer to have time be the most rapidly varying dimension and would like to be able to aggregate along the time dimension -- which I think requires time to be the first dimension as in streamflow(time,feature_id).
There is a partial solution -- to chunk the data and counter the axis order, but I can't aggregate files over time with that approach.
I see that the CF spec has the axis order as data(i,o) but is that supposed to be strictly that axis order? I see some text at the end of H.2. that seems to indicate that the order shouldn't be strictly enforced? Either the instance (station) or the element (time) dimension may optionally be the netCDF unlimited dimension. That seems to indicate that either dimension could be the outer dimension... right?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Maybe I'm missing something, but is there no way to have (time,feature_id) axis order in a timeSeries feature type NetCDF-DSG file? I can only get the point featureType to work in THREDDS or toolsUI if I have (feature_id,time) I would prefer to have time be the most rapidly varying dimension and would like to be able to aggregate along the time dimension -- which I think requires time to be the first dimension as in streamflow(time,feature_id).
There is a partial solution -- to chunk the data and counter the axis order, but I can't aggregate files over time with that approach.
I see that the CF spec has the axis order as data(i,o) but is that supposed to be strictly that axis order? I see some text at the end of H.2. that seems to indicate that the order shouldn't be strictly enforced?
Either the instance (station) or the element (time) dimension may optionally be the netCDF unlimited dimension.
That seems to indicate that either dimension could be the outer dimension... right?The text was updated successfully, but these errors were encountered: