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.
Chris, See http://nco.sf.net#help for NCO issues. The -X option behaves well with unstructured grid coordinates formatted in the CF-ish way NCO expects. It is agnostic about UGRID. Please move this thread to the site above if it does not work for you on a UGRID dataset. Charlie On 3/25/19 10:16, Chris Barker wrote:
On Mon, Mar 18, 2019 at 7:18 PM Charlie Zender <zender@xxxxxxx <mailto:zender@xxxxxxx>> wrote:I suggest you store it as Dave Allured says, with dimensions (time, ID). This is often called an "unstructured grid". NCO has no problem subsetting data on unstructured grids, where lon(ID) and lat(ID) are known as auxiliary coordinate variables.Good to know. I just took a look at the NCO docs, and it's not totally clear to me if it will "just work" with a file that conforms to the UGRID standard:http://ugrid-conventions.github.io/ugrid-conventions/ will it? -CHB Just use ncks -X lon_min,lon_max,lat_min,lat_max -X .... It's all in the manual, which has an index that points to examples of using unstructured grids and their proper CF formatting. Charlie-- Charlie Zender, Earth System Sci. & Computer Sci.University of California, Irvine 949-891-2429 )'(
-- Charlie Zender, Earth System Sci. & Computer Sci. University of California, Irvine 949-891-2429 )'(
netcdfgroup archives: