<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
<br>Hello Paul and Paraview,<br><br>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.<br><br>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:<br><br>(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<br><br>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.<br><br>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.<br>Attached some screen caps to show the workings - hopefully I have got it sorted.<br><br>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.<br><br>Regards<br><br>Lester </div></body>
</html>