I have a geotiff file that I want to view in Paraview. But, Paraview seems to not show the correct offset (0,0 instead of respected the offset). The work around I have been trying is to warp it to the correct location using gdalwarp and to export it as a netCDF. Then Paraview should be able to show it correctly. But, I have run into a crash. If I do this: gdalwarp -t_srs EPSG:3652 -of netCDF test.tiff test_ft.nc
then I try to open test.nc in Paraview immediately crashes. While, instead if do this: gdalwarp -t_srs EPSG:3651 -of netCDF test.tiff test_m.nc then it opens fine. The difference between these two files is that EPSG 3652 uses feet (which is better for me, for this particular project) while 3651 uses meters. Both appear to be valid NetCDF files. I’ve tried both readers “CAM NetCDF (Unstructured)” and “NetCDF files generic and CF conventions” with the same results. I’m running Paraview 5.2.0 64-bit on Mac OS 10.12.3. But, I have seen identical results on an older Mac with a prior OS. I had also tried an older version of Paraview with the same result. Any ideas why this consistently crashes Paraview, or what to do about it? Using netCDF was already a work around, and I willing to try others to view these files. The offset and scale are important because I then need to put in other data that is in the correct location and units. The files are too big for me to send to the mailing list, so I have not posted them. Thanks, -- Adam
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView Search the list archives at: http://markmail.org/search/?q=ParaView Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/paraview
