Version 0.29 (14 April 2021)

[kinverarity1]

• Fix lasio changes STEP: adding decimals #404 (lasio changes STEP with imprecise floating-point number behaviour; Apply fmt when writing STEP value #432)
• Add option len_numeric_field=-1, lhs_spacer=" ", and spacer=" " to writer.py:write (see Customize column spacing in the data section #412; PR Add keyword arguments to writer.py:write to accommodate #412 #418)
• Fix Error when LAS data contains text with spaces enclosed in double quotes #271 (Read quoted strings in data section properly; Read quoted strings in data section properly (Fixes #271) #423)
• Fix Incorrect parsing of null values with negative values #427 (Change null_policy to handle small non-zero values; Change null_policy to handle small non-zero values #429)
• Fix Data section not identified if ~Other line immediately precedes ~ASCII line #417 (Fix parsing for empty ~Other section; Fix parsing for empty ~Other section #430)
• Fix Parse unit starting with dot #402 (fixes issue when unit starts with dot; fix issue when unit starts with dot #403)
• Fix Update documentation examples to reflect new HeaderItem repr #395 (Update doc examples to reflect new HeaderItem repr; Update doc examples to reflect new HeaderItem repr #410)
• Fix Have an issue with urllib2 when using the lasio package #426 (Update urllib.request to be the preferred urllib; Update urllib.request to be the preferred urllib #428)
• Add check for pushed tag version to version tests (Add check for pushed tag version to version tests #396)
• Update GitHub Action Python CI testing (Update ci-tests.yml #399, Merge request to gh-ci-changes-1 branch: Change continuous integration to make a lasio wheel #400)
• Improve las_items.py:HeaderItem.__repr__ truncation logic (Improve las_items.py:HeaderItem.__repr__ truncation logic #397)
• Remove codecs import (unused) and fix typo (Remove codecs import (unused) and fix typo #406)
• Exclude LAS files from GitHubs Language Stats (Exclude LAS files from GitHubs Language Stats #411)
• Re-add try-except check around call to reader.read_data_section_iterative() (Re-add try-except check around call to reader.read_data_section_iterative() #401)
• Remove reader.py:read_file_contents - unused code (see Re-add try-except check around call to reader.read_data_section_iterative() #401; Remove reader.py:read_file_contents - unused #393)
• Add test for timestring with colon in ~Well section (see Colons in date formats for STRT/STOP confuse parser #419 - PR Add test for timestring with colon in ~Well section #420)
• Fix SyntaxWarning in writer.py (Fix SyntaxWarning in writer.py #425)
• Add bugfix and feature request issue templates to GitHub repository
• Apply black code style to all Python files (Reformat with 'black .' #438, Improve code style in writer.py #398)
• Update demo notebook for using logging levels with current behaviour
• Update contributing guide (Update contributing.rst #437, Add how to contribute to README.md #441)

---

This discussion was created from the release Version 0.29 (14 April 2021).

[scuervo91]

Hi. Is there a way to create a LASFile Object from a Json String?

Suppose I have a LASFile Object that I want to save on a DataBase with Json. I would export the LASFile with the method to_json and save it, but when querying can I build a LASFile from that json?

Thank you

Santiago Cuervo

[kinverarity1]

Hi, sorry I have been slow in replying! It's not currently possible to do that, but it's a great idea. I will post it as an issue so we can hopefully add it in the future.