Thredds calls failing again, Are data deliveries running slow?

[Kenneth schaudt]

Worked over the weekend but is failing again.

Are downloads from the Navy running slow?  This is not within the do not
download hours in the About Comments.


 ncks -D0 -d time,2025-07-14T00:00:00Z,2025-07-20T23:00:00Z -v
water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0.
http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd
-O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4
ERROR: nco__open() unable to open file
"http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd"
ERROR NC_EDAP Generic DAP error
HINT: NC_EDAP errors can occur when NCO is invoked with a request that a
remote DAP server cannot meet, for example, due to the size of the
required data transfer. One workaround might be to re-formulate the NCO
command into more commands that each request smaller subsets/hyperslabs
from the remote DAP server. However, there are a number of DAP-related
errors, only one of which can be reported at a time. The others include:
NC_EDAPSVC (-70, DAP server error), NC_EDDS and NC_EDMR (-72, Malformed
or inaccessible DDS and Dap4 alias, respectively), NC_EDATADDS and
NC_EDATADAP (-73, Malformed or inaccessible DATADDS and Dap4 alias,
respectively), NC_EDAPURL and NC_EURL (-74, Malformed DAP URL and
Malformed URL, respectively), NC_EDAPCONSTRAINT and NC_ECONSTRAINT (-75,
Malformed DAP Constraint and Malformed Constraint, respectively). Few,
if any, of these errors are expected to be caused by NCO, since NCO just
relays user commands to the DAP server. It is more likely that the DAP
syntax employed is incorrect, or there is an error with the DAP server,
or the request exceeds the server constraints.
nco_err_exit(): ERROR Short NCO-generated message (usually name of
function that triggered error): nco__open()
nco_err_exit(): ERROR Error code is -73. Translation into English with
nc_strerror(-73) is "NetCDF: Malformed or inaccessible DAP2 DATADDS or
DAP4 DAP response"
nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)
+ echo 'ERROR: sleeping for 90 seconds and then trying again...'