[Thread Prev][Thread Next][Index]

Re: bottle data (LAS access to relational databases)


If you put your data into a relational database I don't think it matters much what format is used in the tables.  A command line request of the form:

select ~value~ where x >= ~xlo~ and x <= ~xhi~ and ...

will result in ascii output and that is what our code interprets.

Before you get too involved in creating your database you might have a look at the perl code that will access it.  If you look in las/contrib/insitu/server/custom you will see the following files:


You will want to put these in the appropriate places by typing 'make install' while in 'las/contrib/insitu'.

The TMAPDBI.pm module puts some Ferret friendly functionality on top of basic database access through DBI.  The TMAPDBConfig.pl is used to educate the perl code about specifics of the database schema: names of x, y, z, t variables, missing value flags, etc.  The custom_standalone.pl has four lines where you specify a request and then it uses TMAPDBConfig.pl and TMAPDBI.pm to access the relational database, grab the data and create a netCDF file.

You should start off by creating a tiny database and then using custom_standalone.pl to try and access it.  Once you've got this working you can proceed to populate your database.  And you'll probably want to create keys in your database for x, y and t and sort along one of them after it's been populated.

-- Jon

Tim Racz wrote:


I'm currently putting bottle data into a relational database.  I believe
you said that the data format must be either netCDF or a relational
database.  I'm using mySQL to create the database and I need to know if
the datatypes I use are important.  In other words, when I'm creating
tables in the database, do the columns need to be integers, reals,


*Tim Racz               *
*email: racztr@ornl.gov *
*phone: 828-963-3458    *

[Thread Prev][Thread Next][Index]

Dept of Commerce / NOAA / OAR / PMEL / TMAP
Contact Us | Privacy Policy | Disclaimer | Accessibility Statement