The PTAGIS database relies on the use of many standardized codes to record and report those data objects that are common to most or all PIT tag research and monitoring projects in the Columbia Basin.  These common codes sets help ensure the consistent identification and interpretation of PIT tag data collected by many different agencies and projects with diverse goals and objectives.  More information on these Validation and River Kilometer codes can be found in Section IV of the current (2009) PIT Tag Specification Document.  You can also download the current code lists for use in the P3 data entry/edit programs

 

Validation Codes
	A) Species Codes - Each PIT tag detail record included in a data file submitted to PTAGIS must reference a valid Species Code in column 41 of that record.  A Species Code of "0" (Unknown) is used when the host fish is not observed (e.g., during a passive recapture event or when the bare tag is retrieved from a predator).
	B) Run Codes - Each PIT tag detail record included in a data file submitted to PTAGIS must reference a valid Run Code in column 42 of that record.  A Run Code of "0" (N/A) is used when the host fish is not observed, or if the host fish is not a salmonid.  A Run Code of "5" (Unknown) is used by default to describe coho and mid-Columbia sockeye stocks, as well as unknown stocks of lower-Columbia River steelhead.
	C) Rearing Type Codes - Each PIT tag detail record included in a data file submitted to PTAGIS must reference a valid Rearing Type Code in column 43 of that record.
	** Verbose S/R/RT Codes - There are over 200 possible combinations of Species, Run, and Rearing Type codes.  Only those in this list are considered valid references to fish stocks in the Columbia Basin.
	D) Data Coordinator Codes - All Tag Information files submitted to PTAGIS (including those with recapture and/or mortality records) must reference a valid Coordinator ID and, in fact, the data file name itself must include a valid Coordinator ID in its prefix. The Coordinator Contact list contains e-mail addresses and/or phone numbers for all active Tag Data Coordinators.
	E) Conditional Comments (Flag Codes) - Each PIT tag detail record in a data file can be annotated with one or more Flag Codes.  These codes are used to indicate fish condition (e.g., B, FU), life stage (e.g., JA, KL), and to flag other events.  Flag Codes also denote the Recapture (RE, BT) or Mortality (M, MS, etc.) status of previously-tagged fish.
	F) Hatchery Codes - These codes are used to denote the origin of hatchery-reared PIT-tagged fish, and can also denote a tagging and/or release location.
	G) Capture Method Codes - All Tag Information files submitted to PTAGIS must reference a valid Capture Method Code.
	H) Tagging Method Codes - All Tag Information files submitted to PTAGIS must reference a valid Tagging Method Code.
	I) Organization Codes - All Tag Information files submitted to PTAGIS must reference a valid Organization Code.
Tag and Release Sites, and River Kilometer Codes
	J) Tag and Release Site Codes - All hatchery, tagging, and release locations referenced in Tag Information files submitted to PTAGIS are uniquely identified by their Site Code, and can be located geographically within their assigned USGS Hydro-Unit Code (HUC).  Release (and recapture/mortality) locations are also assigned a River Kilometer mask, denoting their positions within the river reachs of the Columbia Basin.  Fixed release sites include dams, bridges, hatcheries, and permanently-located traps; the River Kilometer value for release sites within a stream or river include a three-digit suffix denoting the actual distance from the mouth of that stream or river.
	** Intra-Dam Release Site Codes - Each of these codes, used as a suffix with a three-character Dam prefix, identifies a specific release location at or within a hydroelectric project or its fish passage facilities.
Interrogation Site Codes
	** Interrogation (Obs) Site Codes - All Interrogation Site codes currently and historically defined in the PTAGIS database.

---

Modified on: Thursday, 07-Jan-2010 11:06:12 PST Modified by: Dave.Marvin@ptagis.org