Table topp.public.tblsgprocessingstatus
This table contains data for tracking the status of recovered and/or popup tag data. Typically joins will be made to the sgdkey field. The most common fields used to filter queries are geolocated, ssm_complete, date_last_depth, date_last_etemp, date_last_itemp, date_last_light, no_pdt, no_tad, and no_tat. All of the yes/no fields use 1 and 0 as their values and should be changed from type text to integer. All date fields should be converted from type text to date or timestamp.

 Generated by
SchemaSpy
Legend: SourceForge.net
Primary key columns
Columns with indexes
Implied relationships
Excluded column relationships
< n > number of related tables
 
Column Type Size Nulls Auto Default Children Parents Comments
sgdkey serial 10  √  nextval('tblsgprocessingstatus_sgdkey_seq'::regclass) This field should be called eventid. It is the same as the eventid field in all other tables.
tagnum text 2147483647  √  'unknown'::text Manufacturer serial number of tag.
downloadedby text 2147483647  √  null If the tag was recovered, who downloaded the data.
download_date text 2147483647  √  null The date the tag was downloaded.
timezone_correction text 2147483647  √  null Time correction applied to UTC time series data when running CleanFirst.
depthcorrection_eq text 2147483647  √  null The equation applied to times series data for depth correction. Generally run on time corrected data.
date_last_light text 2147483647  √  null The last date of good time series light data if there was sensor or battery failure.
date_last_itemp text 2147483647  √  null The last date of good time series internal temperature data if there was sensor or battery failure.
date_last_etemp text 2147483647  √  null The last date of good time series external temperature data if there was sensor or battery failure.
date_last_depth text 2147483647  √  null The last date of good time series depth data if there was sensor or battery failure.
findlats_params text 2147483647  √  null No longer used. Generally the longitude and latitude movement values, the search size and surface depth parameters from the official lab findlats output for the tag. These values need to be tracked somehow.
geolocated text 2147483647  √  '0'::text Has the data been run through findlats and a final/official version accepted? Yes = 1 and no = 0, and will not be = 2.
comments text 2147483647  √  null General comments.
findlats_outfile text 2147483647  √  null The name of the final/official findlats output file.
gf_file text 2147483647  √  null No longer used. A reformatted version of the findlats output file. Candidate for deprecation.
pat_lon_cnt int4 10  √  null How many light level longitudes did the tag produce within the deployment period?
ssm_complete text 2147483647  √  '0'::text Has a Block lab SSM output been generated for this tag? Yes = 1 and no = 0, and will not be = 2.
hawaii_track text 2147483647  √  '0'::text Applies to white sharks. Did the animal go to Hawaii?
cafe_track text 2147483647  √  '0'::text Applies to white sharks. Did the animal go to the Cafe?
hawaii_ac text 2147483647  √  '0'::text Was the animal detected by acoustic receivers in Hawaii?
fidelity text 2147483647  √  '0'::text Does the track show fidelity to the deployment location?
fidelity_dates text 2147483647  √  null If the track showed fidelity to the deployment location what were the dates of the return?
tag_shed text 2147483647  √  '0'::text This applies to acoustic tags. Was the tag shed and possibly sitting next to a receiver?
shed_date text 2147483647  √  null What is the approximate date of tag shedding?
ssm_version text 2147483647  √  null What version of the SSM produced the final/official track for this tag?
transmit_days int4 10  √  0 Satellite tag specific. How many days did the tag transmit after popup?
naturalmortality text 2147483647  √  '0'::text Does the data show the animal likely died at some point after deployment? This could be from predatory behavior or any other reason. Yes = 1 and no = 0.
date1_offshore date 13  √  null This applies to white sharks. What date did the animal move offshore?
minipat_ts_percent text 2147483647  √  null MiniPAT transmitted data specific. What percentage of the deployment has both depth and temperature time series data?
tagging_mortality text 2147483647  √  '0'::text Does the data show the tag went to the bottom soon, probably less than 2 weeks, after deployment? Yes = 1 and no = 0.
no_pdt text 2147483647  √  '0'::text PAT tag specific. Is PDT data missing or corrupt? Yes = 1 and no = 0.
no_tad text 2147483647  √  '0'::text PAT tag specific. Is time at depth data missing or corrupt? Yes = 1 and no = 0.
no_tat text 2147483647  √  '0'::text PAT tag specific. Is time at temperature data missing or corrupt? Yes = 1 and no = 0.
ssm_tracklen_km int4 10  √  null Track length in kilometers of the SSM output.
ssm_tracklen_nm int4 10  √  null Track length in nautical miles of the SSM output.
straight_distance int4 10  √  null Marlin specific. What is the straight distance in nautical miles between the deployment and popup/recovery position?
tkey serial 10  √  nextval('tblsgprocessingstatus_tkey_seq'::regclass)
date_last_lon text 2147483647  √  null The last date of good light level longitude data if there was sensor or battery failure.

Table contained 403 rows at Wed Dec 27 13:25 PST 2017

Indexes:
Column(s) Type Sort Constraint Name
sgdkey Primary key Asc tblsgprocessingstatus_pkey