|
Brad Hards created an issue |
Issue Type: |
|
---|---|
Affects Versions: |
2.8-beta |
Assignee: |
|
Components: |
Main |
Created: |
28/Mar/15 7:36 PM |
Priority: |
|
Reporter: |
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. 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. |
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |
|