|
During testing with a third party application, we noticed a problem where that application won't accept zero-length time domain ranges in the WMS capabilities statement (i.e. for something like <start>/<end>/PT1S, start can not be equal to end).
The GeoTools netcdf reader always returns ranges, and some data types (e.g. forecasts) contain multiple "instant" values.
[See http://osgeo-org.1560.x6.nabble.com/Time-dimension-for-a-quot-instant-quot-td5193512.html for the mailing list discussion]
This could be worked around by changing the behaviour on the GeoTools side, or on the GeoServer side. I did look at the GeoTools side, but the change appears easier / less intrusive / less risky on the GeoServer side. Also, there is a chance that there are other coverage sources other than NetCDF that might also require that change if implemented on GeoTools side.
|
