...
- Report_date
The report_date element is the date of the production being reported. - Federal_processor_number
The federal_processor_number is the federal_processor_permit number for the processor who submitted the report. It is typically omitted from salmon reports. The federal_processor_number element includes three attributes:- name - the name of the processing company, plant, or at-sea processing vessel
- at_sea_proc - a boolean flag indicating the permit is a federal fisheries permit for an at-sea processor. This attribute is omitted from landing reports exported from eLandings.
- license_year - the most recent year for which the processor was licensed. This attribute is omitted from landing reports exported from eLandings.
- No_deliveries
The no_deliveries element is a flag indicating that no deliveries from catcher vessels were received on the date. - No_production
The no_production element is a flag indicating that no processing was done on the date. If the no_production element is set to "true" then the report will not have production_item elements. - Vessel
The vessel element is the vessel ADF&G number, for at-sea operations. It will not be present for shoreside reports.- The vessel element includes a name attribute, which contains the name of the vessel
- Gear
The gear element is the ADF&G gear code, as entered on fish tickets. It will be present on at-sea reports, but will not be on shoreside reports.- then gear element includes a name attribute, which contains the name of the gear type.
- Crew_size
The crew_size element is the number of crew onboard, including the skipper, but excluding any observers. It will only be present for at-sea production reports. - Port_of_landing
The port_of_landing element is the ADF&G port code, as entered on fish tickets. It will be present for at-sea production reports, and it will contain the port code value for the at-sea operation type, such as Catcher/Processor or floating inshore processor.
The port_of_landing element includes two attributes.- the name attribute contains the text name of the port or at-sea operation type
- the ifq_port_code contains the numeric IFQ system port code, as used on IFQ reports. The IFQ port code appears even on reports that do not include IFQ. It is merely an attribute of the alphabetic port code and its presence does not imply IFQ reporting.
- Observers
The observers element is the number of observers in the plant or onboard the vessel. - Proc_code
The proc_code element identifies the entity that purchases or otherwise controls the fish, and is equivalent to the proc code embossed on paper fish tickets. It will only be present for shoreside production reports.- The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.
- Fed_area
The fed_area element contains the Federal reporting area number where the fish were harvested. It will only be present for at-sea production reports. - Special_area
The special_area element contains the special area code where the fish were harvested, if the harvest was within one of the special areas. It will only be present for at-sea production reports, and will only be present if the harvest took place within a special area.- Management_program
The management_program element identifies the management program under which the fishing took place. It will be present only for at-sea reports.- Program
The program element is the management program abbreviation such as IFQ, CDQ, AFA, or OA. - Program_id
The program_id element is participant identifier. It will be present if the management program has participant IDs. CDQ numbers for CDQ and Co-op numbers for AFA, are examples of program ids. If the management program has no participant numbers, such as ADAK, then this element will be omitted.
- Program
- Management_program
- Trip_event_code
The trip_event_code element indicates events that can occur on at-sea processor trips, which affect maximum retainable amounts. It will be present only for at-sea reports, and only if one of the events occurred on the date of the report.
Stat_area_worksheet
The stat_area_worksheet element will be present for at-sea reports, but not for shoreside reports.
More that one stat_area_worksheet elements may be specified.
- Item_number
he item_number element is just the sequential item number for the stat area worksheet item. However, item numbers may have a break in their sequence if a report is submitted, and then a stat area worksheet item is deleted. - Stat_area
The stat_area element always present This is the ADF&G 6 digit groundfish statistical area. - Percent
The percent element will always be present. The total of percents for all stat_area_worksheet elements will equal 100. - Effort
The effort element is not used for production reports, and will always be omitted. - Count
The count element is not used on production reports, and will always be omitted.
Coded_comment
The coded_comment element is used for agency purposes. It will not appear in reports exported from eLandings, and should not be specified for reports that are to be imported to eLandings.
- Proc_code
The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.- The proc_code element includes a processor attribute, which contains the name of the processor, as listed on their intent to operate application.
- Proc_code
- Proc_code_processor
The proc_code_processor element identifies the custom processor, if there was one. This element is present only if custom processing took place.- Proc_code
The proc_code element is the ADF&G intent to operate processor code, also known as the F-code.
- Proc_code
- Date_fishing_began
The date_fishing_began element is the date the gear went in the water. - Days_fished
The days_fished element is the number of days the vessel was actually fishing. This element may not be present. - Date_of_landing
The date_of_landing element is the date the offload completed. The date_of_landing actually a date and time. Time of landing is only used in salmon fisheries, but the element's definition requires the time component always be present. For non-salmon landings, or salmon landings where time of landing is not captured, the time component will be set to the eLandings default value, 12:00:01. When provided time for salmon landing reports, the resolution of time is in minutes. The seconds portion of time will always be 00. The 01 seconds of the default value is the indication that time should be ignored. - Partial_delivery
The partial_delivery element is a flag indicating whether the landing report was for a partial delivery or not. - Last_delivery_for_trip
The last_delivery_for_trip element is a flag indicating that the landing is the last for the trip. - Multiple_ifq_permits
The multiple_ifq_permits element provides historic compatibility with fish tickets. - Manual_ifq_report
The manual_ifq_report element indicates that the IFQ reporting for this landing was done by contacting the NMFS Enforcement data clerks by telephone and making the IFQ reports manually to them. If the manual_ifq_report element is set to true then no IFQ reports will be included in the landing report XML file. - Nearest_bay_or_headland
The nearest_bay_or_headland element contains a text description of the area fished. It is not used for IFQ crab or groundfish, but is used for salmon. - Registered_buyer_number
The registered_buyer_number the buyer identification for IFQ halibut and sablefish. It is typically omitted from salmon reports. This element includes two attributes.- name - the name of the processing company, plant, or at-sea processing vessel
- license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.
- Registered_crab_receiver_number
The registered_crab_receiver_number identifies the receiver for IFQ crab. It is the RCR number issued by NMFS. This element will be omitted for groundfish and salmon landings. This element includes two attributes.- name - the name of the processing company, plant, or at-sea processing vessel
- license_year - the most recent year for which the buyer was licensed. This attribute is omitted from landing reports exported from eLandings.
- Discard_report
The discard_report element indicated that the processor either did or did not receive the discard report blue sheets from the fisherman. It is required for groundfish, but will be omitted for salmon and crab reports. The values for discard_report are:The discard_report element includes a desc attribute, with the text value of the discard report code.Value
Description
RC
Received
NC
Not received
NP
Not required, vessel not federally permitted
NL
Not required, vessel less than 60 feet
- Tender_vessel
The tender_vessel element contains the ADF&G number of the tender that took the delivery that generated the landing report. It is omitted for non-tender deliveries.- The tender_vessel element includes a name attribute, which contains the name of the vessel.
- chill_type
The chill_type element is used to indicate the refrigeration method used aboard the catcher vessel for salmon reports. It is omitted for non-salmon landings. The values for chill_type are:The chill_type element includes a desc attribute, with the text value of the chill type code.Value
Description
CSW
Circulating seawater
FAS
Frozen at sea
ICE
Ice
LIV
Fish were delivered or pumped live
RSW
Refrigerated seawater
SLH
Slush ice
- Rsw_temp
The rsw_temp element is used to record the temperature of the fish or the chill system aboard the catcher vessel. The term rsw temp is a misnomer, the actual chill type is specified in the chill_type element and does not have to be RSW. The rsw_temp element can repeat up to 3 times, to allow for storage of sample data on unsubmitted reports. However, when the landing report is submitted the temperatures are averaged, and only one temperature is stored and returned on landing reports exported from eLandings. Rsw_temp is omitted if the report does not include chill_type. - Dock_delivery
The dock_delivery element is a boolean flag that indicates if a tender delivery took place at a tender tied up at the processing plant dock. It is omitted for landings that are not dock deliveries. - Buying_station_name
The buying_station_name element contains the operation name if the operation that submitted the report is a buying station operation, and can be so identified from the permit numbers and processor codes on the landing report. In some cases the operation cannot be determined, so this element may not be present even if the originating operation was a buying station. If the originating operation was not a buying station this element will be omitted. - Agency_header_data
The agency_header_data element is used internally by the eLandings system. It will not be seen in export files. - Permit_worksheet
At least one permit_worksheet element will be present in landing report files exported from eLandings. Each permit worksheet element allows a CFEC permit to be specified, so multiple worksheet items indicate permit stacking.- Item_number
The item_number element is just the sequential permit item number for the report. However, item numbers may have a break in their sequence if a report is submitted, and then a permit item is deleted. - Cfec_permit
The cfec_permit element is the entire CFEC permit information needed to identify the permit.- Fishery
The fishery element is the fishery code on the CFEC permit card. - Permit_number
The permit_number element is is the unique permit number on the CFEC card. It is a five digit number followed by one alphabetic check character. - Year_seq
The year_seq element is is the year and card sequence from the CFEC card. It is a two digit year, a two digit sequence number, and one alphabetic check character.
- Fishery
- Mag_stripe_read
The mag_stripe_read element identifies identifies whether the CFEC permit date was read into the eLandings system by swiping the magnetic stripe on the CFEC permit card.
- Item_number
...