Contacts

Identifiers and Keywords

ANZLIC Id

ANZVI0803008496 

Victorian Spatial Data Library (VSDL) Schema

PLANNING:PLAN_EXHIBITED 

Jurisdiction

Victoria 

Topic category

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

Resource Constraints

Use limitation

. 

Classification

Unclassified  

Creative Commons Attribution 4.0 (CC-BY)

• 
• License Text

Other Dataset Details

Date ( Revision )

2019-09-09

Date ( Publication )

2025-12-04T12:42:28

Status

Completed  

Supplemental Information

Relationship to other Datasets: Vicmap Planning is related to other VGIS framework information, including Vicmap Property, Transport, Address, etc. Related Documents: None http://www.delwp.vic.gov.au/vicmap > Vicmap Planning 

Maintenance and update frequency

Weekly  

Maintenance date ( Publication )

2023-03-18T01:59:13

Spatial

Spatial representation type

Vector  

Description

General - Victoria 

Reference system identifier

4283

N

S

E

W

Temporal

Begin date

2019-08-05 

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

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. · Alignment checking routines that check for relative accuracy. (Relative to Vicmap Property) · 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. · Periodic alignment checks are made and compared to existing benchmarks. · Feedback regarding data quality is provided from the Planning Certificates area of Land Registry who use the data extensively. 

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 exhibited amendment polygons must be node-for-node aligned to neighbouring polygons. Therefore, the positional accuracy of this data is as accurate as Vicmap Property. 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. 

Lineage

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. Metropolitan planning scheme digital data capture began in the late 80's/early 90's and was captured by Ministry of Planning and Environment (MPE) staff matching zone boundary nodes to Vicmap Property nodes. This was done in Eagle GIS. Where zone boundaries deviated from Vicmap Property, MPE used the Department's hard copy zone boundary definition information contained in 1:2500 cadastral plans or existing definition plans which had been produced at various times and various scales since 1955. All these plans contained dimension information that was used to align zone boundaries in relation to Vicmap Property. The history of the rural/regional data is quite different and also not so centralised. Information is derived from 3 different sources. · Planning schemes maintained by the Town and Country Planning Board; · Planning schemes maintained by Local Government where they had the resources to perform this function; · Some schemes were a mix of both because the minister had the power in those days to create schemes within Local Government areas. (An example of this was the Lake Eppalock Planning Scheme that bordered 3 municipalities.) All of these rural/regional and metropolitan schemes were consolidated in the mid 80's into individual single municipal schemes with the exception of three schemes that are not Local Government boundary based - French Island, Alpine Resorts and Port of Melbourne Planning Schemes. The rural/regional planning scheme digital data was captured by external contractors matching zone boundary nodes to Vicmap Property nodes. Where zone boundaries deviated from Vicmap Property then the relevant local Government authority was consulted for zone boundary definition information. Data was realigned to a more current version of Vicmap Property as part of DOI's change from Eagle GIS to MapInfo in 1999/2000. Updates of the DOI corporate copy of Vicmap Property involves realignment of planning scheme data where new or altered cadastral boundaries coincide with zoning boundaries. Governmental changes saw the Planning Area within DOI transferred to the Built Environment division within the Department of Sustainability and Environment. Online Initiatives, within the Built Environment, maintain the planning scheme data in Mapinfo format (as individual files for each zone/overlay in each local government area). More recently (since July 2017) planning scheme data is maintained by DELWP Planning in a state wide dataset that is aligned to current property boundaries using topology processes incorporated in ESRI software. This alignment is checked and maintained on current property data on a weekly basis. 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
PFI_CREATED	O	N	DATE	7						PFI_CR
UFI	O	N	NUMBER	22	38	8				UFI
PFI	O	N	NUMBER	22	38	8				PFI
SUBMISSION_END_DATE	O	N	DATE	7						SUBENDDATE
ZONE_DESCRIPTION	O	N	VARCHAR2	100						ZONE_DESC
EXH_END_DATE	O	N	DATE	7						EXHENDDT
AMEND_NUM	O	N	VARCHAR2	16						AMEND_NUM
SCHEME_CODE	O	N	VARCHAR2	8						SCHEMECODE
LGA_CODE	O	N	VARCHAR2	3						LGA_CODE
EXH_BEGIN_DATE	O	N	DATE	7						EXHBEGINDT
UFI_CREATED	O	N	DATE	7						UFI_CR
ZONE_CODE	O	N	VARCHAR2	12						ZONE_CODE
URL	O	N	VARCHAR2	255						URL
ZONE_STATUS	O	N	VARCHAR2	1						ZONESTATUS
LGA	O	N	VARCHAR2	45						LGA
ZONE_NUM	O	N	NUMBER	22	10	0				ZONE_NUM
SE_ANNO_CAD_DATA	O	N	BLOB	4000						SEANNOCAD

About the Metadata Record

Metadata identifier

urn:uuid / 482b0415-f592-5ebf-bf4e-74108a54d0b4