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

This dataset contains line features representing a boundary which indicates the long-term limits of urban development in metropolitan Melbourne. It only affects 17 LGAs within the Melbourne metropolitan area. This dataset has fields joined from the Codelist. This layer is attributed with: - scheme code - zone number - zone status - zone code - LGA name - LGA code - zone code group - zone code group label

This dataset Victorian Planning Provisions Ordinance links contains URL links to Planning Scheme Ordinance representing zone and overlay controls for all Victorian planning schemes. This layer is attributed with: - zone description - zone number - zone code (parent) - LGA code - URL

This dataset contains polygon features representing overlay controls for all Victorian planning schemes. Overlays reflect specific characteristics of land in an area, such as areas of significant vegetation or heritage value. Some fields of note are Code_Parent and Zone_Code_Group along with standard fields form part of this dataset. This layer is attributed with: - scheme code - zone number - zone status - zone code - LGA name - LGA code

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

This dataset Victorian Planning Provisions Ordinance links contains URL links to Planning Scheme Ordinance representing zone and overlay controls for all Victorian planning schemes. This data contains an additional LGA (LGA_CODE) attribute to enable access to the new format html planning scheme ordinance web pages. This layer is attributed with: - scheme code - zone number - zone code - LGA name - LGA code -URL

Vicmap Planning is the map data representing the land use zone and overlay controls for all Victorian planning schemes. Planning schemes cover the 79 local government areas and three other areas in Victoria. Planning schemes are regularly amended, and Vicmap Planning is continually updated to reflect the official planning scheme at any time. Datasets in the series are listed below. See them for more detailed metadata. - Planning scheme zones - Vicmap Planning (VMPLAN_PLAN_ZONE); - Planning scheme overlay - Vicmap Planning (VMPLAN_PLAN_OVERLAY); - Planning scheme Urban Growth Boundary - Vicmap Planning (VMPLAN_PLAN_UGB); - Planning scheme Urban Growth Area - Vicmap Planning (VMPLAN_PLAN_UGA); - Planning scheme codelist - Vicmap Planning (VMPLAN_PLAN_CODELIST) Current data model is Version 3.0.1

Part of the Vicmap Admin dataset series. This dataset contains the polygons for the authoritative Locality boundary dataset for Victoria. Locality Boundaries are as defined by Local Governments and registered by the Registrar of Geographic Names (GeoNames). The Vicmap Admin Locality data only contains Bounded Localities (known as LOCB in the GeoNames data). There are also unbounded localities/neighbourhoods (LOCU or NBHD) in the GeoNames data but this is NOT contained within Vicmap Admin Locality. Aligned to Vicmap Property.

This dataset contains line features representing a boundary which indicates the long-term limits of urban development in metropolitan Melbourne. It only affects 17 LGAs within the Melbourne metropolitan area. This layer is attributed with: - scheme code - zone number - zone status - zone code - LGA name - LGA code

Product version containing the following 2 datasets:- For detailed metadata, see individual records. VMPLAN_PLAN_ORDINANCE_LPP_URL (ANZVI0803005951) VMPLAN_PLAN_ORDINANCE_VPP_URL (ANZVI0803005954) Note: The VPP table was updated 14/7/2022 to accommodate changes to the the new format Planning Scheme webpages.The field LGA_CODE was added and a unique url for each zone and overlay for every scheme now exists. Hence, the number of records n the table has significantly increased.