Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

There are two different trip numbers in the eLandings system:
  1. ODDS Trip Number – This is a trip number assigned by the North Pacific Groundfish and Halibut Observer Program’s Observer Declare and Deploy System (ODDS) to vessels greater than 40 feet LOA in partial coverage fisheries.  Processors are asked to provide the ODDS trip number on groundfish landing reports.  See the eLandings User Manual (Adding Observer Declare and Deploy System -ODDS- trip number to elandings) for additional information on the ODDS trip number and instructions for reporting it in eLandings.
  2. eLandings Trip Number – This is a trip number automatically assigned to groundfish and crab landing reports by eLandings in an attempt to identify a landing report or landing reports that constitute a fishing trip.  After being automatically assigned, the eLandings trip number can be modified by agency staff.  (Note that trip numbers are NOT assigned to salmon landing reports, as ADF&G salmon management can effectively rely upon landing report fish tickets to determine effort.)

eLandings Trip Number

A common unit of effort for groundfish fishing is the fishing trip.  Crab agency managers rely primarily on the total harvest and associated pot pulls to establish effort, but also rely on fishing trip.  Depending on the type of fishing operation, where deliveries occur, the fisheries agency, and what the trip designation is used for, a fishing trip may be defined in different ways.[1]  The eLandings trip number reflects the fishing activity of a single vessel which may be documented on a single landing report or on more than one landing report as a result of overlapping fishing dates for deliveries to more than one processor.  It is common for crab vessels to deliver product from one trip to multiple processing facilities.  These individual off-loads are identified as partial deliveries.  When all off-loads have been completed, the Last Delivery of Trip identification is activated. 

 The following documentation describes the automated identification of trips, the automated trip number assignment to landing reports, and the process with which agency staff review and potentially change the trip number assignment. 

The eLandings trip number can be found in the Agency Web under under Trip in the Reports Menu.

Enter Vessel # and Year.

Click 'Search'.

Figure 1. eLandings trip number 7620165385 on a groundfish landing report for ADF&G vessel number 00076, in 2016, with sequential trip number 5385


Figure 2. eLandings trip number 5192720160030 on a crab landing report for ADF&G vessel number 51927, in 2016, with sequential trip number 30


Note that trip numbers are NOT assigned to salmon landing reports.

TRIP NUMBER FORMAT – The trip number may be in one of two formats:

  1. VVVVVYYYYTTTT – The trip number reflects the vessel ADF&G number, the 4-digit landing year, and a sequential trip number.  This eLandings trip number format began in 2016 and is a unique number.  Note, any leading zeros in the vessel ADF&G number (i.e., 00045) are NOT included in the trip number.
  2. YYTTTTT – The trip number reflects the 2-digit landing year and a sequential trip number.  This eLandings trip number format was used prior to 2016 and is not a unique number.  Different vessels may have the same trip numbers.  Note, any leading zeros in the 2-digit landing year (i.e., 07) are NOT included in the trip number.  For more information on how trip numbers were assigned prior to 2016 see /wiki/spaces/et/pages/136282116.


[1] For example, CFR 679.2 (https://alaskafisheries.noaa.gov/sites/default/files/679a2.pdf) and 5 AAC 39.130(o)(16) (http://www.legis.state.ak.us/basis/aac.asp#5.39.130).


Trip Identification

The landing reports of a vessel are identified as part of the same trip by an automated, nightly batch process if the time between the date fishing began and the date landed on one landing report overlaps with those of another landing report.

Figure 3. Four landing reports identified as one trip for a vessel.


Landing reports are not considered part of the same trip by the automated process if their dates do not overlap with one another.  For 2016 and onward, if a landing report has the same date landed as the date fishing began on another landing report (or the same date fishing began as another’s date landed) the landing reports are not considered the same trip.  For example, in figure 4, it is assumed that the vessel finished trip 20 and started a new trip (trip 30) on the same day.

Figure 4. Four landing reports identified as four different trips for a vessel.


Note, prior to 2016 landing reports for a vessel that had the same date landed as the date fishing began on another landing report (or the same date fishing began as another’s date landed) were considered the same trip in the automatic process and the same trip number was assigned to both landing reports. Trip number assignments for a vessel that have the same date landed as the date fishing began on another landing report (or the same date fishing began as another’s date landed) will be flagged for agency staff to review (see the Trip Number Status section for more information about agency review).



Trip Number Assignment

A landing report will not have a trip number assigned immediately upon submission; trip numbers are assigned nightly through a batch process.  The first landing report submitted for a vessel for the year is assigned a trip number with a sequential trip number of 10.  Subsequent landing reports are assigned a trip number based on whether it is identified as its own trip or whether it is identified as part of the trip on another landing report.   

The following diagram illustrates how a trip number is assigned to a landing report if it is identified as its own trip:

Figure 5. The business rules for assigning the eLanding trip number to a groundfish landing report that does not overlap another landing report.  Note, the same business rules are followed for a crab landing report.


The following diagram illustrates how a trip number is assigned to a landing report if it is identified as part of the trip on another landing report:

Figure 6. The business rules for assigning the eLanding trip number to a groundfish landing report that overlaps another landing report.  Note, the same business rules are followed for a crab landing report.



Trip Number Status


The trip number status serves two purposes:

  1. it provides a qualitative assessment of the trip number that has been assigned to a landing report, and 
  2. it flags trip number assignments that need to be reviewed by agency staff.

The eLandings trip number status can also be found in the Trip section of groundfish and crab landing reports on the Agency Desktop:

Figure 7. eLandings trip number 7620165385 on a groundfish landing report with an unverified trip number status

Figure 8. eLandings trip number 7620160275 on a groundfish landing report with a verified trip number status


TRIP NUMBER STATUS – The trip number status has four values:

  1. NULL: the trip number has not been assigned yet. Trip numbers are assigned nightly.
  2. REVIEW:  the trip number has been assigned, but there was an edit to the landing report or there was ambiguity so the trip number needs manual review by agency staff.
  3. VERIFIED:  the trip number has been reviewed by agency staff and trip number is confirmed.
  4. UNVERIFIED:  the trip number was assigned through the automatic process and business rules, and the assignment was unambiguous.  The trip number is believed to be correct.

Figure 9. The four trip number statuses


CHANGES TO TRIP NUMBER STATUS – the trip number status can change for a number of reasons:

  1. INITIAL SUBMISSION: each evening the nightly batch job will assign a trip number and trip number status to all new groundfish and crab landing reports. The trip number status will change from:
    • NULL to UNVERIFIED: if the trip number assignment through the automated process is unambiguous.  For example, the new landing report has dates fishing began and date landed that do not overlap with any other landing report for the vessel; or

Figure 10. The trip number status changes on a new landing report from NULL to UNVERIFIED with the unambiguous assignment of a trip number.


    • NULL to UNVERIFIED:  if the new landing report has dates fishing began and date landed that clearly overlap with another landing report for the vessel; or

Figure 11. The trip number status changes on a new landing report from NULL to UNVERIFIED with the unambiguous assignment of a trip number.


    • NULL to REVIEW: if the trip number assignment through the automated process is ambiguous.  For example, if the date fishing began on the new landing report is the same as the date landed on another landing report.  eLandings assumes it is a different trip, that the vessel finished a trip and started a new trip on the same day, but flags it for review by agency staff as the landing may reflect a single trip with a partial delivery.

Figure 12. The trip number status changed on a new landing report from NULL to REVIEW if the trip number assignment is ambiguous. 


2. LANDING REPORT EDITS: if edits are made to the date fishing began, date landed, vessel ADF&G number, or partial delivery flag on an existing landing report, the trip number status will change during the nightly batch process from:  

    • UNVERIFIED or VERIFIED to REVIEW: so agency staff can determine if the landing report edits require a change to the trip number that was previously assigned to the landing report.

Figure 13. The trip number status of a landing report with a revised fishing begin date changes from UNVERIFIED to REVIEW.


3. AGENCY STAFF REVIEW: if agency staff review the trip number assigned to a landing report, the trip number status may change from:

    • REVIEW or UNVERIFIED to VERIFIED: this indicates that agency staff have reviewed the trip number assignment based on additional information available (like logbooks or dockside interviews) and verified it as correct or changed the assigned trip number. (See the Agency Review and Edit of Trip Numbers section.)

Figure 14. Following agency staff review and edit to a landing report's trip number, the trip number status changes from REVIEW to VERIFIED.


(If the diagrams on this page need to be edited, they can be found in this file: Trip Number Diagrams.pptx)


Agency Review and Edit of Trip Numbers

Because thousands of landing reports are created through eLandings each year, it is not feasible for agency staff to review the trip number assigned to every groundfish or crab landing report.  The following documentation illustrates how agency staff can query for, review, verify, or edit the trip number and trip number status of select landing reports.

Search for a Trip Number

Select the Reports Menu dropdown.

Click the Trips menu option.

This will open the Landing Report Trip Numbers search screen.

Enter information into the required fields (you select options from from 'Type' and 'Status' to further refine the results)

  1. ADFG Vessel # and
  2. Year

Click the 'Search' Button.

Review a Trip Number

From your results table determine which 'Trip Number' you would like to review.

Click the 'Rpt ID' associated with that 'Trip Number'.

The associated Report will open in view mode. You can review all the Trip information in the section at the right of the form.

Edit a Trip Number

Once you've reviewed the Trip information (see above), you may determine that the information needs to be edited or the status of the trip updated. 

Select the Menu icon in the upper right corner.

Click on the Edit menu item. 

The Report will open in an editable form. You will be able to change the status and the trip number here. If you just need to change the trip number you are also able to do so on the initial search results screen (see above).



  • No labels