I'm not sure vtkImageData (and everything that uses it) really supports
negative spacing. See, for example, this email thread:
http://www.vtk.org/pipermail/vtkusers/2009-May/100989.html.
I agree. And that's why I have added the function fabs to make positive the
tolerance variable.
I have identified those points which causes problems with the actual
/ParaView3/VTK/IO/vtkNetCDFCOARDSReader.cxx
- if a regular spacing coordinate variable decreases (90 to -90 for
example), you always get a vtkRectilinear grid.
It should reach, wth the computing choice made, to the creation of
I have identified those points which causes problems with the actual
/ParaView3/VTK/IO/vtkNetCDFCOARDSReader.cxx
- if a regular spacing coordinate variable decreases (90 to -90 for
example), you always get a vtkRectilinear grid.
It should reach, wth the computing choice made, to the creation
The netCDF reader in ParaView implements the COARDS convention, which is a
subset of the CF convention. To the best of my knowledge, both conventions
define the spherical coordinates in the same way. So if you have a netCDF file
containing the CF convention for latitude and longitude, then
Moreland, Kenneth a écrit :
The netCDF reader in ParaView implements the COARDS convention, which
is a subset of the CF convention. To the best of my knowledge, both
conventions define the spherical coordinates in the same way. So if
you have a netCDF file containing the CF convention for
