View: V_GAF_REPORT
Entity (ENT) | Alaska Regional Office (AKRO)GUID: gov.noaa.nmfs.inport:27349 | Updated: August 9, 2022 | Published / External
-
View As
- Full List View
- Printable Form
- EXPORTS
- InPort XML
- View in Hierarchy
Summary
This view retrieves information about the fishing activity of Guided Angler Fish (GAF) permit holders/skippers..It combines data from GAF_REPORT, GAF_REPORT_DAY and GAF_REPORT_FISH.
DescriptionThis view retrieves information about the fishing activity of Guided Angler Fish (GAF) permit holders/skippers..It combines data from GAF_REPORT, GAF_REPORT_DAY and GAF_REPORT_FISH.
Entity Information
Entity Type
Data View
Data Attribute / Type | Description |
---|---|
GAF_PERMIT_ID
Character |
Unique GAF permit number for the GAF permit being reported on. |
GAF_REPORT_ID
Character |
Unique ID of GAF Landing Report. |
PERSON_REPORTING_ID
Character |
Unique NMFS ID of the person making the report. |
REPORTING_NAME
Character |
Name of the person making the report. |
DATE_REPORTED
Character |
The date the halibut was caught. |
LOG_BOOK_NUMBER
Character |
The saltwater logbook number which records the catch. |
COAST_GUARD_NUMBER
Character |
The Coast Guard Number of the vessel used to catch GAF. The Coast Guard Number may be null, if Alaska License Number was entered instead. |
AK_LICENSE_NUMBER
Character |
The Alaska License Number, issued by the Division of Motor Vehicles, of the vessel used to catch GAF. The Alaska License Number may be null, if Coast Guard Number was entered instead. |
GUIDE_LICENSE_NUMBER
Character |
The ADFG sport fishing guide license number. |
MULTI_DAY_REPORT_FLAG
Character |
User-reported check of whether the trip was more than one day. |
LANDING_CITY
Character |
The community or port where trip ended. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. |
LANDING_CITY_OTHER
Character |
The community or port where trip ended. Only valid if landing_city is OTHER. |
START_CITY
Character |
The community or port where trip started. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. |
START_CITY_OTHER
Character |
The community or port where trip started. Only valid if start_city is OTHER. |
COMMENTS
Character |
Comments added by Data Techs or Enforcement. |
DATE_HARVESTED
Character |
Day the fish were caught. |
LOG_PAGE_NUMBER
Character |
The page in the saltwater logbook specified by LOG_BOOK_NUMBER on which the catch is reported. |
LENGTH
Character |
The physical length of each fish. |
Child Items
No Child Items for this record.
Contact Information
No contact information is available for this record.
Please contact the owner organization (AKRO) for inquiries on this record.
Extents
2014 - Present
Guided Angler reporting started in 2014?
Item Identification
Title: | View: V_GAF_REPORT |
---|---|
Short Name: | V_GAF_REPORT |
Status: | Completed |
Abstract: |
This view retrieves information about the fishing activity of Guided Angler Fish (GAF) permit holders/skippers..It combines data from GAF_REPORT, GAF_REPORT_DAY and GAF_REPORT_FISH. |
Notes: |
Loaded by batch 7095, 09-22-2015 13:02 |
Entity Information
Entity Type: | Data View |
---|---|
Active Version?: | Yes |
Schema Name: | AKFISH |
Description: |
This view retrieves information about the fishing activity of Guided Angler Fish (GAF) permit holders/skippers..It combines data from GAF_REPORT, GAF_REPORT_DAY and GAF_REPORT_FISH. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
GAF_PERMIT_ID | Character | Unique GAF permit number for the GAF permit being reported on. | |
100
|
GAF_REPORT_ID | Character | Unique ID of GAF Landing Report. | |
100
|
PERSON_REPORTING_ID | Character | Unique NMFS ID of the person making the report. | |
100
|
REPORTING_NAME | Character | Name of the person making the report. | |
100
|
DATE_REPORTED | Character | The date the halibut was caught. | |
100
|
LOG_BOOK_NUMBER | Character | The saltwater logbook number which records the catch. | |
100
|
COAST_GUARD_NUMBER | Character | The Coast Guard Number of the vessel used to catch GAF. The Coast Guard Number may be null, if Alaska License Number was entered instead. | |
100
|
AK_LICENSE_NUMBER | Character | The Alaska License Number, issued by the Division of Motor Vehicles, of the vessel used to catch GAF. The Alaska License Number may be null, if Coast Guard Number was entered instead. | |
100
|
GUIDE_LICENSE_NUMBER | Character | The ADFG sport fishing guide license number. | |
100
|
MULTI_DAY_REPORT_FLAG | Character | User-reported check of whether the trip was more than one day. | |
100
|
LANDING_CITY | Character | The community or port where trip ended. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. | |
100
|
LANDING_CITY_OTHER | Character | The community or port where trip ended. Only valid if landing_city is OTHER. | |
100
|
START_CITY | Character | The community or port where trip started. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. | |
100
|
START_CITY_OTHER | Character | The community or port where trip started. Only valid if start_city is OTHER. | |
100
|
COMMENTS | Character | Comments added by Data Techs or Enforcement. | |
100
|
DATE_HARVESTED | Character | Day the fish were caught. | |
100
|
LOG_PAGE_NUMBER | Character | The page in the saltwater logbook specified by LOG_BOOK_NUMBER on which the catch is reported. | |
100
|
LENGTH | Character | The physical length of each fish. |
Attribute Details
GAF_PERMIT_ID
Seq. Order: | 1 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique GAF permit number for the GAF permit being reported on. |
GAF_REPORT_ID
Seq. Order: | 2 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique ID of GAF Landing Report. |
PERSON_REPORTING_ID
Seq. Order: | 3 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique NMFS ID of the person making the report. |
REPORTING_NAME
Seq. Order: | 4 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Name of the person making the report. |
DATE_REPORTED
Seq. Order: | 5 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The date the halibut was caught. |
LOG_BOOK_NUMBER
Seq. Order: | 6 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The saltwater logbook number which records the catch. |
COAST_GUARD_NUMBER
Seq. Order: | 7 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The Coast Guard Number of the vessel used to catch GAF. The Coast Guard Number may be null, if Alaska License Number was entered instead. |
AK_LICENSE_NUMBER
Seq. Order: | 8 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The Alaska License Number, issued by the Division of Motor Vehicles, of the vessel used to catch GAF. The Alaska License Number may be null, if Coast Guard Number was entered instead. |
GUIDE_LICENSE_NUMBER
Seq. Order: | 9 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The ADFG sport fishing guide license number. |
MULTI_DAY_REPORT_FLAG
Seq. Order: | 10 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
User-reported check of whether the trip was more than one day. |
LANDING_CITY
Seq. Order: | 11 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Scale: | 0 |
Status: | Active |
Description: |
The community or port where trip ended. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. |
LANDING_CITY_OTHER
Seq. Order: | 12 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The community or port where trip ended. Only valid if landing_city is OTHER. |
START_CITY
Seq. Order: | 13 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The community or port where trip started. This is only required for Community Charter Halibut Permit (CHP), and should not be entered by other GAF permit holders. |
START_CITY_OTHER
Seq. Order: | 14 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The community or port where trip started. Only valid if start_city is OTHER. |
COMMENTS
Seq. Order: | 15 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Comments added by Data Techs or Enforcement. |
DATE_HARVESTED
Seq. Order: | 16 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Day the fish were caught. |
LOG_PAGE_NUMBER
Seq. Order: | 17 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The page in the saltwater logbook specified by LOG_BOOK_NUMBER on which the catch is reported. |
LENGTH
Seq. Order: | 18 |
---|---|
Data Storage Type: | Character |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The physical length of each fish. |
Extents
Extent Group 1
Extent Group 1 / Time Frame 1
Time Frame Type: | Continuing |
---|---|
Start: | 2014 |
Description: |
Guided Angler reporting started in 2014? |
Catalog Details
Catalog Item ID: | 27349 |
---|---|
GUID: | gov.noaa.nmfs.inport:27349 |
Metadata Record Created By: | Pamela A Mason |
Metadata Record Created: | 2015-09-22 13:02+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2016-01-04 |
Owner Org: | AKRO |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2016-01-04 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2017-01-04 |