Contacts

Identifiers and Keywords

ANZLIC Id

ANZVI0803009457 

Victorian Spatial Data Library (VSDL) Schema

PLANNING:PLAN_ORDINANCE_VPP_LGA_URL 

Jurisdiction

Victoria 

Topic category

• Environment
• Society
• Boundaries
• Economy
• Structure
• Transportation

Resource Constraints

Use limitation

Access through www.delwp.vic.gov.au/vicmapdata or www.data.vic.gov.au 

Classification

Unclassified  

Creative Commons Attribution 4.0 (CC-BY)

• 
• License Text

Other Dataset Details

Date ( Revision )

2022-09-08

Date ( Publication )

2024-11-20T15:22:33

Status

Completed  

Purpose

Victorian Planning Provisions ordinance links Areas of application may include: · Town Planning/Strategic Planning · Real Estate management · Property Developers · Infrastructure/facilities location and management · Reference framework · Research systems · Valuations analysis - Web based planning scheme discovery tools 

Supplemental Information

Relationship to other Datasets: Vicmap Planning is related to other VGIS framework information, including Vicmap Property, Transport, Address, etc. 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 https://www.land.vic.gov.au/maps-and-spatial/spatial-data/vicmap-catalogue 

Maintenance and update frequency

Weekly  

Maintenance date ( Publication )

2023-03-18T01:59:27

Spatial

Spatial representation type

Text, table  

Description

General - Victoria 

Reference system identifier

4283

N

S

E

W

Temporal

Begin date

2022-05-06 

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

Vicmap Planning covers the whole state completely with the exception of the Port of Melbourne Planning Scheme area. Completeness Verification: The following procedures are undertaken as normal update/maintenance routines, to ensure conformity of the data to Specification. These procedures are applied to the original data: · Virus check software for digitally supplied input data; · Return of data to source authorities (Local Government) to confirm content. · Input check-list to prompt operator; · Automated data capture software that restricts attribute entry to allowable data. · Automated quality routines, reflecting business rules for data population, to ensure data consistency. The following post-production validation exercises have been undertaken to ensure that no detail has been lost as a result of the capture process. These are carried out on the original data. · Logical consistency and attribute checks are conducted on the data each time it is updated before it is posted back to production. - Each Url is checked for availability and each zone code has a related URL Records are never retired There will be records that no longer relate to a represented polygon feature however all polygon features in the spatial data of Zones and overlays has a URL 

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

Description

The planning scheme map data (maintained as Mapinfo files by the Online Initiatives Group, DSE) is provided to Spatial Information Infrastructure on a weekly basis, and the data is then converted into ArcSDE format, and translated from AGD66 to GDA94. 

Statement

Dataset Source: The Metropolitan scheme maintenance began in 1955 with the production of the 1954 Interim Development Order. It was maintained continuously within the Melbourne Metropolitan Board of Works, (MMBW), Planning Branch until 1985 when the MMBW Planning Branch became part of a new Planning and Environment Department and the maintenance has continued within State Government to the present. During this time the name/s of the data changed from the Melbourne Metropolitan Planning Scheme to the individual Municipal names (pre Local Government amalgamation), to the new (now current), Municipal names. Recent governmental changes to adopt online systems as a primary means of Planning Scheme interogation has meant that maintaining a lookup table that assists in the retrieval of relevant ordinance documentation stored at http://planning-schemes.delwp.vic.gov.au/ 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
ZONE_DESCRIPTION	O	N	VARCHAR2	100						ZONE_DESC
ZONE_NUM	O	N	NUMBER	22	10	0				ZONE_NUM
UFI_CREATED	O	N	DATE	7						UFI_CR
URL	O	N	VARCHAR2	255						URL
PFI_CREATED	O	N	DATE	7						PFI_CR
LGA_CODE	O	N	VARCHAR2	3						LGA_CODE
DOC_EXISTS	O	N	VARCHAR2	1						DOC_EXISTS
UFI	O	N	NUMBER	22	10	0				UFI
PFI	O	N	NUMBER	22	10	0				PFI
ZONE_CODE	O	N	VARCHAR2	12						ZONE_CODE

About the Metadata Record

Metadata identifier

urn:uuid / 86aefed7-30e4-5dfe-aed2-eb42b586e6d8