EvanBianco
commented
8 years ago @mlaloux, Fair request. I'll work at composing an example with shareable data. Indeed, this project was and still very much is a fit for purpose tool for visualizing a multitude of surface and subsurface data along arbitrarily polylines (shapefile transects). The concept of the visualizations is to produce Atlas-like sheets aggregating a variety of information.
In case we haven't mentioned it specifically in the documentation, Geotransect intends to consume:
- Shapefiles (bed rock geology)
- Raster data (digital elevation models, potential field data)
- Petrophysical and well data (Petrophysical names require a very strict configuration and naming in the current implementation)
- seismic data (2d or 3d)
- seismic interpretation elements (horizons, faults, etc).
- well tops, markers, labels, etc.
The current view, shown here, features a title and header block, a basemap, a transect, and a single "feature plot" showing a full-petrophysical composite for a single well (defined in the config.yaml file). We don't support additional views at the moment; 2 or more petrophysical plots side-by-side side.
Please be advised Geotransect isn't suitable for Python 3 at the moment. Check out the develop branch for a list of python_requirements.txt, and conda_requirements.txt for the specific packages we've been able to get this running on. There is a hefty amount of dependencies, (perhaps too many!) and this tool is likely some distance away from public consumption, so please bear with us.
Interested to hear of your use case(s), and the data formats / outputs that you'd like Geotransect to serve.
Hello, is it possible to have all the example files used in the notebooks ("Dropbox", "Dropbox/Agile/", ...) to learn and understand all the aspects of the module ?
Many thanks