Vicmap Admin - Locality Polygon Aligned to Property
dataset:
LOCALITY_POLYGON
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.
|
Citation proposal Citation proposal
(2021) Vicmap Admin - Locality Polygon Aligned to Property Department of Transport and Planning https://metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/47352a58-1fd6-5b50-a2ec-9df8afdf8ac9 |
Details
Contacts
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Cited responsible party
No information provided.
Point of contact
Identifiers and Keywords
- ANZLIC Id
- ANZVI0803003027
- Victorian Spatial Data Library (VSDL) Schema
- VMADMIN:LOCALITY_POLYGON
- Jurisdiction
- Victoria
- Topic category
-
- Environment
- Planning cadastre
- Boundaries
Resource Constraints
- Use limitation
- LGA size area is available via Land Channel web site www.delpw.vic.gov.au/vicmapdata or large volumes via DELWP Data Service Providers www.delwp.vic.gov.au/vicmapdsp or DataVic www.data.vic.gov.au
- Classification
- Unclassified
- Creative Commons Attribution 4.0 (CC-BY)
Other Dataset Details
- Date ( Revision )
- 2021-03-17
- Date ( Publication )
- 2024-11-22T20:15:16
- Status
- Completed
- Purpose
- Vicmap Admin provides an accurate representation of various adminstrative boundaries across Victoria, at a capture scale of 1:25,000. It is used in a variety of applications, particularly in emergency services, natural resource management, planning and development, and digital map publications.
- Supplemental Information
- History: Defined locality boundaries were needed to provide clear definition in developing GIS systems, particularly those of the Australian Bureau of Statistics, emergency service dispatch and local government. ABS provided the necessary impetus to enable the Registrar of Geographic Names to pursue the goal of defined boundaries across the state. 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-11T01:13:22
Spatial
- Spatial representation type
- Vector
- Reference system identifier
- 4283
Temporal
- Begin date
- 2005-05-15
- End date
- now
Resolution
- Horizontal Accuracy
- 3m
Quality
- Conceptual Consistency
- Topologically structured.
- Missing Data
- Complete.
- Attribute Quality
- Approx. 99%. Suburbs/rural Districts Geographic Names employed contractors to systematically go through the submissions from Local Governments and compare them to the mapped boundaries and names. All discrepancies were sent to LIG for inclusion into the base data set. Geographic Names forwards to LIG any changes to the Rural Districts/Suburbs as they occur. In this dataset a locality is defined by Loc_Name
- Positional Accuracy
- Varies as per scale of capture of VicMap Digital Property. Vicmap Digital Property 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. Within the metropolitan area, 'Melbourne Water' requires subdivisions exceeding nine lots to be submitted in digital form. When input into the base, every effort is made to use this 'survey accurate' data to extend the accuracy of the immediately surrounding detail. No 'shift' of data as a means of 'cartographic enhancement' to facilitate presentation has been employed for any real world feature.
Lineage
- Description
- Local Government defines suburb, town and rural district boundaries after seeking appropriate consultation with all interested parties. Proposed boundaries/names are submitted to Registrar of Geographic Names for approval and formal gazettal. As boundary and name information changes are processed through the formal definition and gazettal process at the Registrar of Geographic Names, the amendments will be flagged and the dataset will be updated and all new boundaries aligned to Vicmap Property.
- Statement
- Dataset Source: Local Government defines suburb, town and rural district boundaries after seeking appropriate consultation with all interested parties. Proposed boundaries/names are submitted to Registrar of Geographic Names for approval and formal gazettal. Dataset Originality: Derived
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 NONE NONE NONE PFI_CR The date that the persistent Feature Identifier was created UFI_CREATED O N DATE 7 NONE NONE NONE UFI_CR The date the UFI was created VICNAMES_ID M Y NUMBER 22 9 0 VICNAMESID GNR (Vicnames) Identifier UFI O N NUMBER 22 10 0 NONE NONE NONE UFI Database wide Unique Feature identifier. Assigned at every feature creation or edit, superseded by each edit to the feature. UFI_OLD O N NUMBER 22 10 0 NONE NONE NONE UFI_OLD UFI of feature prior to last edit LOCALITY_NAME M Y VARCHAR2 46 VMREFTAB LOCALITY LOCALITY_UNIQUE LOCALITY PFI O N VARCHAR2 10 NONE NONE NONE PFI Persistent Feature Identifier. Assigned at the creation of the feature and is retained for the life of the feature. GAZETTED_LOCALITY_NAME O N VARCHAR2 40 VMREFTAB LOCALITY LOCALITY GAZLOC
About the Metadata Record
- Metadata identifier
- urn:uuid / 47352a58-1fd6-5b50-a2ec-9df8afdf8ac9
Processor
DEECA
-
Spatial, VDP
Contact
No information provided.
- Resource Type
- Dataset
- Date info ( Creation )
- Date info ( Revision )
- 2021-03-17
- Standard Name
- ISO 19115-3:2018
- Profile Name
- DELWP Profile
- Profile Version
- Version 1
- Profile Date
- 2019-05-24
Metadata Constraints
- Classification
- Unclassified
Overviews
Provided by
Views Views
47352a58-1fd6-5b50-a2ec-9df8afdf8ac9
Access to the portal Access to the portal
Read here the full details and access to the data. Read here the full details and access to the data.
Associated resources
Not available