-
Notifications
You must be signed in to change notification settings - Fork 179
CF timeSeries featureType and forecast_reference_time don't play nice together. #1080
Comments
Yes, 2D time probably should work for DGSs, but bear in mind that your dataset is no longer CF-compliant once you add the |
Interesting... I wouldn't read the DSG spec as disallowing 2D time, but I can see how it could be interpreted that way. |
@dblodgett-usgs I'm agree with you about DSG spec it's more general than the implicit interpretation been made when examples, in the CF, are exposed. |
@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. |
Do I mind? Not one bit! Just didn't want to muddy your issue list with open ended requests! |
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: