Fishgroup table 'tblfgsatdeployments'
field | comment |
---|---|
whole table | This table contains deployment metadata from all satellite and acoustic tagged fishgroup animals. Typically joins will be made to the fgsdkey, toppid or ptt fields. Important fields used as query filters are project, seriesname, successful, taggingdate, tagmodel, tagtype and releasetype. This can be a confusing table. There are probably some unnecessary fields. 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. |
angler | Who caught the fish to be tagged? |
animal_id | This is a unique integer ID value for each animal. It is most relevant for animals that are tagged on multiple occasions. These taggings will have different toppids so the only way to identify them as the same animal is with some kind of common ID. |
argosaccno | Not used much. Duplicated in tbltmsat. The program number for owner of tag. Good candidate for deprecation. |
baittype | What type of bait was used to catch the fish? |
capcomments | For comments related to animal capture, e.g., "Associated with Dolphins.". |
capturevessel | What vessel was used to capture the fish? |
chaffing | Not used much. Refers to tag leader construction. Should be in programming table if anywhere. Candidate for deprecation. |
commonname | Matches commonname in toppspecies table. |
contag1number | Serial number of first conventional tag. |
contag1position | Where on the fish was conventional tag 1 applied. |
contag1type | Generally either floy or hallprint. |
contag2number | Serial number of second conventional tag. |
contag2position | Where on the fish was conventional tag 2 applied. |
contag2type | Generally either floy or hallprint. |
correctedsstc | The SST in celsius after applying sensor correction algorithm. |
darttype | What type of dart was used, e.g., deck, nylon, OTS titanium. |
datesstcorrected | Why is this important? Should be in processing table if anywhere. Candidate for deprecation. |
daystartlat | Only rarely used by ABFT. Latitude at start of deployment day. Candidate for deprecation. |
daystartlon | Only rarely used by ABFT. Longitude at start of deployment day. Candidate for deprecation. |
daystartsst | Only rarely used by ABFT. SST at start of deployment day. Candidate for deprecation. |
daystarttimelocal | Only rarely used by ABFT. Local time at start of deployment day. Candidate for deprecation. |
deploycomment | Generic comments field. |
deployloc_estimated | A yes/no field indicating the deployment lat and lon are estimated positions. |
dlatdd | Deployment latitude in decimal degrees. |
dlatdeg | The latitude degree value of deployment location. |
dlatmin | The latitude minute value of deployment location. Generally in decimal minute format. |
dlondd | Deployment longitude in decimal degrees. |
dlondeg | The longitude degree value of deployment location. |
dlonmin | The longitude minute value of deployment locations. Generally in decimal minute format. |
dnanumber | What number is on the DNA vial. |
dnasamplelocation | What part of the fish was sampled for DNA. |
ease2boat | Very confusing field of limited use. Sometimes it has a value like "Easy" or sometimes it is "Medium", but often it is fight time which already has its own field. Candidate for deprecation. |
ew | Deployment hemisphere where e is east and w is west. |
fdcomment | Hardly ever used. Not sure of definition. Good candidate for deprecation. |
fgsdkey | This field should be called eventid. It joins to fgsdkey in tblfgsatrecovery, fgdkey in tblfgprocessingstatus and fgsdkey in tblfgmk10programming as well as any other place eventid works for satellite or acoustic tags. It breaks down into several components. The first 2 digits are species ID. Digits 3 and 4 represent deployment year. Digits 5 - 7 count from 1 and represent individual animal deployments for the year. Digits 8 and 9 count from 0 and represent individual tags from the individual animal deployment. |
fighttime | Time in minutes to land the fish. |
fishingdepth | Another confusing field. Sometimes it gets bathymetric depth and sometimes depth of lure etc. Candidate for deprecation. |
fishmethod | How the animal was caught. |
fish_num | Specific to IGFA marlin. What is the number assigned to this fish from its particular race? |
gpsused | What GPS was used to generate deployment location? |
halfgirth | What is the half girth measurement in centimeters? |
handlingtime | Time in minutes from when the fish was brought to the boat until it was released. |
hooktype | What type of hook was used to catch the fish. |
injuries | What injuries happened to the fish during capture and/or tagging. |
irrigation | Was the fish irrigated during tagging? |
leaderlength | This is a confusing field. Can be interpreted as either the length of the fishing line leader or the tag leader. It has been used for both. Should only be for fishing line leader. Probably needs to be renamed for clarification. |
leadertest | The leader line test in pounds. |
leadertype | The material of the leader line. |
leadtagger | The person attaching the tag to the fish. |
len1 | The length of the fish in centimeters. |
len1type | How was the fish length measured, e.g., CFL, SFL or TL. |
len2 | A second length measurement of the fish in centimeters. |
len2type | Same as len1type but for second measurement. |
linetest | Fishing line test in pounds. |
localendtime | Rarely used. Candidate for deprecation. |
localssttime | Rarely used. Candidate for deprecation. |
localstoptime | Rarely usded. Candidate for deprecation. |
localtaggingdate | Rarely used. Duplicated by taggingdate. Candidate for deprecation. |
localtaggingtime | Rarely used. Duplicated by taggingtime. Candidate for deprecation. |
loops | The Block lab creates loop darts out of conventional tags and uses these loops to hold PAT tags close to the body of the fish. How many loops were used? |
mass | The mass of the fish in kilograms. |
masstype | How was the mass measurement taken, e.g., estimated, measured, LMDerived. |
mrna_number | What number is on the mRNA vial? |
ns | Deployment hemisphere where s is south and n is north. |
numberofhooks | Not used very often. If the fish was caught on a longline how many hooks were used? |
paint | Rarely used. Should be in programming table if anywhere. What anti-fouling paint was used on the tag? Candidate for deprecation. |
penetrationdepth | Depth of the tagging dart in centimeters. |
popoffdate | Duplicated in programming table. What date is the tag programmed to popoff? |
progdate | Duplicated in programming table. The date the tag was programmed. Good candidate for deprecation. |
project | The group responsible for tagging, e.g., TOPP, GTOPP, NonTOPP, IGFA or TAG. Not a seriously important field but can be useful in queries. |
psatleaderno | Block lab specific number on tag leader. |
ptt | The Argos PTT number for satellite tags. The transmitter ID code for acoustic tags. This is one of the main tag identification fields. |
pullstarttime | Not used very often. If the fish was caught on a longline what time did they start pulling in the set? |
releasetype | Generally not too important except in the case of PBFT released from a pen or into a pen only, e.g., Pen2wild or Pen. |
seastate | Description of ocean conditions like wave height. |
seriesname | Simple geographic desciptor of deployment location including year. |
setstarttime | Not used very often. If the fish was caught on a longline what time was the line deployed? |
sex | Never used for fish. The sex of the fish where F = female, M = male and U = unknown. |
soaktime | Not used very often. If the fish was caught on a longline how long was the line left in the water? |
species | Matches genus and species from toppspecies table. |
sponsor | Specific to IGFA marlin. Who sponsored the tag? |
sst | The sea surface temperature in degrees celsius. |
sstalgorithm | The sensor correction algorithm applied to the raw SST reading. |
sstdate | The date the SST was measured. |
sstprobe | The instrument used to measure SST. |
stableiso_num | What number is on the container with the stable isotope sample? |
successful | Was the deployment successful? Almost always true but there are some PBFT that died in pen before release. Yes is 1 and no is 0. |
surgeryboat | What boat did the tagging take place on? |
tag2code | The tagcode of the second tag if the fish was double-tagged. |
tag2position | Where on the fish was the second tag placed? |
tag2progdate | Duplicated in programming table. The date the second tag was programmed if the fish was double-tagged. Good candidate for deprecation. |
tag2ptt | The Argos PTT number of the second tag if the fish was double-tagged. |
tagapplocation | Another confusing and unnecessary field. Candidate for deprecation. |
tagcode | Serial number of the tag. |
tageventcomment | For comments related to the tagging event, e.g., "Fish tagged itself. Beautiful implantation.". |
taggingdate | Local date at deployment of tag. |
taggingtime | Local time at deployment of tag. |
tagmodel | Should match model name in tbltmsat. |
tagposition | Where on the fish was the tag placed? |
tagreleasecomment | For comments related to the release event, e.g., "Looked good going out the door.". |
tagteam | Who was involved in the tagging event? |
tagtype | Generic description of tag type, e.g., satellite or acoustic. |
tether | Not used much. Not entirely sure about this one. Could refer to how closely the tag is riding against the body. The currently used values are loose and tight. |
toppid | The basic ID number for a specific animal deployment. Matches the first 7 digits of eventid. |
transferboat | Was a boat used to transfer the fish to the tagging boat? If so what was the name of the boat? |
transfercaptain | Was a boat used to transfer the fish to the tagging boat? If so who was the captain of the boat? |
wc_id | ID number used for accessing tag data on Portal. |
weather | General description of temperature and cloud cover. |