Public Land Management (PLM25)
  • MetaShare PROD
  •  
  •  
  •  

  Public Land Management (PLM25)

dataset: PLM25
This dataset describes public land management for the State of Victoria, where Public Land is defined as land held by/vested in/or owned by DEECA and other government departments, public authorities, Commonwealth government and municipalities. Refer to VEAC Act 2001 for more details. Public land includes state forests, parks and reserved and unreserved Crown land, including estuarine, coastal and marine areas to the 3 nautical mile limit (5.5 km) from the high watermark. This layer is represented at a scale of 1:25 000 and describes the primary management, land manager and the VEAC recommendations. PLM25 is a derived layer, using VMPROP.PARCEL_CROWN_APPROVED as the base layer. It relies on tabular and spatial sources to get the land description. PORTAL, PRIMS are the tabular sources of information. PARKRES, VEACRECS25 and CL_TENURE are the spatial sources. Additional layers were also created to describe areas of state forests, plantations, water frontages and commonwealth land. PLM25 has replaced the old PLM100 datasets. Any errors can be reported to Plm25.info@delwp.vic.gov.au
 
Citation proposal Citation proposal
(2022)

Public Land Management (PLM25)

Department of Energy, Environment and Climate Action

https://metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/7cb9cfb1-86ff-5432-bf9b-e3070d04f507
 

Details

Contacts

Cited responsible party  

No information provided.

Cited responsible party  

No information provided.

Cited responsible party  

No information provided.

  Point of contact

Department of Energy, Environment and Climate Action - PLM25 Info   ()  
 

Identifiers and Keywords

ANZLIC Id
ANZVI0803003978 
Victorian Spatial Data Library (VSDL) Schema
CROWNLAND:PLM25 
Jurisdiction
Victoria 
Topic category
  • Environment
  • Society
  • Boundaries
  • Inland waters
 

Resource Constraints

Classification
Unclassified  
Creative Commons Attribution 4.0 (CC-BY)
  • License Text
 

Other Dataset Details

Date ( Revision )
2022-04-04
Date ( Publication )
2025-12-03T16:02:54
Status
Completed  
Purpose
The PLM25 dataset holds land management information on parcels of land for: Park and Conservation Reserves VEAC recommendations Plantation State Forest Water Frontage and other public land. The PLM25 dataset represents public land management across the state. It allows users to identify the different land use categories, the local name, the legal status, the LCC recommendations associated with that entity, the land manager and whether any committees of management are present. This dataset supercedes PLM100 and its associated layers. 
Supplemental Information
History: Refer to metadata for PLM100_POLYGON, PARKRES, PARCEL_VIEW, VEACRECS25 and V_CL_TENURE. Relationship to other Datasets: VMPROP.PARCEL_CROWN_APPROVED, PLM100_POLYGON, PARCEL_VIEW, PARKRES, VEACRECS25, V_CL_TENURE, PRIMS and LIMS (text based business application) Current Design Issues: Polygons showing boundaries of areas scheduled under the National Parks Act 1975 are a guide only. The actual boundaries are defined by the linework and annotations on the certified (legal) plan, and by additional notes in the Act. Some of these plans are available from DEECA web site, while others can be viewed at DEECA offices. These annotations may be included in future versions of the dataset. Use of this layer is currently limited to display, query and some spatial analysis work since the data does not have a persistent unique identifier. This is due to the complexity associated with sourcing the spatial data from a variety of sources. This should be taken into consideration by those intending to integrate PARKRES with applications and or building processes around it. Data relating to certain land use categories from PRIMS database have attributes linked to the PRIMS id and may not have data attached to specific parcels. Potential errors: There is a known limitation when loading shapefiles from a postGIS/non ESRI software into a geodatabase as a feature class. Geometry errors are created when checking the imported shapefiles topology. It is recommended not to import the shapefile into a feature class. Instead analysis or geoprocessing should occur outside the geodatabase environment. ESRI and other GIS software have different specifications when writing an output to a shapefile. Thus, topological checks and geoprocessing undertaken in a geodatabase can create geometric errors, as it tries to fix identified topological errors. A description of the issue from ESRI helpdesk: The Shapefile format is an open format to which many software packages write to natively. Unfortunately some of these software packages (sometimes due to bugs) do not follow the documented specification for the Shapefile format. Also of note is that when Shapefiles are loaded into personal or file geodatabase, the features are copied as they are (with the geometry problem) to these other formats, so the same caution and care which needs to be used when using Shapefile data needs to be taken when using personal and file geodatabase feature classes. The exception to this when the data is loaded to an SDE Geodatabase. Before it is stored in the feature class, each record's geometry is checked for geometry problems, and repaired if necessary. Future Design Issues: The process will need to be updated once the CLIP project has been completed. Related Documents: None Refer to CROWNLAND.PLM100_POLYGON, CROWNLAND.PARKRES, PUBLICLAND.VEACRECS25, VMPROP.V_CL_TENURE and PARCEL_VIEW. Legal data from CLR textual database. 
Maintenance and update frequency
Quarterly  
Maintenance date ( Publication )
2023-03-04T01:13:41
 

Spatial

Spatial representation type
Vector  
Reference system identifier
4283



 

Temporal

Begin date
2008-11-30 
End date
2019-07-03 
 

Resolution

Horizontal Accuracy
25m  
 

Quality

Missing Data
The statewide dataset is complete. It includes PARKRES, VEACRECS25, CL_TENURE, PARCEL_CRWON APPROVED data. The data from PRIMS and PORTAL and the other datasets are overlaid on this data providing more accurate and additional information where available. Completeness Verification: Area comparisons between PLM25 and previous versions have been conducted. A comprehensive visual comparison has also been undertaken. 
Attribute Quality
Parks and Reserves are getting populated with their Land Manager from the PRIMS database. For remaining parcels the Land Manager is being populated from the Portal database and CL tenure dataset. These datasets have known issues, so use the land manager information with care and check were possible. The LCC Approval date is initially being populated with the main approval date for the LCC investigation, individual recommendations were often approved at a later date, these dates will be added as the information is compiled and will not be available in the initial release of the data. State game reserve data is incomplete. There are issues with names across the dataset. State forest names vary in their reliability, some are from official naming processes, while others are draft names using locality information to try to give all forest blocks a name rather than the generic "unnamed state forest" tag. Over time regional staff will systematically check these names and provide official names. 
Positional Accuracy
Polygons are derived from multiple sources: - Vicmap parcels (1:2 500 - 1:25 000) - Digital certified plan boundaries for areas recently scheduled under the National Parks Act 1975 at (1:25 000) - Boundaries digitised by the Parks and Protected Areas Branch (based on 1:25 000 topography) - CL_Tenure polygons - Data provided by Parks Victoria for Port Phillip 
 

Lineage

Description
The PLM process is made up of 30 modules based on python scripts and SQL queries in postGIS to create outputs which are then exported to a shapefile, then imported into the VSDL. 
Statement
Dataset Source: Text attributes are sourced from PRIMS, LIMS and CLR data. Polygons are derived from Vicmap parcels, National Parks Act 1975 certified plans, additional mapping based on 1:25 000 topography, PARKRES, PLM100_POLYGON, V_CL_TENURE and VEACRECS25. New datasets are based on VicMap parcels to create datasets showing plantations, state forest and water frontages. These datasets are based on certified plans, and from gazettals. Refer to metadata for PLM100_POLYGON and PARCEL_VIEW. Dataset Originality: Primary & Derived 
 

Attributes

Column Name Obligation Unique Data Type Data Length Data Precision Data Scale Reference Table Owner Reference Table Name Reference Table Code Column Name Short Column Name Definition
REC_CODE O N VARCHAR2 6 REC_CODE LCC/ECC/VEAC final recommendation code
LABEL O N VARCHAR2 120 LABEL Label field for 1:100 000 scale with the full length name in sentence case (e.g. Mt Buffalo National Park)
IMPL_STAT O N VARCHAR2 15 IMPL_STAT Implementation status of the LCC/ECC/VEAC recommendations
RES_DATE O N DATE 7 RES_DATE Date of Reservation from Crown Land Registry
GENER_DESC O N VARCHAR2 100 GENER_DESC General Description (e.g. marine, crown, water body, island, commonwealth)
ADDTL_ACTS O N VARCHAR2 100 ADDTL_ACTS Any additional legislation impacting on a parcel
REC_CAT O N VARCHAR2 100 REC_CAT LCC/ECC/VEAC land use major category recommendation
STUDY_AREA O N VARCHAR2 70 STUDY_AREA LCC/ECC/VEAC Study area
IUCN_CAT O N VARCHAR2 100 IUCN_CAT World Conservation Union protected area categories
PKAREA_TY O N NUMBER 22 30 11 PKAREA_TY Park and Reserves Information system area type
SCHED O N VARCHAR2 50 SCHED Section or Schedule under the Act
VERS_DATE O N DATE 7 VERS_DATE Date published
MNG_SPEC O N VARCHAR2 100 MNG_SPEC Specific Land Manager e.g. DHS, DOJ
PRIMS_ID O N NUMBER 22 30 11 PRIMS_ID Parks and reserve information management system ID
DATE_LCCAP O N DATE 7 DATE_LCCAP Date of LCC/ECC/VEAC approval by Governor-in-council
MMTGEN O N VARCHAR2 60 MMTGEN Management Generalized field used for statewide scale map display. Some public land categories are grouped into major land descriptions (i.e. services and utilities into other public land)
NAME O N VARCHAR2 100 NAME Local name or description (for all polygons where a name is available, in uppercase)
AREA_CODE O N NUMBER 22 30 11 AREA_CODE LCC/ECC/VEAC Study area code
STGAME_RES O N VARCHAR2 10 STGAME_RES State Game Reserve (Y/N)
AREA_HA O N NUMBER 22 30 11 AREA_HA Area of polygon (Hectares)
PERIMETER O N NUMBER 22 30 11 PERIMETER Perimeter of polygon (m)
POLY_SOURC O N VARCHAR2 100 POLY_SOURC Polygon source e.g. VICMAP parcel
MMGT_ONGEN O N VARCHAR2 100 MMGT_ONGEN Generalised Management Categories
DATE_EST O N DATE 7 DATE_EST Date of establishment of the original reserve
MNG_GROUP O N VARCHAR2 50 MNG_GROUP Grouped land manager e.g. Other Government Department
MMGT_ONGRD O N VARCHAR2 100 MMGT_ONGRD Current management on ground - may not reflect LCC
ACT O N VARCHAR2 200 ACT Legal status description
NAME_SOURC O N VARCHAR2 50 NAME_SOURC Name source either LCC/ECC/VEAC recommendation or local description
PLM_ID O N NUMBER 22 30 11 PLM_ID Unique Feature identifier
REC_SBCAT O N VARCHAR2 100 REC_SBCAT LCC/ECC/VEAC land use sub-category recommendation
LABELSHORT O N VARCHAR2 100 LABELSHORT Label field for 1:100 000 scale with the land tenure abbreviated in the name (e.g. Mt Buffalo NP)
PLU_CODE O N VARCHAR2 3 PLU_CODE A combination of future use and current use codes from VEACRECS25 data
GENER_TYPE O N NUMBER 22 30 11 GENER_TYPE General description code
LGA_CODE O N VARCHAR2 3 LGA_CODE Local government area code
LGA_NAME O N VARCHAR2 50 LGA_NAME Local government area name
LU_CODE O N NUMBER 22 9 0 LU_CODE Label Use code is used for scaling the labels in map production
 

About the Metadata Record

Metadata identifier
urn:uuid / 7cb9cfb1-86ff-5432-bf9b-e3070d04f507

  Processor

DEECA - Spatial, VDP  

Contact  

No information provided.
Resource Type
Dataset  
Date info ( Creation )
Date info ( Revision )
2025-06-19T14:39:04
Standard Name
ISO 19115-3:2018 
Profile Name
DELWP Profile 
Profile Version
Version 1 
Profile Date
2019-05-24  
 

Metadata Constraints

Classification
Unclassified  
 
 

    Overviews

Graphic Overview of Data Footprint

  Provided by

  Share on social sites

         

  Views Views

  • Simple
  • Simple
  • Full
  • XML
7cb9cfb1-86ff-5432-bf9b-e3070d04f507   Access to the portal Access to the portal Read here the full details and access to the data. Read here the full details and access to the data.

  Associated resources

Not available


  •  
  •  
  •