AlexanderJuestel

Results 166 comments of AlexanderJuestel

Issue addressed in https://github.com/cgre-aachen/gemgis/pull/336/commits/8ee959a9b149ddbf67cf9ba6292539eea1b65fdc

This should be fixed in https://github.com/cgre-aachen/gemgis/pull/336/commits/1e9d0d50a8497e85aca4a4e85730932fda601cab

A Pre-Submission inquiry was opened at https://github.com/pyOpenSci/software-submission/issues/126

The Pre-Submission inquiry was accepted and a Submission was made to pyOpenSci at https://github.com/pyOpenSci/software-submission/issues/128

Dear @phasyn8, thanks for mentioning that. In efforts to make GemGIS compatible with the latest versions of GemPy, GeoPandas and NumPy, I will put this on the list of To-Dos

Fixed in https://github.com/cgre-aachen/gemgis/commit/3bd4087c10f831c50c84117103c26ec797c410ed

https://github.com/cgre-aachen/gemgis/commit/c682bb934998476ca45118ab8acd417a738de7ec fixes the issue

I can also reproduce this in pure PyVista. Within the GemPy Viewer Package, the vertical exaggeration is correctly used: ``gempy_vista.p.set_scale(zscale=ve)``

It is at least odd behavior that I am seeing. Also reported that on the pyvista discussions

Yes, I can confirm that the lith_block covers the entire area. If you have the code for the marching cubes at hand, I gladly take it.