Paleoterra Blog
Reading SQL with PySqlite
About a year or so ago, I wrote a special script to run the FOAM climate model. The primary goal of this script, besides running the model, was to store a wide variety of information about the run, including settings, system information (like CPU temperature), and the timing and duration of the run. The storing process stored some of the information before the model starts and after the model ends. It's a great log of my model run and system performance history.
Finishing up DLD 2.0
It's been a long time coming, but I'm finishing up DLD 2.0 for iOS. I hope to submit next week.
What's new? Everything. Depending on whether it gets through the approval process, here's a summary:
Migrating the Devonian Lithological Database to a Fully Relational System: The Story So Far
The Devonian Lithological Database (DLD for short) is a database I published as part of my PhD work at the University of Arizona. As databases go, it was quite primitive but it got the job done. Over the past year or so, I've been migrating the database to a more modern SQL format using SQLite. SQLite is a public domain database designed to work without a server. It is easy to use (for a SQL database) and the data file is generally cross platform.
The migration from the original DLD format to the SQLite format has not been easy. DLD originally consisted of two basic tables: the data records and the source list. The data records were based in Microsoft Excel with 34 columns of information. The reference list was just a Endnote database. Inserting these tables into SQLite is actually quite easy. However, early on, issues made themselves apparent.
A Case for Spatially-Enabled Reference Databases
In my latest video, I try to make the case that spatially-enabled reference databases are very powerful tools. Thus, I show how such a reference database can be used to work with developing geological databases like the Devonian Lithological Database.
Here's the video:
Why should scientific papers be "spatially enabled"
Now that I'm starting to build the databases needed for my new lithological database, I'm coming back to how I created my Devonian database. The papers I generally worked with contained reports from the field, including lithology, measurements, location, etc. That can be a LOT of information. Collecting it all from each paper is time consuming to say the least. Howevever, there was another problem...
