We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are users with a workflow that generates point clouds, which they then serialize to .vtk.
.vtk
They then wish to load the .vtk and convert the xyz points on the mesh back to lons, lats and zlevels.
xyz
lons
lats
zlevels
At present it is possible to achieve this for lons and lats, but not for zlevels.
We require an enhancement to the following functions:
iris.common.to_lonlat
iris.common.to_lonlats
iris.common.from_cartesian
to extend their behaviour to also return the zlevel, if requested i.e., this is an opt-in behaviour.
zlevel
The use case for this enhancement is driven by the ORCA2 Point Cloud example and this GH Discussion request from @berndbecker.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
✨ Feature Request
Motivation
There are users with a workflow that generates point clouds, which they then serialize to
.vtk
.They then wish to load the
.vtk
and convert thexyz
points on the mesh back tolons
,lats
andzlevels
.At present it is possible to achieve this for
lons
andlats
, but not forzlevels
.We require an enhancement to the following functions:
iris.common.to_lonlat
iris.common.to_lonlats
iris.common.from_cartesian
to extend their behaviour to also return the
zlevel
, if requested i.e., this is an opt-in behaviour.The use case for this enhancement is driven by the ORCA2 Point Cloud example and this GH Discussion request from @berndbecker.
The text was updated successfully, but these errors were encountered: