Reloading the GMT grid and not selecting spherical coordinates will "trick" it to work the warp, but recognises the dimensions as lat-long. In other words, applying a flat earth model works!
So I guess the question that arises is, how do you do warping (exagerated elevations) on a sphere? Cheers Lester On 25 February 2015 at 22:39, Lester Anderson <[email protected]> wrote: > Hello, > > I rechecked the GMT grids and the Warp by Scalar only seems to work on > some data (if the reference frame is cartesian), but not with > longitude-latitude grids. I checked both the classic GMT netCDF format (cf) > and the new format (nf) and although there is no problem loading the data, > the warp by scalar is greyed out. > > I generated a topo grid from Sandwell & Smith (area = 10/10/-10/10) at 1 > arc minute cell size and it loads as a structured (curvilinear) grid. The Z > values are correct for the bathymetry and topography. In this case, the > surface is curved as expected for a section on the sphere, so maybe that is > why the warp by scalar is not available? > > The file I got to work before was a simple flat surface in cartesian > units. This grid was defined as an image (uniform rectilinear grid) before > the warp was applied. > > Still not sure about this one. > > Lester > > On 25 February 2015 at 19:35, Lester Anderson <[email protected]> > wrote: > >> Thanks Utkarsh, that solved the issue fine :) >> >> Cheers >> Lester >> >> On 25 February 2015 at 14:17, Utkarsh Ayachit < >> [email protected]> wrote: >> >>> Have you tried the "Warp By Scalar" filter? The filter allows you to >>> select the scalar to warp with as well as the normal along which to >>> warp the mesh. >>> >>> Utkarsh >>> >>> On Tue, Feb 24, 2015 at 5:37 AM, Lester Anderson <[email protected]> >>> wrote: >>> > Hello, >>> > >>> > I can see how to load a GMT (netCDF) grid into Paraview but cannot >>> seem to >>> > see how to translate it into an elevation surface. >>> > >>> > The data is a gridded surface of a subducting slab geometry, with X, Y >>> as >>> > longitude and latitude respectively, and Z as the depth range 0 to >>> -700 km. >>> > Here the Z value represents the scalar depth. >>> > >>> > Do I need to pre-process the data prior to loading into Paraview? When >>> > loaded the Z-dimension is 1 so it is still essentially a 2D surface. >>> Loading >>> > point data (eg earthquake solutions) is fine as I can edit the data >>> table, >>> > but not sure what else I need to get a slab surface in correctly: for >>> > plotting the Z-dimension would need to have an extent of 0 to 699 >>> (d=700). >>> > >>> > Be good to know how I can solve this simply. >>> > >>> > Cheers >>> > >>> > Lester >>> > >>> > _______________________________________________ >>> > 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 >>> > >>> >> >> >
_______________________________________________ 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
