[5.5-SNAPSHOT]: WMS error: Coordinate values must increase or decrease monotonically about netcdf-java HOT 9 CLOSED

ah my bad, I missed that. Thanks @ethanrd !

from netcdf-java.

Duplicate of #1060

from netcdf-java.

Duplicate of #1060

Is there any possible solution on my end? or any chance you could explain the problem ?

from netcdf-java.

There is no solution as of now but we're working on the problem. You can see a description of why it is occurring as well as updates on progress on the other issue.

from netcdf-java.

This is a netCDF-4 file rather than GRIB. So, while similar symptoms, I don't think this is a duplicate of #1060.

It looks like the depth variable isn't a legal "coordinate variable". To be a "coordinate variable", the variable must be strictly monotonic either increasing or decreasing. The depth array in this file starts with three values of 4600 (ncdump -v depth wms_not_working_2023051700.nc):

netcdf wms_not_working_2023051700 {
...
data:

 depth = **4600, 4600, 4600**, 4334.079, 3956.516, 3577.858, 3205.621, 2851.658, 
    2523.303, 2212.311, 1929.255, 1673.802, 1442.16, 1236.618, 1051.309, 
    900.1193, 761.5495, 642.9122, 540.6172, 453.3608, 379.6924, 317.8554, 
    265.8571, 222.3855, 185.9007, 155.3554, 130.2982, 109.4334, 92.16574, 
    77.78061, 65.77026, 55.71438, 47.28482, 40.32711, 34.41242, 29.41823, 
    25.19542, 21.58195, 18.48265, 15.80275, 13.45813, 11.39787, 9.565165, 
    6.738814, 4.952401, 3.271224, 1.747637, 0.329119, -1.036858, -2.297761 ;
}

from netcdf-java.

This is a netCDF-4 file rather than GRIB. So, while similar symptoms, I don't think this is a duplicate of #1060.

It looks like the depth variable isn't a legal "coordinate variable". To be a "coordinate variable", the variable must be strictly monotonic either increasing or decreasing. The depth array in this file starts with three values of 4600 (ncdump -v depth wms_not_working_2023051700.nc):

netcdf wms_not_working_2023051700 {
...
data:

 depth = **4600, 4600, 4600**, 4334.079, 3956.516, 3577.858, 3205.621, 2851.658, 
    2523.303, 2212.311, 1929.255, 1673.802, 1442.16, 1236.618, 1051.309, 
    900.1193, 761.5495, 642.9122, 540.6172, 453.3608, 379.6924, 317.8554, 
    265.8571, 222.3855, 185.9007, 155.3554, 130.2982, 109.4334, 92.16574, 
    77.78061, 65.77026, 55.71438, 47.28482, 40.32711, 34.41242, 29.41823, 
    25.19542, 21.58195, 18.48265, 15.80275, 13.45813, 11.39787, 9.565165, 
    6.738814, 4.952401, 3.271224, 1.747637, 0.329119, -1.036858, -2.297761 ;
}

@haileyajohnson @ethanrd

Any idea why this same NetCDF's wms access works on this thredds data server v4.6:

http://thredds.maretec.org/thredds/catalog/IST_MOHID_BIO_DATA/TAGUS_0.007DEG_50L_1H/FORECAST/catalog.html?dataset=MOHIDWATERDatasetScan/TAGUS_0.007DEG_50L_1H/FORECAST/2023051700.nc

from netcdf-java.

TDS 4.6 uses ncWMS 1.x while TDS 5.x uses EDAL-Java 2.x (the underpinnings of ncWMS 2.x). The newer software is stricter about a number of requirements on datasets.

from netcdf-java.

TDS 4.6 uses ncWMS 1.x while TDS 5.x uses EDAL-Java 2.x (the underpinnings of ncWMS 2.x). The newer software is stricter about a number of requirements on datasets.

would it be possible to change the version of ncWMS ?

from netcdf-java.

Unfortunately that is not possible. Your best bet is either to recreate the dataset or edit it virtually with ncml.

from netcdf-java.