[Paraview] Reading netCDF files Earth models

[Manochehr Bahavar]

Ken,

Your comments helped me a lot to see the issue and I appreciate you raising a bug on this.

Thanks again for your prompt replies.

Best,

—manoch



> On Jan 18, 2018, at 6:32 AM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> 
> Manochehr,
> 
> ParaView always renders in a Cartesian space. So if you want the lat/lon/depth values to look like a sphere, the coordinates have to be converted and you will loose the original values. I can see the point of your use case. It just never came up before. It seems reasonable to be able to save the original lat/lon values in a field, so I raised a bug for it.
> 
> https://gitlab.kitware.com/paraview/paraview/issues/17943 <https://gitlab.kitware.com/paraview/paraview/issues/17943>
> 
> As far as getting the coordinates in a script, it is possible but not recommended. If you need to access field or coordinate values directly, it is usually best to do so in a programmable filter.
> 
> -Ken
> 
> Sent from my iPad
> 
> On Jan 18, 2018, at 7:06 AM, Manochehr Bahavar <manoch at iris.washington.edu <mailto:manoch at iris.washington.edu>> wrote:
> 
>> Hi Aashish,
>> 
>> Thank you for your reply. That will be great if it gets looked into:) Going back and forth between coordinate systems may be a little confusing, but I will give it a try and see how it works out.
>> 
>> 
>> Could you also point me in the right direction for getting the latitude, longitude and depth arrays? As I mentioned in my reply to Ken (below), using Python, I go as far as getting the extents and bounds but cannot get the actual values.
>> 
>> Thank you again for your quick reply and useful suggestions.
>> 
>> Best,
>> 
>> —manoch
>> 
>> 
>> 
>>> On Jan 17, 2018, at 10:29 PM, Aashish Chaudhary <aashish.chaudhary at kitware.com <mailto:aashish.chaudhary at kitware.com>> wrote:
>>> 
>>> Hi Manoch, 
>>> 
>>> I think what you want is not possible right now but let us get back to you on it as something we might want to look into before we can say it for sure. One workaround would be you load the data (uncheck the sphere coordinate system), apply the filter, and then write the data back as NetCDF. It is not ideal by any means. You can also look into vtkSphericalTransform (if you want to convert data back to spherical coordinate system) but you will not get the exact shape of earth which is a ellipsoid (which I am not sure if you would be interested in anyways). 
>>> 
>>> Hope this helps. 
>>> 
>>> On Wed, Jan 17, 2018 at 7:12 PM Manochehr Bahavar <manoch at iris.washington.edu <mailto:manoch at iris.washington.edu>> wrote:
>>> Ken,
>>> 
>>> Thanks for your reply. The problem with that approach is that all the features I am interested in make sense if they are plotted on a sphere (they approximate the Earth surface). So, there is no builtin solution for that?
>>> 
>>> One more question: How can I access the actual latitude, longitude and depth parameter values using Python. I can see their extent and bounds, but I can not see how I can access the individual values:
>>> 
>>> temp.GetBounds()
>>> (0.0, 359.0, -89.0, 89.0, -2750.0, 50.0)
>>> temp.GetDimensions()
>>> (360, 179, 57)
>>> temp.GetExtent()
>>> (0, 359, 0, 178, 0, 56)
>>> temp.GetCenter()
>>> (179.5, 0.0, -1350.0)
>>> temp.GetNumberOfPoints()
>>> 3673080L
>>> 
>>> Really appreciate your help
>>> 
>>> —manoch
>>> 
>>> 
>>>> On Jan 17, 2018, at 3:57 PM, Moreland, Kenneth <kmorel at sandia.gov <mailto:kmorel at sandia.gov>> wrote:
>>>> 
>>>> Manochehr,
>>>> 
>>>> If you uncheck the “Spherical Coordiantes” option, then the longitude, latitude, and depth values will be preserved as x, y, and z coordinates. (Instead of translated to a sphere, the data will appear in a rectangle.)
>>>> 
>>>> -Ken
>>>> 
>>>> 
>>>> On 1/17/18, 4:34 PM, "ParaView on behalf of Manochehr Bahavar" <paraview-bounces at paraview.org <mailto:paraview-bounces at paraview.org> on behalf of manoch at iris.washington.edu <mailto:manoch at iris.washington.edu>> wrote:
>>>> 
>>>>    Hello,
>>>> 
>>>>    I am trying to see if I can visualize my netCDF Earth models (longitude, latitude,depth) using ParaView. I have been able to load the models, with the "Spherical Coordinates" option selected. However it appears that I now lose my coordinates and depth values and as a result to extract a subset, I have to use the depth index (not the actual depth value). Is there a way to preserve the latitude, longitude and depth values and work with ParaView using the actual values (not their index) directly?
>>>> 
>>>>    Thank you,
>>>> 
>>>>    —manoch
>>>>    _______________________________________________
>>>>    Powered by www.kitware.com <http://www.kitware.com/>
>>>> 
>>>>    Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>>> 
>>>>    Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>>> 
>>>>    Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>>> 
>>>>    Follow this link to subscribe/unsubscribe:
>>>>    https://paraview.org/mailman/listinfo/paraview <https://paraview.org/mailman/listinfo/paraview>
>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> Powered by www.kitware.com <http://www.kitware.com/>
>>> 
>>> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html <http://www.kitware.com/opensource/opensource.html>
>>> 
>>> Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView <http://paraview.org/Wiki/ParaView>
>>> 
>>> Search the list archives at: http://markmail.org/search/?q=ParaView <http://markmail.org/search/?q=ParaView>
>>> 
>>> Follow this link to subscribe/unsubscribe:
>>> https://paraview.org/mailman/listinfo/paraview <https://paraview.org/mailman/listinfo/paraview>
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://paraview.org/pipermail/paraview/attachments/20180118/edd0ff73/attachment.html>