- To: "netcdf-java@xxxxxxxxxxxxxxxx" <netcdf-java@xxxxxxxxxxxxxxxx>
- Subject: [netcdf-java] Issue directly accessing an ERDDAP dataset from Java application after upgrading netcdf from v4.x to 5.5.2 / 5.5.3
- From: "Paganetti, Robert D CIV USN NUWC DIV NEWPORT RI (USA)" <robert.d.paganetti.civ@xxxxxxxxxxx>
- Date: Tue, 22 Mar 2022 17:12:45 +0000
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=us.navy.mil;
- Ironport-data: A9a23:ri6KEK5O0UCPNVPgVGr/CwxRtFHGchMFZxGqfqrLsTDasI4Tp2RHj j5GCjjCY6DUfSKuKJpxdc7vohRX/dOXm+bXenIv8HBoQjRS9tGt6b+xch+hYijOcJObEhtpt 50TYILLJp5vRy+E+kf0aua8oSFxha3RSrP2V77JYX5/SwNuECwqgE87wLVh2dY0j9XlWmth1 T+cT+j3YDdJjBYqbTpOg076lC5SgRjShN85lgU0O/0W51LSyyRNAMNHLv7pIyOkSdQKFOCzT beYx+3jojqJrhwgNIiow+3xGqEorh8+HuQsZl5+AfXKbiBq/3d0iuBnXBYlQR8/Zw+hx7id8 /0Q883oIesVFveUwr5FCEMCS3oW0ZBuoNcrH1Du6aR/8GWbKxMA8902ZK0HFdVwFtRfWAmix tRBQNw5VS1vssrtqF6NpkmAsex4RCXjFNt3VniNVlg1B95+KXzIa/2iCdO1QF4Nas5y8fb2P 6L1aBJJRTnpRSdhGX4nU8g52sGBqkLCSBBx7nS8iZFxxUHt/UpU8ZyF3Nj9IITXA5UI2B3D4 DiaoQwVATlDXDCb4SCC+H+2mqnD2zvyV4sUGaGk97hhgUO723dVDhQIRB2+oP3RZkuWAIsFd xxOpXF+xUQ13AnxJjXnZDW+rWKPshBZWdNOGsUn7gCBw7bdpRuSD3JCQzJcAOHKHudeqScC0 FaEltXzCz9moObPD3SY/bbSqzqsKG4QLGtqWMPNdiNdi/GLnW35pkunogpLeEJtsuDIJA==
- Ironport-hdrordr: A9a23:sgVTV6PdZxAFUsBcTy3155DYdb4zR+YMi2TDiHofdfUFSKClfp 6V8cjzjSWE9Qr4WBkb6LW90dq7MA/hHP9OkMMs1NKZMjUO11HYVb2KgbGSoAEIXheOjNK1tp 0QPpSWaueAdWSS5PySiGLTcrYdKZu8gduVbI/lvjJQpGpRGsVdBnJCe2Cm+zpNNW577PQCZf ihz/sCgwDlVWUcb8y9CHVAdfPEvcf3mJXvZgNDLwI76SGV5AnYpILSIly95FMzQjlPybAt/S zuiAri/JiutPm911v1y3LT1ZJLg9Hso+EzS/Bky/JlZAkEuDzYJLiJaIfy/wzdldvfqWrC3u O84SvIdP4DlE85NlvF3ycFnTOQlArGokWSuGOwkD/tp9f0Syk9DNcEjYVFcgHB405lp91k1r lXtljp/qa/ICmw6xgV3eK4IS2CV3DE1EYKgKoWlThSQIEeYLheocgW+15UCo4JGGb/5Jo8GO djAcnA7LIOGGnqJEzxry1q2pihT34zFhCJTgwLvdGUySFfmDR8w1EDzMISk38c/NY2SoVC5e 7DLqN0/Ys+BvP+rZgNcNvpbfHHeVAlGyi8QF56CW6XZp06Bw==
Hi, I started seeing this issue when I upgraded netcdf from v4.x to 5.5.2, and I wanted to ask if you might have any ideas as to what is causing this. With cdm v4.x, the following worked as intended: NetcdfFile nc = NetcdfDataset.openFile(https://coastwatch.pfeg.noaa.gov/erddap/griddap/NCEP_Global_Best, null); After upgrading the dependencies to 5.5.3 (cdm-core and opendap), the above line is deprecated (but still produces the same error as below). I changed to the following in line with the API update: NetcdfFile nc = NetcdfDatasets.openFile(https://coastwatch.pfeg.noaa.gov/erddap/griddap/NCEP_Global_Best, null); With both lines, I get the following error: java.io.IOException: Unknown service type: OPENDAP at ucar.nc2.dataset.NetcdfDatasets.openProtocolOrFile(NetcdfDatasets.java:450) at ucar.nc2.dataset.NetcdfDatasets.openFile(NetcdfDatasets.java:347) at ucar.nc2.dataset.NetcdfDatasets.openFile(NetcdfDatasets.java:320) I also tried removing the individual component dependencies and just using netcdfAll 5.5.2, but am seeing the same exception. NetcdfDatasets.openDataset() is also producing the same exception. I might be missing something entirely, but any thoughts or ideas on this would be greatly appreciated - thanks very much! Drew
Attachment:
smime.p7s
Description: S/MIME cryptographic signature