Public Land Management (PLM25) Closures

dataset: PLM25_CLOSURES
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 DELWP 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) Closures

Department of Energy, Environment and Climate Action
 

Description

Title
Public Land Management (PLM25) Closures 
Alternate title
PLM25_CLOSURES 
Resource Type
Dataset  
Purpose
Provide closure information on PLM25. This data is edited in Mapshare. 
Credit
Martin Talento Naomi Withers 
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 DELWP web site, while others can be viewed at DELWP 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. 
Status
Completed  
 
 

Temporal

Time period
2022-09-012023-07-03 
 
 

Spatial

Spatial representation type
Vector  
Horizontal Accuracy
25m  
Code
4283 
Description
General - Victoria 
N
S
E
W


 

 

Maintenance

Maintenance and update frequency
Quarterly  
 
 

Format

Title
DIGITAL - Oracle SDE feature class 10 
 
 

Contacts

  Point of contact

Cited responsible party  

No information provided.

Cited responsible party  

No information provided.
 
 

Keywords

Topic category
  • Society
  • Environment
  • Boundaries
 
 

Resource Constraints

Classification
Limited Distribution  
 
 

Lineage

Statement
Dataset Source: PLM25 Dataset Originality: Primary & Derived 
Description
Collection Method: Refer to metadata for PLM25 
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. 
 
 

Metadata Constraints

Classification
Limited Distribution  
 
 

Quality

Attribute Quality
Comments
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
Comments
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 
Conceptual Consistency
Missing Data
Comments
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. 
Excess Data
 
 

    Overviews

  Provided by

  Share on social sites

         

  Views Views

Read here the full details and access to the data. Read here the full details and access to the data.

  Associated resources

Not available