Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
punkish>> A typical search would be to retrieve all the values 
punkish>> of  for  or <for a set of points> 
punkish>> <for a particular year+yday combination>.

dws> If those are the typical search patterns,
Those are typical search patterns. There are a few other search patterns as well, so I have to find a format that can accommodate *all* of them.

dws> is a relational database the right hammer to reach for? 
Dunno. Hence this thread.
dws> Why not flat files?
Well, the data are already in some kind of flat files. Actually, they are in files, but not flat files. They are in NetCDF format. The format is very compact, and very suitable for storing array of arrays, however, it is not very amenable to spatial searches. Hence, my desire to put the data in a database.

As shown in my original post, the db table is very simple, almost like a flat file (with a little overhead per "line" added by the db). However, it allows me to JOIN this simple table with a location table. I can do a spatial search on the location table, retrieve the value of points that fall within my search, and then retrieve the variables from this simple but mongo table.

--

when small people start casting long shadows, it is time to go to bed

In reply to Re^2: Strategy for managing a very large database with Perl by punkish
in thread Strategy for managing a very large database with Perl by punkish

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (3)
As of 2024-04-25 14:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found