ok, now i dont understand why this ever worked if in fact it did (!!),
unless java.util.zip.ZipInputStream has changed its behavior.
anyway im seeing that unzipping zip files is broken, and I will have a
fix for this in the next release.
On 12/14/2011 3:20 AM, Comiskey, Glenn wrote:
Thanks John, you confirmed my understanding. However, have a problem
with several ZIP (.zip) files in a dataset:
[2011-12-14T10:13:55.900+0000] ERROR ucar.nc2.ft.fmrc.FmrcDataset: Cant
java.io.IOException: Cant read C:/<dir1>/<dir2>/<filename>.nc.zip: not a
valid CDM file.
The netCDF-Java version in use is v4.2.25.
The files can readily be opened with ZIP applications and the compressed
NetCDF file (.nc) extracted without issue.
Date: Tue, 13 Dec 2011 10:09:50 -0700
From: John Caron<caron@xxxxxxxxxxxxxxxx>
Subject: Re: [thredds] Supported file compression methods
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
On 12/13/2011 2:33 AM, Comiskey, Glenn wrote:
Can anyone list what file compression methods THREDDS can support when
accessing data files, i.e. can a data file be stored in a compressed
format, such as bzip2, and yet THREDDS can still access the file and
Data System Administrator
If the URL ends with a with ".Z", ".zip", ".gzip", ".gz", or ".bz2", the
file is assumed to be/*compressed*/. The netCDF-Java library will
uncompress/unzip and write a new file without the suffix, then read from
the uncompressed file. Generally it prefers to place the uncompressed
file in the same directory as the original file. If it does not have
write permission on that directory, it will use thecache directory
thredds mailing list
For list information or to unsubscribe, visit: