Hi all We've got a bunch of netcdf files that we are trying to read with geotools following the instructions here: http://docs.geotools.org/latest/userguide/library/coverage/multidim.html
Most of the files cause an exception in the NetCDFReader constructor (java.lang.IllegalStateException: Unable to create envelope for this dataset). We have tracked this down to the netCDF files using a rotated grid instead of a cartesian grid. The upshot of this is that the files define lat/lon as a secondary lookup (2-d) instead of as a linear (1-d) variable. However NetCDFGeoreferenceManager reports these as "unsupported axes", with the result being that NetCDFReader finds no lat/lon axis and throws the above exception. I'm assuming that this is by design but wondered if am I missing something obvious? Assuming that I am not, the methodology of creating a rotated grid appears to conform to the CF-convention specs and we have examples of these files from at least two different software origins - all of which implies that they are being created correctly to spec. Bearing this in mind is there any interest if we were to extend gt-netcdf to handle these files? And/or is there a good reason why we shouldn't try to do this that anyone knows of? Thanks :) Iain -- Sent from my ZX80 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ GeoTools-GT2-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
