lasio icon indicating copy to clipboard operation
lasio copied to clipboard

Ensure that anything lasio can read, welly can read

Open kinverarity1 opened this issue 3 years ago • 0 comments

Is your feature request related to a problem? Please describe. Many users will never use lasio directly, but will instead use it via functions like welly.Well.from_las. I want to explore whether (and ideally make sure that) welly is capable, wherever possible, of loading data from LAS files that lasio can already load.

Describe the solution you'd like It could take a different form, but one idea is to take large archives of LAS files - compiling a list of any such easily-available archives could be a useful side-product - and attempt to parse the LAS files using (1) welly and (2) lasio, to see what happens. We can then look at fixing any bugs that we find, if worthwhile.

Describe alternatives you've considered

Additional context The repository https://github.com/agile-geoscience/LASinfections could be a useful starting place.

kinverarity1 avatar Apr 16 '21 05:04 kinverarity1