Metadata Name Description
Resource Name: VMPLAN_PLAN_ZONE
Title: Planning scheme zones - Vicmap Planning
Anzlic Id: ANZVI0803002909
Custodial Program: Planning
Custodian: Department of Environment, Land, Water & Planning
Abstract: This dataset contains polygon features representing land use zones (such as residential, industrial or rural) for all Victorian planning schemes.

This layer is attributed with:
- scheme code
- zone number
- zone status
- zone code
- LGA name
- LGA code
Search Words: LAND Use, HUMAN ENVIRONMENT Planning, HUMAN ENVIRONMENT Urban Design, LAND, TRANSPORTATION, INDUSTRY, BOUNDARIES
Nominal Input Scale: 1:2,500 (metropolitan Melbourne), 1:10,000 and 1:25,000 scales.
Currency Date: 17 October 2019
Dataset Status: Completed
Progress: In Progress
Access Constraint: Creative Commons Attribution 4.0 International licence, Copyright and Attribution, Terms of Use - http://creativecommons.org/licenses/by/4.0/
Access through www.delwp.vic.gov.au/vicmapdata or Vicmap Data Service Providers www.delwp.vic.gov.au/vicmapdsp or DataVic www.data.vic.gov.au
Data Existence:
Metadata Name Description
Resource Name: VMPLAN_PLAN_ZONE
Title: Planning scheme zones - Vicmap Planning
Anzlic Id: ANZVI0803002909
Custodian: Department of Environment, Land, Water & Planning
Owner: Department of Environment, Land, Water & Planning
Jurisdiction: Victoria
Abstract: This dataset contains polygon features representing land use zones (such as residential, industrial or rural) for all Victorian planning schemes.

This layer is attributed with:
- scheme code
- zone number
- zone status
- zone code
- LGA name
- LGA code
Search Words: LAND Use, HUMAN ENVIRONMENT Planning, HUMAN ENVIRONMENT Urban Design, LAND, TRANSPORTATION, INDUSTRY, BOUNDARIES
Purpose: Ideally, it is recommended that Vicmap Planning is to be used in conjunction with Vicmap Property, as zone boundaries generally align to property boundaries. 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
Geographic Extent Polygon:
Geographic Bounding Box:
-34
141
 
150
-39
Beginning Date: 01JAN1955
Ending Date: Current
Maintainence and Update Frequency: Weekly
Stored Data Format: Oracle data base tables
Available Format(s) Types: All major digital formats available:
Lineage: Primary
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.
Atribute Accuracy: 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.
Logical 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.
Data 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. Recent governmental changes have seen 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).
Completeness:
Contact Organisation: Department of Environment, Land, Water & Planning
Contact Position: Dataset Data Manager
Address: PO Box 500
East Melbourne  Vic 3002
Australia
Telephone: N/A
Facsimile: N/A
Email Address: Planning.MappingServices@delwp.vic.gov.au
Metadata Date: 2019-09-09 00:00:00.0
Additional Metadata: http://www.delwp.vic.gov.au/vicmap > Vicmap Planning
Resource Name: VMPLAN_PLAN_ZONE
Title: Planning scheme zones - Vicmap Planning
Object Name: VMPLAN.PLAN_ZONE
Column Name Column Name 10 Obligation Unique Data Type Reference Table Comments
GAZ_BEGIN_DATE GAZ_B_DATE O N DATE Gazetted Date
LGA LGA O N VARCHAR2(45) Name of Local Government Area that zone/overlay polygon falls within (not the Gazetted name).
LGA_CODE LGA_CODE O N VARCHAR2(3) Number identifying Local Government Area that zone/overlay polygon falls within.
PFI PFI M Y NUMBER(11) Permament Feature Identifier
PFI_CREATED PFI_CR M N DATE The date the Persistent Feature Identifier was created.
SCHEME_CODE SCHEMECODE O N VARCHAR2(8) Code denoting whether the feature is a zone or overlay (and what type of overlay).
UFI UFI O N NUMBER(11) Database wide Unique Feature identifier. Assigned at every feature creation or edit, superseded by each edit to the feature.
UFI_CREATED UFI_CR O N DATE The date the UFI was created
ZONE_CODE ZONE_CODE M N VARCHAR2(12) VMPLAN.PLAN_CODELIST A unique code that links map data to the written part of the Planning Scheme.
ZONE_DESCRIPTION ZONE_DESC O N VARCHAR2(100)
ZONE_NUM ZONE_NUM M N NUMBER(6) VMPLAN.PLAN_CODELIST A unique number used by DSE for automatic issuing of planning certificates. Also used to link to the codelist.
ZONE_STATUS ZONESTATUS O N VARCHAR2(1) A single character that represents the current status of the data. Options: g=approved data, p=exhibited data