<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Rupert,</p>
<p>I can't help you with netcdf files/formats. However, the
following two items could be of help.</p>
<p>(1) ParaView has a Transform filter that will translate and/or
scale and/or rotate your datum set.</p>
<p>(2) In the coordinate 3-tuple (x,y,z). if all of your z-values
are zero, then PV will "come up in a "2D" mode. There is a 2D/3D
toggle button (button number 3) in the upper left location in each
display frame that may be of help to you.</p>
<p>Samuel Key</p>
<p>FMA Development.<br>
</p>
<br>
<div class="moz-cite-prefix">On 5/15/2017 1:37 AM, Rupert Gladstone
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CACvTYE7wGhHiQUJ+hzkP4B99NV+fcuyJoSUMcP0-eaGoLruQ3A@mail.gmail.com">
<div dir="ltr">
<div>
<div>
<div><br>
</div>
Hi, I have a question about netcdf formats. I am developing
a coupled ice sheet - ocean model. Currently both models
run in the same cartesian coordinate system. The ice model
outputs unstructured .vtu files, which paraview reads just
fine. The ocean model outputs structured netcdf files. If
I naively select the "generic and CF conventions" option
when reading the ocean netcdf file then the data display ok,
but not to scale. It seems like the structured fields have
been read in just fine, but the coordinate variables have
not. I don't think the netcdf files are CF compliant. I
would like to be able to read in both .vtu files and netcdf
files and display the data sets together on the same scale.<br>
<br>
Do you know what I need to do to read in the netcdf
coordinate vars correctly? I am hoping that I can simply
insert a post-processing step to implement some minor
manipulation to the ocean model output files so that
Paraview can read them in to scale. Is it simply a case of
renaming the coordinate variables in the netcdf file such
that they have the same names as the corresponding
dimensions? Note that this is not in general possible as
some of the coordinate variables are two-dimensional
variables (in the horizontal plane), though for most of the
simulations we plan in the near future I can enforce that
the coord vars will have a one to one correspondence to the
dimension vars (i.e. I can enforce that coord vars are 1D).<br>
<br>
Is the ordering of dimensions important?<br>
Is the ordering of coordinate vars important?<br>
Is the naming of dimensions important?<br>
Is the naming of coord vars important?<br>
Can Paraview cope with 2D coord vars? If so, how does
Paraview know which coordinate var applies to which var?<br>
<br>
</div>
Thanks very much for your help.<br>
<br>
</div>
Regards,<br>
Rupert Gladstone<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a>
Visit other Kitware open-source projects at <a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a>
Please keep messages on-topic and check the ParaView Wiki at: <a class="moz-txt-link-freetext" href="http://paraview.org/Wiki/ParaView">http://paraview.org/Wiki/ParaView</a>
Search the list archives at: <a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=ParaView">http://markmail.org/search/?q=ParaView</a>
Follow this link to subscribe/unsubscribe:
<a class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview">http://public.kitware.com/mailman/listinfo/paraview</a>
</pre>
</blockquote>
<br>
</body>
</html>