Multi_obs table include the few extra columns(prefixed 'd_' like 'd_top_of_hour' for 'display') used for display purposes.

Note that for the below sql, some of the row_id's have been hard-coded for expediency, they should be inspected if used for a new xenia setup since the row_id's will probably be different.

Initial setup for organization, platform type, sensor type
sql file

Note that for ADCP, the sensor_type's are regular, surface, bottom and depth-average. The same bin may be listed under two sensor_id's, once as a regular bin and another as a surface bin. The bin order follows the NDBC convention of listing bins in order from shallowest to deepest, so the first bin is considered the surface bin and last bin the bottom bin. The sensor.s_order field is used to distinguish the order of the bins from 1 to n for the 'regular' bin listing. The depth-average bin has no associated depth and this is represented as missing value(-99999) for multi_obs.m_z

Initial setup for platform,sensor_id's for a few NDBC adcp platforms - other NDBC ADCP platforms would be added similarly as available
sql file

Perl script using the above setup to add observations to the multi_obs table via creation of an sql file to run against the xenia_v2 instance. Note you'll need to inspect the 'Environment' settings at the top of the file for filepaths, database and xenia row_id's to make sure they are set as needed
perl file

-- JeremyCothran - 10 Jan 2007
to top