Harvested Logging Coupes (One layer per logging season)

dataset: LOG_SEASON
Polygon coverage displaying Victorian commercial timber harvesting event data in State forest, by financial year. Other information recorded is silvicultural operation type, forest type, start/end dates of the logging event. The dataset has been updated with the 2021-22 information. Complete to the end of June 2022
 
Citation proposal Citation proposal

(2023)

Harvested Logging Coupes (One layer per logging season)

Department of Jobs, Precincts and Regions

Description

Title
Harvested Logging Coupes (One layer per logging season) 
Alternate title
LOG_SEASON 
Purpose
This dataset provides a statewide coverage of a single season (financial year) of logging events in Victorian State forest. 
Supplemental Information
Relationship to other Datasets: The suite of layers that comprise the LOG_xxxxxx set are complied through a standard automated process into a layer called LASTLOG25. Current Design Issues: The current layer design has been kept as simple as possible as this layer is used at the forest district level and therefore must be commensurate with currently available resources for update, maintenance and accessibility. The design also has to accommodate the needs of the Statewide Forest Resource Inventory (SFRI) in quantifying the start and end dates of logging events. Logging history data is an important input to periodic updates in the SFRI, where logging event data is correlated with aerial photography. The unique polygon identifier used in this layer is LOGHISTID. This field is a composite string that comprises Forest Management Area number, forest block number, forest compartment number, coupe number, logging season identifier and coupe section number separated by slashes to make interpretation easier. The items which make up the LOGHISTID identifier are also held separately as string type items to facilitate attribute editing via ArcView. The logging event data must be able to be linked to a variety of textual databases and spreadsheets. Some examples being LOGSALES and locally maintained spreadsheets for coupe management. The link to this external information is the field COUPEADD. This is used as the concept of a "coupe" incorporates both single and multiple polygons. Future Design Issues: The current polygon attribute table contains a forest type field FOREST_TYPE. This field may become redundant of the longer term as the SFRI datasets are completed for the State. Related Documents: Mapping Harvested Coupes: A User Guide. - This document describes procedures for mapping harvested coupes, for the purpose of updating harvesting history records. 
Status
Completed 
 
 

Spatial

Horizontal Accuracy
25m 
Code
4283 
 
 

Maintenance

Maintenance and update frequency
Annually 
 
 

Contacts

  Point of contact

Cited responsible party

No information provided.

Cited responsible party

No information provided.

Cited responsible party

No information provided.

Cited responsible party

No information provided.
 
 

Keywords

Topic category
  • Biota
 
 

Constraints

Use limitation
. Access Subject to Custodial Approval 
Classification
Unclassified 
Creative Commons Attribution 4.0 (CC-BY)
 
 

Lineage

Statement
Dataset Source: This dataset is derived from 1:25,000 and 1:100,000.mapped information on logging events, aerial photography transferred to 1:25,0000 mapping and other regionally available logging records. A full list of mapping methodology sources is associated with the layer in the data field MAPLOG_SRC. Dataset Originality: Primary 
Description
Collection Method: Various 
Description
The series layers that comprise the LOG_xxxxxx suite are initially created on an FMA basis using local resources. These coverages are translated and validated using an ARC/INFO aml (LH_TRANS.AML) into the standard library data structure. A standard process (LH_PROCESS.AML) is performed as appropriate to recreate the derived layer called LASTLOG25. 
 
 

Metadata Constraints Metadata Constraints

Classification
Unclassified 
 
 

Quality

Attribute Quality
Comments
Required to be 100% for reporting purposes. Datasets will be subjected to standard CGDL audit processes. 
 
Positional Accuracy
Comments
Precision: 10m to 100m depending on survey method used for each coupe as documented in dataset. Determination: Comparisons to existing 1:25,000 topographic mapping and internal database consistencies. GPS sourced data may be inconsistent with existing 1:25000 map base roads and hydrology. 
 
Conceptual Consistency
Comments
1.LOGHISTID must be consistent with FMA, BLOCK, COMPARTMENT COUPE SEASON and SECTION. 2.COUPEADD must be consistent with FMA, BLOCK, COMPARTMENT COUPE. 3. ENDDATE cannot be earlier than STARTDATE 4. STARTDATE and ENDDATE must be consistent with logging season identifier. 5. SILVSYS cannot be inconsistent with FORESTYPE 6. FMA, BLOCK and COMPARTMENT must be consistent with data stored in the FORMB100 and FORMB25 layers. 7. FMA, BLOCK, COMPARTMENT must be consistent with data stored in FORMB100 layer. 
 
Missing Data
Comments
Data is processed and stored on an FMA basis. Extent of annual records varies from one FMA to another. All FMA's should have complete records from season 199798 onwards. 
 
Excess Data
 
 

Overviews

Graphic Overview of Data Footprint


Provided by

Share on social sites