Table: CRUISE
Entity (ENT) | Alaska Fisheries Science Center (AFSC)GUID: gov.noaa.nmfs.inport:69747 | Updated: October 26, 2023 | Published / External
-
View As
- Full List View
- Printable Form
- EXPORTS
- InPort XML
- View in Hierarchy
Summary
A lookup table for every cruise that is in the RACEBASE database. It summarizes locations, dates, the country performing the survey and cruise name for each cruise
DescriptionA lookup table for every cruise that is in the RACEBASE database. It summarizes locations, dates, the country performing the survey and cruise name for each cruise
Entity Information
Entity Type
Data Table
Data Attribute / Type | Description |
---|---|
CRUISEJOIN
NUMBER |
This is a unique numeric identifier assigned to each (VESSEL,CRUISE) combination |
REGION
VARCHAR2 |
Valid Values: AI=Aleutian Islands, BS=Bering Sea, GOA=Gulf of Alaska, WC=West Coast,HBS=Hydroacoustic Bering Sea, HG=Hydroacoustic Gulf of Alaska, HWC=Hydroacoustic West Coast, TAG=Denotes that no biological data exist for this cruise other than those related to tags released or recovered. |
VESSEL
NUMBER |
Codebooks: https://www.fisheries.noaa.gov/resource/document/groundfish-survey-species-code-manual-and-data-codes-manual |
CRUISE
NUMBER |
This is a six-digit number identifying the Cruise number of the form: YYYY99 (where YYYY = year of the cruise; 99 = 2-digit number and is sequential; 01 denotes the first cruise that vessel made in this year, 02 is the second, etc.) |
START_DATE
DATE |
Date. This is the date of the first haul of the cruise; this field is populated using a query - select min (start_time)from racebase.haul |
END_DATE
DATE |
Date. This is the date of the last haul of the cruise; this field is populated value using a query - select max (start_time) from a racebase.haul |
MIN_LATITUDE
NUMBER |
Latitude in decimal degrees. These are the southern bounding coordinates of cruise. |
MAX_LATITUDE
NUMBER |
Latitude in decimal degrees. These are the northern bounding coordinates of the cruise. |
MIN_LONGITUDE
NUMBER |
Longitude in decimal degrees. These are the eastern bounding coordinates of cruise. |
MAX_LONGITUDE
NUMBER |
Longitude in decimal degrees. These are the western bounding coordinates of cruise. |
AGENCY_NAME
VARCHAR2 |
Text. Name of country or countries that conducted the cruise |
SURVEY_NAME
VARCHAR2 |
Text. Description of the survey. |
AUDITJOIN
NUMBER |
This is a unique identifier for each record in the base table, to be used in corresponding audit tables to identify the original record in the base table |
Child Items
No Child Items for this record.
Contact Information
No contact information is available for this record.
Please contact the owner organization (AFSC) for inquiries on this record.
Item Identification
Title: | Table: CRUISE |
---|---|
Short Name: | CRUISE |
Status: | Completed |
Abstract: |
A lookup table for every cruise that is in the RACEBASE database. It summarizes locations, dates, the country performing the survey and cruise name for each cruise |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | RACEBASE |
Description: |
A lookup table for every cruise that is in the RACEBASE database. It summarizes locations, dates, the country performing the survey and cruise name for each cruise |
Data Attributes
Attribute Summary
![]() |
![]() |
Name | Type | Description |
---|---|---|---|---|
100
|
CRUISEJOIN | NUMBER | This is a unique numeric identifier assigned to each (VESSEL,CRUISE) combination | |
100
|
REGION | VARCHAR2 | Valid Values: AI=Aleutian Islands, BS=Bering Sea, GOA=Gulf of Alaska, WC=West Coast,HBS=Hydroacoustic Bering Sea, HG=Hydroacoustic Gulf of Alaska, HWC=Hydroacoustic West Coast, TAG=Denotes that no biological data exist for this cruise other than those related to tags released or recovered. | |
100
|
VESSEL | NUMBER | Codebooks: https://www.fisheries.noaa.gov/resource/document/groundfish-survey-species-code-manual-and-data-codes-manual | |
100
|
CRUISE | NUMBER | This is a six-digit number identifying the Cruise number of the form: YYYY99 (where YYYY = year of the cruise; 99 = 2-digit number and is sequential; 01 denotes the first cruise that vessel made in this year, 02 is the second, etc.) | |
100
|
START_DATE | DATE | Date. This is the date of the first haul of the cruise; this field is populated using a query - select min (start_time)from racebase.haul | |
100
|
END_DATE | DATE | Date. This is the date of the last haul of the cruise; this field is populated value using a query - select max (start_time) from a racebase.haul | |
100
|
MIN_LATITUDE | NUMBER | Latitude in decimal degrees. These are the southern bounding coordinates of cruise. | |
100
|
MAX_LATITUDE | NUMBER | Latitude in decimal degrees. These are the northern bounding coordinates of the cruise. | |
100
|
MIN_LONGITUDE | NUMBER | Longitude in decimal degrees. These are the eastern bounding coordinates of cruise. | |
100
|
MAX_LONGITUDE | NUMBER | Longitude in decimal degrees. These are the western bounding coordinates of cruise. | |
100
|
AGENCY_NAME | VARCHAR2 | Text. Name of country or countries that conducted the cruise | |
100
|
SURVEY_NAME | VARCHAR2 | Text. Description of the survey. | |
100
|
AUDITJOIN | NUMBER | This is a unique identifier for each record in the base table, to be used in corresponding audit tables to identify the original record in the base table |
Attribute Details
CRUISEJOIN
Seq. Order: | 1 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 12 |
Scale: | 0 |
Status: | Active |
Description: |
This is a unique numeric identifier assigned to each (VESSEL,CRUISE) combination |
General Data Type: | NUMBER |
REGION
Seq. Order: | 2 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Valid Values: AI=Aleutian Islands, BS=Bering Sea, GOA=Gulf of Alaska, WC=West Coast,HBS=Hydroacoustic Bering Sea, HG=Hydroacoustic Gulf of Alaska, HWC=Hydroacoustic West Coast, TAG=Denotes that no biological data exist for this cruise other than those related to tags released or recovered. |
General Data Type: | VARCHAR2 |
VESSEL
Seq. Order: | 3 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 4 |
Scale: | 0 |
Status: | Active |
Description: |
Codebooks: https://www.fisheries.noaa.gov/resource/document/groundfish-survey-species-code-manual-and-data-codes-manual |
General Data Type: | NUMBER |
CRUISE
Seq. Order: | 4 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 6 |
Scale: | 0 |
Status: | Active |
Description: |
This is a six-digit number identifying the Cruise number of the form: YYYY99 (where YYYY = year of the cruise; 99 = 2-digit number and is sequential; 01 denotes the first cruise that vessel made in this year, 02 is the second, etc.) |
General Data Type: | NUMBER |
START_DATE
Seq. Order: | 5 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Date. This is the date of the first haul of the cruise; this field is populated using a query - select min (start_time)from racebase.haul |
General Data Type: | DATE |
END_DATE
Seq. Order: | 6 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Date. This is the date of the last haul of the cruise; this field is populated value using a query - select max (start_time) from a racebase.haul |
General Data Type: | DATE |
MIN_LATITUDE
Seq. Order: | 7 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 7 |
Scale: | 5 |
Status: | Active |
Description: |
Latitude in decimal degrees. These are the southern bounding coordinates of cruise. |
General Data Type: | NUMBER |
MAX_LATITUDE
Seq. Order: | 8 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 7 |
Scale: | 5 |
Status: | Active |
Description: |
Latitude in decimal degrees. These are the northern bounding coordinates of the cruise. |
General Data Type: | NUMBER |
MIN_LONGITUDE
Seq. Order: | 9 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 8 |
Scale: | 5 |
Status: | Active |
Description: |
Longitude in decimal degrees. These are the eastern bounding coordinates of cruise. |
General Data Type: | NUMBER |
MAX_LONGITUDE
Seq. Order: | 10 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 8 |
Scale: | 5 |
Status: | Active |
Description: |
Longitude in decimal degrees. These are the western bounding coordinates of cruise. |
General Data Type: | NUMBER |
AGENCY_NAME
Seq. Order: | 11 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 40 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Text. Name of country or countries that conducted the cruise |
General Data Type: | VARCHAR2 |
SURVEY_NAME
Seq. Order: | 12 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 80 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Text. Description of the survey. |
General Data Type: | VARCHAR2 |
AUDITJOIN
Seq. Order: | 13 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 12 |
Scale: | 0 |
Status: | Active |
Description: |
This is a unique identifier for each record in the base table, to be used in corresponding audit tables to identify the original record in the base table |
General Data Type: | NUMBER |
Catalog Details
Catalog Item ID: | 69747 |
---|---|
GUID: | gov.noaa.nmfs.inport:69747 |
Metadata Record Created By: | Nancy Roberson |
Metadata Record Created: | 2023-05-01 17:43+0000 |
Metadata Record Last Modified By: | Nancy Roberson |
Metadata Record Last Modified: | 2023-10-26 19:04+0000 |
Metadata Record Published: | 2023-10-26 |
Owner Org: | AFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2023-10-26 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2024-10-26 |