NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Thanks, Jonathan! We had intended to produce a regular grid but I see now on close inspection that latitude spacing varies between ~0.0368 and 0.0352 deg. We'll even these out and report back... Cheers, John Maurer PacIOOS On Thu, Apr 19, 2012 at 7:24 AM, John Caron <caron@xxxxxxxxxxxxxxxx> wrote: > Yes, of course. The lat coordinate is irregular. > > its lame that WCS only allows regular spacing. I think thats fixed in WCS > 2.1 (?) > > thanks for seeing that, Jonathan! > > > On 4/19/2012 9:27 AM, Jonathan Wilkins wrote: > > Hi, > > I think the problem is that latitude values are not regularly spaced as > specified > by http://www.unidata.ucar.edu/projects/THREDDS/tech/reference/WCS.html > > I faced the same problem and after regridding my dataset, it was available > through WCS. > > Regards > > Jonathan Wilkins > > > Le 11/04/2012 17:07, John Caron a écrit : > > Hi John: > > Nothing obviously wrong here. > > Can you look and see if theres any messages in the logs. Probably it would > be in models.log and/or featureCollectionScan.log. You can just send me the > whole thing if you want. > > John > > On 4/11/2012 5:26 AM, John Maurer wrote: > > P.S. To make sure, I checked that my files are CF compliant at > http://puma.nerc.ac.uk/cgi-bin/cf-checker.pl and all looks good. After > trying several more things, I still cannot see what is wrong. Seems strange > that all other services besides WCS would work (including WMS, NCSS, > OPeNDAP, ISO, NcML). Perhaps a bug in the FMRC-to-WCS side of things? > Though I don't see what's tripping it up since I have other FMRC's whose > WCS works fine. Note that some variables are 3-D (surface elevation) while > others are 4-D (temperature, salinity, u/v velocities). Anyways, hoping > somebody can eventually give this a look. I realize Unidata's swamped with > 4.3 right now, so maybe after that sometime... > Thanks!, > John Maurer > > On Thu, Apr 5, 2012 at 12:04 AM, John Maurer <jmaurer@xxxxxxxxxx> wrote: > >> Hi everyone, >> I'm stumped: any ideas why the following regular gridded FMRC dataset >> produces an empty WCS capabilities document (no variables/coverages get >> listed; ContentMetadata section is entirely missing)?: >> >> >> http://oos.soest.hawaii.edu/thredds/catalog/hioos/roms_forec_regridded/hiig/catalog.html >> >> In particular, I'm looking at the Best Time Series at: >> >> >> http://oos.soest.hawaii.edu/thredds/catalog/hioos/roms_forec_regridded/hiig/catalog.html?dataset=roms_hiig_forecast_regridded/ROMS_Hawaii_Regional_Ocean_Model_Regridded_best.ncd >> >> Whose WCS URL is this: >> >> >> http://oos.soest.hawaii.edu/thredds/wcs/hioos/roms_forec_regridded/hiig/ROMS_Hawaii_Regional_Ocean_Model_Regridded_best.ncd?service=WCS&version=1.0.0&request=GetCapabilities >> >> The other services all work fine, including OPeNDAP, NCSS, WMS, ISO, and >> NcML. >> >> Although the original ROMS ocean forecast model was on a curvilinear grid >> (which WCS cannot handle), we've regridded onto a regular grid. One >> positive outcome of this was that I should be able to turn on WCS for it >> now (so that people can download GeoTIFFs); however, I'm not having any >> luck yet. The logs are not showing anything useful. threddsServlet.log just >> shows this: >> >> 2012-04-04T23:19:53.210 -1000 [ 847655][ 643] INFO - >> thredds.server.wcs.WCSServlet - Remote host: 128.171.151.240 - Request: >> "GET >> /thredds/wcs/hioos/roms_forec_regridded/hiig/ROMS_Hawaii_Regional_Ocean_Model_Regridded_best.ncd?service=WCS&version=1.0.0&request=GetCapabilities >> HTTP/1.1" >> 2012-04-04T23:19:53.214 -1000 [ 847659][ 643] INFO - >> thredds.server.wcs.v1_0_0_1.WcsHandler - Request Completed - 200 - -1 - 4 >> >> I have other regular gridded FMRC's whose WCS works fine; one example >> (NCOM): >> >> >> http://oos.soest.hawaii.edu/thredds/catalog/pacioos/ncom/hawaii/catalog.html >> >> http://oos.soest.hawaii.edu/thredds/catalog/pacioos/ncom/hawaii/catalog.html?dataset=ncom_hawaii/NCOM_Hawaii_Regional_Ocean_Model_best.ncd >> >> http://oos.soest.hawaii.edu/thredds/wcs/pacioos/ncom/hawaii/NCOM_Hawaii_Regional_Ocean_Model_best.ncd?service=WCS&version=1.0.0&request=GetCapabilities >> >> In case it helps, I've placed my catalog file and one of the data files >> (174 MB) on anonymous FTP: >> >> ftp ftp.soest.hawaii.edu >> cd jmaurer >> get ocn_mod_hiig.xml >> get hiig_forec_gridded_20120402.nc >> >> Thanks for your help on this!, >> John Maurer >> Pacific Islands Ocean Observing System (PacIOOS) >> University of Hawaii at Manoa >> > > > > _______________________________________________ > thredds mailing listthredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ > > > > _______________________________________________ > thredds mailing listthredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ > > > > _______________________________________________ > thredds mailing list > thredds@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ > >
thredds archives: