-
Notifications
You must be signed in to change notification settings - Fork 179
ncWMS2 renders incorrect imagery from NcML aggregates #968
Comments
I think this might be related to #977. I'm going to try to get a a snapshot version of 5.0 out with updated |
I have an updated version of |
ooo, @danwild I'm following you around :) I'm going to guess the data is from either gbr1_2.0 or gbr4_2.0 at https://dapds00.nci.org.au/thredds/catalog/catalogs/fx3/catalog.html |
@lesserwhirls I have finally sent you some example files (check email). |
I have the same issue with the tds 5.0.0 snapshot: But the getFeatureInfo is OK (values change with the time parameter). If i update the edal jars to 1.4.1, the issue is the same: (maybe related to #1041) |
I'm using v5.0.0-alpha3.
I have a fairly simple aggregate, which performs a joinExisting on a directory of files with single time steps in each file:
The virtual dataset produced by this aggregation is correct.. however, when accessing the resulting WMS services the same imagery is returned regardless of the time parameter. The correct time steps are declared in GetCapabilities, but no matter which of these time steps you request in a GetMap query - it always returns the same image.
I have just deployed ncWMS (v2.2.12) as a separate application in tomcat, and am able to publish a WMS service using the OpenDAP endpoint derived from the same virtual dataset - and this behaves as expected.
The text was updated successfully, but these errors were encountered: