Once upon a time (2014-2015) I served on the Canadian Well Logging Society's (CWLS) executive committee as the Committee/Website Chair. The CWLS is a non-profit professional organisation in the Oil & Gas industry and the executive committee consists of elected volunteers.
I volunteered for the position of Website Chair because of family/friend connections (members) to the organisation and also because their website was 'Under Construction' for quite a long time. I wanted to see if I could help advise and/or participate in getting it back online. To make a long story short, I was able to help but it was a slow process... but I digress, back to the CWLS LAS file format.
The CWLS committee was responsible for spear-heading an industry wide effort to standardise the format of oil well logging digital data. This format is known as the Log ASCII Standard or LAS for short. It was created back when XML was becoming popular but felt to be too verbose and the INI format too limiting. JSON was not developed at that time, to my knowledge. I am not sure what else the CWLS committee considered back then.
One of the questions that periodically comes up is that of open source libraries for the LAS specification. Here is a recent reply (names removed for privacy) I penned on this topic.
I have cc'd the current CWLS exec website chair for reference. I was on the CWLS exec committee a few years ago and am a software developer so have an interest in your question and hope I can provide some assistance on what I have found.
To first answer your question directly, the practice has been for you to develop your own readers as the CWLS committee is a volunteer organisation and does not have the resources to develop or maintain software libraries. The LasApps free software available on the site is there because of a member's generosity and interest in the CWLS specification.
Having said that, there still appear to be some independent efforts (ie. not connected with the CWLS committee) to create open source readers/libraries for the LAS file format. Re-doing my search from a few years ago turns up:
Python - https://lasio.readthedocs.io/en/latest/index.html
Ruby - https://github.com/gpcarmo/cwls-las-reader
For Java the question on stackoverflow:
Just points to the commercial Petroware library:
I have not run across anything else significant for other languages, but perhaps was not looking hard enough.
Which programming language(s) are you interested in?
Personally, I ended up writing my own reader in Java because at that time I could not find any reasonable open source Java libraries and naively thought 'how hard can it be?' ... as you may already know, since the LAS format is text based, the challenge becomes handling files which are close to the spec but not quite - does one fail or fix/absorb the issue. I continue to enhance my reader to handle the edge cases as I encounter them :-).
I wrote my reader to handle version 3.0 files but in practice mostly run across LAS version 2.0. Another local Calgary company who's product handles LAS files has echoed the same.
If you would like to chat more, feel free to call or email.
Hope this helps you decide on your approach.
Well it's officially in the books and GeoConvention 2019 is done. Thanks to Dustin Menger and the GeoConvention committee for accommodating my 11th hour addition!
The reason I was in the 11th hour was that I was not sure I was going to have a 'ready for distribution' version of EESi LAS Viewer by the convention exhibitor deadlines. Client projects in the past few months took precedence over final touches and quickly the time was squeezed. Since I am the sole owner and operator of this endeavor, all activities are sequential in nature - marketing does not happen in parallel with development. Yes you can round-robin it but it's still one step at a time (just like hiking up a mountain).
As a developer I usually don't spend too much time thinking like a marketing professional so am quite naive about what goes into that job. This was my very first experience as an exhibitor at a convention and having to go through the process of pulling together an exhibit in such a short time frame certainly gives me much more appreciation for those who do it daily/weekly/monthly.
Although that helped me get through the setup and opening day, I'm certain the impact was on connecting with my potential audience - so thanks to those people who were able to see through my low-tech marketing, stop, say hi and ask about the viewer.
I enjoyed meeting you and hope this product helps you. Please reach out if you have questions, comments or suggestions. If you picked up a feature sheet, note the coupon code for a discount at checkout - if you missed picking up a feature sheet then send me an email at email@example.com.
If you are reading this and were not a convention attendee then also feel free to send me an email - but to get the coupon code you'll have to tell me what you are up to (i.e. how will the viewer help you), just like you would have done had you visited me at the booth ;-)
In summary, I would say my learning and recommendation would be to try to avoid low-tech marketing if at all possible, get help if you can (I now have business cards of companies that specialise in this ;-), but don't be afraid to exercise the low-tech marketing option as a last resort.
Well, it was only a matter of time until I had a good reason to figure out how to change the background colour on Weebly's blogs to fix the white text on white background issue.
Turns out it's not that hard but it is hidden a little.
Also because it's hidden you may need to keep an eye on it should Weebly change how it works or if you change your theme.... but here's what to look for:
Hope you found this useful.