Technical Specifications (Licensee)
Technical Specifications (Licensee)
Table Of Contents
FTA 1
Data Submission 2
Overview 3
FTA Common Elements 10
XML Schema v9 14
Submission Item 15
Harvest Application (CP) 16
Harvest Application (No CP) 81
Range Tenure 142
Road Tenure 164
Timber Licence 202
Timber Licence Elimination 217
Data Mapping Table Key 230
Change History from Schema 8 to Schema 9 231
General 231
Harvest Application with CP 231
Harvest Application No CP 231
Roads 232
Timber Licence 232
Timber Licence Elimination 232
Previous Versions 244
Code Tables 255
Error Messages 282
FTA
Welcome to FTA Submission Technical Specifications.
This website is a guide for creating submissions for the FTA application. It is intended to assist submission authors in producing valid submission documents and as a guide for developers that will be creating automated tools for this purpose.
The components of a valid FTA submission are described in the order they should appear in a submission document and examples are provided for each. A Business Rules section is also included that discusses the business rules, regulations and restrictions in regards to the data being submitted.
Contents of this website is available in .pdf format and may be downloaded here
[pic]Note: To ensure that you see the most up to date copy of these specs, please set your browser to refresh upon every visit to this page.
(On IE: Tools / Internet Options / Temporary Internet Files - Settings / click top radio button - Every visit to the Page)
Data Submission
Overview
Overview
This website is a guide for creating submissions for the Forest Tenure Application (FTA). It is intended to assist submission authors in producing valid submission documents and as a guide for developers that will be creating automated tools for this purpose.
Important: Although every effort has been taken to ensure the accuracy of this website, it should be noted that the rapid development cycle has necessitated many changes in a short time period. The schema, sample files and this guide are intended to be in synch with regard to their content, however in the case of discrepancies the schema should be consulted as the correct and final authority.
What is a Submission?
|A submission is an XML document that is uploaded via the ESF website for processing by application |[pic] |
|specific systems, in this case FTA. It allows both attribute and spatial data to be submitted in a | |
|single file. Spatial data will be embedded using GML. | |
| | |
|A FTA submission document can contain: | |
|CP Applications and Amendments | |
|File Based Tenures Applications and Amendments (No CP) | |
|Road Permit Applications and Amendments (Inc. Forest Service Roads and SUP Roads) | |
|Range Tenures | |
|Timber Licence | |
|Timber Licence Eliminations | |
Who Can Make a Submission?
There are four candidate groups that will be submitting data electronically:
1. BC Timber Sales
2. Industry (Major Licensee or delegate)
3. Districts
4. Ministry of Sustainable Resource Mgmt
Though it is not strictly necessary, users who are familiar with XML, GML, or HTML should find the creation of these documents very straightforward.
If you are unfamiliar with these acronyms, the ESF website () has some resources that may be helpful.
How Do I Make a Submission?
1. Create the document, following the instructions in this guide (samples are provided in this document and are available for download on the website)
2. Save it as an .XML file (a text file with an extension of .XML)
3. Logon and upload the document via the ESF submission website
The document structure and geometry data will be validated upon upload. You’ll be notified if there’s a problem so that you can fix it and try again.
Once it’s passed the initial validation, the submission is sent to the appropriate business system that will apply further checks to the actual content. If those fail, the submitter will receive a message through the website requesting it be fixed.
Layout
The components of a valid FTA submission are described in the order they should appear in a submission document. Common elements and specific data types that are referenced throughout are discussed in the Data Types section. Each component section contains detailed descriptions of the individual fields and examples.
Document Structure
The diagram below describes the overall structure of an FTA submission document. Not all components are mandatory and some can be represented more than once, e.g. multiple submission items can be contained within a single document.
Separate sections of this document are dedicated to each component.
[pic]
XML? GML?
Extensible Markup Language (XML) is a language for documents that contain structured data. It uses a format that is easily readable by both humans and computers and is a standard supported by the W3C, the standards body for the World Wide Web. Many tools are available for authoring, translating and viewing XML documents.
Geography Markup Language (GML) is a subset of XML that allows for the encoding of geographic information; including both the spatial and non-spatial properties of geographic features.
FTA Common Elements
Geometry
Several components accept geometry data. This can be comprised of metadata (mof:spatialMetaData) and gml (rst:extentOf) components. The format for this data is the same for all instances, although the acceptable types vary by component. For FTA, the acceptable types for each component are:
|COMPONENT |GEOMETRY TYPE |
|Harvest Application (CP) |Polygon or MultiPolygon |
|Harvest Application (No CP) |Polygon or MultiPolygon |
|Road Permit |LineString or MultiLinestring |
|Range Tenure |Polygon or MultiPolygon |
|Timber Licence |Polygon or MultiPolygon |
|Timber Licence Elimination |Polygon or MultiPolygon |
Some geometry content allows for the capture of spatial metadata as well. Metadata is information about the geometry data itself, for example how it was captured. The tags for both components are mandatory but the content is optional.
GML & extentOf
Geometry is represented as GML; the rst:extentOf tags are used to delineate the GML tags. The following exemplify the syntax for all geometry types that are acceptable in a FTA submission document.
Spatial Coordinate Systems
ESF requires spatial objects in submissions to specify the coordinate system used to represent them. The "srsName" attribute is used to define this. Note that it is permissible (but not recommended) that different coordinate systems can be used within the same submission. Refer to the following table in the Code Tables for valid entries.
|SRS Name |Coordinate System |
|EPSG:4326 |WGS 84 (Geographics) |
|EPSG:32607 |WGS 84 / UTM zone 7N |
|EPSG:32608 |WGS 84 / UTM zone 8N |
|EPSG:32609 |WGS 84 / UTM zone 9N |
|EPSG:32610 |WGS 84 / UTM zone 10N |
|EPSG:32611 |WGS 84 / UTM zone 11N |
|EPSG:42102 |NAD83 BC Albers |
|EPSG:4269 |NAD83 (Geographics) |
|EPSG:26907 |NAD83 / UTM zone 7N |
|EPSG:26908 |NAD83 / UTM zone 8N |
|EPSG:26909 |NAD83 / UTM zone 9N |
|EPSG:26910 |NAD83 / UTM zone 10N |
|EPSG:26911 |NAD83 / UTM zone 11N |
Note: GML supports two fields which, excepting Charts, are not presented for use in this document or the sample file: and . They are noted here since they exist in the schema. They are not required fields and their use is discouraged.
GML Examples
3651.8,1109.5 4056.9,1238.9 3663.0,1514.6 4085.0,1734.0 3674.3,1942.2
2271.0,1000.0 2271.0,2000.0 3271.0,2000.0 3271.0,1000.0 2271.0,1000.0
4586.790988700565,2604.7224576271187 393.268333333333,2315.6079378531076
5301.969011299436,1509.130593220339 4647.657203389831,2011.2768644067799
5591.0835310734465,2011.2768644067799
4525.9247740113,3426.4163559322037 5317.185564971752,3167.734943502825
4632.440649717514,2924.2700847457627 5332.402118644068,2756.8879943502825
2237.7,2513.4 2237.7,3513.4 3237.7,3513.4 3237.7,2513.4 2237.7,2513.4
2737.7,2983.1 3069.6,2983.1 3069.6,3225.1 2737.7,3225.1 2737.7,2983.1
988.7,2524.7 988.7,3524.7 1988.7,3524.7 1988.7,2524.7 988.7,2524.7
XML Schema v9
Submission Item
Submission Item
Required. Submissions must contain at least one submission item. Note that the document can contain multiple submission items, but each one must be contained within its own set of submissionItem tags.
There are six separate types of submission items that can be contained in this document:
1. Harvest Applications and Amendments with CP
2. Harvest Applications and Amendments No CP
3. Road Permit Applications and Amendments (Inc. Forest Service Roads and SUP Roads)
4. Range Tenures
5. Timber Licence
6. Timber Licence Elimination
Harvest Application (CP)
Harvest Application (CP) - Business Rules
Business Rules:
1. If the application is for a new CP then:
1. The supplied Forest File ID must exist
2. The district must be valid and belong to the files admin org unit (region)
3. The supplied cutting permit ID must not already exist
4. The Marking Method must be valid
5. The Marking Instrument must be valid
6. The Cascade Split Code must be valid
7. If a File Type is provided and the existing code file type code is U1 or U2 then allow a BCTS file as defined in BCTS_FILE_TYPE_CODE.
2. If purpose to amend an existing CP then:
1. The supplied file CP must exist
2. The licensee making the submission must own CP
3. The amendments reason for the block must be valid
3. Cut Block Validations:
1. If the Cut Block is new then the cut block ID must not exist
2. If the Cut Block is not new then the cut block ID must exist
3. The Owned by File/CP/Block can only be specified if the application is for an A02 or A04 file type. The cut block will be added to the cut block table using values from Owned by File/CP and Block. The values should be for a private mark.
4. A20, A21, A23, A24:
1. For these file types there is no CP Geometry required. The user must be a BCTS user.
|Validation Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for harvest with cp application submissions. Validation is only called after the XML submission has been|
|successfully validated by ESF. This module is implemented as the FTA_XML_VALIDATION.VALIDATE_HARVEST_CP database routine. |
| |
| |
|Interface Parameters |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_parent_record_ind |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_geo_district |
|IN |
|VARCHAR2 |
| |
|p_location |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_cutting_permit_id |
|IN |
|VARCHAR2 |
| |
|p_higher_level_plan_ref |
|IN |
|VARCHAR2 |
| |
|p_salvage_type_code |
|IN |
|VARCHAR2 |
| |
|p_cascade_split_code |
|IN |
|VARCHAR2 |
| |
|p_marking_method_cd |
|IN |
|VARCHAR2 |
| |
|p_markng_instrmnt_cd |
|IN |
|VARCHAR2 |
| |
|p_deciduous_ind |
|IN |
|VARCHAR2 |
| |
|p_catastrophic_ind |
|IN |
|VARCHAR2 |
| |
|p_cruise_based_ind |
|IN |
|VARCHAR2 |
| |
|p_crown_granted_ind |
|IN |
|VARCHAR2 |
| |
|p_hva_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_hva_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_cut_block_id |
|IN |
|VARCHAR2 |
| |
|p_cut_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_cut_block_description |
|IN |
|VARCHAR2 |
| |
|p_amend_reason_st |
|IN |
|VARCHAR2 |
| |
|p_owned_by_file |
|IN |
|VARCHAR2 |
| |
|p_owned_by_cp |
|IN |
|VARCHAR2 |
| |
|p_prov_for_conflict_code |
|IN |
|VARCHAR2 |
| |
|p_planned_gross_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_net_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_harvest_date |
|IN |
|VARCHAR2 |
| |
|p_cruise_volume |
|IN |
|VARCHAR2 |
| |
|p_cut_regulation_code |
|IN |
|VARCHAR2 |
| |
|p_cb_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_cb_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_bcts_org_unit |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_bcts_file_type_ind |
|IN |
|VARCHAR2 |
| |
|p_prev_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
| |
| |
| |
|Validations |
|1. For each cut permit in the file: |
|a. If the cut permit purpose is New then: |
|i. Ensure CP for provided file type is valid. E.g.. File type is either |
|A01,A02,A03,A04,A06,A11,A20,A21,A23,A24,A25,A26,A28,A30,A27,A29,A44,A41,U1,U2,A18,A31 |
|ii. If BCTS org unit provided and file type code is either U1 or U2, then ensure a conversion file type has been provided. |
|iii. If BCTS org unit provided then: |
|1. Validate the BCTS org. |
|2. Ensure the BCTS org matches the BCTS org assigned to the file. |
|3. If assigned file type code is U1 and (supplied file type code is not a minor TSL file type (U1,A24,A23,A21,A20) or supplied file type code is U1) |
|then raise Error “Cannot convert U1 file type code to ”. |
|4. If assigned file type code is U2 and (supplied file type code is not a major TSL file type (A03,A25,A26,A27,U1,U2) or supplied file type is either |
|U1 or U2) then raise Error “Cannot convert U2 file type to ”. |
|5. Provide warning if submitter is not BCTS but has supplied a BCTS office in submission. |
|iv. If BCTS org unit not provided: |
|1. If assigned file type code is U1 or U2 than raise error “Only BCTS may submit U1 or U2 files”. |
|v. Validate the CP |
|1. Duplicate CPs in a file not permitted. |
|2. If file type is not provided then validate that supplied file type is same as that currently assigned to the file. |
|3. If file type IN ('A04','A44','A06','A30'), or tsl minor file type (20,21,23,24,U1): |
|a. If mark is not already assigned: |
|i. If file type code is A06, and second letter in file is not a zero, and length of CP > 1 then raise error “CP can only have one letter. |
|ii. If file type code is A06, and second letter is a zero, and length of CP > 2 then raise error “CP can have max of two letters.” |
|iii. If file type is any other of the above CP can be max of one letter. |
|b. If mark designate is assigned: |
|i. If file type code is A06, then ensure CP length is no greater than 2 digits. |
|ii. If A04/A44 then ensure CP length is no greater than 3 digits. |
|iii. If A30, then ensure CP length is no greater than 1 digits. |
|c. Validate CP formatting: |
|i. Ensure No “I”’s or “O”’s except if file type is A01,A02,A03. |
|ii. Ensure CP does not contain blanks and special characters. |
|iii. If file type is A04,A44,A06 then ensure that CP only contains letters. |
|d. If admin org for file is not same as district supplied in submission then verify that district falls within file’s admin org. |
|e. Ensure that licensee is one of the main or secondary licensee for the file. (location code is irrelevant) |
|f. Validate Codes: |
|i. Cascade split code |
|ii. Marking Method code |
|iii. Marking instrument code. |
|b. If CP application purpose is Amend: |
|i. Validate that file and CP exist. |
|ii. Validate that neither file or CP status is HI. |
|iii. File type code cannot be U1 or U2 for amendments. |
|iv. Validate that existing CP org falls within the supplied CP org |
|v. Verify that licensee supplied owns the CP. |
|1. If BCTS org unit is not supplied and licensee does not own the CP then: |
|a. If valid minor tsl file type then raise error “Client is not the licensee for this mark: |
|b. Otherwise raise error “Client is not the licensee for the CP”. |
|2. If BCTS org unit supplied, ensure that it matches that assigned to the file. |
|vi. Validate the cascade code. |
|c. Validate blocks: |
|i. Validate amendment reason for the blocks (Eg. A –Access Additional Cut blocks, E-Engineering, S-Salvage. |
|ii. Verify that cruise volume is supplied. |
|iii. Ensure that if cut block supplied and file type is A30, that owned-by file and owned-by cp is provided and valid. |
|iv. If owned by file and owned by cp are not provided then block is owned by file/cp. Otherwise block owned by owned by file, owned by cp. |
|v. If cut block purpose is “Amend” then: |
|1. Managed by file must be blank. |
|2. If cut block already exists and owned-by file provided, then verify that owned-by relationship exists with managing CP: If not then raise error: |
|“This block should be submitted under the correct managed by file/cp.” |
|3. If CP purpose is “New”, then: |
|a. Raise error “Cannot amend a block under a new cp. |
|b. If file type is A06, and managed by file/cp not valid then raise error “Block should be submitted under the managed by file/cp”. |
|c. Verify that the cut block exists. If not then if owned by file/cp provided see if block exists under owned by file/cp. If not raise error “Block |
|does not exist”. |
|d. If cut block exists, verify that block status is “HB-Approved for Harvesting”. (Unless for data cleanup) |
|e. If cut block does not exist but owned by file provided, then verify that block is in either “HB”,”LC”, or “S” status. |
|vi. If cut block purpose is “New” |
|1. If managed by file provided and file type is not A06, then raise error “Managed by file is not applicable for this CP application”. |
|2. Verify that cut block does not already exist. |
|3. If owned by file or owned by cp provided then: |
|4. If file type code is either 'A02', 'A04', 'A44', 'A30', 'A28', 'A29' then validate owned by file/cp/block. If file type is not one of the above |
|then raise error “Given file cannot have an Owned by file/cp specified.” |
|5. If managed by file/cp provided then raise error “Managed by File/CP fields are no longer supported. You must submit under the CP managing this |
|block.” |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for harvest with CP application submissions. Processing is called only after the |
|submission has been successfully validated using FTA_XML_VALIDATION.VALIDATE_HARVEST_CP. The processing module is implemented as|
|the FTA_XML_PROCESS.PROCESS_HARVEST_CP database routine. |
| |
| |
|Interface Parameters |
| |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_parent_record_ind |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_geo_district |
|IN |
|VARCHAR2 |
| |
|p_location |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_cutting_permit_id |
|IN |
|VARCHAR2 |
| |
|p_higher_level_plan_ref |
|IN |
|VARCHAR2 |
| |
|p_harvest_type_code |
|IN |
|VARCHAR2 |
| |
|p_salvage_type_code |
|IN |
|VARCHAR2 |
| |
|p_cascade_split_code |
|IN |
|VARCHAR2 |
| |
|p_marking_method_cd |
|IN |
|VARCHAR2 |
| |
|p_markng_instrmnt_cd |
|IN |
|VARCHAR2 |
| |
|p_deciduous_ind |
|IN |
|VARCHAR2 |
| |
|p_catastrophic_ind |
|IN |
|VARCHAR2 |
| |
|p_cruise_based_ind |
|IN |
|VARCHAR2 |
| |
|p_crown_granted_ind |
|IN |
|VARCHAR2 |
| |
|p_hva_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_hva_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_cut_block_id |
|IN |
|VARCHAR2 |
| |
|p_cut_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_cut_block_description |
|IN |
|VARCHAR2 |
| |
|p_amend_reason_st |
|IN |
|VARCHAR2 |
| |
|p_owned_by_file |
|IN |
|VARCHAR2 |
| |
|p_owned_by_cp |
|IN |
|VARCHAR2 |
| |
|p_prov_for_conflict_code |
|IN |
|VARCHAR2 |
| |
|p_planned_gross_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_net_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_harvest_date |
|IN |
|VARCHAR2 |
| |
|p_cruise_volume |
|IN |
|VARCHAR2 |
| |
|p_cut_regulation_code |
|IN |
|VARCHAR2 |
| |
|p_cb_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_cb_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_bcts_org_unit |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
|p_userid |
|IN |
|VARCHAR2 |
| |
|p_timber_mark |
| |
| |
| |
|p_amendment_id |
| |
| |
| |
| |
| |
|Processing |
|1. If CP application purpose is “New”: |
|a. BCTS Requirement: If supplied file type is either U1 or U2 then: |
|i. Update the file type and BCTS org unit, and SB funded indicator for the file. |
|ii. Create an entry in HARVEST_SALE. |
|b. If timber mark is not supplied in submission: |
|i. Generate the timber mark. |
|c. If file type code is A31 then automatically set the small scale salvage indicator to SSS, otherwise use supplied small scale |
|salvage value. |
|d. Calculate the CP area and perimeter from supplied geometry. |
|e. If harvest type code is submission is FSJ then set harvest type is “F-Fort St. John”, otherwise “G-Green”. |
|f. Create the Harvest Authority (CP). |
|g. Create the Hauling Authority (Timber Mark) |
|h. Create the Harvesting/Hauling Authority cross reference entry. (HARVESTING_HAULING_XREF) |
|i. If client number provided is not the district manager, and not the A licensee for the file, then create Harvesting Authority |
|Client entry. |
|j. Create entry for the harvesting authority geometry. |
|k. Crete the harvesting authority amendment. |
|l. Create and entry for the harvesting authority amendment geometry. |
|m. Update the tenure application CP feature with the derived amendment id. |
|2. If cut block purpose is “New”. |
|a. If timber mark is not supplied in the file, then generate the timber mark. |
|b. If owned by file supplied and file type code is either 'A02', 'A04', 'A44', 'A30', 'A28', 'A29': |
|i. Create a timber mark for the owned by file/cp if it does not already exist. |
|ii. Create the hauling authority entry. |
|iii. Create the Harvesting/Hauling Authority cross reference entry. (HARVESTING_HAULING_XREF) |
|iv. Create entry for cut block. |
|v. Create entry in cut block open admin. |
|c. If CP purpose is “New” |
|i. Create the cut block geometry. |
|ii. Create cut block amendment entry. |
|iii. Calculate the cut block area and perimeter. |
|iv. Create the cut block amendment geometry. |
|v. Update the block in the application with the generated block amendment id. |
|d. If CP application purpose is “Amend” and cut block id provided. |
|i. Create the harvest amendment entry. |
|ii. Create cut block amendment geometry |
|iii. Update the block in the application with the generated block amendment id. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. |
| |
| |
| |
| |
Harvest Application (CP) - Field Information
| | | | | |
|Field Specification: |
|Harvest Application (CP) |
|Field Specification: |
|forestFileID |
|fileType |
|applicationDescription |
|district |
|applicationPurpose |
|tenureTerm |
|cuttingPermitID |
|location |
|markingInstrumentCode |
|markingMethodCode |
|deciduousIndicator |
|catastrophicIndicator |
|cruiseGrantedIndicator |
|crownGrantedIndicator |
|higherLevelPlanReference |
|bCTSOffice |
|spatialMetaData |
|salvageTypeCode |
|extentOf -- Optional (Only entered when CP is squared-off or salvageTypeCode is SSS and file is not of these types: A20, A21, |
|A23, A24. ) |
| |
|Cut Block (CP) |
|Mandatory for non-salvage submissions. |
|Field Specification: |
|cutBlockID |
|applicationPurpose |
|blockDescription |
|amendmentReason |
|plannedGrossArea |
|plannedNetArea |
|cruiseVolume |
|plannedHarvestDate |
|ownedByFile |
|ownedByCuttingPermit |
|extentOf -- Optional (Not required for salvage cut blocks of less than 1 hectare.) |
|Data Mappings |
| |
| |
|This document maps the XML elements for this application to the columns in the database where they're stored. |
|Please refer to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no HVA.forest_district |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number HVAC.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code HVAC.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id TAMF.forest_file_id HVA.forest_file_id HA.forest_file_id HS.forest_file_id CB.forest_file_id|
|CBA.forest_file_id CBOA.forest_file_id |
|TA.forest_file_id TAMF.forest_file_id CB.forest_file_id CBA.forest_file_id |
| |
| |
| |
| |
| |
|fileType |
|PFU.file_type_code |
| |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|district |
|HVA.geographic_district |
| |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|tenureTerm |
|HVA.tenure_term |
| |
| |
| |
| |
| |
| |
|cuttingPermitID |
|TAMF.cutting_permit_id CB.cutting_permit_id CBA.cutting_permit_id |
|TAMF.cutting_permit_id CB.cutting_permit_id CBA.cutting_permit_id |
| |
| |
| |
| |
| |
|location |
|TAMF.reference_name |
|HVA.location |
|TAMF.reference_name |
| |
| |
| |
| |
| |
|markingInstrumentCode |
|HA.marking_instrument_code |
| |
| |
| |
| |
| |
| |
|markingMethodCode |
|HA.marking_method_code |
| |
| |
| |
| |
| |
| |
|deciduousIndicator |
|HVA.deciduous_ind |
| |
| |
| |
| |
| |
| |
|catastrophicIndicator |
|HVA.catastrophic_ind |
| |
| |
| |
| |
| |
| |
|cruiseBasedIndicator |
|HVA.cruise_based_ind |
| |
| |
| |
| |
| |
| |
|crownGrantedIndicator |
|HVA.crown_granted_ind |
| |
| |
| |
| |
| |
| |
|BCTSOffice |
|PFU.bcts_org_unit HS.bcts_org_unit |
| |
| |
| |
| |
| |
| |
|dataSourceCode |
|TAMF.data_source_code |
|TAMF.data_source_code |
| |
| |
| |
| |
| |
|captureMethodCode |
|TAMF.capture_method_code |
|TAMF.capture_method_code |
| |
| |
| |
| |
| |
|observationDate |
|TAMF.observation_date |
|TAMF.observation_date |
| |
| |
| |
| |
| |
|dataQualityComment |
|TAMF.data_quality_comment |
|TAMF.data_quality_comment |
| |
| |
| |
| |
| |
|salvageTypeCode |
|HVA.salvage_type_code |
| |
| |
| |
| |
| |
| |
|geometry |
|geometry HVA.geometry HVAA.geometry |
|HVAA.geometry |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
| |
| |
| |
| |
|cutBlockId |
|TAMF.cut_block_id CB.cut_block_id CBA.cut_block_id CBOA.cut_block_id |
|TAMF.cut_block_id CBA.cut_block_id |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|blockDescription |
|TAMF.reference_name |
|TAMF.reference_name |
| |
| |
| |
| |
| |
|regulationCode |
|CB.cut_regulation_code |
| |
| |
| |
| |
| |
| |
|amendmentReason |
|CBA.amend_reason_st |
|CBA.amend_reason_st |
| |
| |
| |
| |
| |
|plannedGrossArea |
|CBA.est_gross_blk_area |
|CBOA.planned_gross_block_area |
|CBA.est_gross_blk_area |
| |
| |
| |
| |
| |
|plannedNetArea |
|CBA.est_net_blk_area |
|CBOA.planned_net_block_area |
|CBA.est_net_blk_area |
| |
| |
| |
| |
| |
|cruiseVolume |
|CBA.cruise_volume |
|CBA.cruise_volume |
| |
| |
| |
| |
| |
|plannedHarvestDate |
|CBOA.planned_harvest_date |
| |
| |
| |
| |
| |
| |
|ownedByFile |
|TAMF.owned_by_file |
|HA.forest_file_id |
|CB.forest_file_id |
|CBA.forest_file_id |
|CBOA.forest_file_id |
|TAMF.owned_by_file |
| |
| |
| |
| |
| |
|ownedByCuttingPermit |
|TAMF.owned_by_cp |
|CB.cutting_permit_id |
|CBA.cutting_permit_id |
|CBOA.cutting_permit_id |
|TAMF.owned_by_cp |
| |
| |
| |
| |
| |
|dataSourceCode |
|TAMF.data_source_code |
|TAMF.data_source_code |
| |
| |
| |
| |
| |
|captureMethodCode |
|TAMF.capture_method_code |
|TAMF.capture_method_code |
| |
| |
| |
| |
| |
|observationDate |
|TAMF.observation_date |
|TAMF.observation_date |
| |
| |
| |
| |
| |
|dataQualityComment |
|TAMF.data_quality_comment |
|TAMF.data_quality_comment |
| |
| |
| |
| |
| |
|geometry |
|CB.geometry |
|CBA.geometry |
|CBA.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Harvest Application (CP) - Cut Block (CP)
Description:
At least one cut block must be included for all submissions except when the cutting permit is a small scale salvage.
Harvest Application (CP) - Cut Block (CP) - amendmentReason
XML Schema (subset)
Field Information
| | |
|amendmentReason: |
|Description: | The reason for amending a block. |
| |E - Engineering |
| |F - Forest service initiated |
| |S - Salvage |
| |A - Access Additional Cut Blocks |
| |This value is mandatory for amendments. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - applicationPurpose
XML Schema (subset)
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew block or an (A)mendment of an existing block. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |if cutblock purpose is 'N'ew then |
| |- cutblock must not exist |
| |if cutblock purpose is 'A'mend then |
| |- cutblock must exist and must be in HB status |
| |if CP file type is A02,A04,A30,A28,A29 then |
| |- owned by file/cp can be specified |
| |- and the file type of the owned by must be A06, B08,B09 or B14 |
| |- owned by file/cp can be specified |
| |- if owned by file/cp entered then file must exist |
| |- it must be the same district as the district that is managing it |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - blockDescription
XML Schema (subset)
Field Information
| | |
|blockDescription: |
|Description: |A description of the location of the feature |
|Data Type: |String |
|Total Length: |120 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - cruiseVolume
XML Schema (subset)
Field Information
| | |
|cruiseVolume: |
|Description: | The cruise volume for the amendment. |
|Data Type: |Number |
|Total Length: |13,2 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - cutBlockID
XML Schema (subset)
Field Information
| | |
|cutBlockID: |
|Description: |The cut block ID. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - ownedByCuttingPermit
XML Schema (subset)
Field Information
| | |
|ownedByCuttingPermit: |
|Description: |For A02 or A04, identifies the CP of the private mark for any blocks on private land. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - ownedByFile
XML Schema (subset)
Field Information
| | |
|ownedByFile: |
|Description: |For A02 or A04, identifies the file of the private mark for any blocks on private land. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |- owned by file/cp can be specified |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - plannedGrossArea
XML Schema (subset)
Field Information
| | |
|plannedGrossArea: |
|Description: |The planned gross area of the block. |
| |This is only required if there is no geometry for the cut block. If there is geometry, this value will be |
| |overwritten with the area of the geometry. |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - plannedHarvestDate
XML Schema (subset)
Field Information
| | |
|plannedHarvestDate: |
|Description: |The date harvesting is planned to start |
|Data Type: |Date |
|Total Length: |N/A |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - plannedNetArea
XML Schema (subset)
Field Information
| | |
|plannedNetArea: |
|Description: |The planned net area of the block. |
| |This value must be less than or equal to |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - Cut Block (CP) - regulationCode
XML Schema (subset)
Field Information
| | |
|regulationCode: |
|Description: |Code defining the regulation the cut block is harvested under. |
| |Currentyly the only valid values are BBR (Bark Bettle Regulation) or blank. |
| |This value is mutually exclusive of salvageTypeCode on the CP. ie. if the CP has a salvage TypeCode of SSS, |
| |this must be blank. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP)
Description:
Used for major tenures (A file types) where the harvesting authority is defined by a cutting permit. Cutting Permits may include one or more cut-blocks. For these types of submissions the FTA file must always exist.
The FTA File Types and features that can be submitted using this type of application include:
|Feature |File Type |
|Forest Licence Cut Block |A01,A41 |
|Forest Licence Cutting Permit |A01,A41 |
|Tree Farm Licence Cut Block |A02 |
|Tree Farm Licence Cutting Permit |A02 |
|Timber Sale Licence Major Cut Block |A03 |
|Timber Sale Licence Major Cutting |A03 |
|Permit | |
|Wood Lot Licence Cut Block |A04,A44 |
|Wood Lot Licence Cutting Permit |A04,A44 |
|Timber Licence Cut Block |A06 |
|Timber Licence Cutting Permit |A06 |
|Non-Replaceable Forest Licence |A25 |
|Timber Sale Licence Minor Cutting |A26,A27 |
|Permit | |
|Timber Sale Licence Minor Cut Block |A26,A27 |
|Community Forest Cut Block |A28,A29 |
|Community Forest Cutting Permit |A28,A29 |
|Consolidated Timber Licence |A30 |
|Community Salvage |A31 |
|Timber Sale Licence Cut Block - |A20,A21,A23,*A24 |
|Multi-Mark | |
|Timber Sale Licence - Multi-Mark |A20,A21,A23,*A24 |
Each cutting permit submission must include at least one cut-block. Amendments to cutting permits must include at least one cut block, unless they fall under one of these conditions:
• The cutting permit is a small scale salvage (identified by a non-null salvage type code, either in the submission for a new CP application or in the HARVEST_AUTHORITY table for amendments).
• The cutting permit includes at least one Bark Beetle Regulation cut block (identified by a non-null cut regulation code, either in the submission for new applications or in CUT_BLOCK table for amendments.
In these cases, a submission may be made to update the cutting permit boundary only.
Harvest Application (CP) - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |A description for the cutting permit application. |
|Data Type: |String |
|Total Length: |255 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - applicationPurpose
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates wether it is a new (N) application or an amendment (A) of an existing cutting permit. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |If purpose is 'N' for new CP application then |
| |- must be a valid file id |
| |- file must exist for that CP |
| |- district must belong/within the file's admin org unit |
| |- CP must NOT exist |
| |- marking method must be valid |
| |- marking instrument must be valid |
| |- cascade split code must be valid |
| |- if a file type code is provided and file type of given file is a U1 or U2 allow only BCTS file type |
| |- cascade split code must be valid |
| |- bcts org must match the bcts org assigned to the file |
| |- only BCTS may submit a BCTS file type (U1/U2) |
| |- if licensee is one of the main/secondary licensee for file then LOCATION CODE does not have to be the same |
| |If purpose is 'A' for amendment of CP then |
| |- file/cp must exist |
| |- File Status or Mark Status must be 'HI' |
| |- licensee must own the cp |
| |- File Type code must NOT be U1 |
| |- must be a valid district |
| |- Licensee must own the CP |
| |- amendment reason must be valid |
| |- bcts org must match the bcts org assigned to the file |
| |- cascade must be valid |
| |- amendment reason must be valid |
| |- A30 must be submitted with Owned by |
|Notes: |None |
Harvest Application (CP) - bCTSOffice
XML Schema (subset)
inapplicable
Field Information
| | |
|bCTSOffice: |
|Description: |The MOF organization unit code of the office that is making the submission. This will be used to deem the |
| |submission BCTS funded. |
| |This value is mandatory for BCTS submissions. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: | |
|Notes: |None |
Harvest Application (CP) - catastrophicIndicator
XML Schema (subset)
inapplicable
Field Information
| | |
|catastrophicIndicator: |
|Description: |Indicates if the damage to the stand of timber is catastrophic. Otherwise it is endemic. |
| |This value is mandatory for new applications. This value is ignored for amendments. |
|Data Type: |Boolean |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - crownGrantedIndicator
XML Schema (subset)
inapplicable
Field Information
| | |
|crownGrantedIndicator: |
|Description: |Indicator to signify whether the land that the timber mark pertains to has a verifiable crown grant document. |
| |This value is mandatory for new applications. This value is ignored for amendments. |
|Data Type: |Boolean |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - cruiseBasedIndicator
XML Schema (subset)
inapplicable
Field Information
| | |
|cruiseBasedIndicator: |
|Description: |Indicates whether a cruise was used for billing purposes. |
| |This value is mandatory for new applications. This value is ignored for amendments. |
|Data Type: |Boolean |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - cuttingPermitID
XML Schema (subset)
inapplicable
Field Information
| | |
|cuttingPermitID: |
|Description: |The cutting permit ID. BCTS will supply a CP for files they use to call multi-mark (A20-A24). The CP will be |
| |used to determine when to create another mark and which blocks are associated with it. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - deciduousIndicator
XML Schema (subset)
inapplicable
Field Information
| | |
|deciduousIndicator: |
|Description: |Indicates whether the timber mark is primarily for harvesting deciduous species. Otherwise, coniferous. |
| |This value is mandatory for new applications. This value is ignored for amendments. |
|Data Type: |Boolean |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The geographical district that the cutting permit resides in. This is most often the same as the |
| |administrative district but in certain situations can be different. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - fileType
XML Schema (subset)
inapplicable
Field Information
| | |
|fileType: |
|Description: |The file type of the submission. This is only used is the BCTS Office is not null. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |must be a valid file type |
|Notes: |None |
Harvest Application (CP) - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The forest file ID of the cutting permit. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |must be a valid file id |
|Notes: |None |
Harvest Application (CP) - higherLevelPlanReference
XML Schema (subset)
inapplicable
Field Information
| | |
|higherLevelPlanReference: |
|Description: |Reference to a higher level plan, ie Sustainable Forest Management Plan. |
|Data Type: |String |
|Total Length: |30 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - location
XML Schema (subset)
inapplicable
Field Information
| | |
|location: |
|Description: |A location description of the CP area. E.g. Wilson Creek. Gets stored in the reference name column in the |
| |Tenure Application Map Feature table. |
|Data Type: |String |
|Total Length: |50 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - markingInstrumentCode
XML Schema (subset)
inapplicable
Field Information
| | |
|markingInstrumentCode: |
|Description: |Code indicating the means of marking the timber for identification to the timber mark, eg. hammer, paint. |
| |B - Paint and/or Crayon |
| |C - Crayon |
| |H - Hammer |
| |P - Paint |
| |T - Tag |
| |This is mandatory for new applications |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |- marking instrument must be valid |
|Notes: |None |
Harvest Application (CP) - markingMethodCode
XML Schema (subset)
inapplicable
Field Information
| | |
|markingMethodCode: |
|Description: |Code indicating the method of marking the truckload of harvested timber. |
| |0 - 100% Marking |
| |1 - 100% One End |
| |2 - 2 Marks Front, 2 on Sides |
| |3 - 2 Marks Front, 2 on Sides to Site; 100% at Site |
| |4 - Four Corner Marking |
| |5 - 4 Corner Marking to Site; 100% at Site |
| |8 - Eight Corner Marking |
| |A - 35% With Mark Painted Orange on Each Side of Load |
| |B - 35% With Mark Painted Blue on Each Side of Load |
| |C - 20% With 16 Log Minimum |
| |D - Bottom Tier Front and Back on Area, 100% at Scale Site |
| |E - Exempt From Marking |
| |S - Full, Standard Marking |
| |This value is mandatory for new applications. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |- marking method must be valid |
|Notes: |None |
Harvest Application (CP) - salvageTypeCode
XML Schema (subset)
inapplicable
Field Information
| | |
|salvageTypeCode: |
|Description: |Indicates the type of salvage. |
| |Currently the only valid values are SSS (Small Scale Salvage) or blank. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (CP) - tenureTerm
XML Schema (subset)
inapplicable
Field Information
| | |
|tenureTerm: |
|Description: |The term of the tenure in months. |
|Data Type: |Integer |
|Total Length: |4 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP)
Harvest Application (No CP) - Business Rules
Business Rules:
1. If the application is for a new tenure:
1. The file type code must be valid
2. The geographic district must be valid
3. Type Management Unit Type / Unit must be valid
4. The amendment reason must be valid if the file type is S01, B04, B05 or B06.
5. A BCTS org unit can only be provided if the file type is for B20, B21 or B23.
6. If a file type code is provided and the existing file type of the provided Forest File ID is U1 or U2, then the file type must be a BCTS file type as defined in BCTS_FILE_TYPE_CODE.
2. If the application is to amend a tenure then:
1. The supplied file must exist.
2. The licensee must own the file.
3. The amendment reason on the block must be valid.
3. Cut Block Business Rules:
1. If the application purpose on the cut block is New then the cut block ID must not exist.
2. The the application purose on the cut block is amend then the cut block ID must exist.
|Validation Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for harvest with cp application submissions. Validation is only called after the XML submission has been|
|successfully validated by ESF. This module is implemented as the FTA_XML_VALIDATION.VALIDATE_HARVEST_CP database routine. |
| |
| |
|Interface Parameters |
|Name |
|Direction |
|DataType |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_parent_record_ind |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_harvest_type_code |
|IN |
|VARCHAR2 |
| |
|p_harvesting_authority_id |
|IN |
|VARCHAR2 |
| |
|p_higher_level_plan_ref |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_geo_district |
|IN |
|VARCHAR2 |
| |
|p_location |
|IN |
|VARCHAR2 |
| |
|p_refer_to_file_no |
|IN |
|VARCHAR2 |
| |
|p_mgmt_unit_type |
|IN |
|VARCHAR2 |
| |
|p_mgmt_unit_id |
|IN |
|VARCHAR2 |
| |
|p_purpose_code |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_cascade_split_code |
|IN |
|VARCHAR2 |
| |
|p_hva_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_hva_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_cut_block_id |
|IN |
|VARCHAR2 |
| |
|p_cut_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_cut_block_description |
|IN |
|VARCHAR2 |
| |
|p_prov_for_conflict_code |
|IN |
|VARCHAR2 |
| |
|p_planned_gross_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_net_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_harvest_date |
|IN |
|VARCHAR2 |
| |
|p_cruise_volume |
|IN |
|VARCHAR2 |
| |
|p_cut_regulation_code |
|IN |
|VARCHAR2 |
| |
|p_reforest_decl_type_code |
|IN |
|VARCHAR2 |
| |
|p_amend_reason_st |
|IN |
|VARCHAR2 |
| |
|p_cb_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_cb_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_bcts_org_unit |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
| |
| |
| |
|Validations |
|1. For each cut permit in the file: |
|a. If the cut permit purpose is New then: |
|i. Ensure CP for provided file type is valid. E.g.. File type is either |
|A01,A02,A03,A04,A06,A11,A20,A21,A23,A24,A25,A26,A28,A30,A27,A29,A44,A41,U1,U2,A18,A31 |
|ii. If BCTS org unit provided and file type code is either U1 or U2, then ensure a conversion file type has been provided. |
|iii. If BCTS org unit provided then: |
|1. Validate the BCTS org. |
|2. Ensure the BCTS org matches the BCTS org assigned to the file. |
|3. If assigned file type code is U1 and (supplied file type code is not a minor TSL file type (U1,A24,A23,A21,A20) or supplied file type code is U1) |
|then raise Error "Cannot convert U1 file type code to ". |
|4. If assigned file type code is U2 and (supplied file type code is not a major TSL file type (A03,A25,A26,A27,U1,U2) or supplied file type is either |
|U1 or U2) then raise Error "Cannot convert U2 file type to ". |
|5. Provide warning if submitter is not BCTS but has supplied a BCTS office in submission. |
|iv. If BCTS org unit not provided: |
|1. If assigned file type code is U1 or U2 than raise error "Only BCTS may submit U1 or U2 files". |
|v. Validate the CP |
|1. Duplicate CPs in a file not permitted. |
|2. If file type is not provided then validate that supplied file type is same as that currently assigned to the file. |
|3. If file type IN ('A04','A44','A06','A30'), or tsl minor file type (20,21,23,24,U1): |
|a. If mark is not already assigned: |
|i. If file type code is A06, and second letter in file is not a zero, and length of CP > 1 then raise error "CP can only have one letter. |
|ii. If file type code is A06, and second letter is a zero, and length of CP > 2 then raise error "CP can have max of two letters." |
|iii. If file type is any other of the above CP can be max of one letter. |
|b. If mark designate is assigned: |
|i. If file type code is A06, then ensure CP length is no greater than 2 digits. |
|ii. If A04/A44 then ensure CP length is no greater than 3 digits. |
|iii. If A30, then ensure CP length is no greater than 1 digits. |
|c. Validate CP formatting: |
|i. Ensure No "I"'s or "O"'s except if file type is A01,A02,A03. |
|ii. Ensure CP does not contain blanks and special characters. |
|iii. If file type is A04,A44,A06 then ensure that CP only contains letters. |
|d. If admin org for file is not same as district supplied in submission then verify that district falls within file's admin org. |
|e. Ensure that licensee is one of the main or secondary licensee for the file. (location code is irrelevant) |
|f. Validate Codes: |
|i. Cascade split code |
|ii. Marking Method code |
|iii. Marking instrument code. |
|b. If CP application purpose is Amend: |
|i. Validate that file and CP exist. |
|ii. Validate that neither file or CP status is HI. |
|iii. File type code cannot be U1 or U2 for amendments. |
|iv. Validate that existing CP org falls within the supplied CP org |
|v. Verify that licensee supplied owns the CP. |
|1. If BCTS org unit is not supplied and licensee does not own the CP then: |
|a. If valid minor tsl file type then raise error "Client is not the licensee for this mark: |
|b. Otherwise raise error "Client is not the licensee for the CP". |
|2. If BCTS org unit supplied, ensure that it matches that assigned to the file. |
|vi. Validate the cascade code. |
|c. Validate blocks: |
|i. Validate amendment reason for the blocks (Eg. A -Access Additional Cut blocks, E-Engineering, S-Salvage. |
|ii. Verify that cruise volume is supplied. |
|iii. Ensure that if cut block supplied and file type is A30, that owned-by file and owned-by cp is provided and valid. |
|iv. If owned by file and owned by cp are not provided then block is owned by file/cp. Otherwise block owned by owned by file, owned by cp. |
|v. If cut block purpose is "Amend" then: |
|1. Managed by file must be blank. |
|2. If cut block already exists and owned-by file provided, then verify that owned-by relationship exists with managing CP: If not then raise error: |
|"This block should be submitted under the correct managed by file/cp." |
|3. If CP purpose is "New", then: |
|a. Raise error "Cannot amend a block under a new cp. |
|b. If file type is A06, and managed by file/cp not valid then raise error "Block should be submitted under the managed by file/cp". |
|c. Verify that the cut block exists. If not then if owned by file/cp provided see if block exists under owned by file/cp. If not raise error "Block |
|does not exist". |
|d. If cut block exists, verify that block status is "HB-Approved for Harvesting". (Unless for data cleanup) |
|e. If cut block does not exist but owned by file provided, then verify that block is in either "HB","LC", or "S" status. |
|vi. If cut block purpose is "New" |
|1. If managed by file provided and file type is not A06, then raise error "Managed by file is not applicable for this CP application". |
|2. Verify that cut block does not already exist. |
|3. If owned by file or owned by cp provided then: |
|4. If file type code is either 'A02', 'A04', 'A44', 'A30', 'A28', 'A29' then validate owned by file/cp/block. If file type is not one of the above |
|then raise error "Given file cannot have an Owned by file/cp specified." |
|5. If managed by file/cp provided then raise error "Managed by File/CP fields are no longer supported. You must submit under the CP managing this |
|block." |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for harvest No CP application submissions. Processing is called only after the |
|submission has been successfully validated using FTA_XML_VALIDATE.VALIDATE_FILE_NO_CP. The processing module is implemented as |
|the FTA_XML_PROCESS.PROCESS_FILE_NO_CP database routine. |
| |
| |
|Interface Parameters |
| |
|Name |
|Direction |
|DataType |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_parent_record_ind |
|IN |
|VARCHAR2 |
| |
|p_harvesting_authority_id |
|IN |
|VARCHAR2 |
| |
|p_higher_level_plan_ref |
|IN |
|VARCHAR2 |
| |
|p_harvest_type_code |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_geo_district |
|IN |
|VARCHAR2 |
| |
|p_location |
|IN |
|VARCHAR2 |
| |
|p_refer_to_file_no |
|IN |
|VARCHAR2 |
| |
|p_mgmt_unit_type |
|IN |
|VARCHAR2 |
| |
|p_mgmt_unit_id |
|IN |
|VARCHAR2 |
| |
|p_purpose_code |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_cascade_split_code |
|IN |
|VARCHAR2 |
| |
|p_hva_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_hva_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_cut_block_id |
|IN |
|VARCHAR2 |
| |
|p_cut_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_cut_block_description |
|IN |
|VARCHAR2 |
| |
|p_prov_for_conflict_code |
|IN |
|VARCHAR2 |
| |
|p_planned_gross_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_net_block_area |
|IN |
|VARCHAR2 |
| |
|p_planned_harvest_date |
|IN |
|VARCHAR2 |
| |
|p_cruise_volume |
|IN |
|VARCHAR2 |
| |
|p_cut_regulation_code |
|IN |
|VARCHAR2 |
| |
|p_reforest_decl_type_code |
|IN |
|VARCHAR2 |
| |
|p_amend_reason_st |
|IN |
|VARCHAR2 |
| |
|p_cb_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_cb_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_bcts_org_unit |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_userid |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|INOUT |
|VARCHAR2 |
| |
|p_timber_mark |
|INOUT |
|VARCHAR2 |
| |
|p_amendment_id |
|INOUT |
|VARCHAR2 |
| |
| |
| |
|Processing |
|1. If harvest type code is “FSJPPR” then set harvest type code to F-Fort St. John, else G-Green. |
|2. If application purpose is “New” then: |
|a. If forest file id is not null then: |
|b. If file type code for supplied file is U1 and submission provided file type code is null then raise error “ cannot be converted to a blank file type”. |
|c. If file type specified the change file type from U1, and set the file status to PE. |
|d. If file is null then: |
|i. Generate the file. |
|ii. Create entry in PROV_FOREST_USE. |
|iii. Create entry in HARVEST_SALE. |
|e. If timber mark is null then: |
|i. Determine if licensee for file already exists: |
|1. If yes, then update FOR_CLIENT_LINK setting A-licensee to C-Previous Main licensee, and create new A-licensee entry in |
|FOR_CLIENT_LINK for supplied client. |
|f. Create entry in tenure term. |
|g. If file type is S01 or S02, create entry in SPEC_USE_PERMIT. |
|h. If file type is valid licence to cut, (B04,B05,B06,B07), then create entry in LICENCE_TO_CUT. |
|i. If file type codes starts with A or B, then: |
|i. If harvest type code is not “G-Green” then: |
|1. Generate Timber Mark |
|2. Validate timber mark. If timber mark already used then generate error “Timber mark already exists”. |
|j. If purpose code is SS and file type code is B04 or B07 then set salvage type to Small Scale Salvage. |
|k. Calculate harvest area and perimeter from supplied geometry. |
|l. Create the harvest authority. |
|m. Create the hauling authority. |
|n. Create the harvesting/hauling xref entry. |
|o. Create CP geometry (except for S01,S02) |
|p. Create Harvest authority amendment. |
|q. Create CP amendment geometry. |
|r. Update CP feature in tenure application with generated amendment_id. |
|s. Calculate cut block area and perimeter from supplied geometry. |
|t. If application purpose is “N” then create special use geometry. |
|u. Create special use amendment geometry. |
|v. If cut block purpose is “New” and cut block id is not null then: |
|i. Create entry in CUT_BLOCK |
|ii. Create entry in CUT_BLOCK_OPEN_ADMIN |
|iii. If file type not S01,S02,B03 then: |
|1. if application purpose is “New” then create entry in CUT_BLOCK_GEOM. |
|iv. Create entry in HARVEST_AMEND |
|v. Calculate cut block area and perimeter from supplied geometry. |
|vi. Create entry in CUT_BLOCK_AMEND_GEOM. |
|vii. Update block in tenure application with generated amendment_id. |
|w. If application purpose is “Amend” and cut block id is not null then: |
|x. If valid single mark type code (B01,B02,B04,B05,B06,B07,B20,B21,B22,B23) then : |
|i. If file type is not B02 then: |
|1. Create entry in HARVEST_AMEND |
|2. Create entry in CUT_BLOCK_AMEND_GEOM. |
|3. Update block in tenure application with generated amendment_id. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. |
| |
| |
| |
| |
Harvest Application (No CP) - Field Information
| | | | | |
|Field Specification: |
|Harvest Application (No CP) |
|Field Specification: |
|forestFileID |
|fileType |
|applicationDescription |
|district |
|managementUnitType |
|managementUnitID |
|applicationPurpose |
|location |
|tenureTerm |
|referToFileNumber |
|blockID |
|purposeCode |
|higherLevelPlanReference |
|licenseeHarvestingAuthorityID |
|licenceRegulationCode |
|bCTSOffice |
|spatialMetaData -- Optional |
|extentOf -- Mandatory |
|cutBlockMember -- Conditional (Mandatory for all but Christmas tree permits or Special Use permits) |
| |
|Cut Block (No CP) |
|Field Specification: |
|spatialMetaData -- Optional |
|cutBlockID |
|applicationPurpose |
|blockDescription |
|regulationCode |
|amendmentReason |
|plannedGrossArea |
|plannedNetArea |
|cruiseVolume |
|plannedHarvestDate |
|extentOf -- Mandatory |
|Data Mappings |
| |
|Description |
|This document maps the XML elements for this application to the columns in the database where they're stored. Please refer|
|to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no |
|HVA.forest_district |
|SUP.admin_forest_dist |
|PFU.forest_region |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number |
|FFC.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code |
|FFC.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id |
|TAMF.forest_file_id |
|PFU.forest_file_id |
|HVA.forest_file_id |
|HA.forest_file_id |
|HS.forest_file_id |
|CB.forest_file_id |
|CBA.forest_file_id |
|TT.forest_file_id |
|FFC.forest_File_id |
|SUP.forest_file_id |
|LTC.forest_file_id |
|LUG.forest_file_id |
|LUAG.forest_file_id |
|CBOA.forest_file_id |
|TA.forest_file_id |
|TAMF.forest_file_id |
|CB.forest_file_id |
|CBA.forest_file_id |
|LUG.forest_file_id |
|LUAG.forest_file_id |
| |
| |
| |
| |
| |
|fileType |
|PFU.file_type_code |
| |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|district |
|HVA.geographic_district |
| |
| |
| |
| |
| |
| |
|managementUnitType |
|TAMF.management_unit_number |
|PFU.management_unit_type |
|HVA.management_unit_type_code |
|TAMF.management_unit_number |
| |
| |
| |
| |
| |
|managementUnitID |
|TAMF.management_unit_block |
|PFU.management_unit_id |
|HVA.management_unit_id |
|TAMF.management_unit_block |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|location |
|TAMF.reference_name |
|HVA.location |
|TAMF.reference_name |
| |
| |
| |
| |
| |
|tenureTerm |
|TT.tenure_term |
|HVA.tenure_term |
| |
| |
| |
| |
| |
| |
|referToFileNumber |
|TAMF.refer_to_file_number_desc |
|TAMF.refer_to_file_number_desc |
| |
| |
| |
| |
| |
|blockID |
|TAMF.map_block_id |
|TAMF.map_block_id |
| |
| |
| |
| |
| |
|purposeCode |
|SUP.special_use_code OR |
|LTC.licence_to_cut_cd |
| |
| |
| |
| |
| |
| |
|higherLevelPlanReference |
|HVA.higher_level_plan_reference |
| |
| |
| |
| |
| |
| |
|licenseeHarvestAuthorityID |
|HVA.harvesting_authority_id |
| |
| |
| |
| |
| |
| |
|licenceRegulationCode |
|HVA.harvest_type_code |
| |
| |
| |
| |
| |
| |
|BCTSOffice |
|PFU.bcts_org_unit |
|HS.bcts_org_unit |
| |
| |
| |
| |
| |
| |
|dataSourceCode |
|TAMF.data_source_code |
|TAMF.data_source_code |
| |
| |
| |
| |
| |
|captureMethodCode |
|TAMF.capture_method_code |
|TAMF.capture_method_code |
| |
| |
| |
| |
| |
|observationDate |
|TAMF.observation_date |
|TAMF.observation_date |
| |
| |
| |
| |
| |
|dataQualityComment |
|TAMF.data_quality_comment |
|TAMF.data_quality_comment |
| |
| |
| |
| |
| |
|geometry |
|HVA.geometry |
|HVAA.geometry OR |
|LUG.geometry |
|LUAG.geometry |
|HVAA.geometry OR |
|LUAG.geometry |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
| |
| |
| |
| |
|cutBlockId |
|TAMF.cut_block_id |
|TAMF.cut_block_id |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|blockDescription |
|TAMF.reference_name |
|TAMF.reference_name |
| |
| |
| |
| |
| |
|regulationCode |
|CB.cut_regulation_code |
| |
| |
| |
| |
| |
| |
|amendmentReason |
|CBA.amend_reason_st |
|CBA.amend_reason_st |
| |
| |
| |
| |
| |
|plannedGrossArea |
|CBA.est_gross_blk_area |
|CBOA.planned_gross_block_area |
|CBA.est_gross_blk_area |
| |
| |
| |
| |
| |
|plannedNetArea |
|CBA.est_net_blk_area |
|CBOA.planned_net_block_area |
|CBA.est_net_blk_area |
| |
| |
| |
| |
| |
|cruiseVolume |
|CBA.cruise_volume |
|CBA.cruise_volume |
| |
| |
| |
| |
| |
|plannedHarvestDate |
|CBOA.planned_harvest_date |
| |
| |
| |
| |
| |
| |
|dataSourceCode |
|TAMF.data_source_code |
|TAMF.data_source_code |
| |
| |
| |
| |
| |
|captureMethodCode |
|TAMF.capture_method_code |
|TAMF.capture_method_code |
| |
| |
| |
| |
| |
|observationDate |
|TAMF.observation_date |
|TAMF.observation_date |
| |
| |
| |
| |
| |
|dataQualityComment |
|TAMF.data_quality_comment |
|TAMF.data_quality_comment |
| |
| |
| |
| |
| |
|reforestationDeclarationCode |
|CB.reforest_declare_type_code |
| |
| |
| |
| |
| |
| |
|geometry |
|CB.geometry |
|CBA.geometry |
|CBA.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Harvest Application (No CP) - Cut Block (No CP)
Description:
Each application may contain one of more cut blocks.
Harvest Application (No CP) - Cut Block (No CP) - amendmentReason
XML Schema (subset)
Field Information
| | |
|amendmentReason: |
|Description: |The reason for amending a block. E - engineering, F - forest service initiated, S - salvage, A - access |
| |additional cut blocks. |
| |This value is mandatory for amendments. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - applicationPurpose
XML Schema (subset)
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew block or an (A)mendment of an existing block. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |If purpose is 'N' for new File (no CP) application then |
| |- file type code must be valid |
| |- district must be valid |
| |- licence regulation code must be valid |
| |- management type/unit must be valid |
| |- cascade split code must be valid |
| |- special purpose must be valid |
| |- Forestry Licence to Cut must be valid |
| |- for S01,S02,B04,B05,B06,B07 purpose must be valid |
| |- BCTS ORG unit can only be provided for BCTS file types or a B07 |
| |- if a file type code is provided and file type of given file is a U1 or U2 allow only BCTS file type |
| |If purpose is 'A' for amendment of File then |
| |- file/CP must exist |
| |- licensee must own the file |
| |- amendment reason must be valid |
| |- file type code must be valid |
| |- file type code must NOT be U1 |
| |- district must be valid |
| |- cascade split code must be valid |
| |- If file is a BCTS file type check that client is one of the owners of the file |
| |- BCTS Org must match the BCTS Org assigned to file |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - blockDescription
XML Schema (subset)
Field Information
| | |
|blockDescription: |
|Description: |A description of the location of the feature. |
|Data Type: |String |
|Total Length: |120 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - cruiseVolume
XML Schema (subset)
Field Information
| | |
|cruiseVolume: |
|Description: |The cruise volume for the amendment. |
|Data Type: |Number |
|Total Length: |13,2 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - cutBlockID
XML Schema (subset)
Field Information
| | |
|cutBlockID: |
|Description: |The cut block ID |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - plannedGrossArea
XML Schema (subset)
Field Information
| | |
|plannedGrossArea: |
|Description: |The planned gross area of the block. |
| |This is only required if there is no geometry for the cut block. If there is geometry, this value will be |
| |overwritten with the area of the geometry. |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - plannedHarvestDate
XML Schema (subset)
Field Information
| | |
|plannedHarvestDate: |
|Description: |The date harvesting is planned to start |
|Data Type: |Date |
|Total Length: |N/A |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - plannedNetArea
XML Schema (subset)
Field Information
| | |
|plannedNetArea: |
|Description: |The planned net area of the block. |
| |This value must be less than or equal to |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - reforestationDeclarationCode
XML Schema (subset)
Field Information
| | |
|reforestationDeclarationCode: |
|Description: |Valid values are C (Coniferous), D (Deciduous), or M (Mix). |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - Cut Block (No CP) - regulationCode
XML Schema (subset)
Field Information
| | |
|regulationCode: |
|Description: |Code defining the regulation the cut block is harvested under. |
| |Currently the only valid values are BBR (Bark Beetle Regulation) or blank. |
| |This value is mutually exclusive of salvageTypeCode. ie if a salvageTypeCode is provided for the CP then this |
| |must be blank. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP)
Description:
Used for applications that don’t have cutting permits. Some of these tenures have cut blocks others don’t. For new applications the file type is required.
The file types submitted under this format include:
|Feature |File Type |
|Fort St John Pilot Project Regulation (determined by |Various |
|the licenceRegulationCode) | |
|Christmas Tree Permit |B02 |
|Licence to Cut |B04, B05, B06 |
|Forestry Licence to Cut |B07 |
|Timber Sale Licence - Single Mark |B20, B21, B23 |
|Special use Permit |S01, S02 |
Harvest Application (No CP) - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |Submitters’ description or reason for the application |
|Data Type: |String |
|Total Length: |255 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - applicationPurpose
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether this is a (N)ew application or an (A)mendment of an existing file. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - bCTSOffice
XML Schema (subset)
inapplicable
Field Information
| | |
|bCTSOffice: |
|Description: |The MOF organization unit code of the office that is making the submission. This will be used to deem the |
| |submission BCTS funded. |
| |This value is mandatory for BCTS submissions. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - blockID
XML Schema (subset)
inapplicable
Field Information
| | |
|blockID: |
|Description: |The spatial representation of the licence area is often divided into blocks when the boundary is divided by a |
| |natural feature such as a river. This field allows a unique identifier to be defined for each block. Each |
| |block would result in one of these types of submissions. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The org unit code of the district that the tenure resides within. This is most often the same as the |
| |administrative district but can be different. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - fileType
XML Schema (subset)
inapplicable
Field Information
| | |
|fileType: |
|Description: |The file type must be supplied so the proper file can be generated for new applications. |
| |This value is mandatory for new applications. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |Only BCTS may submit U1/U2 |
| |For U1 BCTS applications the conversion file type must be provided |
| |If file ID is a BCTS file type check that client is one of the owners of the file |
| |. |
|Notes: |None |
Harvest Application (No CP) - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The forest file ID of the submission. |
| |This value is mandatory for amendments. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |If File ID supplied then File Status must be in PA status for non BCTS submissions |
| |File id must NOT be blank if BCTS is submitting file |
|Notes: |None |
Harvest Application (No CP) - higherLevelPlanReference
XML Schema (subset)
inapplicable
Field Information
| | |
|higherLevelPlanReference: |
|Description: |Reference to a higher level plan, ie Sustatinable Forest Management Plan. |
|Data Type: |String |
|Total Length: |30 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - licenceRegulationCode
XML Schema (subset)
inapplicable
Field Information
| | |
|licenceRegulationCode: |
|Description: |A code defining the regulation the Licence is harvested under. |
| |There are only two valid values: F (Fort St. John) and G (Forest and Range Practices Act). If this value is |
| |not supplied it will default to G. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |G |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - licenseeHarvestingAuthorityID
XML Schema (subset)
inapplicable
Field Information
| | |
|licenseeHarvestingAuthorityID: |
|Description: |For FSJ applications. Allows for assignment of a name against Peace Forest District harvesting authorities |
|Data Type: |VARCHAR2 |
|Total Length: |30 |
|Data Source: |HARVESTING_AUTHORITY.HARVESTING_AUTHORITY_ID |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - location
XML Schema (subset)
inapplicable
Field Information
| | |
|location: |
|Description: |A location description of the harvest area. E.g. Wilson Creek. This is stored in the reference name column in |
| |the Tenure Application Map Feature table. |
|Data Type: |String |
|Total Length: |50 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - managementUnitID
XML Schema (subset)
inapplicable
Field Information
| | |
|managementUnitID: |
|Description: |The identifier for the management unit. |
|Data Type: |String |
|Total Length: |4 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - managementUnitType
XML Schema (subset)
inapplicable
Field Information
| | |
|managementUnitType: |
|Description: |The type of management unit the tenure is within. (e.g. TFL or TSA). |
| |This value is mandatory for new applications. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - purposeCode
XML Schema (subset)
inapplicable
Field Information
| | |
|purposeCode: |
|Description: |A code that defines the reason for the licence to cut or special use permit application. |
| |This value is required for files of type S01, S02, B04, B07 and if BCTS Org unit is not null, this value must |
| |be RW (Right of Way) |
|Data Type: |String |
|Total Length: |2 |
|Data Source: |N/A |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - referToFileNumber
XML Schema (subset)
inapplicable
Field Information
| | |
|referToFileNumber: |
|Description: |The file number that the tenure is cleared under. E.g. Chart A12345 |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Harvest Application (No CP) - tenureTerm
XML Schema (subset)
inapplicable
Field Information
| | |
|tenureTerm: |
|Description: |The term of the tenure in months |
|Data Type: |Number |
|Total Length: |N/A |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure
Range Tenure Application - Business Rules
Business Rules:
1. If the application is for a new Range Tenure then:
1. The file type code must be a valid range tenure as defined in RANGE_TENURE_TYPE_CODE
2. The district must be a valid org unit.
2. If the application is to amend an existing range tenure then:
1. The file must exist
2. The licensee must own the file
|Validation Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for range application submissions. Validation is only called after the XML |
|submission has been successfully validated by ESF. This module is implemented as the FTA_XML_VALIDATION.VALIDATE_RANGE database |
|routine |
| |
|Interface Parameters |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_issue_date |
|IN |
|VARCHAR2 |
| |
|p_authorized_harvest_tonnes |
|IN |
|VARCHAR2 |
| |
|p_hay_cutting_area_no |
|IN |
|VARCHAR2 |
| |
|p_range_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_map_block_id |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
| |
| |
|Validations |
|1. If application purpose is “New” then: |
|a. If forest file id is not null then: |
|i. If file status is not PA then raise error “file must be in PA status”. |
|b. Validate range file type code. I.e. file type must be either E01,E02,E03,H01,H02,H03. If not valid range file type then raise|
|error “Invalid Range file type”. |
|c. Verify that file type matches that of give file. |
|d. Validate the district. |
|2. If application purpose is “Amend” then: |
|a. Verify that file exists. |
|b. If file status is not equal to “A-active” then raise error “Invalid Range file status for Amendment”. |
|c. Validate range file type code. I.e. file type must be either E01,E02,E03,H01,H02,H03. If not valid range file type then raise|
|error “Invalid Range file type”. |
|d. Validate the district. |
|e. Verify that licensee owns the file |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for timber licence application submissions. Processing is called only after the |
|submission has been successfully validated using FTA_XML_VALIDATE. VALIDATE_RANGE. The processing module is implemented as the |
|FTA_XML_PROCESS.PROCESS_RANGE database routine |
| |
|Interface Parameters |
| |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_file_type_code |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_tenure_term |
|IN |
|VARCHAR2 |
| |
|p_issue_date |
|IN |
|VARCHAR2 |
| |
|p_authorized_harvest_tonnes |
|IN |
|VARCHAR2 |
| |
|p_hay_cutting_area_no |
|IN |
|VARCHAR2 |
| |
|p_range_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_map_block_id |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_userid |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_amendment_id |
|IN |
|VARCHAR2 |
| |
| |
| |
|Processing |
|1. If application purpose is “New” then: |
|a. Generate the file id. |
|b. Verify that the file id does not already exist. |
|c. Create the file entry (PROV_FOREST_USE). |
|2. If application purpose is not “New” then: |
|3. Update the file status from PA to PE. |
|4. Create range tenure entry (RANGE_TENURE). |
|5. Determine if licensee for file already exists: |
|a. If yes, then update FOR_CLIENT_LINK setting A-licensee to C-Previous Main licensee, and create new A-licensee entry in |
|FOR_CLIENT_LINK for supplied client. |
|6. Create tenure term entry (TENURE_TERM) |
|a. If file type is E01 or H01, then set tenure term to 120 |
|b. If file type is H02,H02,or E03 the set tenure term to 12 |
|c. For all other range file types set tenure term to that supplied in submission. |
|7. Calculate range area and perimeter from supplied geometry. |
|8. If application purpose is “New” then create range geometry. (RANGE_GEOM.) |
|9. Create entry for range amendment geometry (RANGE_TENURE_AMEND_GEOM). |
|10. Update the range feature in the application with the generated amendment id |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. |
| |
| |
| |
| |
Range Tenure Application - Field Information
| | | | | |
|Field Specification: |
|Range Tenure Application |
|Field Specification: |
|boundedBy -- Mandatory |
|forestFileID |
|fileType |
|applicationDescription |
|district |
|applicationPurpose |
|authorizedHarvestableForage |
|hayCuttingAreaNumber |
|tenureTerm |
| |
|Range Map Block |
|Field Specification: |
|spatialMetaData -- Optional |
|tenureBlock |
|applicationPurpose |
|extentOf -- Mandatory |
|Data Mappings |
| |
|Description |
|This document maps the XML elements for this application to the columns in the database where they're stored. |
|Please refer to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no |
|PFU.forest_region |
|RT.admin_forest_district_no |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number |
|FFC.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code |
|FFC.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id |
|TAMF.forest_file_id |
|PFU.forest_file_id |
|RT.forest_file_id |
|FFC.forest_File_id |
|TT.forest_file_id |
|RTG.forest_file_id |
|RTAG.forest_file_id |
|TA.forest_file_id |
|TAMF.forest_file_id |
|RTAG.forest_file_id |
| |
| |
| |
| |
| |
|fileType |
|PFU.file_type_code |
| |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|district |
| |
| |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|authorizedHarvestableForage |
|RT.authorized_harvest_tonnes |
| |
| |
| |
| |
| |
| |
|hayCuttingAreaNumber |
|RT.hay_cutting_area_no |
| |
| |
| |
| |
| |
| |
|tenureTerm |
|TT.tenure_term |
| |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|tenureBlock |
|TAMF.map_block_id |
|RTG.map_block_id |
|RTAG.map_block_id |
|TAMF.road_section_id |
|RTAG.map_block_id |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|geometry |
|RTG.geometry |
|RTAG.geometry |
|RTAG.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Range Tenure Application - Range Map Block
Description:
Each range tenure can have multiple range blocks.
Range Tenure Application - Range Map Block - applicationPurpose
XML Schema (subset)
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew block or an (A)mendment of an existing block. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure Application - Range Map Block - tenureBlock
XML Schema (subset)
Field Information
| | |
|tenureBlock: |
|Description: |If the range tenure has multiple geographic blocks then this allows each block to be referenced by rotations |
| |individually. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure Application
Description:
A Range Tenure can contain one or more Range Map Blocks.
The file types that will be submitted using this application type include:
|Feature |File Type |
|Grazing Licence |E01 |
|Grazing Permit |E02, E03 |
|Hay Cutting Licence |H01 |
|Hay Cutting Permit |H02, H03 |
Range Tenure Application - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |Submitter's description or reason for the application. |
|Data Type: |String |
|Total Length: |255 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure Application - applicationPurpose
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew application or an (A)mendment of an existing range tenure. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |If Application Purpose is 'N - New' |
| |File Type code must be valid |
| |District must be valid |
| |File Type code must match that of the given file |
| | |
| |If Application Purpose is 'A - Amendment' |
| |File Status must be A |
| |Forest File ID must exist |
| |District must be valid |
| |Must be an issued/active tenure |
| |Licensee must own the file. |
| |Must be a valid range File Type |
| |Client Number must be the licensee for this file. |
|Notes: |None |
Range Tenure Application - authorizedHarvestableForage
XML Schema (subset)
inapplicable
Field Information
| | |
|authorizedHarvestableForage: |
|Description: |A measurement in tonnes as to the quantity of hay that can be cut on an annual basis. |
| |This is mandatory for H01, H02, H03. |
|Data Type: |Number |
|Total Length: |5 |
|Data Source: |RANGE_TENURE.AUTHORIZED_HARVEST_TONNES |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure Application - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The org unit code of the district that the tenure resides within. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |PROV_FOREST_USE.FOREST_REGION |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |Must be a valid District |
| |If Admin Org of file is a Region then district must fall within it |
| |District must match the file's Administrative Org. |
|Notes: |None |
Range Tenure Application - fileType
XML Schema (subset)
inapplicable
Field Information
| | |
|fileType: |
|Description: |The file type for new applications. Used to ensure the correct file type is created. |
| |This value is mandatory for new applications. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |many tables |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |Check if valid File Type (E01, E02, E03, H01, H02 and H03) |
| |File Type code must be valid |
| |For Amendments the File Type must match the File Type for the existing record |
|Notes: |None |
Range Tenure Application - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The range tenure number. This number will also identify the tenure type via Prov Forest Use. |
| |This value is mandatory for an amendment. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |PROV_FOREST_USE.FOREST_FILE_ID |
|Optionality: |Conditional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |If file Id is supplied the File Status code must be in PA status |
|Notes: |None |
Range Tenure Application - Range Map Block - hayCuttingAreaNumber
XML Schema (subset)
inapplicable
Field Information
| | |
|hayCuttingAreaNumber: |
|Description: |A range tenure often corresponds to a hay cutting area. This field allows that reference to be made. |
|Data Type: |String |
|Total Length: |4 |
|Data Source: |RANGE_TENURE.HAY_CUTTING_AREA_NO |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Range Tenure Application - tenureTerm
XML Schema (subset)
inapplicable
Field Information
| | |
|tenureTerm: |
|Description: |The term of the tenure in months. |
|Data Type: |Integer |
|Total Length: |4 |
|Data Source: |TENURE_TERM.TENURE_TERM |
|Optionality: |Optional |
|Default Value: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure
Road Permit - Business Rules
Business Rules:
1. If the application is for a new road permit or FSR then:
1. Type file type code must be valid (B40, B01).
2. The Forest File ID for a B40 must be in NNNNN format.
3. The geographic district must be valid.
4. The BCTS org unit, if supplied, must be valid.
5. The management type and management unit ID must be valid.
6. The cascade split code must be valid.
2. If the application is to amend an existing road permit of FSR then:
1. The supplied Forest File ID must exist
2. The licensee must own the file
3. The amendment type must be valid as defined in ROAD_AMENDMENT_TYPE_CODE.
3. Road Section Validations:
1. If the Application Purpose defined with the road section is New then the road section ID must not already exist
2. If the road section purpose is Amend then the road section ID must exist
|Validation Rules |
| |
| |
|(Last Updated 17-July-2006, Version 3.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for road application submissions. Validation is only called after the XML |
|submission has been successfully validated by ESF. This module is implemented as the FTA_XML_VALIDATION.VALIDATE_ROAD database |
|routine. |
| |
| |
|Interface Parameters |
|None. |
| |
| |
|Validations |
|Perform file-level validations: |
|If application purpose is new, then: |
|Ensure that file type provided for road application is either B01, B40, S01, or S02. |
|If valid file provided and BCTS office supplied, then ensure the file is assigned to the BCTS office |
|Ensure File Id is blank file type of application is B01. (I.e. Road Permits are always auto-generated by the system. Only file |
|ids for FSR may be supplied in a submission.) |
|If File type is B40 then file id must be supplied. |
|Ensure B40 file id does not exceed length of 5 characters. |
|If file type is B40, and file id already exists in FTA, then ensure that file ids is in PA status. |
|Ensure that district provided exists and is valid. |
|viii. If BCTS district provided then ensure that exists and is valid. |
|ix. If Management unit provided ensure that exists and is valid. |
|x. If file type is B01, then ensure cascade split code provided is valid. |
|xi. If BCTS org unit is supplied, and file type is B40 then verify that client number provided is for the BCTS Timber Sales |
|office. |
|xii. If file type is B40 and BCTS Org unit is not supplied, then verify that client number provided is for the district manager.|
| |
| |
|If application purpose is Amend then: |
|Ensure that file type provided for road application is either B01, B40, S01, or S02. |
|iIf file type is B01, then ensure cascade split code provided is valid. |
|Ensure that district provided exists and is valid. |
|If file type is B01 and BCTS org unit is blank, then ensure the client number provided is the same that which owns the file. |
|If BCTS org unit is provided then ensure that client number supplied is the same as that which owns the file. |
| |
|Perform road section-level validations: |
|Ensure that section id is not blank. |
| |
| |
|Ensure that none of the following characters are contained within the section id. < (less than) , > (greater than) , ‘ (single |
|quote) , “ (double quote), & (ampersand) , / (forward slash) |
| |
| |
|Verify that duplicate section ids not exist in the same application. |
| |
| |
|Ensure that geometry supplied with submission exists and is valid. |
| |
| |
|If section purpose is “Retire” then: |
|Verify that file is not in PE or PI status. |
|Verify that road section exists. |
| |
| |
|If section purpose is “Amend” then ensure that file status is currently HI. |
|If road section amendment type code is not valid for section then: |
|Allow processing to continue if road section amendment type code is XXX or if road submission application purpose is new. (To |
|allow for data cleanup) |
|If road section purpose is “Amend” then ensure road amendment type has been provided and is valid. |
|Ensure that road section purpose is not “Amend” when road application Purpose is New. |
|If road section purpose is “Amend” then: |
|Ensure application purpose is not new. |
|Verify that road section already exists. |
|If road section purpose is “New” then: |
|Verify that road section does not exist. |
|If file type is B01, ensure that section name does not begin with letters “SEC%”. |
|If file type is B40, ensure that section name does not begin with the letters “BRANCH%”, “BR.%”, “BR#”,”BR-%”,”BR”. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 31-Aug-2006, Version 3.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for road application submissions. Processing is called only after the submission |
|has been successfully validated using FTA_XML_VALIDATION.VALIDATE_ROAD. The processing module is implemented as the |
|FTA_XML_PROCESS.PROCESS_ROAD database routine. |
| |
| |
|Interface Parameters |
| |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_userid |
|IN |
|prov_forest_use.entry_userid%TYPE |
| |
|p_forest_file_id |
|IN |
|road_permit.forest_file_id%TYPE |
| |
|p_amendment_id |
|IN |
|road_prmt_amend.amendment_id%TYPE |
| |
| |
| |
|Processing |
|If application purpose is New and file type code is either B01, S01, or S02 then: |
|Generate the file id. |
|Verify that the generated file id does not already exist. |
|Create the file in PROV_FOREST_USE. |
| |
| |
|If file already exists then: |
|Set the file status from PA to PE. |
|If the submitted licensee of the application does not equal the current licensee of the file then: |
|Update the current licensee from A-Licensee to C- Previous Main Licensee. |
|Insert and entry into FOREST_FILE_CLIENT specifying the submitted licensee as the A-Licensee. |
| |
| |
|If file type code is either B01, B40, S01, or S02 then: |
|Create an entry in ROAD_PERMIT specifying following values: |
|Valid Mark Indicator = N |
|Initial Road Length = NULL |
|Current Road Length = NULL |
| |
| |
|Create an entry in HARVEST_SALE specifying following values |
|If BCTS org unit provided then: |
|SB_FUND_IND = Y |
|SALE_METHOD_CODE = T- Auction, Sealed Tender. |
|If BCTS org unit not provided then: |
|SB_FUND_IND = N |
|SALVAGE_IND = N |
|PAYMENT_METHOD_CODE = A-Automatic Invoice. |
|If file type is B01, then SALE_TYPE_CD = SL-Sawlog. |
| |
| |
|If file type code is B40, then create an entry in LAND_CLEAR_FILE. |
|If file type code is B01, S01, or S02, then create an entry in TENURE_TERM. |
|If file type code is B01 then create entry in HARVESTING_AUTHORITY specifying following values: |
|HARVEST_TYPE_CODE = R-Road. |
| |
| |
|If file type code is S01, or S02 then create entry in SPEC_USE_PERMIT specifying following values: |
|SPECIAL_USE_CODE = 19- Road, Right of Way. |
| |
| |
|Perform Road Section processing |
|Calculate the road length from the supplied geometry. |
|If road section id is not blank and road section purpose is New then create entry in ROAD_SECTION. |
|If road section id is not blank and road section purpose is Amend then update the existing road section status from blank to PE.|
|If road section id is not blank and road section purpose is New then create entry in ROAD_SECTION_GEOM. |
|If ROAD_SECTION_ID IS NOT NULL then create an entry in ROAD_PRMT_AMEND. |
|Create an entry in ROAD_SECTION_AMEND_GEOM. |
| |
| |
|Perform Road Segment Level processing (For each section). |
|If file type code is B40 then: |
|If BCTS org unit supplied with submission then ROAD_RESPONSIBILITY_TYPE_CODE = BC – BC Timber Sales. |
|If BCTS org unit is null then ROAD_RESPONSIBILITY_TYPE_CODE = OS – Operations Division. |
| |
| |
|If road section purpose is New, then |
|Create entry in ROAD_SECTION_AMEND_SEGMENT. |
|If road section purpose is Amend and file type is not B40 then: |
|Create entry in ROAD_SECTION_AMEND_SEGMENT. |
|If road section purpose is Amend and file type is B40 then: |
|Carry forward the existing segments for the current road section from FTA and modify them using the following rules. |
|If length of the section in the submission is greater than the existing section length then: |
|Create a single additional segment with length equal to the difference between the original section length and the new section |
|length. |
|If length of the section in the submission is less than the existing section length then: |
|Starting from the start of the section, trim down the existing segments until their total length equals that of the new section.|
| |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|31-Aug-2006, Ross Nanton |
| |
| |
|Updated. Created "Interface Parameters" section. |
| |
| |
| |
| |
Road Permit - Field Information
| | | | | |
|Field Specification: |
|Road Tenure Application |
|Field Specification: |
|boundedBy -- Optional |
|forestFileID |
|fileType |
|applicationDescription |
|location |
|district |
|managementUnitType |
|managementUnitID |
|applicationPurpose |
|higherLevelPlanReference |
|licenceRegulationCode |
|bCTSOffice |
| |
|Road Section |
|Field Specification: |
|spatialMetaData -- Optional |
|roadSectionID |
|roadName |
|applicationPurpose |
|tenureWidth |
|amendmentStartStation |
|amendmentEndStation |
|amendmentType |
|centreLineOf |
|Data Mappings |
| |
|Description |
|This document maps the XML elements for this application to the columns in the database where they're stored. Please |
|refer to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no |
|HVA.forest_district |
|LCF.admin_forest_dist |
|SUP.admin_forest_dist |
|PFU.forest_region |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number |
|FFC.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code |
|FFC.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id |
|TAMF.forest_file_id |
|PFU.forest_file_id |
|HVA.forest_file_id |
|HA.forest_file_id |
|HS.forest_file_id |
|RP.forest_file_id |
|RS.forest_file_id |
|RPA.forest_file_id |
|RSG.forest_file_id |
|RSAG.forest_file_id |
|TT.forest_file_id |
|FFC.forest_File_id |
|LCF.forest_file_id |
|SUP.forest_file_id |
|SEG.forest_file_id |
|SEGA.forest_file_id |
|RSAS.forest_file_id |
|TA.forest_file_id |
|TAMF.forest_file_id |
|RS.forest_file_id |
|RPA.forest_file_id |
|RSG.forest_file_id |
|RSAG.forest_file_id |
|SEG.forest_file_id |
|SEGA.forest_file_id |
|RSAS.forest_file_id |
| |
| |
| |
| |
| |
|fileType |
|PFU.file_type_code |
| |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|location |
|TAMF.reference_name |
|HVA.location |
|TAMF.reference_name |
| |
| |
| |
| |
| |
|district |
|HVA.geographic_district |
| |
| |
| |
| |
| |
| |
|managementUnitType |
|TAMF.management_unit_number |
|PFU.management_unit_type |
|HVA.management_unit_type_code |
|TAMF.management_unit_number |
| |
| |
| |
| |
| |
|managementUnitID |
|TAMF.management_unit_block |
|PFU.management_unit_id |
|HVA.management_unit_id |
|TAMF.management_unit_block |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|higherLevelPlanReference |
|HVA.higher_level_plan_reference |
| |
| |
| |
| |
| |
| |
|licenceRegulationCode |
|HVA.harvest_type_code |
| |
| |
| |
| |
| |
| |
|BCTSOffice |
|PFU.bcts_org_unit |
|HS.bcts_org_unit |
| |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|roadSectionId |
|TAMF.road_section_id |
|RS.road_section_id |
|RSG.road_section_id |
|RPA.road_section_id |
|SEG.road_section_id |
|TAMF.road_section_id |
|RPA.road_section_id |
| |
| |
| |
| |
| |
|roadName |
|TAMF.road_name |
|TAMF.road_name |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|tenureWidth |
|RS.section_width |
|RPA.section_width |
| |
| |
| |
| |
| |
| |
|amendmentStartStation |
|RPA.start_station |
| |
| |
| |
| |
| |
| |
|amendmentEndStation |
|RPA.end_station |
| |
| |
| |
| |
| |
| |
|amendmentType |
|RPA.road_amendment_type_code |
| |
| |
| |
| |
| |
| |
|geometry |
|RSG.geometry |
|RSAG.geometry |
|RSAG.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Road Tenure Application - Road Section
Description:
A road permit application has one or more road sections.
Road Tenure Application - Road Section - amendmentEndStation
XML Schema (subset)
Field Information
| | |
|amendmentEndStation: |
|Description: |The distance in kilometres from the start of the existing road where the amendment ends. |
| |This value is ignored for retirements. |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |FTA_TA_ROAD_SECTION.END_STATION |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - Road Section - amendmentStartStation
XML Schema (subset)
Field Information
| | |
|amendmentStartStation: |
|Description: |The distance in kilometres from the start of the existing road where the amendment starts. |
| |This value is ignored for retirements. |
|Data Type: |Number |
|Total Length: |11,4 |
|Data Source: |FTA_TA_ROAD_SECTION.START_STATION |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - Road Section - amendmentType
XML Schema (subset)
Field Information
| | |
|amendmentType: |
|Description: |As discussed Jan 8. (ADD) is adding length, (REM) deactivating or removing length, (REN) indicates re-aligning|
| |the road. |
| |This value is mandatory for amendments. |
| |This value is ignored for retirements. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |FTA_TA_ROAD_SECTION.AMENDMENT_TYPE_CODE |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - Road Section - applicationPurpose
XML Schema (subset)
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a new section, an amendment of an existing section or a retirement of the section. (N,|
| |A, R) |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |FTA_TA_ROAD_SECTION.APPLICATION_PURPOSE |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |Road Section: |
| |- if road section purpose is 'N - New' then section must not exist |
| |- if road section purpose is 'A'mend then section must exist |
|Notes: |None |
Road Tenure Application - Road Section - centreLineOf
XML Schema (subset)
Field Information
| | |
|centreLineOf: |
|Description: |The geometry of the road. This value is required for application purpose = N or A. |
| |This value is ignored for retirements. |
|Data Type: |Linestring, MultiLinestring |
|Total Length: |N/A |
|Data Source: |FTA_TA_ROAD_SECTION. |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - Road Section - roadName
XML Schema (subset)
Field Information
| | |
|roadName: |
|Description: |A description name for the road. |
| |This value is ignored for retirements. |
|Data Type: |String |
|Total Length: |20 |
|Data Source: |FTA_TA_ROAD_SECTION. |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - Road Section - roadSectionID
XML Schema (subset)
Field Information
| | |
|roadSectionID: |
|Description: |A unique identifier for a branch or section of road. |
|Data Type: |String |
|Total Length: |30 |
|Data Source: |FTA_TA_ROAD_SECTION.ROAD_SECTION_ID |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |Must have a valid Road Section ID |
| |Road Section ID File Status must not be PE or PI. |
|Notes: |The following characters will not be permitted in road section IDs. |
| |> (greater than) |
| |& (ampersand) |
| |' (single quote) |
| |" (double quote) |
| |/ (forward slash) |
Road Tenure Application - Road Section - tenureWidth
XML Schema (subset)
Field Information
| | |
|tenureWidth: |
|Description: |This specifies the tenure width tenure width (in m) of the SUP road permit. NOTE: this is only valid for SUP |
| |road applications. Also, this is the total width of the tenure, it will be split by the centre line. |
| |Tenure width of FSR’s and Road Permits will be 75m. The minimum tenure width of an SUP road is 20m. This value|
| |will become the greater value of the submitted value and 20m. |
| |This value is ignored for retirements. |
|Data Type: |Number |
|Total Length: |3 |
|Data Source: |FTA_TA_ROAD_SECTION.SECTION_WIDTH |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application
Description:
Used to submit applications or amendments to road permits or Forest Service Roads.
The file types submitted under this format include:
|Feature |File Type |
|Fort St John Pilot Project Regulation (determined by the |Various |
|licenceRegulationCode) | |
|Road Permit |B01 |
|Forest Service Road (FSR) |B40 |
|Special Use Permit (SUP) Roads |S01, S02 |
Road Tenure Application - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |Submitters’ description or reason for the application. |
|Data Type: |String |
|Total Length: |255 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.APPLICATION_DESCRIPTION |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - applicationPurpose
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a new application or an amendment of an existing road permit. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.APPLICATION_PURPOSE |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |If purpose is 'N - New' for new Road Permit/Forest Service Road application |
| |- file type code must be valid |
| |- file id must be given for B40 and must be in NNNNN format |
| |- district must be valid |
| |- bcts org must be valid |
| |- management type/unit must be valid |
| |- cascade split code must be valid for B01 Road Permit |
| |If purpose is 'A - Amendment' for amendment of File then |
| |- file type code must match that of the given file |
| |- file must exist |
| |- licensee must own the file |
| |- road amendment type must be valid |
| | |
|Notes: |None |
Road Tenure Application - bCTSOffice
XML Schema (subset)
inapplicable
Field Information
| | |
|bCTSOffice: |
|Description: | The MOF organization unit code of the office that is making the submission. This will be used to deem the |
| |submission BCTS funded. |
| |This value is mandatory for BCTS submissions. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.BCTS_ORG_UNIT_NO |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The org unit code of the district the tenure resides within. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.ADMIN_DISTRICT_NO |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - fileType
XML Schema (subset)
inapplicable
Field Information
| | |
|fileType: |
|Description: |Identifies the type of road tenure being applied for. This value is mandatory for a new application. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.FILE_TYPE_CODE |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The file ID of the road permit, forest service road, or special use permit road. |
| |This value is mandatory for any amendment or for a new Forest Service Road and may be null for a new Road |
| |Permit or Special User Permit Road. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.FOREST_FILE_ID |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |File ID must be blank if file type is B01 |
| |File ID must be supplied if File Type is 'B40' |
| |If File ID supplied then File Status must be in PA status |
| | |
|Notes: |None |
Road Tenure Application - higherLevelPlanReference
XML Schema (subset)
inapplicable
Field Information
| | |
|higherLevelPlanReference: |
|Description: |Reference to a higher level plan, ie Sustatinable Forest Management Plan. |
|Data Type: |String |
|Total Length: |30 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.HIGHER_LEVEL_PLAN_REF |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - licenceRegulationCode
XML Schema (subset)
inapplicable
Field Information
| | |
|licenceRegulationCode: |
|Description: |A code defining the regulation the Licence is harvested under. |
| |There are only two valid values: F (Fort St. John) and G (Forest and Range Practices Act). If this value is |
| |not supplied it will default to G. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |. |
|Optionality: |Optional |
|Default Value: |G |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - location
XML Schema (subset)
inapplicable
Field Information
| | |
|location: |
|Description: |A location description of the harvest area. E.g. Wilson Creek. This is stored in the reference name column in |
| |the Tenure Application Map Feature table. |
|Data Type: |String |
|Total Length: |50 |
|Data Source: |N/A |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - managementUnitID
XML Schema (subset)
inapplicable
Field Information
| | |
|managementUnitID: |
|Description: |The identifier for the management unit. |
|Data Type: |String |
|Total Length: |4 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.MGMT_UNIT_ID |
|Optionality: |Optional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Road Tenure Application - managementUnitType
XML Schema (subset)
inapplicable
Field Information
| | |
|managmentUnitType: |
|Description: |The type of management unit the tenure is within. (e.g. TFL or TSA). |
| |This value is mandatory for new applications. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |FTA_TA_ROAD_TENURE_APP.MGMT_UNIT_TYPE |
|Optionality: |Conditional |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence
Timber Licence - Business Rules
Business Rules:
1. If the application is for a new Timber Licence then:
1. The Forest File ID supplied must exist
2. If the application is the amend an existing Timber License then:
1. The Forest File ID supplied must exist and be of the type A06
3. TL Block Validations:
1. If the TL Block applications purpose is to (A)mend or (D)elete then the TL block must exist.
2. If the TL Block application purpose is for a New Block then the TL Block must not previously exist.
|Validation Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for timber licence application submissions. Validation is only called after the |
|XML submission has been successfully validated by ESF. This module is implemented as the FTA_XML_VALIDATION.VALIDATE_TL_BLOCK |
|database routine |
| |
| |
|Interface Parameters |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_tl_block_id |
|IN |
|VARCHAR2 |
| |
|p_tl_block_gross_area |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
| |
| |
| |
|Validations |
|1. Ensure file type is either A06 or A30. |
|2. Verify that licensee owns the file. |
|3. Verify that supplied district falls within file’s admin org. |
|4. Verify that TL block exists. |
|5. If block purpose is “Amend” and block does not exist then raise error “Invalid TL Block”. |
|6. If block purpose is “New” and block does exist then raise error “Block already exists”. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for timber licence application submissions. Processing is called only after the |
|submission has been successfully validated using FTA_XML_VALIDATE. VALIDATE_TL_BLOCK. The processing module is implemented as |
|the FTA_XML_PROCESS.PROCESS_TL_BLOCK database routine |
| |
| |
|Interface Parameters |
| |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_tl_block_id |
|IN |
|VARCHAR2 |
| |
|p_tl_block_gross_area |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_userid |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
|p_amendment_id |
|IN |
|VARCHAR2 |
| |
| |
| |
|Processing |
|1. Calculate net area for the block as equal to gross block area. (Since eliminated area is unknown) |
|2. If application purpose is “New” then: |
|a. Create entry in TIMBER_LIC_AREA for given file. |
|b. Create entry in TL_BLOCK_AREA |
|3. If block application purpose is “New” then: |
|a. Set amendment id to zero. |
|4. Create entry in TL_BLOCK_AREA_AMEND. |
|5. Calculate TL block area and perimeter from supplied geometry. |
|6. Create entry for TL block amendment geometry. (TIMBER_LIC_AMEND_GEOM) |
|7. Update the block in the application with the generated amendment id. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. |
| |
| |
| |
| |
Timber Licence - Field Information
| | | | | |
|Field Specification: |
|Timber Licence |
|Field Specification: |
|boundedBy -- Mandatory |
|spatialMetaData -- Optional |
|forestFileID |
|applicationDescription |
|district |
|applicationPurpose |
| |
|Timber Licence Map Block |
|Field Specification: |
|spatialMetaData -- Optional |
|mapBlockID |
|applicationPurpose |
|extentOf -- Mandatory |
|Data Mappings |
| |
|Description |
|This document maps the XML elements for this application to the columns in the database where they're |
|stored. Please refer to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id |
|TAMF.forest_file_id |
|TLA.forest_file_id |
|TBA.forest_file_id |
|TBAA.forest_File_id |
|TLG.forest_file_id |
|TLAG.forest_file_id |
|TA.forest_file_id |
|TAMF.forest_file_id |
|TBA.forest_file_id |
|TBAA.forest_File_id |
|TLG.forest_file_id |
|TLAG.forest_file_id |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|district |
| |
| |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|mapBlockID |
|TAMF.map_block_id |
|TBA.map_block_id |
|TBAA.map_block_id |
|TLG.forest_file_id |
|TLAG.forest_file_id |
|TAMF.road_section_id |
|TBAA.map_block_id |
|TLAG.forest_file_id |
| |
| |
| |
| |
| |
|applicationPurpose |
|TAMF.tenure_app_purp_code |
|TAMF.tenure_app_purp_code |
| |
| |
| |
| |
| |
|geometry |
|TLG.geometry |
|TLAG.geometry |
|TLAG.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Timber Licence
Description:
The Timber Licence boundary identifies the outer boundary of a Timber Licence. Updates to these will be completed and submitted by MSRM.
The file types that will be submitted using this application type include:
|Feature |File Type |
|Timber Licence |A06 |
Timber Licence - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |Submitters’ description or reason for the application |
|Data Type: |String |
|Total Length: |120 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence - applicationPurpose
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew Timber Licence or an (A)mendment of an existing licence. No new Timber |
| |Licence’s are to be created. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The org unit code of the district that Timber Licence geographically resides within. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The Forest File ID of the tenure. This number will also identify the tenure type via Prov Forest Use. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |Must be a valid file id |
|Notes: |None |
Timber Licence - Timber Licence Map Block
Description:
Each Timber Licence has at lest one Timber Licence map block.
Timber Licence - Timber Licence Map Block - applicationPurpose
XML Schema (subset)
Field Information
| | |
|applicationPurpose: |
|Description: |Indicates whether it is a (N)ew map block or an (A)mendment of an existing block or a request to (D)elete an |
| |existing block. |
|Data Type: |String |
|Total Length: |1 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence - Timber Licence Map Block - mapBlockID
XML Schema (subset)
Field Information
| | |
|mapBlockID: |
|Description: |The identifier for a map or geographical block that makes up the Timber Licence. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence Elimination
Timber Licence Elimination - Business Rules
Business Rules:
1. The TL Block must exist
2. The licensee must own the file
|Validation Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Validations |
|Change History |
| |
| |
|Description |
|This document identifies the validation rules for timber licence elimination application submissions. Validation is only called |
|after the XML submission has been successfully validated by ESF. This module is implemented as the |
|FTA_XML_VALIDATION.VALIDATE_TL_ELIMINATION database routine |
| |
| |
|Interface Parameters |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_tl_block_id |
|IN |
|VARCHAR2 |
| |
|p_tl_block_gross_area |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
| |
| |
|Validations |
|1. Ensure file type is either A06 or A30. |
|2. Verify that supplied district falls within file’s admin org. |
|3. Verify that licensee owns the file. |
|4. Verify that TL block exists. |
|5. If block does not exist then raise error “Invalid TL Block”. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. Added "Interface Parameters" section. |
| |
| |
| |
| |
|Processing Rules |
| |
| |
|(Last Updated 11-Sept-2006, Version 4.0) |
|Description |
|Interface Parameters |
|Processing |
|Change History |
| |
| |
|Description |
|This document identifies the processing rules for timber licence application submissions. Processing is called only after the |
|submission has been successfully validated using FTA_XML_VALIDATE. VALIDATE_TL_ELIMINATION. The processing module is implemented|
|as the FTA_XML_PROCESS.PROCESS_TL_ELIMINATION database routine |
| |
| |
|Interface Parameters |
| |
|NAME |
|DIRECTION |
|TYPE |
| |
|p_application_purpose |
|IN |
|VARCHAR2 |
| |
|p_application_desc |
|IN |
|VARCHAR2 |
| |
|p_forest_file_id |
|IN |
|VARCHAR2 |
| |
|p_district |
|IN |
|VARCHAR2 |
| |
|p_client_number |
|IN |
|VARCHAR2 |
| |
|p_client_locn_code |
|IN |
|VARCHAR2 |
| |
|p_block_appl_purpose |
|IN |
|VARCHAR2 |
| |
|p_tl_block_id |
|IN |
|VARCHAR2 |
| |
|p_tl_block_gross_area |
|IN |
|VARCHAR2 |
| |
|p_map_feature_id |
|IN |
|VARCHAR2 |
| |
|p_geometry |
|IN |
|MDSYS.SDO_GEOMETRY |
| |
|p_userid |
|IN |
|VARCHAR2 |
| |
|p_trace_ind |
|IN |
|VARCHAR2 |
| |
|p_amendment_id |
|IN |
|VARCHAR2 |
| |
| |
| |
| |
|Processing |
|1. Create entry in TL_BLOCK_AREA_AMEND. |
|2. Calculate TL block area and perimeter from supplied geometry. |
|3. Create entry for TL block amendment geometry. (TIMBER_LIC_AMEND_GEOM) |
|4. Update the block in the application with the generated amendment id. |
| |
| |
|Change History |
| |
| |
| |
| |
|17-July-2006, Andrew Barclay |
| |
| |
|Created. |
| |
| |
| |
| |
|01-Sept-2006, Ross Nanton |
| |
| |
|Updated. |
| |
| |
| |
| |
Timber Licence Elimination - Field Information
|Field Specification: |
|Timber Licence Elimination |
|Field Specification: |
|boundedBy -- Mandatory |
|spatialMetaData -- Optional |
|forestFileID |
|applicationDescription |
|district |
| |
|Timber Licence Elimination Map Block |
|Field Specification: |
|spatialMetaData -- Optional |
|mapBlockID |
|extentOf -- Mandatory |
|Data Mappings |
| |
|Description |
|This document maps the XML elements for this application to the columns in the |
|database where they're stored. Please refer to this document for Data Mapping Keys. |
| |
|Application Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|districtCode |
|_unit_no |
|_unit_no |
| |
| |
| |
| |
| |
|clientCode |
|TA.client_number |
|TA.client_number |
| |
| |
| |
| |
| |
|clientLocationCode |
|TA.client_locn_code |
|TA.client_locn_code |
| |
| |
| |
| |
| |
|forestFileID |
|TA.forest_file_id |
|TLEG.forest_file_id |
|TLEAG.forest_file_id |
|TA.forest_file_id |
|TLEG.forest_file_id |
|TLEAG.forest_file_id |
| |
| |
| |
| |
| |
|applicationDescription |
|TA.description |
|TA.description |
| |
| |
| |
| |
| |
|district |
| |
| |
| |
| |
|Feature Level |
|XML Element |
|Application Purpose = N |
|Application Purpose = A |
| |
|mapBlockID |
|TAMF.map_block_id |
|TLEG.map_block_id |
|TLEAG.map_block_id |
|TAMF.map_block_id |
|TLEG.map_block_id |
|TLEAG.map_block_id |
| |
| |
| |
| |
| |
|geometry |
|TLAG.geometry |
|TLAG.geometry |
| |
| |
|Change History |
| |
| |
|05-Sept-2006, Laurie Michaelis |
| |
| |
|Created |
| |
| |
| |
| |
Timber Licence Elimination
Description:
Licensee’s must annually submit the areas they have harvested or eliminated from a Timber Licence. This submission represents the total area of the Timber Licence that has been harvested from a Timber Licence Block
The file types that will be submitted using this application type include:
|Feature |File Type |
|Timber Licence Elimination |A06 |
Timber Licence Elimination - applicationDescription
XML Schema (subset)
inapplicable
Field Information
| | |
|applicationDescription: |
|Description: |Submitters’ description or reason for the application |
|Data Type: |String |
|Total Length: |255 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |None |
|Notes: |None |
Timber Licence Elimination - district
XML Schema (subset)
inapplicable
Field Information
| | |
|district: |
|Description: |The org unit code of the district that the Timber Licence resides within. |
|Data Type: |String |
|Total Length: |3 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |district must be within/belongs to file's admin org unit |
|Notes: |None |
Timber Licence Elimination - forestFileID
XML Schema (subset)
inapplicable
Field Information
| | |
|forestFileID: |
|Description: |The file ID of the timber licence. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |licensee must owns the file |
| |Must be a valid file id |
| | |
|Notes: |None |
Timber Licence Elimination - Timber Licence Elimination Map Block
Description:
Each Timber Licence Elimination has at least one map block.
Timber Licence Elimination - Timber Licence Elimination Map Block - mapBlockID
XML Schema (subset)
Field Information
| | |
|mapBlockID: |
|Description: |An ID of a geographic block that makes up the timber licence. |
|Data Type: |String |
|Total Length: |10 |
|Data Source: |N/A |
|Optionality: |Mandatory |
|Default Value: |N/A |
|Edit: |N/A |
|Format: |N/A |
|Validation: |TL block must exist |
|Notes: |None |
Data Mapping Table Key
Tenure_Application – TA
Tenure_Application_Map_Feature – TAMF
Prov_Forest_Use - PFU
Harvesting_Authority – HVA
Harvest_Authority_Amend – HVAA
Hauling_Authority – HA
Cut_Block – CB
Cut_Block_Geom – CBG
Harvest_Amend – CBA
Cut_Block_Amend_Geom – CBAG
Harvest_Sale – HS
Harvest_Authority_Client – HVAC
Cut_block_Open_Admin – CBOA
Land_use_geom – LUG
Land_use_amend_geom – LUAG
Special_use_permit – SUP
Licence_to_cut - LTC
Forest_file_client – FFC
Road_permit – RP
Road_section – RS
Road_permit_amend – RPA
Road_section_geom – RSG
Road_section_amend_geom - RSAG
Land_clear_file – LCF
Road_segment – SEG
Road_segment_amend – SEGA
Road_section_amend_segment – RSAS
Range_tenure – RT
Range_tenure_geom – RTG
Range_tenure_amend_geom – RTAG
Timber_lic_area – TLA
Tl_block_area – TBA
TL_block_area_amend – TBAA
Timber_lic_geom – TLG
Timber_lic_amend_geom – TLAG
Timber_lic_elim_geom – TLEG
Timber_lic_elim_amend_geom - TLEAG
All district codes are converted to their associated org unit no’s to store in the database.
Note: the application purpose for application level xml is the application level application purpose. Application purpose for the feature level xml is the feature level application purpose.
XML Schema Most Recent Change History
Change History from Schema 8 to Schema 9
General
• Removed licenseeContact from FTA Submission Metadata
• Removed batchReferenceDate from FTA Submission Metadata
• Removed legalDescriptionProperty from all files
• Removed Charts as a submission type
• Removed Oil and Gas as a submission type
Harvest Application with CP
• Added higherLevelPlanReference
• Renamed salvageIndicator to salvageTypeCode and datatype from Boolean to Alpha3
• Renamed cuttingPermitName to location and reduced datatype length to AlphaNumeric50
• Changed plannedGrossArea from mandatory to optional
• Changed markingInstrumentCode from mandatory to conditional (mandatory for new applications)
• Changed markingMethodCode from mandatory to conditional (mandatory for new applications)
• Changed deciduousIndicator from mandatory to conditional (mandatory for new applications)
• Changed catastrophicIndicator from mandatory to conditional (mandatory for new applications)
• Changed cruiseBasedIndicator from mandatory to conditional (mandatory for new applications)
• Changed crownGrantedIndicator from mandatory to conditional (mandatory for new applications)
• Removed cascadeSplitCode
• Removed bcgsMapReference
• Removed provincialForestConflictCode
Cut Block
• Added regulationCode
• Removed managedByFile
• Removed managedByCuttingPermit
• Removed ownedByBlock
Harvest Application No CP
• Added higherLevelPlanReference
• Added licenceRegulationCode
• Added licenseeHarvestingAuthorityID
• Added location
• Changed managementUnitID from mandatory to conditional (mandatory for new applications)
• Changed managementUnitType from mandatory to conditional (mandatory for new applications)
• Changed extentOf to optional
• Removed cascadeSplitCode
• Removed bcgsMapReference
• Removed provincialForestConflictCode
Cut Block
• Added regulationCode
• Added reforestationDeclarationCode
• Changed extentOf to optional
• Removed provincialForestConflictCode
Roads
• Added higherLevelPlanReference
• Added licenceRegulationCode
• Added location
• Changed managementUnitID from mandatory to conditional (mandatory for new applications)
• Changed managementUnitType from mandatory to conditional (mandatory for new applications)
• Removed cascadeSplitCode
• Removed deemedOwnedIndicator
Road Section
• Added tenureWidth
• Changed roadSectionID from AlphaNumeric10 to AlphaNumeric30
• Removed withALRInd
• Removed bcgsMapReference
• Removed provincialForestConflictCode
• Removed roadStateCode
Timber Licence
Map Block
• Removed referenceName
• Removed bcgsMapReference
Timber Licence Elimination
Restructured to allow multiple map blocks per TLE application. See Submission Item details or XML Example
FTA Submission Metadata
Required. Each submission must provide information indicating the source of the submission and how it is to be processed.
DJA
12345678
31
The must be included only once per submission document and is detailed in the following table.
|FIELD |TYPE |DESCRIPTION |
|fta:submissionMetadataProperty |N/A |Required tag |
|fta:SubmissionMetadata |N/A |Required tag |
|fta:districtCode |String (3)|This is the administrative district for the submission identified by an|
| | |Org Unit Code. The value in this field is used to determine which |
| | |district to forward the submission to for processing (Inbox). A single |
| | |submission document can only contain applications for one |
| | |administrative district. |
|fta:clientCode |String (8)|The Ministry of Forests and Range client number of the licensee making |
| | |the submission. |
| | | |
| | |The credentials of the person logged into ESF over-rides this value |
| | |unless it is a Ministry of Forests employee or designate making a |
| | |submission on behalf of a licensee. In that case this value will be |
| | |used. The district will be checked to ensure they are the admin |
| | |district of the file. |
|fta:clientLocationCode |String (2)|Each client can have multiple locations. This code is the location code|
| | |as defined by the Ministry of Forests and Range. |
Spatial MetaData
Survey
DifferentialGS
2003-04-28
An example of metadata
|Field |Description |
|mof:spatialMetaData |Optional tag. |
|mof:dataSourceCode |Optional. The source of the spatial data. Use the Data Spatial Data Source table in the |
| |Code Tables section. |
|mof:captureMethodCode |Optional. The source of the spatial data. Use the Data Spatial Data Source table in the |
| |Code Tables section. |
|mof:observationDate |Optional. The data the observation was made. This applys to the data. For example the data|
| |of arial photograhpy or the data of the survey. |
|mof:dataQualityComment |Optional. A maxium 2000 character description that can be used to clarify any of the |
| |values in the spatial meta-data. |
XML Sample
mailto:John.Doe@
6044445555
A sample submission
Optional name.
unknown
DLA
12345678
31
inapplicable
A12345
A1
Some description.
DLA
N
12
A33
Some name.
B
5
true
false
false
false
TSG
AirPhoto
RubberSheeting
2003-04-28
Example metadata
false
AirPhoto
RubberSheeting
2003-04-28
Example data
1
N
A description.
A
125.22
123.077
123665.02
2003-02-13
X999999999
X99
inapplicable
A12345
B02
2003-02-15
DLA
O
YOP2
N
12
PPo99
Kj998
CL
FRPA
TSG
AirPhoto
RubberSheeting
2003-04-28
Example metadata
AirPhoto
RubberSheeting
2003-04-28
Example data
A11
N
A description.
A
125.22
123.077
123665.02
2003-02-13
M
inapplicable
R12345
B01
Some description.
some where
DLA
4
aaff
N
ANything
FRPA
TSG
AirPhoto
RubberSheeting
2003-04-28
Example data
998
Rough Road
N
25
210
233.01
ADD
inapplicable
RAN12125
E01
More description...
DLA
N
2254
asd
1111
AirPhoto
RubberSheeting
2003-04-28
Example data
112
N
inapplicable
T0001
Some descriptive text
DLA
N
AirPhoto
RubberSheeting
2003-04-28
This is an example of metadata
A
N
inapplicable
AirPhoto
RubberSheeting
2003-04-28
This is an example of metadata
T0001
Some descriptive text
DLA
AirPhoto
RubberSheeting
2003-04-28
This is an example of metadata
A
Previous Versions
Electronic Forest Management Website
Please refer to the EFM website for previous FTA schema definitions as well as a summary of their changes.
Data Submission Conventions
1. LAYOUT
Each section that follows defines a separate component of an FTA XML document. Indications of whether the component is required or optional are given; omitting a required section will result in an invalid submission.
Each field is described for every component, again including indications of whether the field is required or optional. Data types are listed with maximum sizes in following parentheses where applicable, for example: Alphanumeric (3). Precision is identified by a further set of parentheses, for example: Decimal (6) (2).
More information on specific data types can be found in the Data Types section.
2. REQUIRED, OPTIONAL OR CONDITIONAL
Throughout the document, sections and individual fields are marked as “Required”, “Optional” or “Conditional”.
Required: This indicates that the information is specifically required regardless of circumstance – e.g. the submission will fail if a required field isn’t filled in.
Optional: This indicates that the information is at the discretion of the submitter. Omitting optional data should not cause a failure, though it may still be important for business purposes.
Conditional: This indicates that the information is required under specific conditions. For instance, new submission items typically require a file type to be supplied while amendments may not.
It is important to note that these designations do not always relate to business requirements. In other words, something designated “optional” may be important from a business point of view under certain circumstances. ESF cannot generally enforce these situations because of exceptions or external criteria – i.e. the business rule cannot be strictly defined or properly validated within the bounds of the system.
3. SYNTAX
+ signs indicate collapsed sections, i.e. sub-sections that are contained within the section being discussed. Each collapsed section is either described in turn in succeeding sub-sections (where they are specific to the parent component), or in the Data Types section (where they are common to several components). Where subsections are small, they are not broken out into separate sections, but are distinguished as shaded rows in the tables.
XML uses tags to delineate information. Tags begin with the field or section name in a set of angled brackets and end with the same text in another set, preceded by a slash. The content is contained between the two. For example:
content
Tip: Missing, or misnamed, end tags are a common problem. Check that all your tags have corresponding end tags before submitting.
Tags are often nested within each other to represent hierarchical information, for example:
Honda
Red
Tip: XML is case sensitive. If a tag is expected to read “MultiPolygon”, but is entered as “multipolygon”, the validation will fail.
For more information on XML and GML, please refer to the ESF website where you can find links to several useful resources.
Data Submission Data Types
There are several data types that have specific requirements. This section describes the proper syntax and formatting to be used when entering content for these types.
• ANYURI
This is a standard XML data type for representing a Uniform Resource Identifier. For the purposes of FTA they are used for email addresses; the "mailto:" prefix should be used as in the example.
Example: mailto:John.Doe@
• BOOLEAN
In XML, Boolean (logical) values can be given as either 1/0 or true/false. The name of a Boolean field always indicates the effect of a true value. Thus "openingCentricIndicator" indicates that if the field has a value of true, the submission should be processed on an opening-by-opening basis. The effect of a false value is provided in the documentation for the field.
Example: true
• CODE TYPES
Data types that have the suffix "CodeType" can contain only predefined values. Valid content for these types is defined in the Code Tables section.
• DATE
In XML, dates must always be given in the format YYYY-MM-DD. Thus 2003-04-10 indicates April 10, 2003.
Example: 2002-05-10
• GYEAR
This is a standard XML data type for representing a specific Gregorian calendar year. For the purposes of RESULTS, the type should contain a positive, four-digit number.
Example: 2002
• TELEPHONE NUMBERS
Telephone numbers use the custom data type, "TelephoneNumberType". A valid telephone number must be 10 digits, starting with the area code.
Example: 6042515612
ESF Submission Header
Required. Each submission document starts with information required to carry out correct XML processing. This information will be identical for each submission document, with the exception of the version number.
The XML header defines several things:
• The element esf:ESFSubmission indicates that this is a submission to be processed via the ESF.
• The namespaces (xmlns) used in FTA submission documents are defined
• The schemaLocation attribute associates the namespaces with a URL that indicates the version of the schema being used.
Tip: The version specified in the XML header must match the version of the schema you are using, i.e. the schema you downloaded from the website.
Data Submission - ESF Submission Metadata
Required. Each submission must provide information indicating the source of the submission and how it is to be processed.
mailto:John.Doe@
6044445555
|FIELD |TYPE |DESCRIPTION |
|esf:emailAddress |anyURI |The email address of the person or organization submitting. |
| | |Refer to the Data Types section for description |
|esf:telephoneNumber |TelephoneNumberType |Required. The telephone number of the person or organization |
| | |submitting. A valid telephone number must be 10 digits, |
| | |starting with the area code. For example: '6045542233' |
Data Submission - Submission Content
Required. This is the container for the submission details. It includes required structure tags as well as some optional descriptive information.
A sample submission of FTA data
Optional name.
inapplicable
|FIELD |TYPE |DESCRIPTION |
|gml:description |String |Optional. High level description of the submission |
|gml:name |String |Optional. Name for the submission |
|gml:boundedBy |BoundingShapeType |Required. GML requires a bounding box to be specified. This bounding box |
| | |is not used by ESF and should be set to null, as in the example. |
XML Requirements Specifications
The technical specifications for the FTA Business Agent will be driven from the content of the electronic submissions. Therefore it makes sense to specify the XML submission as part of this website. The Business Agent specification will reference both the submission and the data model. The following is the requirements for the XML schema which will can be viewed on the XML Schema webpage at the root level of this website's Table of Contents.
With regards to the Forest Tenures Administration system there are four clients that will be submitting data electronically. The four groups are:
• BC Timber Sales
• Industry (Major Licensee or delegate)
• Districts
• Ministry of Sustainable Resource Management
A submission document is an XML file based on an XML schema. An XML schema defines the rules that a submission must adhere to. (e.g. Field Size, whether or not a field is required, etc.) The Electronic Submission Framework uses the schema to validate a client's submission document. You could also view the XML schema as the data model and the submission document as the data.
FTA has one schema:
• Harvesting Application Submission
Each submission schema and resulting submission document, contains one or more submission items. Each schema contains some standard items but also some very business focused items. A Harvesting Application Submission contains six submission items that this website refers to as Application Types.
They are broken down this way as each of these have a different business role within the FTA system.
|Tenure Application Type |Map Feature Types |
|Harvest Application with CP |Cutting Permit (CP) |
| |Cut Block (CB) |
|Harvest Application No CP |Tenure Boundary (F) |
| |Cut Block (CB) |
|Road Permit Application |Road Permit/Sections (RD) |
|Range Tenure Application |Range Boundary (RT) |
|Timber Licence Application |Timber Licence Blocks (TL) |
|Timber Licence Elimination |Timber Licence Eliminated Areas (TLE) |
Table 1 - Tenure Application Types
The following table associates the tenure application types with the client or submitter.
|Tenure Application Type |Submitter(s) |
|Harvest Application with CP |BC Timber Sales |
| |Industry |
|Harvest Application No CP |BC Timber Sales |
| |Districts |
| |Industry |
|Road Permit Application |BC Timber Sales |
| |Industry |
| |Districts (FSR's) |
|Range Tenure Application |Districts |
|Timber Licence Application |MSRM |
|Timber Licence Elimination |Industry |
Table 2 - Data Submitter by Tenure Application Type
Each of the feature classes that are within the scope of FTA are included in the following table. The Map Feature Type column identifies the specific type of the feature class and allows it to be mapped back to the application type. Using an example of CP Applications and Amendments it may contain a cutting permit boundary and one or more cut blocks.
|Feature Class Name |FTA File Type |Submitter |Map Feature Type |
|Forest Licence Cut Block |A01, A41 |INDUSTRY |CB |
|Forest Licence Cutting Permit |A01, A41 |INDUSTRY |CP |
|Tree Farm Licence Cut Block |A02 |INDUSTRY |CB |
|Tree Farm Licence Cutting Permit |A02 |INDUSTRY |CP |
|Timber Sale Licence Cut Block |A03 |INDUSTRY/BCTS |CB |
|Timber Sale Licence Cutting Permit |A03 |INDUSTRY/BCTS |CP |
|Wood Lot Licence Cut Block |A04,A44 |INDUSTRY |CB |
|Wood Lot Licence Cutting Permit |A04,A44 |INDUSTRY |CP |
|Timber Licence Cut Block |A06 |INDUSTRY |CB |
|Timber Licence Cutting Permit |A06 |INDUSTRY |CP |
|Timber Licence Elimination |A06 |INDUSTRY |TLE |
|Timber Licence |A06 |MSRM |TL |
|Timber Sale Licence Cut Block - Multi-Mark |A20, A21, A23, A24 |BCTS |CB |
|Timber Sale Licence - Multi-Mark |A20, A21, A23, A24 |BCTS |CP |
|Non-Replaceable Forest Licence |A25 |BCTS/DISTRICT |CP/CB |
|No specific feature classes to handle this type. | | | |
|They will be treated like a Forest Licence. | | | |
|Timber Sale Licence Minor Cutting Permit |A26, A27 |BCTS |CP |
|Timber Sale Licence Minor Cut Block |A26, A27 |BCTS |CB |
|Community Forest Cut Block |A28, A29 |INDUSTRY |CB |
|Community Forest Cutting Permit |A28, A29 |INDUSTRY |CB |
|Consolidated Timber Licence |A30 |DISTRICT |CP/CB |
|These file types may be submitted electronically. | | | |
|They will be treated like a Timber Licence. | | | |
|Community Salvage |A31 |INDUSTRY |CP/CB |
|Road Permit |B01 |INDUSTRY/BCTS |RD |
|Christmas Tree Permit |B02 |DISTRICT |F |
|Licence To Cut Block |B05, B06, B04 |DISTRICT |CB |
|Licence To Cut |B05, B06, B04 |DISTRICT/BCTS |F |
|Forestry Licence to Cut Block |B07 |INDUSTRY |CB |
|Forestry Licence to Cut |B07 |INDUSTRY |F |
|Timber Sale Licence Cut Block - Single Mark |B20, B21, B23 |BCTS |CB |
|Timber Sale Licence - Single Mark |B20, B21, B23 |BCTS |F |
|Forest Service Road (FSR) |B40 |DISTRICT |RD |
|Administrative Area |C01 |DISTRICT |C |
|Grazing Licence |E01 |DISTRICT |RT |
|Grazing Permit |E02, E03 |DISTRICT |RT |
|Hay Cutting Licence |H01 |DISTRICT |RT |
|Hay Cutting Permit |H02, H03 (Non-Replaceable Hay |DISTRICT |RT |
| |Cutting Permit) | | |
|Special Use Permit |S01, S02 |DISTRICT |F |
Table 3 - Map Feature Types for each Feature Class within the scope of FTA
Code Tables
Code Tables
Several fields accept only specifically defined values. This section defines all possible values for those fields.
In the case of “File Types”, possible values are further restricted by the type of item being submitted.
• Amendment Reason
• Amendment Type
• Application Purpose
• Capture Method
• Cut Regulation
• Data Source
• Districts
• File Type
• Harvest No CP Purpose
• Licence Regulation
• Management Unit ID
• Management Unit Type
• Marking Instrument
• Marking Method
• Reforestation Declaration
• Salvage Type
• Special Use Code
Code Tables
The following xls spreadsheet contains all the code tables and their legal values.
Code Tables Spreadsheet.xls
Amendment Reason
|Code |Description |
|A |Access Additional Cut Blocks |
|E |Engineering |
|F |Forest Service Initiated |
|S |Salvage |
|X |System Amendment |
Amendment Type
|Code |Description |
|ADD |Add |
|RMV |Remove |
|REN |Re-engineer |
Application Purpose
|Code |Description |
|N |New |
|A |Amendment |
Capture Method
|Code |Description |
|Photogrammetric |Photogrammetric |
|coordinateGeometryWithControl |COGO using control points |
|differentialGPS |Differentially corrected GPS Survey |
|monoRestitution |Mono restitution |
|nondifferentialGPS |GPS Survey without differential correction |
|orthoPhotography |Ortho-photography |
|rubberSheeting |Rubber sheeting |
|satelliteImagery |Satellite imagery |
|scanning |Scanning |
|sketchMap |Sketch map |
|tabletDigitizing |Tablet digitizing |
|unknown |Unknown |
Cut Regulation
|Code |Description |
|BBR |Bark Beetle |
Data Source
|Code |Description |
|AP |Air Photo |
|CDMS |Cadastral Data Management System |
|FC1 |Forest Cover Maps |
|SAT |Satellite |
|SUR |Survey |
|TRIM |Terrain Resource Information Management |
|UNK |Unknown |
Districts
|Code |Description |
|DMH |100 Mile House Forest District |
|DAB |Arrow Boundary Forest District |
|DCR |Campbell River Forest District |
|DCS |Cascades Forest District |
|DCC |Central Cariboo Forest District |
|DCH |Chilcotin Forest District |
|DCK |Chilliwack Forest District |
|DCO |Columbia Forest District |
|DFN |Fort Nelson Forest District |
|DJA |Fort St. James Forest District |
|DHW |Headwaters Forest District |
|DKM |Kalum Forest District |
|DKA |Kamloops Forest District |
|DKL |Kootenay Lake Forest District |
|DMK |MacKenzie Forest District |
|DND |Nadina Forest District |
|DNC |North Coast Forest District |
|DNI |North Island - Central Coast Forest District |
|DOS |Okanagan Shuswap Forest District |
|DPC |Peace Forest District |
|DPG |Prince George Forest District |
|DQC |Queen Charlotte Islands Forest District |
|DQU |Quesnel Forest District |
|DRM |Rocky Mountain Forest District |
|DSS |Skeena Stikine Forest District |
|DSI |South Island Forest District |
|DSQ |Squamish Forest District |
|DSC |Sunshine Coast Forest District |
|DVA |Vanderhoof Forest District |
File Type
|File Type |Code |
|Harvest Application with CP |
|A01,A41 |Forest Licence Cut Block |
|A01,A41 |Forest Licence Cutting Permit |
|A02 |Tree Farm Licence Cut Block |
|A02 |Tree Farm Licence Cutting Permit |
|A03 |Timber Sale Licence Major Cut Block |
|A03 |Timber Sale Licence Major Cutting Permit |
|A04,A44 |Wood Lot Licence Cut Block |
|A04,A44 |Wood Lot Licence Cutting Permit |
|A06 |Timber Licence Cut Block |
|A06 |Timber Licence Cutting Permit |
|A25 |Non-Replaceable Forest Licence |
|A26,A27 |Timber Sale Licence Minor Cutting Permit |
|A26,A27 |Timber Sale Licence Minor Cut Block |
|A28,A29 |Community Forest Cut Block |
|A28,A29 |Community Forest Cutting Permit |
|A30 |Consolidated Timber Licence |
|A31 |Community Salvage |
|A20,A21,A23,*A24 |Timber Sale Licence Cut Block - Multi-Mark |
|A20,A21,A23,*A24 |Timber Sale Licence – Multi-Mark |
|Harvest Application No CP |
|B02 |Christmas Tree Permit |
|B05,B06,B04 |Licence to Cut Block |
|B05,B06,B04 |Licence to Cut |
|B07 |Forestry Licence To Cut |
|B20, B21, B23 |Timber Sale Licence Cut Block –Single Mark |
|B20, B21, B23 |Timber Sale Licence – Single Mark |
|S01,*S02 |Special Use Permit |
|Range |
|E01 |Grazing Licence |
|E02, E03 |Grazing Permit |
|H01 |Hay Cutting Licence |
|H02, H03 |Hay Cutting Permit |
|Road |
|B01 |Road Permit |
|B40 |Forest Service Road (FSR) |
|S01, S02 |Special Use Permit (SUP) Roads |
|Timber Licence / Timber Licence Elimination |
|A06 |Timber Licence |
Harvest No CP Purpose
|Code |Description |
|AL |Agricultural Lease |
|AP |Agreement to Purchase |
|BB |Bark Beetle |
|CG |Crown Granted Lands (Timber Reserved) |
|CL |Clearing and Levelling |
|CO |Communications |
|CT |Christmas Trees |
|DL |Dominion Patented Lands Timber Reserve |
|DT |Decked Timber |
|EA |Easement |
|EX |Experimental < 500m3 |
|FH |Forest Health Contract |
|FN |First Nations |
|GL |Grazing Lease |
|GP |Gravel Pit |
|GT |50m3 Green |
|IL |Industrial Lease |
|LL |Log and Lake Salvage |
|LS |Log Salvage |
|MC |Mineral Claim |
|OG |Oil and Gas |
|OT |Other |
|PA |Pulpwood Agreement |
|PI |Pipeline |
|PL |Placer Lease |
|PR |Parks |
|RD |Roads |
|RE |Recreational Lease (Cat., Heli-skiing) |
|RL |Residential Lease |
|RW |Right of Way |
|SL |Seismic Line |
|SS |Small Scale Salvage < 2000m3 |
|TC |TSL (major) Conversion |
|TN |Transportation |
|TR |Trails (ski, horse) |
|UT |Utility (BC Hydro) |
|WL |Waterlines |
|WS |Well Site |
|WT |Windthrow |
Harvest Type Code
|Code |Description |
|F |Fort St. John |
|G |Green |
|M |Multi-Mark |
|R |Road |
Licence Regulation
|Code |Code Description |
|F |Fort St. John |
|G |Forest and Range Practices Act |
Management Unit ID
|Type* |ID |Description |
|N |01 |Nisga Treaty Settlement Lands |
|T |01 |TFL 01 Port Edward |
|T |03 |TFL 03 Little Slocan |
|T |05 |TFL 05 Mac-Cariboo |
|T |06 |TFL 06 Quatsino |
|T |08 |TFL 08 Boundary |
|T |10 |TFL 10 Toba |
|T |13 |TFL 13 Blue River |
|T |14 |TFL 14 Spillimacheen |
|T |15 |TFL 15 Inkaneep |
|T |18 |TFL 18 Clearwater |
|T |19 | TFL 19 Tahsis |
|T |23 |TFL 23 Arrow Lakes |
|T |24 |TFL 24 Moresby |
|T |25 |TFL 25 Naka |
|T |26 |TFL 26 Mission |
|T |30 |TFL 30 Sinclair |
|T |33 |TFL 33 Sicamous |
|T |35 |TFL 35 Jamieson Ck |
|T |37 |TFL 37 Nimpkish |
|T |38 |TFL 38 Squamish |
|T |39 |TFL 39 Haida |
|T |41 |TFL 41 Kitimat |
|T |42 |TFL 42 Tanizul |
|T |43 |TFL 43 Fraser-Homathco-Kingcome |
|T |44 |TFL 44 Alberni |
|T |45 |TFL 45 Cordero-Knight |
|T |46 |TFL 46 West Coast |
|T |47 |TFL 47 Duncan Bay |
|T |48 |TFL 48 Chetwynd |
|T |49 |TFL 49 Okanagan |
|T |51 |TFL 51 Cranberry |
|T |52 |TFL 52 Bowron-Cottonwood |
|T |53 |TFL 53 Naver |
|T |54 |TFL 54 Maquinna |
|T |55 |TFL 55 Selkirk |
|T |56 |TFL 56 Goldstream |
|T |57 |TFL 57 Clayoquot |
|U |01 |Arrow TSA |
| | | |
| | | |
|U |02 |Boundary TSA |
|U |03 |Bulkley TSA |
|U |04 |Cassiar TSA |
|U |05 |Cranbrook TSA |
|U |07 |Golden TSA |
|U |08 |Fort Nelson TSA |
|U |09 |Invermere TSA |
|U |10 |Kalum TSA |
|U |11 |Kamloops TSA |
|U |12 |Kispiox TSA |
|U |13 |Kootenay Lake TSA |
|U |14 |Lakes TSA |
|U |15 |Lillooet TSA |
|U |16 |MacKenzie TSA |
|U |17 |Robson Valley TSA |
|U |18 |Merritt TSA |
|U |19 |Mid Coast TSA |
|U |20 |Morice TSA |
|U |21 |North Coast TSA |
|U |22 |Okanagan TSA |
|U |23 |100 Mile House TSA |
|U |24 |Prince George TSA |
|U |25 |Queen Charlotte TSA |
|U |26 |Quesnel TSA |
|U |27 |Revelstoke TSA |
|U |29 |Williams Lake TSA |
|U |29 |Williams Lake TSA |
|U |30 |Fraser TSA |
|U |31 |Soo TSA |
|U |33 |Kingcome TSA |
|U |37 |Strathcona TSA |
|U |38 |Arrowsmith TSA |
|U |39 |Sunshine Coast TSA |
|U |40 |Fort St. John TSA |
|U |41 |Dawson Creek TSA |
|U |42 |Cranberry TSA |
|U |43 |Nass TSA |
|V |01B |Arrow TSA Block B |
|V |01D |Arrow TSA Block D |
|V |01E |Arrow TSA Block E |
|V |01F |Arrow TSA Block F |
|V |01G |Arrow TSA Block G |
|V |01H |Arrow TSA Block H |
|V |01I |Arrow TSA Block I |
|V |01K |Arrow TSA Block K |
|V |01L |Arrow TSA Block L |
|V |01M |Arrow TSA Block M |
|V |02A |Boundary Block A (To be confirmed) |
|V |02B |Boundary Block B (To be confirmed) |
|V |02C |Boundary TSA Block C |
|V |02D |Boundary TSA Block D |
|V |02E |Boundary TSA Block E |
|V |02F |Boundary TSA Block F |
|V |02G |Boundary TSA Block G |
|V |03A |Bulkley TSA Block A |
|V |03B |Bulkley TSA Block B |
|V |03C |Bulkley TSA Block C |
|V |04A |Cassiar TSA Block A |
|V |04B |Cassiar TSA Block B |
|V |04C |Cassiar TSA Block C |
|V |04D |Cassiar TSA Block D |
|V |04E |Cassiar TSA Block E |
|V |04F |Cassiar TSA Block F |
|V |05A |Cranbrook TSA Block A |
|V |05B |Cranbrook TSA Block B |
|V |05D |Cranbrook TSA Block D |
|V |05E |Cranbrook TSA Block E |
|V |05F |Cranbrook TSA Block F |
|V |05G |Cranbrook TSA Block G |
|V |05H |Cranbrook TSA Block H |
|V |05I |Cranbrook TSA Block I |
|V |05J |Cranbrook TSA Block J |
|V |05K |Cranbrook TSA Block K |
|V |05L |Cranbrook TSA Block L |
|V |07A |Golden TSA Block A |
|V |07B |Golden TSA Block B |
|V |07C |Golden TSA Block C |
|V |07D |Golden TSA Block D |
|V |07E |Golden TSA Block E |
|V |07F |Golden TSA Block F |
|V |07G |Golden TSA Block G |
|V |08A |Fort Nelson TSA Liard Block |
|V |08B |Fort Nelson TSA Ft Nelson Blk |
|V |08C |Fort Nelson TSA Sikanni Block |
|V |08D |Fort Nelson TSA Kotcho Block |
|V |08E |Fort Nelson TSA Kechika Block |
|V |09A |Invermere TSA Block A |
|V |09B |Invermere TSA Block B |
|V |09C |Invermere TSA Block C |
|V |09D |Invermere TSA Block D |
|V |09E |Invermere TSA Block E |
|V |09F |Invermere TSA Block F |
|V |09G |Invermere TSA Block G |
|V |10A |Kalum TSA Block A |
|V |10B |Kalum TSA Block B |
|V |10C |Kalum TSA Block C |
|V |10D |Kalum TSA Block D |
|V |10E |Kalum TSA Block E |
|V |10F |Kalum TSA Block F |
|V |11A |Kamloops TSA Block 1 |
|V |11B |Kamloops TSA Block 2 |
|V |11C |Kamloops TSA Block 3 |
|V |11D |Kamloops TSA Block 4 |
|V |12A |Kispiox TSA Block A |
|V |12B |Kispiox TSA Block B |
|V |12C |Kispiox TSA Block C |
|V |12D |Kispiox TSA Block D |
|V |12E |Kispiox TSA Block E |
|V |12F |Kispiox TSA Block F |
|V |13A |Kootenay Lake TSA Block A |
|V |13B |Kootenay Lake TSA Block B |
|V |13C |Kootenay Lake TSA Block C |
|V |13D |Kootenay Lake TSA Block D |
|V |13E |Kootenay Lake TSA Block E |
|V |13F |Kootenay Lake TSA Block F |
|V |13G |Kootenay Lake TSA Block G |
|V |13H |Kootenay Lake TSA Block H |
|V |13I |Kootenay Lake TSA Block I |
|V |13J |Kootenay Lake TSA Block J |
|V |14A |Lakes TSA Block A |
|V |14B |Lakes TSA Block B |
|V |14C |Lakes TSA Block C |
|V |14D |Lakes TSA Block D |
|V |14E |Lakes TSA Block E |
|V |14F |Lakes TSA Block F |
|V |14G |Lakes TSA Block G |
|V |15A |Lillooet TSA Block 1 |
|V |15B |Lillooet TSA Block 2 |
|V |16A |MacKenzie TSA Block A |
|V |16B |MacKenzie TSA Block B |
|V |16C |MacKenzie TSA Block C |
|V |16D |MacKenzie TSA Block D |
|V |16E |MacKenzie TSA Block E |
|V |16F |MacKenzie TSA Block F |
|V |16G |MacKenzie TSA Block G |
|V |16H |MacKenzie TSA Block H |
|V |16I |MacKenzie TSA Block I |
|V |16J |MacKenzie TSA Block J |
|V |16K |MacKenzie TSA Block K |
|V |16L |MacKenzie TSA Block L |
|V |16M |MacKenzie TSA Block M |
|V |16N |MacKenzie TSA Block N |
|V |16O |MacKenzie TSA Block O |
|V |16P |MacKenzie TSA Block P |
|V |17A |McBride TSA Block A |
|V |17B |McBride TSA Block B |
|V |17C |McBride TSA Block C |
|V |17D |McBride TSA Block D |
|V |17E |McBride TSA Block E |
|V |17F |McBride TSA Block J |
|V |17G |McBride TSA Block G |
|V |17H |McBride TSA Block H |
|V |17I |McBride TSA Block I |
|V |17J |McBride TSA Block J |
|V |18A |Merritt TSA Block 1 |
|V |18B |Merritt TSA Block 2 |
|V |18C |Merritt TSA Block 3 |
|V |18D |Merritt TSA Block 4 |
|V |18E |Merritt TSA Block 5 |
|V |18F |Merritt TSA Block 6 |
|V |18G |Merritt TSA Block 7 |
|V |18H |Merritt TSA Block 8 |
|V |18I |Merritt TSA Block 9 |
|V |19A |Mid-Coast TSA Block A |
|V |19B |Mid-Coast TSA Block B |
|V |19C |Mid-Coast TSA Block C |
|V |19D |Mid-Coast TSA Block D |
|V |19E |Mid-Coast TSA Block E |
|V |19F |Mid-Coast TSA Block F |
|V |20A |Morice TSA Block A |
|V |20B |Morice TSA Block B |
|V |20C |Morice TSA Block C |
|V |20D |Morice TSA Block D |
|V |20E |Morice TSA Block E |
|V |21A |North Coast TSA Stewart Block |
|V |21B |North Coast TSA Alice Arm Blk |
|V |21C |North Coast TSA Skeena Block |
|V |21D |N. Coast TSA Outer Coast Blk |
|V |21E |North Coast TSA Douglas Block |
|V |22A |Okanagan TSA Block 1 |
|V |22B |Okanagan TSA Block 2 |
|V |22C |Okanagan TSA Block 3 |
|V |22D |Okanagan TSA Block 4 |
|V |22E |Okanagan TSA Block 5 |
|V |22F |Okanagan TSA Block 6 |
|V |22G |Okanagan TSA Block 7 |
|V |22H |Okanagan TSA Block 8 |
|V |22I |Okanagan TSA Block 9 |
|V |23A |100 Mile House TSA Meadow Blk |
|V |23B |100 Mile House TSA Loon Block |
|V |23C |100 Mile House Bonaparte Blk |
|V |23D |100 Mile House Sheridan Blk |
|V |23E |100 Mile House Holden Block |
|V |23F |100 Mile House Rail Block |
|V |23G |100 Mile House Ruth Block |
|V |23H |100 Mile House Canim Block |
|V |24A |Prince George TSA Block A |
|V |24B |Prince George TSA Block B |
|V |24C |Prince George TSA Block C |
|V |24D |Prince George TSA Block D |
|V |24E |Prince George TSA Block E |
|V |24F |Prince George TSA Block F |
|V |24G |Prince George TSA Block G |
|V |24H |Prince George TSA Block H |
|V |24I |Prince George TSA Block I |
|V |25A |Queen Charlotte TSA Block A |
|V |25B |Queen Charlotte TSA Block B |
|V |25C |Queen Charlotte TSA Block C |
|V |25D |Queen Charlotte TSA Block D |
|V |26A |Quesnel TSA South Kluskus Blk |
|V |26B |Quesnel TSA Narcosli West Blk |
|V |26C |Quesnel TSA Narcosli East Blk |
|V |26D |Quesnel TSA S.S.A. Block |
|V |26E |Quesnel TSA Cottonwood Block |
|V |26F |Quesnel TSA Big Valley Block |
|V |26G |Quesnel TSA Bowron Block |
|V |26H |Quesnel TSA Cunningham Block |
|V |26I |Bowron (UNREG) |
|V |27A |Revelstoke TSA Block A |
|V |27D |Revelstoke TSA Block D |
|V |27E |Revelstoke TSA Block E |
|V |27F |Revelstoke TSA Block F |
|V |27G |Revelstoke TSA Block G |
|V |27U |Revelstoke TSA Block U |
|V |27V |Revelstoke TSA Block V |
|V |27W |Revelstoke TSA Block W |
|V |27X |Revelstoke TSA Block X |
|V |27Y |Revelstoke TSA Block Y |
|V |29A |Wms Lk TSA Anahim Block |
|V |29B |Wms Lk TSA Chezacut Block |
|V |29C |Wms Lk TSA Tatla Block |
|V |29D |Wms Lk TSA Chilcotin Block |
|V |29E |Wms Lk TSA Kloacut Block |
|V |29F |Wms Lk TSA Gaspard Block |
|V |29G |Wms Lk TSA Churn Block |
|V |29H |Wms Lk TSA Springhouse Block |
|V |29I |Wms Lk TSA Palmer Lake Block |
|V |29J |Wms Lk TSA Skelton Block |
|V |29K |Wms Lk TSA Moffat Block |
|V |29L |Wms Lk TSA Cariboo Block |
|V |29M |Wms Lk TSA Upper Horsefly Blk |
|V |29N |Wms Lk TSA Junction Block |
|V |30B |Fraser TSA Chilliwack Block |
|V |30C |Fraser TSA Harrison Block |
|V |30D |Fraser TSA Yale Block |
|V |30E |Fraser TSA Nahatlatch Block |
|V |30F |Fraser TSA Stave Block |
|V |30G |Fraser TSA Upper Pitt Block |
|V |30H |Fraser TSA Maple Ridge Block |
|V |31A |Soo TSA Squamish Block |
|V |31B |Soo TSA Port Douglas Block |
|V |31C |Soo TSA Pemberton Block |
|V |33A |Kingcome TSA Brooks Block |
|V |33B |Kingcome TSA Cape Scott Block |
|V |33C |Kingcome TSA Seymour Block |
|V |33D |Kingcome TSA Broughton Block |
|V |33F |Kingcome TSA Klinaklini Block |
|V |37A |Strathcona TSA Sayward Block |
|V |37B |Strathcona TSA Kyuquot Block |
|V |37D |Strath. TSA Loughborough Blk |
|V |38A |Arrowsmith TSA, Barkley S.B. |
|V |38B |Arrowsmith TSA Nanaimo Block |
|V |38C |Arrowsmith TSA Cowichan Block |
|V |39B |Sunsh Coast TSA Sechelt Block |
|V |39C |Sunsh Coast TSA Powell R. Blk |
|V |40A |Fort St John TSA Block A |
|V |40B |Fort St John TSA Block B |
|V |40C |Fort St John TSA Block C |
|V |40D |Fort St John TSA Block D |
|V |40E |Fort St John TSA Block E |
|V |40F |Fort St John TSA Block F |
|V |41A |Dawson Creek TSA Block A |
|V |41B |Dawson Creek TSA Block B |
|V |41C |Dawson Creek TSA Block C |
|V |41D |Dawson Creek TSA Block D |
|V |41E |Dawson Creek TSA Block E |
|V |41F |Dawson Creek TSA Block F |
|V |42A |Cranberry Creek TSA Block A |
|V |43A |Nass TSA Stewart Block |
|V |43E |Nass TSA Block E |
|W |01 |Greater Vancouver Watershed Lease |
* See Management Unit Type
Management Unit
|Code |Description |
|A |AGRICULTURAL LAND RESERVE |
|B |BLUE MOUNTAIN FOREST RESERVE |
|C |COMMUNITY FOREST |
|D |DOMINION GOVERNMENT BLOCK |
|E |E & N LAND BELT |
|F |Woodlot |
|G |GULF ISLANDS |
|H |Organizational Unit Designation |
|J |ECOLOGICAL RESERVE |
|K |PROVINCIAL FOREST |
|L |WILDERNESS AREA |
|N |TREATY SETTLEMENT LANDS |
|O |PUBLIC SUSTAINED YIELD UNIT |
|P |PARKS & WILDERNESS CONSERV. |
|R |RECREATIONAL AREA |
|S |SPECIAL SALE AREA |
|T |TREE FARM LICENCE |
|U |TIMBER SUPPLY AREA |
|V |TIMBER SUPPLY BLOCK |
|W |WATERSHED LEASE OR RESERVE |
|X |CERTIFIED TREE FARM |
|Z |Outside Managed Units |
Marking Instrument
|Code |Description |
|B |Paint and/or Crayon |
|C |Crayon |
|H |Hammer |
|P |Paint |
|T |Tag |
Marking Method
|Code |Description |
|0 |100% Marking |
|1 |100% One End |
|2 |2 Marks Front, 2 on Sides |
|3 |2 Marks Front, 2 on Sides; 100% at Site |
|4 |Four Corner Marking |
|5 |4 Corner Marking to Site; 100% at Site |
|8 |Eight corner marking |
|A |35% Mark Painted Orange on Each Side of Load |
|B |35% Mark Painted Blue on Each Side of Load |
|C |20% With 16 Log Minimum |
|D |Bottom Tier Front and Back on Area, 100% at Scale Site |
|E |Exempt From Marking |
|S |Full, Standard Marking |
Reforestation Declaration
|Code |Description |
|CON |Coniferous |
|DEC |Deciduous |
|MIX |Mix |
Salvage Type
|Code |Description |
|SSS |Small Scale/Patch Salvage |
|BBR |Bark Beetle Cut Regulation |
Special Use Code
|Code |Description |
|01 |Agriculture |
|02 |Aquaculture |
|03 |Industrial |
|04 |Commercial |
|05 |Residential |
|06 |Utility |
|07 |Community |
|08 |Institutional |
|09 |Quarrying |
|10 |Transportation |
|11 |Communication |
|12 |Miscellaneous Land Use |
|13 |Trappers Cabin |
|14 |Dryland Sort |
|15 |Logging Camp, Shop, Offices |
|16 |Waste Disposal |
|17 |Gravel Pit, Rock Quarry |
|18 |Repeater Site |
|19 |Road, Right of Way |
|20 |Airstrip, Landing Field |
|21 |Lookout, Weather Station |
|22 |Map Notation |
|23 |Grazing |
|24 |Recreation |
|25 |Non-Profit, Charity Organization |
|26 |Governmental |
|27 |Miscellaneous Forest Use |
|28 |Millsite |
|29 |Magazine, Explosive Site |
|30 |Research |
|31 |Christmas Trees |
Error Messages
Data Submission (Error Messages)
This section describes all acceptable values for those fields requiring specific codes. The descriptions for each field include a reference to the applicable table where applicable.
• 1 - An unexpected error has occurred in the package/procedure
• 2 - At least one Preferred Species must exist before approval
|200 - {value} - The Cut Block ID is mandatory |
| |
|Solution |
| |
|The Cut Block ID is mandatory |
|201 - {value} - Geometry is required for the cut block. Geometry is only optional for cut blocks that are for Bark Beetle or |
|Small Scale Salvage CP's and that are less than 1 ha in size. |
| |
|Solution |
| |
|Geometry is required for the cut block. Geometry is only optional for cut blocks that are for Bark Beetle or Small Scale Salvage|
|CP's and that are less than 1 ha in size. |
|203 - {value} - The Planned Harvest Date is mandatory |
| |
|Solution |
| |
|The Planned Harvest Date is mandatory |
|204 - {value} - Planned Net Area ({value}) must be less than or equal to the area of the geometry supplied for the cut block |
|({value}). |
| |
|Solution |
| |
|Planned Net Area must be less than or equal to the area of the geometry supplied for the cut block. |
|205 - {value} - Planned Net Area ({value}) must be less than or equal to Planned Gross Area ({value}). |
| |
|Solution |
| |
|Planned Net Area must be less than or equal to Planned Gross Area |
|206 - {value} - The Planned Net Area is mandatory |
| |
|Solution |
| |
|The Planned Net Area is mandatory |
|207 - {value} - The Application Purpose is mandatory |
| |
|Solution |
| |
|The Application Purpose is mandatory |
|208 - {value} - If you are specifying this block as ''Owned By'' another tenure, then you must specify an ''ownedbyFile'' and |
|optionally an ''ownedByCP''. If this block is not ''Owned By'' another tenure, then the ''ownedbyFile'' and ''ownedByCP'' |
|elements must not be entered. |
| |
|Solution |
| |
|If you are specifying this block as 'Owned By' another tenure, then you must specify by an 'ownedbyFile' and optionally an |
|'ownedByCP'. If this block is not 'Owned By' another tenure, then the 'ownedbyFile' and an 'ownedByCP' elements must not be |
|entered. |
|209 - There was a problem processing your submission. Please contact APPHELP with the following information: {value}. |
| |
|Solution |
| |
|Please contact APPHELP. |
|400 - CP exists already. |
| |
|Solution |
| |
|The CP already exists. |
|401 - CP ID can only be 1 letter. |
| |
|Solution |
| |
|The CP ID can only be 1 letter long. |
|402 - CP ID cannot contain I or O. |
| |
|Solution |
| |
|The CP ID cannot contain a I or a O. |
|403 - CP ID can only be 1 letter. |
| |
|Solution |
| |
|The CP ID can only be 1 letter long. |
|404 - CP ID cannot contain spaces or special characters or the letters I and O. |
| |
|Solution |
| |
|The CP ID cannot contain spaces or special characters or the letters I and O. |
|405 - CP ID cannot be more than 2 letters. |
| |
|Solution |
| |
|The CP ID cannot be more than 2 letters. |
|406 - The Application Purpose is required to process this application |
| |
|Solution |
| |
|The Application Purpose is required to process this application |
|407 - Invalid Application. Please contact APPHELP with the following information: {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|408 - Unable to generate BCGS Map Reference: {value} |
| |
|Solution |
| |
|The application was unable to generate a BCGS Map Reference. Please contact APPHELP. |
|409 - The supplied client number/lcoation code is not a valid client of the Ministry of Forests. {value}/{value} |
| |
|Solution |
| |
|The supplied client number/lcoation code is not a valid client of the Ministry of Forests. {value}/{value} |
|410 - A valid client must be supplied in the submission. |
| |
|Solution |
| |
|A valid client must be supplied in the submission. |
|411 - Invalid file type ({value}) specified. Please contact APPHELP. |
| |
|Solution |
| |
|You have entered an invalid file type code. |
|412 - Error retrieving User information from FTA user directory. Please contact APPHELP with the following information: {value}.|
|{value} |
| |
|Solution |
| |
|Error retrieving User information from FTA user directory. |
|413 - The Special Use Code is invalid |
| |
|Solution |
| |
|The Special Use Code is invalid |
|414 - {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|415 - Client {value} is not the district manager for {value} |
| |
|Solution |
| |
|The client number is not the district manager for District. |
|416 - The file id {value} generated already exists. There is a problem with the control table. Please notify Application |
|Services (250-387-8888) |
| |
|Solution |
| |
|The forest file ID already exists. |
|417 - Cruise Volume is required in submission for amendments. |
| |
|Solution |
| |
|Cruise Volume is required in submission for amendments. |
|418 - Amendment {value} already exists for cut block {value} |
| |
|Solution |
| |
|The amendment ID already exists for the cut block. HARVEST_AMEND.dup_val_on_index error occurred creating amendment for Cut |
|Block. |
|419 - Owned By File/CP: {value} {value}: Amendment {value} already exists for cut block {value} |
| |
|Solution |
| |
|The Amendment ID already exists for this cut block. HARVEST_AMEND.dup_val_on_index error occurred creating amendment for Owned |
|by Block. |
|420 - Invalid Owned By File: {value}; |
| |
|Solution |
| |
|Unexpected error occurred getting timber mark for Owned By File. Please check the value. It does not exist in |
|FTA. |
|421 - {value} files may not be amended. |
| |
|Solution |
| |
|U1/U2 files may not be amended. |
|422 - {value} cp(s) cannot have an Owned By file/cp specified. |
| |
|Solution |
| |
|Files of this type cannot have an owned by file/cp specified. Only Woodlots, TFLs, Community Forests and Consolidated Licences |
|can. |
|423 - Client {value} is not the licensee for this cutting permit. |
| |
|Solution |
| |
|Client number is not the licensee for this cutting permit. |
|424 - Client {value} is not the licensee for this mark. |
| |
|Solution |
| |
|Client number is not the licensee for this mark. |
|427 - Owned By File/CP: {value} {value} Block: {value}. This block already exists. |
| |
|Solution |
| |
|Cut block already exists. Check your purpose code. |
|428 - Error occured generating file id. |
| |
|Solution |
| |
|An error occurred generating the file ID. Please contact APPHELP. |
|429 - File type of given file id must be the same as the submitted file type. |
| |
|Solution |
| |
|The in the xml file does not match the file type of the file id provided in . You do not really|
|need to supply the file type if file id is supplied as the system by default will use the file type of the given file. |
|430 - File Type not found for given file. |
| |
|Solution |
| |
|The file type cannot be found for the given file you have provided. |
|431 - Unexpected error occured inserting FOR_CLIENT_LINK. |
| |
|Solution |
| |
|Please contact APPHELP. |
|432 - {value} is an invalid amendment reason. |
| |
|Solution |
| |
|There was an invalid amendment reason. Please contact APPHELP. |
|433 - Client {value} is not the licensee for this file. |
| |
|Solution |
| |
|The Client number is not the licensee for this file. |
|434 - Cut Block does not exist. |
| |
|Solution |
| |
|The Cut Block does not exist in FTA. Please check the value in your xml file. |
|438 - Cannot convert U1 (single mark) file to {value} type. |
| |
|Solution |
| |
|Cannot convert a 'U1' single mark file to a 'p' file type code. |
|439 - Invalid BCTS org unit |
| |
|Solution |
| |
|The BCTS office supplied is incorrect. Please check the value in your xml file. |
|440 - Invalid occupant licence to cut code: {value} |
| |
|Solution |
| |
|Please check the value in your xml file. |
|441 - Invalid District Code |
| |
|Solution |
| |
|Please check the value in your xml file. |
|442 - Unexpected error occurred retrieving timber mark for file/cp |
| |
|Solution |
| |
|An error occurred retrieving the timber mark for file/cp. Please Contact APPHELP. |
|443 - Invalid file type for this submission |
| |
|Solution |
| |
|Please check the value in your xml file. For Road applications this value should be (B40, B01). For Range |
|applications this value should be (E01,E02,E03,H01,H02,H03). For Harvest No CP this value should be |
|(B02,B04,B05,B06,B07,U1,S01,S02). For new Admin Area this value should be C01. |
|444 - Invalid Forest File ID |
| |
|Solution |
| |
|Please check the value in your xml file. It does not exist in FTA. |
|445 - Invalid forestry licence to cut code: {value} |
| |
|Solution |
| |
|Please check the value in your xml file. |
|446 - Invalid Management Type/Unit: {value} {value} |
| |
|Solution |
| |
|Please check the and values in your xml file. |
|447 - Amendments can only be processed for issued/active tenures. |
| |
|Solution |
| |
|The file or cp you are trying to amend must be in HI status. For range tenures the file must be in A status. Please contact the |
|district and they can change the status. |
|448 - Invalid special use permit code: {value} |
| |
|Solution |
| |
|Please check the value in your xml file. |
|449 - Duplicate Error occured inserting LICENCE_TO_CUT. |
| |
|Solution |
| |
|A duplicate error occurred inserting LICENCE_TO_CUT. Please contact APPHELP. |
|450 - Unexpected error occured inserting LICENCE_TO_CUT. |
| |
|Solution |
| |
|An error occurred inserting LICENCE_TO_CUT. Please contact APPHELP. |
|452 - Owned By File/CP: {value} {value} Block: {value}. This block does not exist. |
| |
|Solution |
| |
|Cut block already exists. Check your purpose code. |
|456 - Could not assign CP id as maximum has been reached. |
| |
|Solution |
| |
|Could not assign a CP id as the maximum has been reached. |
|457 - Amendment reason must be provided in XML file for block |
| |
|Solution |
| |
|An amendment reason must be provided in XML file. |
|458 - File type must be provided in submission |
| |
|Solution |
| |
|A file type must be provided in submission. |
|459 - Supplied file type {value} is not the same as the file type of the given file: {value} |
| |
|Solution |
| |
|The supplied file type is not the same as the given file type. |
|460 - Cut blocks are not valid for this type |
| |
|Solution |
| |
|Cut blocks are not applicable for Special Use/Christmas Tree Permits. |
|461 - You have specified an Owned By CP without an Owned By File. Take out the Owned By fields if this block is not owned by a |
|private mark or timber licence. |
| |
|Solution |
| |
|You have specified an Owned By CP without an Owned By File. Take out the Owned By fields if this block is not owned by a private|
|mark or timber licence, |
|462 - Update of BCTS file type failed |
| |
|Solution |
| |
|Contact MOF Application Services help desk and give them the submission id so they may look into it. |
|463 - Unexpected error occured inserting PRMT_AUTHZD_BLK. |
| |
|Solution |
| |
|An unexpected error occured inserting PRMT_AUTHZD_BLK. Please contact APPHELP. |
|464 - Error occurred processing file type. |
| |
|Solution |
| |
|An error occurred processing the file type. Please contact APPHELP. |
|465 - Error occurred processing Oil and Gas application |
| |
|Solution |
| |
|An error occurred processing the Oil and Gas application. Please contact APPHELP. |
|466 - Duplicate File ID error occurred inserting PROV_FOREST_USE for {value} . |
| |
|Solution |
| |
|A duplicate File ID error occurred inserting PROV_FOREST_USE. Please contact APPHELP. |
|467 - Unexpected error occured inserting PROV_FOREST_USE. |
| |
|Solution |
| |
|An error occurred inserting PROV_FOREST_USE. Please contact APPHELP. |
|468 - For BCTS Forestry Licence To Cuts the purpose code must be RW - Right of Way. |
| |
|Solution |
| |
|For BCTS Forestry Licence To Cuts the purpose code must be RW - Right of Way. |
|469 - You should take out the Owned By fields if this block is not owned by a private mark or timber licence. |
| |
|Solution |
| |
|You should take out the Owned By fields if this block is not owned by a private mark or timber licence. |
|470 - Duplicate record occurred inserting SPEC_USE_PERMIT. |
| |
|Solution |
| |
|A duplicate record occurred inserting SPEC_USE_PERMIT. Please contact APPHELP. |
|471 - Unexpected error occured inserting SPEC_USE_PERMIT. |
| |
|Solution |
| |
|An error occurred inserting SPEC_USE_PERMIT. Please contact APPHELP. |
|472 - Unexpected error occured inserting TENURE_TERM. |
| |
|Solution |
| |
|An error occurred inserting TENURE_TERM. Please contact APPHELP. |
|473 - The timber mark {value} generated already exists. |
| |
|Solution |
| |
|The timber mark {value} generated already exists. |
|474 - Duplicate Timber Mark error occured inserting TIMBER_MARK {value} |
| |
|Solution |
| |
|A duplicate Timber Mark error occured inserting TIMBER_MARK. Please contact APPHELP. |
|475 - Unexpected error occured inserting TIMBER_MARK. |
| |
|Solution |
| |
|An error occured inserting TIMBER_MARK. Please contact APPHELP. |
|476 - An error occurred validating the Road Tenure application. |
| |
|Solution |
| |
|An error occurred validating Road Tenure application. Please contact APPHELP. |
|477 - This file does not belong to {value} office. |
| |
|Solution |
| |
|The BCTS office you are from does not own this file. If you are not from BCTS then there should be no in your |
|xml file. |
|478 - Only BCTS may submit U1/U2 files. If you are from BCTS then check your submission and ensure BCTS office is supplied. |
| |
|Solution |
| |
|There should be a in your xml file. |
|479 - Cannot convert U1 file to {value} type. |
| |
|Solution |
| |
|For BCTS multi mark applications the file type must be a TSL minor mark type (A20,A21,A23,A24). Please check the |
|value in your xml file. |
|480 - Cannot convert U2 file to {value} type. |
| |
|Solution |
| |
|For BCTS cutting permit applications the file type must be a TSL major type (A25,A26,A27). Please check the value|
|in your xml file. |
|481 - This {value} cannot be converted to a blank file type. Please ensure that file type is provided in the submission. |
| |
|Solution |
| |
|Please check that is in the xml file. For BCTS applications the file type that you want to convert your U1/U2 |
|file to must be supplied. |
|482 - For {value} BCTS applications the conversion file type must be provided |
| |
|Solution |
| |
|Please check that is in the XML file. For U2 files this file type should be one of (A25,A26,A27). For U1 files |
|this file type should be one of (B20,B21). If you are not from BCTS then there should be no in your xml file. |
|483 - District {value} does not match the file''s administrative org {value}. |
| |
|Solution |
| |
|District must be the same as the file's admin org. |
|484 - Owned By File {value} {value} does not exist |
| |
|Solution |
| |
|Please check the value. It does not exist in FTA. |
|485 - If you are not a BCTS submitter do not provide a bcts office in the submission. |
| |
|Solution |
| |
|If you are not from BCTS then there should be no in your xml file. |
|486 - District {value} is not within the file''s administrative org {value}. |
| |
|Solution |
| |
|District must be within the file's admin org. |
|487 - Cut block already exists |
| |
|Solution |
| |
|The Owned By Cut block already exists. |
|488 - Owned By File {value} {value} is owned by another licensee |
| |
|Solution |
| |
|The licensee for the private mark or Timber Licence must be the same as the licensee for the cutting permit managing it. |
|489 - Owned by file {value} must be in the same district as {value} CP {value} |
| |
|Solution |
| |
|The owned by file must be in the same district as the cutting permit managing it. |
|490 - Owned by file {value} must be in the same region as {value} |
| |
|Solution |
| |
|The TL block must be in the same region as the cutting permit managing it. |
|491 - Owned By File {value} {value} already exists. You cannot submit an existing TL CP within a new Consolidated TL CP. |
| |
|Solution |
| |
|The Timber Licence cutting permit you have supplied in the Owned By already exists. For new TFL/Consolidated TL cutting permits |
|the TL CP cannot already exist. |
|492 - Owned By File {value} {value} already exists. You cannot submit an existing TL CP within a new TFL CP. |
| |
|Solution |
| |
|The Timber Licence cutting permit you have supplied in the Owned By already exists. For new TFL/Consolidated TL cutting permits |
|the TL CP cannot already exist. |
|493 - File type of Owned By {value} must be a Timber Licence (A06). |
| |
|Solution |
| |
|For A30 Consolidated Timber Licence the Owned By file must be an A06 Timber Licence. A30 may only manage Timber Licence cut |
|blocks. |
|494 - File type of Owned By {value} must be a Timber Licence (A06) or Private Mark (B08,B09,B14) |
| |
|Solution |
| |
|File type of Owned By must be a Timber Licence (A06) or Private Mark (B08,B09,B14). |
|495 - Owned By File {value} does not exist |
| |
|Solution |
| |
|Please check the value. It does not exist in FTA. |
|496 - Timber Licence {value} is in {value} status. It must be in HI status. |
| |
|Solution |
| |
|Please ask MOF to change the cutting permit status of the TL CP to HI. |
|497 - The submitted district code (administrative district) is invalid. |
| |
|Solution |
| |
|The submitted district code (administrative district) is invalid. |
|498 - There was an error retrieving client information for the logged on user. Please contact APPHELP with the following |
|information: {value} - {value} |
| |
|Solution |
| |
|There was an error retrieving client information for the logged on user. Please contact APPHELP. |
|499 - {value} - The Capture Method Code is invalid |
| |
|Solution |
| |
|The Capture Method Code is invalid. |
|502 - This application is currently being processed and cannot be processed until the existing one is complete |
| |
|Solution |
| |
|This application is currently being processed and cannot be processed until the existing one is complete |
|503 - District user is not in the same district that the submission is being submitted to |
| |
|Solution |
| |
|District user is not in the same district that the tenure belongs to. |
|504 - {value} - The Data Source Code is invalid |
| |
|Solution |
| |
|The Data Source Code is invalid |
|505 - Error building final Geometry {value} |
| |
|Solution |
| |
|There was an error building the final geometry. Please contact APPHELP. |
|506 - Forest File ID is required when the Application Purpose is ''A''mend |
| |
|Solution |
| |
|Forest File ID is required when the Application Purpose is 'A'mend |
|507 - There is an invalid combination of 2D and 3D coordinates. GML must be all 2D or all 3D |
| |
|Solution |
| |
|GML msut be all two dimensional or all three dimensional coordinates, not any combination. |
|508 - Expected 2 coordinates for the GML Box element but only {value} found at line {value} |
| |
|Solution |
| |
|Expected 2 coordinates for the GML Box element but only found at line. |
|509 - Invalid coordinate specified ( {value} ) at line {value} |
| |
|Solution |
| |
|Invalid coordinate system specified in the GML ({value} at line 1). |
|510 - Invalid coordinate system specified in the GML: {value} on line {value} is not a number |
| |
|Solution |
| |
|Invalid coordinate system specified in the GML (srsName). |
|511 - Error while validating/reprojecting/applying precision to geometry. Please contact APPHELP with the following infromation:|
|{value} |
| |
|Solution |
| |
|Error while validating/reprojecting/applying precision to geometry. Please contact APPHELP, if required. |
|512 - Error constructing a Box: {value} |
| |
|Solution |
| |
|Error constructing a Box. Please contact APPHELP. |
|513 - Error constructing a LinearRing at line {value} {value} |
| |
|Solution |
| |
|Error constructing a LinearRing at line. Please contact APPHELP, if required. |
|514 - Error constructing a LineString at line {value} {value} |
| |
|Solution |
| |
|Error constructing a LineString at line. Please contact APPHELP, if required. |
|515 - Error constructing a Point at line {value} {value} |
| |
|Solution |
| |
|Error constructing a Point at line. Please contact APPHELP, if required. |
|516 - Error constructing a Polygon at line {value} : {value} |
| |
|Solution |
| |
|Error constructing a Polygon at line. Please contact APPHELP, if required. |
|517 - Error parsing coordinate points at line {value} {value} |
| |
|Solution |
| |
|Error parsing coordinate points at line. Please contact APPHELP, if required. |
|518 - There is an invalid character [{value}] with code [1] |
| |
|Solution |
| |
|There is an invalid GML character [{value}] with code [{value}] |
|519 - There is no coordinate system specified in the GML |
| |
|Solution |
| |
|There is no coordinate system specified in the GML (srsName). |
|520 - Invalid map feature type ({value}) specified. Please contact APPHELP. |
| |
|Solution |
| |
|Invalid map feature type specified. Please contact APPHELP. |
|521 - This file can not be amended until the spatial data has been converted |
| |
|Solution |
| |
|This file can not be amended until the spatial data has been converted. |
|522 - You are not authorized to submit for the client identified in the submission. |
| |
|Solution |
| |
|You are not authorized to submit for the client identified in the application. |
|523 - District user is not authorized to submit on behalf of a licencee |
| |
|Solution |
| |
|District user is not authorized to submit on behalf of a licencee. |
|524 - There is no corresponding Feature Class for file type {value} and map feature type {value}. Please contact APPHELP. |
| |
|Solution |
| |
|There is no corresponding Feature Class for file type and map feature type. |
|525 - Submitter User ID does not exist in the FTA directory |
| |
|Solution |
| |
|Logged on User ID does not exist in the FTA user directory. |
|526 - FTASecurityManager: no webADE user |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|527 - Submission ID: {value} is not supported by this agent; unsupported schema |
| |
|Solution |
| |
|Your submission is not supported by FTA. |
|528 - There was an error retrieving org unit informtion for the submitted user. Please contact APPHELP with the following |
|information: {value} |
| |
|Solution |
| |
|There was an error retrieving org unit information for the logged on user. |
|530 - There was a problem processing your submission. Please contact APPHELP with the following information: {value}. {value} |
| |
|Solution |
| |
|There is a problem processing your submission. Please contact APPHELP. |
|531 - FTA does not currently support users belonging to both BCTS and FS organizational units. Please contact APPHELP. |
| |
|Solution |
| |
|FTA does not currently support users belonging to both BCTS and FS organizational units. |
|532 - Error getting WHSE SDE connection: {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|533 - Unable to fail one or more applications; ie set the status to FAI - {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|534 - Spatial feature already exists. Please contact APPHELP |
| |
|Solution |
| |
|Please contact APPHELP. |
|535 - There was an error saving the spatial feature. Please contact APPHELP. |
| |
|Solution |
| |
|Please contact APPHELP. |
|600 - Error closing connection: {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|601 - Error getting OSDB SDE connection: {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|603 - Error getting database connection from queue connection: {value} |
| |
|Solution |
| |
|There was an error getting a database connection. Please contact APPHELP. |
|604 - Unable to connect to queue: {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|605 - Error occurred when attempting to send TenureApplication Object to sub agents. {value} |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|606 - FTASecurityManager: user is null |
| |
|Solution |
| |
|There was a problem processing your submission. Please contact APPHELP. |
|801 - Application Description for the Harvest No CP Application is mandatory |
| |
|Solution |
| |
|Application Description for the Harvest No CP Application is mandatory. |
|802 - File Type is required when the Application Purpose is ''N''ew |
| |
|Solution |
| |
|File Type is required when the Application Purpose is 'N'ew. |
|803 - The Geographic District for the Harvest No CP Application is mandatory |
| |
|Solution |
| |
|The Geographic District for the Harvest No CP Application is mandatory. |
|804 - The Management Unit ID for the Harvest No CP Application is mandatory |
| |
|Solution |
| |
|The Management Unit ID for the Harvest No CP Application is mandatory for new applications. |
|805 - The Management Unit Type for the Harvest No CP Application is mandatory |
| |
|Solution |
| |
|The Management Unit Type for the Harvest No CP Application is mandatory for new applications. |
|807 - The Application Purpose for the Harvest No CP Application is mandatory |
| |
|Solution |
| |
|The Application Purpose for the Harvest No CP Application is mandatory. |
|808 - If file id specified then it must be in PA status for new application. |
| |
|Solution |
| |
|If a file id is supplied for new applications then the file must be in PA status. If you had the file created ahead of time in |
|FTA with the intent of making a spatial submission then it should already be in PA status. Contact MOF Application Services help|
|desk and give them the submission id so they may look into it. They will either change the status to PA if it is the correct |
|action or they may change the status to HI and ask you to amend instead. |
|809 - File is not the right type |
| |
|Solution |
| |
|For Harvest no CP applications the file must be a major licence (eg. A01 Forest Licence, A02 Tree Farm Licence, A04 Woodlot, |
|etc.). |
|810 - Error occurred processing File no CP application |
| |
|Solution |
| |
|An error occurred processing File no CP application. Please contact APPHELP. |
|811 - Error occurred validating File no CP application |
| |
|Solution |
| |
|An error occurred validating File no CP application. Please contact APPHELP. |
|1000 - File ID is mandatory if BCTS org unit is given. |
| |
|Solution |
| |
|BCTS submitters must provide the file id in the xml file for new applications. If you are not from BCTS then remove the |
| from the xml file. |
|1001 - Duplicate Cut Block detected |
| |
|Solution |
| |
|This cut block already exists in FTA. Please check your xml file and ensure that the cut blocks(s) are unique. |
|1002 - Unexpected error occured inserting CUT_BLOCK. |
| |
|Solution |
| |
|Contact MOF Application Services help desk and give them the submission id so they may look into it. |
|1003 - Unexpected error occured inserting CUT_BLOCK_OPEN_ADMIN. |
| |
|Solution |
| |
|The CUT_BLOCK_OPEN_ADMIN_SEQ.nextval already existed. Please contact APPHELP and give them the submission id so they may look |
|into it. |
|1004 - Unexpected error occured inserting CUT_BLOCK_OPEN_ADMIN. |
| |
|Solution |
| |
|Please contact APPHELP. |
|1005 - Cut Block already exists. |
| |
|Solution |
| |
|Cut Block ID already exists in FTA. |
|1006 - Unexpected error occured inserting HARVEST_AMEND. |
| |
|Solution |
| |
|An error occurred inserting HARVEST_AMEND. Please contact APPHELP. |
|1007 - Unexpected error occured inserting HARVEST_SALE. |
| |
|Solution |
| |
|An error occurred inserting HARVEST_SALE. Please contact APPHELP. |
|1008 - This file cannot be amended due to it being a U1 or U2. |
| |
|Solution |
| |
|You cannot amend a file that is currently a U1 or U2. For these type of files the application purpose should be 'N' and the file|
|type that you want to change it to must be provided. Please check that you have entered the correct file id. |
|1009 - Invalid amendment reason |
| |
|Solution |
| |
|The amendment reason for the cut block is not valid. Please check the code you have entered. |
|1011 - Cannot amend a cutblock within a New CP |
| |
|Solution |
| |
|The cut block application purpose must be N for new applications. |
|1012 - Cutblock does not exist for File/CP |
| |
|Solution |
| |
|The Cut Block does not exist in FTA. Please check the value in your xml file. For example you may have entered 001 instead of |
|01. |
|1013 - Block status must be HB before it can be amended |
| |
|Solution |
| |
|Block status must be HB before it can be amended. Please ask district to change the status to HB if you need to amend the block.|
|1014 - File type of given file must be a U1. |
| |
|Solution |
| |
|If you are a BCTS submitter the file must be a U1 for new Harvest No CP application. Please check the file id in the xml file. |
|If you are not from BCTS please remove from the xml file. |
|1015 - Block {value} is being managed within {value} CP {value}. You need to submit the amendment under that CP instead. |
| |
|Solution |
| |
|This TL block is being managed under the specified file/cp and needs to be submitted against it instead. The owned by fields |
|should be set to the TL file/cp. |
|1016 - Block {value}: For Consolidated Timber Licences the Owned by fields must be provided in the xml file. |
| |
|Solution |
| |
|You must specify the TL cutting permit that the block belongs to for Consolidated Timber Licences. Ensure the Owned by Fields |
|are filled in. |
|1017 - Block {value} is being managed within {value} CP {value}. You need to submit the amendment under that CP instead. |
| |
|Solution |
| |
|This block is being managed under the specified file/cp and needs to be submitted against it instead. |
|1018 - Block {value} is not being managed within {value} CP {value}. |
| |
|Solution |
| |
|This block does not have an entry in PRMT_AUTHZD_BLK. If this block truly is being managed within this CP request a datafix and |
|resubmit afterwards. |
|1200 - CP ID is required for a new CP application. |
| |
|Solution |
| |
|Cutting Permit ID is required for new cutting permit applications. Please ensure XML file has the field filled in. |
|1201 - Unable to generate Within ALR Indicator: {value} |
| |
|Solution |
| |
|Please contact APPHELP. |
|1202 - The Cruise Based Indicator for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Cruise Based Indicator for the Harvest with CP Application is mandatory for new applications. |
|1203 - The Crown Granted Indicator for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Crown Granted Indicator for the Harvest with CP Application is mandatory for new applications. |
|1204 - The Catastrophic Indicator for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Catastrophic Indicator for the Harvest with CP Application is mandatory for new applications. |
|1205 - The Cutting Permit ID for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Cutting Permit ID for the Harvest with CP Application is mandatory. |
|1207 - Application Description for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|Application Description for the Harvest with CP Application is mandatory. |
|1208 - The Deciduous Indicator for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Deciduous Indicator for the Harvest with CP Application is mandatory for new applications. |
|1209 - Forest File ID for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|Forest File ID for the Harvest with CP Application is mandatory. |
|1210 - The Geographic District for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Geographic District (district) for the Harvest with CP Application is mandatory. |
|1211 - You must supply geometry for the Cutting Permit in this application. |
| |
|Solution |
| |
|You must supply geometry for the Cutting Permit in this application. |
|1212 - The Marking Instrument Code for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Marking Instrument Code for the Harvest with CP Application is mandatory for new applications. |
|1213 - The Marking Method Code for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Marking Method Code for the Harvest with CP Application is mandatory for new applications. |
|1215 - The Application Purpose for the Harvest with CP Application is mandatory |
| |
|Solution |
| |
|The Application Purpose for the Harvest with CP Application is mandatory. |
|1216 - Unable to generate cutting permit geometry: {value} |
| |
|Solution |
| |
|There was a problem generating the Cutting Permit boundary from the supplied Cut Block boundaries. Please contact APPHELP. |
|1217 - CP already exists. |
| |
|Solution |
| |
|For new cutting permit applications the file/cp id must not already exist in FTA. If this CP is new you may ask to have the CP |
|deleted from FTA and you can resubmit or you may amend the CP instead. If you do amend ensure the CP status in FTA is at HI. |
|1218 - Invalid File/CP |
| |
|Solution |
| |
|The file/cp combination does not exist in FTA. For example CP 001 is not the same as CP 1. |
|1219 - Invalid Harvesting w/CP File. Incorrect file type for CP application. |
| |
|Solution |
| |
|For cutting permit applications/amendments the file must be a major licence (eg. A01 Forest Licence, A02 Tree Farm Licence, A04 |
|Woodlot, etc.). |
|1220 - Invalid marking instrument code |
| |
|Solution |
| |
|Please check the value in your xml file you have supplied for . |
|1221 - Invalid marking method code |
| |
|Solution |
| |
|Please check the value in your xml file you have supplied for . |
|1222 - Licence must be in HI status before CP can be added. |
| |
|Solution |
| |
|MOF must change the status of the file to HI in FTA before any cutting permits can be issued within it. |
|1223 - Mark Designate missing. |
| |
|Solution |
| |
|This file is missing a mark designate hence the system could not generate a timber mark. Contact MOF Application Services help |
|desk and give them the submission id so they may look into it. |
|1224 - Error occurred processing Harvest w/CP application |
| |
|Solution |
| |
|Contact MOF Application Services help desk and give them the submission id so they may look into it. |
|1225 - Error occured generating timber mark. Contact MOF Application Services help desk. |
| |
|Solution |
| |
|Contact MOF Application Services help desk and give them the submission id so they may look into it. |
|1226 - Error occurred validating Harvest w/CP application |
| |
|Solution |
| |
|Contact MOF Application Services help desk and give them the submission id so they may look into it. |
|1404 - Tenure term cannot be > 60 months. |
| |
|Solution |
| |
|Tenure term cannot be > 60 months. |
|1405 - File must be an Oil and Gas Master Licence To Cut type (A11). |
| |
|Solution |
| |
|File must be an Oil and Gas Master Licence To Cut type (A11). |
|1406 - Invalid Oil and Gas Purpose. Must be PI, WS, SL, or OT. |
| |
|Solution |
| |
|Invalid Oil and Gas Purpose. Must be PI, WS, SL, or OT. |
|1407 - Error occurred validating Oil and Gas application |
| |
|Solution |
| |
|Error occurred validating Oil and Gas application. Please contact APPHELP. |
|1601 - Application Description for the Range Application is mandatory |
| |
|Solution |
| |
|Application Description for the Range Application is mandatory. |
|1602 - Forest File ID is required when the Application Purpose is ''A''mend |
| |
|Solution |
| |
|Forest File ID is required when the Application Purpose is 'A'mend. |
|1603 - File Type for the Range Application is mandatory |
| |
|Solution |
| |
|File Type for the Range Application is mandatory for new applications. |
|1604 - The Geographic District for the Range Application is mandatory |
| |
|Solution |
| |
|The Geographic District for the Range Application is mandatory. |
|1606 - The Application Purpose for the Range Application is mandatory |
| |
|Solution |
| |
|The Application Purpose for the Range Application is mandatory. |
|1608 - {value} - The Application Purpose is mandatory |
| |
|Solution |
| |
|The Application Purpose is mandatory. |
|1609 - {value} - The Tenure Block is mandatory |
| |
|Solution |
| |
|The Tenure Block is mandatory. |
|1610 - Invalid Range file type |
| |
|Solution |
| |
|For Range Tenure applications/amendments the file must be a range tenure type. Either the file type of the file id supplied is |
|not valid for range or the file type supplied is invalid. |
|1611 - Error occurred processing Range application |
| |
|Solution |
| |
|Error occurred processing Range application. Please contact APPHELP. |
|1612 - Unexpected error occured inserting RANGE_TENURE. |
| |
|Solution |
| |
|An error occured inserting RANGE_TENURE. Please contact APPHELP. |
|1613 - Error occurred validating Range application |
| |
|Solution |
| |
|An error occurred validating Range application. Please contact APPHELP. |
|1800 - Licensees are not permitted to submit applications for Forest Service Roads (B40) |
| |
|Solution |
| |
|Licensees are not permitted to submit applications for Forest Service Roads (B40). |
|1802 - The following sections of this application are currently being processed in another application and cannot be processed |
|until all existing applications are complete. {value} |
| |
|Solution |
| |
|The road sections of this application are currently being processed in another application and cannot be processed until all |
|existing applications are complete. |
|1803 - Application Description for the Road Permit Application is mandatory |
| |
|Solution |
| |
|Application Description for the Road Permit Application is mandatory. |
|1804 - The Forest File ID can only be null for a new Road Permit |
| |
|Solution |
| |
|The Forest File ID can only be blank for a new Road Permit. |
|1805 - The Forest File ID is mandatory for Road Tenure Amendment |
| |
|Solution |
| |
|The Forest File ID is mandatory for Road Tenure Amendment. |
|1806 - The File Type is mandatory for new Road Permit Applications |
| |
|Solution |
| |
|The File Type is mandatory for new Road Permit Applications. |
|1807 - The Geographic District for the Road Permit Application is mandatory |
| |
|Solution |
| |
|The Geographic District for the Road Permit Application is mandatory. |
|1810 - The Application Purpose for the Road Permit Application is mandatory |
| |
|Solution |
| |
|The Application Purpose for the Road Permit Application is mandatory. |
|1813 - {value} - The Application Purpose is mandatory |
| |
|Solution |
| |
|The Application Purpose is mandatory. |
|1814 - {value} - The Road Section ID is mandatory |
| |
|Solution |
| |
|The Road Section ID is mandatory. |
|1815 - {value} is an invalid Road amendment type. |
| |
|Solution |
| |
|The road_amendment_type_code you have entered is an invalid Road amendment type. |
|1816 - Road amendment type must be provided in submission. |
| |
|Solution |
| |
|Road amendment type must be provided in submission. |
|1817 - File ID is required for B40 and must be in NNNNN format |
| |
|Solution |
| |
|If you are trying to submit an application for a new Forest Service Road the xml file must have a value for |
|filled in. It must be in NNNNN format. |
|1818 - Road section/branch id cannot contain embedded blanks |
| |
|Solution |
| |
|Please check the value. It should not have any spaces between the characters. For example A 1 is not valid; |
|it should be A1. |
|1819 - Invalid Road Section |
| |
|Solution |
| |
|Road section does not exist in FTA. Please check the value. |
|1820 - Invalid B01 Road Permit/B40 Forest Service Road file |
| |
|Solution |
| |
|For Road applications/amendments the file type of given file must be a B01 Road Permit or a B40 Forest Service Road. |
|1821 - Cannot amend a section on a new Road |
| |
|Solution |
| |
|Please check the value for the road section. It should be 'N' for a new road application. |
|1822 - Unexpected error occured inserting LAND_CLEAR_FILE. |
| |
|Solution |
| |
|An error occured inserting LAND_CLEAR_FILE. Please contact APPHELP. |
|1823 - Client {value} is not the TSO manager for {value} |
| |
|Solution |
| |
|The client_number is not the TSO manager for {value}. |
|1824 - Error occurred processing Road application |
| |
|Solution |
| |
|An error occurred processing Road application. Please contact APPHELP. |
|1825 - Unexpected error occured inserting ROAD_PERMIT. |
| |
|Solution |
| |
|An error occured inserting ROAD_PERMIT. Please contact APPHELP. |
|1826 - Duplicate Road Permit amendment {value} occured inserting ROAD_PRMT_AMEND. |
| |
|Solution |
| |
|A duplicate Road Permit amendment occured inserting ROAD_PRMT_AMEND. Please contact APPHELP. |
|1827 - Unexpected error occured inserting ROAD_PRMT_AMEND. |
| |
|Solution |
| |
|An error occured inserting ROAD_PRMT_AMEND. Please contact APPHELP. |
|1828 - Duplicate road section/branch detected: {value} |
| |
|Solution |
| |
|Please check that you do not have duplicate road sections in your xml file. |
|1829 - Unexpected error occured inserting ROAD_SECTION. |
| |
|Solution |
| |
|An error occured inserting ROAD_SECTION. Please contact APPHELP. |
|1830 - Road section cannot start with SEC. |
| |
|Solution |
| |
|Please check the value. It should not start with 'SEC'. |
|1831 - Branch ID cannot start with BR. |
| |
|Solution |
| |
|Please check the value. It should not start with 'BR'. |
|1832 - Road Section already exists. |
| |
|Solution |
| |
|When adding a new section the section id must not already exist in FTA. Change the for the road section|
|to 'A' if you need to amend otherwise change the value. |
|2000 - Application Description for the Timber Licence Application is mandatory |
| |
|Solution |
| |
|Application Description for the Timber Licence Application is mandatory. |
|2001 - Forest File ID for the Timber Licence Application is mandatory |
| |
|Solution |
| |
|Forest File ID for the Timber Licence Application is mandatory. |
|2002 - The Geographic District for the Timber Licence Application is mandatory |
| |
|Solution |
| |
|The Geographic District for the Timber Licence Application is mandatory. |
|2003 - The Application Purpose for the Timber Licence Application is mandatory |
| |
|Solution |
| |
|The Application Purpose for the Timber Licence Application is mandatory. |
|2004 - {value} - The Map Block ID is mandatory |
| |
|Solution |
| |
|The Map Block ID is mandatory. |
|2005 - {value} - The Application Purpose is mandatory |
| |
|Solution |
| |
|The Application Purpose is mandatory. |
|2006 - Error occurred processing Timber Licence Block application |
| |
|Solution |
| |
|An error occurred processing Timber Licence Block application. Please contact APPHELP. |
|2007 - Error occurred processing Timber Licence Elimination application |
| |
|Solution |
| |
|An error occurred processing Timber Licence Elimination application. Please contact APPHELP. |
|2008 - Duplicate TL Block ID detected. |
| |
|Solution |
| |
|Please check your xml file for duplicate TL blocks. |
|2009 - TL Block already exists. |
| |
|Solution |
| |
|The Timber Licence Block you are trying to add already exists. Please check the value in your xml file. |
|2010 - Error occurred validating Timber Licence Block application |
| |
|Solution |
| |
|Error occurred validating Timber Licence Block application. Please contact APPHELP. |
|2200 - Application Description for the Timber Licence Elimination Application is mandatory |
| |
|Solution |
| |
|Application Description for the Timber Licence Elimination Application is mandatory. |
|2201 - Forest File ID for the Timber Licence Elimination Application is mandatory |
| |
|Solution |
| |
|Forest File ID for the Timber Licence Elimination Application is mandatory. |
|2202 - The Geographic District for the Timber Licence Elimination Application is mandatory |
| |
|Solution |
| |
|The Geographic District for the Timber Licence Elimination Application is mandatory. |
|2203 - The Timber Licence Block ID for the Timber Licence Elimination Application is mandatory |
| |
|Solution |
| |
|The Timber Licence Block ID for the Timber Licence Elimination Application is mandatory. |
|2204 - TL Block ID does not exist |
| |
|Solution |
| |
|Please check the value in your xml file. |
|2205 - Invalid A06 Timber Licence file |
| |
|Solution |
| |
|For Timber Licence Block/Elimination applications the file must be an A06 Timber Licence or A30 Consolidated Timber Licence. |
|2206 - Eliminated area has already been submitted for this block. |
| |
|Solution |
| |
|Eliminated area has already been submitted for this block. Please ask MOF to delete this TL block and resubmit. Make sure that |
|area is the total eliminated area for the TL block to date. NOTE: The process for submitting TL Eliminated areas is still under |
|review. |
|2207 - Error occurred validating Timber Licence Elimination application |
| |
|Solution |
| |
|An error occurred validating Timber Licence Elimination application. Please contact APPHELP. |
|2208 - Unable to fail one or more applications; ie set the status to FAI - {value} |
| |
|Solution |
| |
| Please Contact APPHELP |
|2209 - Spatial feature already exists. Please contact APPHELP |
| |
|Solution |
| |
| Please Contact APPHELP |
|2210 -|
|There |
|was an|
|error |
|saving|
|the |
|spatia|
|l |
|featur|
|e. |
|Please|
|contac|
|t |
|APPHEL|
|P. |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2211 -|
|Road |
|sectio|
|n |
|retire|
|ments |
|cannot|
|be |
|proces|
|sed |
|for |
|tenure|
|s in |
|PE or |
|PI |
|status|
|. |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2212 -|
|You |
|are |
|not a |
|known |
|FTA |
|user. |
|Please|
|talk |
|to |
|your |
|system|
|admini|
|strato|
|r and |
|resubm|
|it. |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2213 -|
|{0} - |
|Road |
|Sectio|
|n Id |
|cannot|
|contai|
|n the |
|follow|
|ing |
|charac|
|ters: |
|,",|
|&,',/ |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2214 -|
|{0} - |
|Geomet|
|ry is |
|requir|
|ed for|
|the |
|road |
|sectio|
|n. |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2215 -|
|{0} - |
|Duplic|
|ate |
|road |
|sectio|
|n ids |
|are |
|not |
|permit|
|ted in|
|an |
|applic|
|ation.|
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2216 -|
|{0} - |
|Invali|
|d |
|Licenc|
|e |
|Regula|
|tion |
|Code |
| |
|Soluti|
|on |
| |
| Pleas|
|e |
|Contac|
|t |
|APPHEL|
|P |
|2217 -|
|Licenc|
|e must|
|be in |
|HI |
|status|
|in |
|order |
|to add|
|new or|
|amend |
|existi|
|ng cut|
|blocks|
| |
|Soluti|
|on |
| |
|Licenc|
|e must|
|be in |
|HI |
|status|
|in |
|order |
|to add|
|new or|
|amend |
|existi|
|ng cut|
|blocks|
|2217 -|
|Cannot|
|amend |
|a |
|Cutblo|
|ck |
|within|
|a New |
|Harves|
|ting |
|Author|
|ity |
| |
|Soluti|
|on |
| |
|Cannot|
|amend |
|a |
|Cutblo|
|ck |
|within|
|a New |
|Harves|
|ting |
|Author|
|ity |
|2219 -|
|Only |
|DPC |
|can |
|submit|
|FSJ |
|applic|
|ations|
|. |
| |
|Soluti|
|on |
| |
|Only |
|DPC |
|can |
|submit|
|FSJ |
|applic|
|ations|
|. |
|2220 -|
|Refore|
|statio|
|n |
|Declar|
|ation |
|Type |
|Code |
|is |
|mandat|
|ory |
|for |
|applic|
|ations|
|that |
|fall |
|under |
|the |
|Fort |
|St |
|John |
|pilot |
|projec|
|t. |
| |
|Soluti|
|on |
| |
|Refore|
|statio|
|n |
|Declar|
|ation |
|Type |
|Code |
|is |
|mandat|
|ory |
|for |
|applic|
|ations|
|that |
|fall |
|under |
|the |
|Fort |
|St |
|John |
|pilot |
|projec|
|t |
|2221 -|
|Refore|
|statio|
|n |
|Declar|
|ation |
|Type |
|Code |
|is |
|invali|
|d: {0}|
| |
|Soluti|
|on |
| |
|Refore|
|statio|
|n |
|Declar|
|ation |
|Type |
|Code |
|is |
|invali|
|d: {0}|
|2222 -|
|Start |
|Statio|
|n and |
|End |
|Statio|
|n must|
|fall |
|within|
|the |
|suppli|
|ed |
|geomet|
|ry |
|length|
|of {0}|
|kms. |
| |
|Soluti|
|on |
| |
|Start |
|Statio|
|n and |
|End |
|Statio|
|n must|
|fall |
|within|
|the |
|suppli|
|ed |
|geomet|
|ry |
|length|
|of {0}|
|kms. |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- 2019 toyota highlander specifications edmunds
- ford v10 specifications motorhome
- florida department of financial services licensee search
- florida dfs licensee search
- vehicle manufacturer specifications using vin
- icd 705 technical specifications 2019
- fda pdf specifications guidance
- aluminum extrusion specifications standards
- briggs and stratton specifications chart
- pc specifications app
- asphalt paving specifications pdf
- specifications manager job description