Manage subsurface well data.
.. image:: https://img.shields.io/travis/agile-geoscience/welly.svg :target: https://travis-ci.org/agile-geoscience/welly :alt: Travis build status
.. image:: https://readthedocs.org/projects/welly/badge/?version=latest :target: https://welly.readthedocs.io/en/latest/?badge=latest :alt: Documentation Status
Welly is a family of classes to facilitate the loading, processing, and analysis of subsurface wells and well data, such as striplogs, formation tops, well log curves, and synthetic seismograms.
.. code-block:: shell
pip install welly
.. code-block:: python
from welly import Well, Project w = Well.from_las('my_wells/my_well.las') # Load a single well. p = Project.from_las('my_wells/*.las') # Load lots of wells. gr = w.data['GR'] # One log; this is a subclassed NumPy array... gr.plot() # ...with some superpowers!
Next, check out the
tutorial </tutorial>_ notebooks.
lasio <https://github.com/kinverarity1/lasio> project provides a very nice way to read and
CWLS <http://www.cwls.org/> Log ASCII Standard files. The result is an object, based on
OrderedDict, that contains all the LAS data — it's more or less analogous to the LAS file.
Sometimes we want a higher-level object, for example to contain methods that have nothing to do
with LAS files. We may want to handle other well data, such as deviation surveys, tops (aka picks),
engineering data, striplogs, synthetics, and so on. This is where
welly comes in.
lasio for data I/O, but hides much of it from the user. We recommend you look at
both projects before deciding if you need the 'well-level' functionality that
We welcome contributions! Please fork the project and submit pull requests, or get in touch with us