Open jacteixeira opened 6 years ago
Can you make an example data file available to download?
sure.. here is an example. thank you..
That looks fine when using Godiva3. What client are you using?
It looks as though you are using a different colour scale for each tile. Usually, the colour scale is determined by:
COLORSCALERANGE
<min>,<max>
will set the explicit rangedefault
will set the ncWMS-configured default valueauto
will attempt to auto-scale to the range of values in the request. If you set this on a tiled WMS, you will get results similar to the aboveCOLORSCALERANGE
is not present, it will use the ncWMS-configured default values (which are set automatically to a reasonable range, but can be configured in the admin interface, or in config.xml
)If none of that helps, can you post the parameters you are using for a couple of the tiles?
Actually this happens also in Godiva. We have currently 12 datasets serving this type of netcdf files.
That's strange, the file you sent me works fine in Godiva at all zoom levels. Which version of ncWMS are you using?
At first they worked fine. When we noticed this issue we tried clearing the cache but it didn't work. We are using ncWMS v2.4.1. Maybe this is related to our ncWMS configuration?
I can't think what sort of configuration would cause that issue, but you could send me the relevant snippet of config.xml
anyway. Can you also send me the WMS request strings for two of the tiles (i.e. ones which are displaying in different colours)?
Hi Guy, can you check this nc file, please? The one I sent before might be slightly different of those in the production server. 1_all-ugrid.zip
That also works fine for me.
Hi Guy, we had to postpone our tests regarding this issue for a while. Just to recap our problem is that GetMap requests are returning incorrect tiles. Also when we request tiles at different time levels the tiles returned don't seem to update, even in Godiva. We even tested with other netcdf files similar to ours, such as this one, and have the same results.
After some testing we realize now that this issue only happens with version 2.4.1, we think it can be related to the EDAL 1.4.1 version. We downgraded to 2.4.0 and experienced different errors, but when we downgraded to 2.2.9 all works fine. We can work with this version but we miss the great feature you added to the 2.4.1 version (managing the datasets through the api). We would be most grateful if you could investigate this matter further.
Hi, We had the exact same tilling issue with our flexible mesh model outputs with a TDS server. So I tested a range of flexible mesh model outputs (ADCIRC, SWAN, SELFE) found on the web, and the results were the same . It looks ok at first but after zooming in/out and changing time the tilling get's completely messy. I then saw this ticket (thanks for the tips !) and tested on both ncWMS 2.4.0 and 2.4.1. I confirm that it works properly up to version 2.4.0, but not from v2.4.1 onward. Is it something that could/will be addressed in the upcoming versions ?
Hi all, We would like to serve our data on a web application and, since our data is consisted in mainly unstructured netCDF files, ncWMS is a great choice for it easily serves more complex data. We tested it with few datasets and it worked ok at first. Now, for some reason, the tiles are not rendering correctly at different zoom levels (see image below). Has this happened to anyone? What can we do to correct this. Any help is appreciated :)