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.
I've been working with some National Water Model data pulled straight off the NCEP feed. Trying to build daily forecast collection files that I'll then glue together along "reference_time" to create stand alone THREDDS services that can be queried like an FMRC.
Have been experimenting with the FMRC aggregation and ran into too many road blocks, so have just been going nco / straight daily NetCDF files for now.
The issue is NetCDF Java (toolsUI) pointFeature isn't recognizing the data once it has a forecast dimension. Thinking about the use cases and applications of the pointFeature that I'm aware of, I guess I'm not surprised that this isn't handled, but figured I'd leave a record that this is something that maybe should work.
Interesting... I wouldn't read the DSG spec as disallowing 2D time, but I can see how it could be interpreted that way.
Thanks. I mostly wanted to leave a record of this and make sure I wasn't missing something. Will close this and bring it back up in the future if it becomes a strict need. -- really not clear how reference_time would play in the ncSOS API and that's really the potential value here IMHO.
@dblodgett-usgs - mind if we leave this issue open? This is something we'd want to address in the future. It'd also be good to ping the CF list to get some clarification on the case of a 2D time coordinate for a DSG.
I've been working with some National Water Model data pulled straight off the NCEP feed. Trying to build daily forecast collection files that I'll then glue together along "reference_time" to create stand alone THREDDS services that can be queried like an FMRC.
Have been experimenting with the FMRC aggregation and ran into too many road blocks, so have just been going nco / straight daily NetCDF files for now.
The issue is NetCDF Java (toolsUI)
pointFeature
isn't recognizing the data once it has a forecast dimension. Thinking about the use cases and applications of thepointFeature
that I'm aware of, I guess I'm not surprised that this isn't handled, but figured I'd leave a record that this is something that maybe should work.This works:
This doesn't work:
The text was updated successfully, but these errors were encountered: