lascheck
Python library for checking conformity of Log ASCII Standard (LAS) files to standards
Derived from lasio
Currently, supports checking against LAS 2.0 standard only
http://www.cwls.org/wp-content/uploads/2014/09/LAS_20_Update_Jan2014.pdf
Simple example
>>> las = lascheck.read('sample.las')
>>> las.check_conformity()
>>> las.get_non_conformities()
The checks present in the package:
The depth value divided by the step value must be a whole number.
The index curve (i.e. first curve) must be depth, time or index.
The only valid mnemonics for the index channel are DEPT, DEPTH, TIME, or INDEX.
Time and date can be included in LAS 2.0 files provided that they are expressed as a number.
"~V" must be the first section.
Embedded blank lines anywhere in the section are forbidden
"~V" is a required section.
"~W" (also known as "WELL INFORMATION SECTION") is a required section.
*"~C" *(also known as ~CURVE INFORMATION SECTION") is a required section.
*"~A" *(also known as ~ASCII LOG DATA") is a required section.
Only one *"~V" *section can occur in an LAS 2.0 file.
~V section must contain the lines: VERS, WRAP.
Only one *"~W" *section can occur in an LAS 2.0 file.
~W section must contain the lines: "STRT", "STOP", "STEP", "NULL", "COMP", "WELL", "FLD", "LOC", "SRVC", "DATE".
Only one *"~C" *section can occur in an LAS 2.0 file.
Only one *"~P" *section can occur in an LAS 2.0 file.
Only one *"~O" *section can occur in an LAS 2.0 file.
The data section ~A is the last section in a file.
The start depth (or time or index) value when divided by the step depth (or time or index) value must be a whole number.
The stop depth (or time or index) value when divided by the step depth (or time or index) value must be a whole number.
If the index is depth, the units must be M (metres), F (feet) or FT (feet).
Metadata
Release files for lascheck 0.1.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| lascheck-0.1.5.tar.gz | 23.4 kB | Without provenance | Details for lascheck-0.1.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| lascheck-0.1.5-py3-none-any.whl | Python 3 | none | any | Details for lascheck-0.1.5-py3-none-any.whl |
Total release size: 46.7 kB
Release files / lascheck-0.1.5.tar.gz
| Download URL | lascheck-0.1.5.tar.gz |
|---|---|
| Size | 23.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8868273238269d5d64b7b8ad94ea445261aa0ef2f4c663632b1d89d318b9841e
|
|
BLAKE2b-256 checksum How to use checksums |
76a2a9ffb4e83bf02c2b8aa146ef3077b57c1c8c5d61ff4af2a65f80ccc4409c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.5
|
Release files / lascheck-0.1.5-py3-none-any.whl
| Download URL | lascheck-0.1.5-py3-none-any.whl |
|---|---|
| Size | 23.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
833a5eb0f7d9fdf8f56115fb4eec7f9d6a7dc1148f49a942a1dca65a06e5d16f
|
|
BLAKE2b-256 checksum How to use checksums |
d341dbfcde8768e51ccd76dca304c56ccebb58f892f300c6cc8e74a733d72a1b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.10.5
|
Security for lascheck 0.1.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.