Hello Paul and Paraview,
Thanks for the reply - resending this without the pics (forgot the 500kb limit!). The data have been projected into spherical coordinates from the original Long/Lat, so X,Y and Z are in kilometers. Not sure if this helps to clarify or not. I am working with seismic tomography data. The original Lat, Long, radius, anomaly matrix was loaded as a CSV file and then projected into a sphere: (coordsZ*cos(coordsX*3.14159265/180)*cos(coordsY*3.14159265/180))*iHat+(coordsZ*sin(coordsX*3.14159265/180)*cos(coordsY*3.14159265/180))*jHat+(coordsZ*sin(coordsY*3.14159265/180))*kHat Loading up a coastline file helps to fix ones position and can use that as a reference for slicing but it is not perfect and needs a lot of tweaking to get the profile right. Looking at the numbers it appears to be radians so one can do the inverse calculation. I now think I have resolved the issue as the values for the normal can be defined as radians and so feeding in the converted value (angle_in_degrees x pi/180) works - tested for 30 degree slices. Attached some screen caps to show the workings - hopefully I have got it sorted. Perhaps it would be useful to have Paraview automatically indicate that the normal values are in Radians (following a degree to Radians conversion in the calculator filter) to avoid confusion. Regards 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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview
