- 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
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