Jiggle Views

Name Columns
JASI_AMPPARMS_VIEW net,sta,seedchan,,location,,ondate,offdate,maxamp,clip
JASI_CHANNEL_VIEW net,sta,seedchan,channel,channelsrc,location,lat,lon,elev,edepth,azimuth,dip,samprate,ondate,offdate
JASI_CONFIG_VIEW name,progid,net,sta,seedchan,location,config,ondate,offdate
JASI_RESPONSE_VIEW net,sta,seedchan,channel,channelsrc,location,natural_frequency,damping_constant,
gain,gain_units,low_freq_corner,high_freq_corner,ondate,offdate
JASI_STATION_VIEW net,sta,lat,lon,elev,staname,ondate,offdate
ML_MAGPARMS_VIEW net,sta,seedchan,channel,channelsrc,location,ondate,offdate,corr,corr_type,corr_flag,auth,clip
MD_MAGPARMS_VIEW net,sta,seedchan,channel,channelsrc,location,ondate,offdate,corr,corr_type,corr_flag,auth,clip
cutoff,gain_corr,summary_wt

These are the "minimalist" set of columns required, order not important, but the code assumes column datatypes and constraints are the same as those already defined for "channel_data" like tables in the NCEDC schema. These views as defined by the DBA could differ between database instances. The DBA should grant the appropriate permissions and create synonyms for the views to be visible to other accounts.


To jiggle installation