You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When there are lots of curves (e.g. a file containing image/sonic (generally 2D) data), the curve mnemonics can be difficult to browse or discover. For example, see test_utah_well.las.txt
(sourced from https://gdr.openei.org/submissions/1076). There are more than a thousand lines in the ~Curves section. I've clipped most of these out with "...":
Describe the solution you'd like
The repr() methods for las.curves should exploit the fact that the mnemonics for FRACTURE_APERTURE and InfoArray already have an index indicated in their mnemonic e.g. [0], and so on, and show only their range. Otherwise there is essentially no way to see the curves at the end of the above list unless you deliberately write code to identify them, or you look at the file in a text editor.
We have already written some code for users to do this manually with LASFile.stack_curves (see #293 and #284). That could possibly be extended or used in some way for this feature request.
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When there are lots of curves (e.g. a file containing image/sonic (generally 2D) data), the curve mnemonics can be difficult to browse or discover. For example, see test_utah_well.las.txt
(sourced from https://gdr.openei.org/submissions/1076). There are more than a thousand lines in the ~Curves section. I've clipped most of these out with "...":
Describe the solution you'd like
The
repr()
methods forlas.curves
should exploit the fact that the mnemonics forFRACTURE_APERTURE
andInfoArray
already have an index indicated in their mnemonic e.g.[0]
, and so on, and show only their range. Otherwise there is essentially no way to see the curves at the end of the above list unless you deliberately write code to identify them, or you look at the file in a text editor.We have already written some code for users to do this manually with
LASFile.stack_curves
(see #293 and #284). That could possibly be extended or used in some way for this feature request.Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: