| field |
comment |
| whole table |
This table contains deployment metadata from all satellite and acoustic tagged sharkgroup animals. Typically joins will be made to the sgdepkey, toppid or ptt fields. Important fields used as query filters are project, seriesname, taggingdate, and tagtype. 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. |
| actpopdate |
I think this is the same as actpopdate in the recovery table. Completely unnecessary. Candidate for deprecation. |
| angler |
Who caught the shark 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 shark? |
| bertarelli_name |
Specific to Chagos deploys. Nickname given to animal by the Bertarelli family. |
| commonname |
Matches commonname in toppspecies table. |
| contag1number |
Serial number of first conventional tag. |
| contag1position |
Where on the shark was conventional tag 1 applied. |
| contag1type |
Generally either floy or hallprint. |
| contag2number |
Serial number of second conventional tag. |
| contag2position |
Where on the shark was conventional tag 2 applied. |
| contag2type |
Generally either floy or hallprint. |
| correctedsst |
The SST in celsius after applying sensor correction algorithm. |
| darttype |
What type of dart was used, e.g., deck, nylon, OTS titanium. |
| 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 shark 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. |
| edna |
Was eDNA collected? |
| ew |
Deployment hemisphere where e is east and w is west. |
| famename |
Looks like a duplicate of nickname. They should be merged and one of them deprecated. |
| fighttime |
Time in minutes to land the shark. |
| fin_id |
Specific to white sharks. Identifies the best photo identification for the specific animal. |
| fishingdepth |
Another confusing field. Sometimes it gets bathymetric depth and sometimes depth of lure etc. Candidate for deprecation. |
| fishmethod |
How the animal was caught. |
| gpsused |
What GPS was used to generate deployment location? |
| halfgirth |
What is the half girth measurement in centimeters? |
| handlingcomments |
How was the animal handled? |
| handlingtime |
Time in minutes from when the shark was brought to the boat until it was released. |
| hooktype |
What type of hook was used to catch the shark. |
| injuries |
What injuries happened to the shark during capture and/or tagging. |
| irrigation |
Was the shark 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 shark. |
| len1 |
The length of the shark in centimeters. Should always be anumber, never unknown or n/a etc. |
| len1type |
How was the shark length measured, e.g., CFL, SFL or TL. |
| len2 |
A second length measurement of the shark in centimeters. |
| len2type |
Same as len1type but for second measurement. |
| len3 |
A third length measurement of the shark in centimeters. |
| len3type |
Same as len1type but for third measurement. |
| linetest |
Fishing line test in pounds. |
| loopnum |
The Block lab creates loop darts out of conventional tags and uses these loops to hold PAT tags close to the body of the shark. What number is on the loop dart? |
| loopposition |
Where was the loop dart placed on the animal? |
| 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 shark. How many loops were used? |
| masskg |
The mass of the shark in kilograms. |
| masstype |
How was the mass measurement taken, e.g., estimated, measured, LMDerived. |
| mrna_number |
What number is on the mRNA vial? |
| nickname |
Specific to white sharks. Duplicated by famename. They should be combined and one deprecated. |
| ns |
Deployment hemisphere where s is south and n is north. |
| numberhooks |
Not used very often. If the shark 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. |
| popup_comment |
This should be in the recovery table. Candidate for deprecation. |
| prboattack |
This is white shark specific. Not sure but possibly a reference to a PRBO witnessed attack. |
| probe |
What probe was used to measure SST? |
| progdate |
Duplicated in programming table. The date the tag was programmed. Good candidate for deprecation. |
| progpopdate |
Duplicated in programming table. The date the tag was programmed to popup. 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. |
| psatleadernumber |
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. |
| pulltime |
Not used very often. If the shark was caught on a longline what time was the set pulled? |
| releasecomment |
For comments related to the release event, e.g., "Looked good going out the door.". |
| releasedevice |
This is a programming field. If the tag was equiped with a Wildlife Computers release device what model is it? Candidate for deprecation. |
| seastate |
Description of ocean conditions like wave height. |
| seriesname |
Simple geographic desciptor of deployment locationincluding year. |
| setnumber |
Not sure about this field. Probably related to longlining. |
| setstarttime |
Not used very often. If the shark was caught on a longline what time was the line deployed? |
| settime |
Not sure about this field. Possibly the same as soaktime in tblsharkdeployment - how long was the longline left in the water? |
| sex |
Never used for shark. The sex of the shark where F = female, M = male and U = unknown. |
| sexmaturity |
Level of sexual maturity. |
| sgdepkey |
This field should be called eventid. It joins to sgdepkey in tblsharkrecovery, sgdkey in tblsgprocessingstatus and sgdepkey in tblsgmk10programming 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 representdeployment 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. |
| sharkapp |
Specific to white sharks. Was this animal included in the Block lab shark app? |
| species |
Matches genus and species from toppspecies table. |
| sst |
The sea surface temperature in degrees celsius. |
| stableiso_num |
What number is on the container with the stable isotope sample? |
| tag1side |
Similar to tagposition. Seems unnecessary. What side of the animal is tag 1 on? |
| tag2code |
The tagcode of the second tag if the shark was double-tagged. |
| tag2progdate |
Duplicated in programming table. The date the second tag was programmed if the shark was double-tagged. Good candidate for deprecation. |
| tag2ptt |
The Argos PTT number of the second tag if the shark was double-tagged. |
| tag2side |
Similar to tagposition. Seems unnecessary. What side of the animal is tag 2 on? |
| 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., "shark tagged itself. Beautiful implantation.". |
| taggingdate |
Local date at deployment of tag. |
| taggingtime |
Local time at deployment of tag. |
| taggingvessel |
What boat did the tagging take place on? |
| tagnumber |
Manufacturer serial number of tag. |
| tagposition |
Where on the shark was the tag placed? |
| tagteam |
Who was involved in the tagging event? |
| tagtype |
Generic description of tag type, e.g., satellite or acoustic. |
| toppid |
The basic ID number for a specific animal deployment.Matches the first 7 digits of eventid. |
| transfercaptain |
Was a boat used to transfer the shark to the tagging boat? If so who was the captain of the boat? |
| waterdepth |
The bathymetric depth of the water at deployment location. |
| wc_id |
ID number used for accessing tag data on Portal. |
| weather |
General description of temperature and cloud cover. |