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.
Hi, Have found archive postings on this matter which have highlighted the relationship between the elements <start>, <size> and <resolution>, i.e. <start> represents the southern/western edge, <start> + <size> represents the northen/eastern edge and <resolution> simply reports the spacing between points. Had got it into my head that <start> represented the southern/western edge and that <start> + (<size> * <resolution>) represented the northern/eastern edge. Having reread the doc. and checked the examples it now seems all so clear, especially as the example gives a <northsouth> <start> value of 10, a <size> value of 80, a <resolution> value of 2, a <eastwest> <start> value of -130, a <size> value of 260 and a <resolution> value of 2 which would have given me a latitude range of 10-170 degrees North and a longtitude range of -130-390 degrees East. Regards, Glenn ------------------------------ Message: 2 Date: Thu, 30 Jun 2011 17:50:40 +0100 From: "Comiskey, Glenn" <g.comiskey@xxxxxxxx> To: <thredds@xxxxxxxxxxxxxxxx> Subject: [thredds] THREDDS Catalog - geospatialCoverage Message-ID: <BBFDF85BF71AD64FAC2CB716502BA1513F21A1@xxxxxxxxxxxxxxxxxxxxx> Content-Type: text/plain; charset="us-ascii" Hi, I have a GRIB-1 file with geospatial coverage of -60 to -30 degrees East with a resolution of 1.25 degrees, i.e. 25 points of longitude. However, to get the correct values to display when viewing the dataset through THREDDS v4.2.7 I have to enter geospatial coverage values "<eastwest><start>-60</start><size>30</size><resolution>1.25</resolution ></eastwest>" as the server does not appear to recognize the resolution value correctly, i.e. it appear to read it as <resolution>1</resolution>. Note: I have not problem with the latitude values "<northsouth><start>10</start><size>40</size><resolution>1.0</resolution ></northsouth>". Anyone else encountered this? Kind regards, Glenn Comiskey Data System Administrator
thredds
archives: