Contacts

Identifiers and Keywords

ANZLIC Id

ANZVI0803008677 

Victorian Spatial Data Library (VSDL) Schema

PLANNING:MICLUP_INDUSTRIAL_AUG2020 

Jurisdiction

Victoria 

Topic category

• Society
• Economy

Resource Constraints

Use limitation

. 

Classification

Unclassified  

Creative Commons Attribution 4.0 (CC-BY)

• 
• License Text

Other Dataset Details

Date ( Revision )

2020-08-05

Date ( Publication )

2020-08-05T01:14:31

Status

Completed  

Purpose

This layer is created for the Melbourne Industrial and Commercial Land Use Plan (MICLUP) and represents the spatial extent of industrial land in metropolitan Melbourne as identified by the MICLUP. 

Supplemental Information

Current Design Issues: As part of Spatial Information Infrastructure's spatial data framework strategy, work will continue to bring Vicmap Planning more closely into alignment with current versions of Vicmap Property, particularly in terms of vertical topology. Currently this is only being carried out for the metropolitan area of Victoria. Future Design Issues: It is anticipated that a new attribute be added to the data, being a unique feature identifier, or similar. This will enable features to be identified individually. A definite timeframe has not been put on this development. Related Documents: None 

Maintenance and update frequency

Not planned  

Maintenance date ( Publication )

2020-08-05T01:14:31

Spatial

Spatial representation type

Vector  

Description

Victoria 

Reference system identifier

4283

N

S

E

W

Temporal

Begin date

2020-08-03 

End date

now  

Resolution

Horizontal Accuracy

25m  

Quality

Conceptual Consistency

Planning scheme map data is required to conform to a defined level of consistency with respect to table structure and attributes. Planning scheme map data is currently stored on the basis of local government areas, (with the exception of Alpine Resorts, French Island and Port of Melbourne Planning Schemes), and the total Victoria-wide data set must be contained in a consistent map projection. Before data is transferred to DSE production environment the data is quality assured according to a predefined set of rules for logical and attribute consistency. This involves checking for: · the correct table structure; · occurrence of non-polygon objects; · records without graphical objects; · duplicate polygons; · polygons within the zoning tables do not overlap; · all polygon boundaries close; · the file name is consistent with naming conventions; · the correct coordinate system; · a valid combination of zone code and zone number; · no control/overlay data is in the zoning table; · no zoning data is in the control/overlay table. Customer feedback and error reports are also encouraged to improve the quality of the data. 

Missing Data

Data covers the greater Melbourne metropolitan area. 

Attribute Quality

The allowable error in attribute accuracy is consistent across the entire data set and would be as little as 1 to 2%. This is checked each time the data is posted back to production and involves checking for: · a valid Zone Number; · a valid Zone Code; · a valid Zone Status; · a valid date; · correct colour. If any attribute fails to match, it is sent back for correction. 

Positional Accuracy

Vicmap Planning is directly aligned to a control version of Vicmap Property 75%-80% of the time, and the remainder (20%-25%) is aligned to natural features such as waterways, vegetation patterns or land contours. Zone and overlay boundaries are generally aligned node-for-node to the Vicmap Property cadastral data. Additionally, the zoning polygons (and where appropriate the overlay polygons) must be node-for-node aligned to neighbouring zoning polygons. Therefore, the positional accuracy of this data is as accurate as Vicmap Property. (Note that the version of Vicmap Property to which it is aligned is not necessarily the latest version, which can lead to inconsistencies when viewing the two datasets together.) As stated in the product description for Vicmap Property, this dataset "is classified as 'BB' accuracy, ie. 90% of well-defined features are within 1mm, at plot scale, of their true position, eg. 1:500 equates to +/- 0.5metre and 1:25,000 equates to +/- 25 metres. Anecdotal evidence suggests that the spatial accuracy of the major part of the data set, at all scales is frequently better than BB. The following topology rules are adhered to in Vicmap Planning: · no gaps exist between polygons (ie. no slivers); · a polygon does not overlap another polygon (no overlaps); · whole polygons are not duplicated (no duplicates). Vicmap Planning is a seamless data set covering the whole state, however some slivers exist between the different planning schemes, due to the original digitising being done against different boundaries. There are also a small number of polygons missing from the final data set. When the data has been processed to convert it from the planning scheme map data to Vicmap Planning, some of the polygons have not formed properly due to topological problems. The "unformed_polygon" layer displays these polygons as lines so users are aware of where the problems exist. 

Lineage

Statement

Dataset Source: Derived from Property Parcels, Urban Development Program, Planning Scheme Zones Dataset Originality: Primary 

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
PRECINCT	O	N	VARCHAR2	100						PRECINCT
LGA_NAME	O	N	VARCHAR2	50						LGA_NAME
MICLUP_CAT	O	N	VARCHAR2	100						MICLUP_CAT
SE_ANNO_CAD_DATA	O	N	BLOB	4000						SEANNOCAD
STATUS	O	N	VARCHAR2	30						STATUS
REGION	O	N	VARCHAR2	50						REGION
PRECINCTNO	O	N	NUMBER	22		0				PRECINCTNO

About the Metadata Record

Metadata identifier

urn:uuid / 76663b0e-369f-5369-aed7-c6dc52482850