Vicmap Property - Parcel Crown Approved Polygon
dataset:
PARCEL_CROWN_APPROVED
This layer contains a view of the Crown land Parcels. A parcel is defined as the smallest area of land capable of sale without further approval to subdivide. It may consist of more than one piece. Parcels are described by a parcel description (either lot/plan or allotment/section/parish).
It includes:
- Parcel Identifiers, both freehold and crown;
- Registered and proposed status;
- Crown land differentiation - this is defined as CROWN_STATUS of "C" for Crown land, "V" for Vested land or "G" for Government Roads,
- LGA code;
- Unique Feature Identifiers, date stamps and data quality information.
The layer replaces the "CROWNLAND.VM_CROWNSIMPLE" layer that was created for Mapshare sites as a quick way of drawing Crown land rather than all the Parcels. The Crownsimple layer has had issues with keeping in sync with the Parcel layer, whereas this layer will be re-created each time the Parcel layer is updated (every week).
MetaX records this dataset as VMPROP.PARCEL_CROWN_APPROVED
|
Citation proposal Citation proposal
(2023) Vicmap Property - Parcel Crown Approved Polygon Department of Transport and Planning https://metashare.maps.vic.gov.au/geonetwork/srv/eng/catalog.search#/metadata/b4abcf80-e2d3-51b4-a3c2-099f770a0b78 |
Details
Contacts
Cited responsible party
No information provided.
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
- ANZVI0803004688
- Victorian Spatial Data Library (VSDL) Schema
- VMPROP:PARCEL_CROWN_APPROVED
- Jurisdiction
- Victoria
- Topic category
-
- Environment
- Planning cadastre
- Boundaries
Resource Constraints
Text
No information provided.
- Classification
- Unclassified
Other Dataset Details
- Date ( Revision )
- 2023-03-16
- Date ( Publication )
- 2024-09-14T06:58:46
- Status
- Completed
- Purpose
- This layer is a view purely of the Crown land Parcels. Crown land differentiation - this is defined as CROWN_STATUS of "C" for Crown land, "V" for Vested land or "G" for Government Roads. The layer replaces the "CROWNLAND.VM_CROWNSIMPLE" layer that was created for Mapshare sites as a quick way of drawing Crown land rather than all the Parcels. The Crownsimple layer has had issues with keeping in sync with the Parcel layer, whereas this layer will be re-created each time the Parcel layer is updated (every week).
- Credit
- LCMP
- Supplemental Information
- History: The parcel layer is the base layer for the LCMP program. Production mapping of crown land commenced in 1991 and was designed to reduce the daily reliance of land administration officers on the old parish plan series by provision of up-to-date cadastral mapping available through new maps or through an online GIS (LIMS dq). Since 1991, the LCMP has progressively mapped Crown land in Victoria with approximately 85% processed into Arc/Info and part verified, and 40% (by area) of the state fully verified and value-added. Full state wide coverage of verified mapping is planned by LCMP for mid-1998. The OGDC and CLA have arranged for digital copies of the verified boundaries of Crown land to be incorporated into the OGDC source version of the DCMB. The cadastral base, with the added LIMS data, also becomes a valuable departmental resource, when added to the GIS corporate library. Combined with other departmental GIS datasets, it cna be used to address many planning and management needs. Current Design Issues: Layer is tiled on a parish basis. Future Design Issues: Possibility of integration of the metropolitan cadastre will require some data restructure due to non-polygonised cadastral data in metropolitan Melbourne. Metropolitan data is tiled on the basis of former LGA boundaries. Parish based polygonised parcel data is likely to be too large to be practically feasible in the metropolitan region. The integration of the two data sets may be possible due to recent work by the OGDC to coordinate the metropolitan DCMB which was derived from the former Melbourne Water Authority and the rural DCMB, originall developed by Survey and Mapping. Related Documents: None LCMP Data Take-on Manual (Version 7), Data Acquisition - Plot Markup procedures, LCMP Drafting Specifications.
- Maintenance and update frequency
- Continual
- Maintenance date ( Publication )
- 2023-03-17T21:04:44
Spatial
- Spatial representation type
- View
- Reference system identifier
- 4283
Temporal
- Begin date
- unknown
- End date
- now
Resolution
- Horizontal Accuracy
- 50m
Quality
- Missing Data
- All islands included All islands included
- Attribute Quality
- All attributes in the PAT for crown parcels have been verified as correct.
- Positional Accuracy
- Precision: Accuracy of +/- 25m Determination:
Lineage
- Description
- Extensive documentation of the data take-on process is described in the LCMP Data Take-on Manual (Version 7), available through LIMS Spatial Systems Group. Essentially, the initial process involves the processing of the GDV data using an IGDSARC command. Classes, levels and weights are outlined in a former Survey and Mapping Victoria document, "Level map, Graphic Attribute and Feature Code Specifications for Cadastral Data Elements".
- Statement
- Dataset Source: Vicmap Property is derived from what were originally two logically and physically separated databases. Melbourne Water created a digital data set covering the Melbourne Metropolitan area. Survey and Mapping Victoria created a similar data set covering rural Victoria. Both data sets consisted of "spaghetti" line work (that is, unintelligent data). Neither data set was suited to GIS applications, as neither was "clean" in terms of line work, topologically-structured, or held any significant degree of "intelligence". The main level of "intelligence" linked to the data was through line style, colour, level, etc, and a feature code, data link which defined the scale origins and type of boundary represented. The Metropolitan Base was created as a reference framework for Melbourne Water's assets and reflected Melbourne Water's business needs by holding subdivisions at both the proposed and approved stages. It focused on rateable properties and placed less emphasis on the cadastral changes that did not relate to 'property Survey and Mapping's rural data set reflected a more basic view of land administration, comprising transferable parcels of land. This project entailed a complete re-compilation of the source data, being original Parish plans, registered plans of subdivision and VicRoads survey plans. The process required the production of pencil-plot compilations at a chosen scale of 1:2,500 over towns and built- up areas (using survey-acquired control) and 1:25,000 for the balance of the state (using existing standard Vicmap 1:25,000 topographic mapping as control). In a small number of areas, where existing base mapping could be used or where compilation at 1:25,000 was impractical (eg along the Murray River and parts of South Gippsland), mapping at 1:10,000 was produced. Where other authorities' (Local Government or Water Boards) mapping at similar or better scale and accuracy was found, it was adopted or upgraded and used in preference to producing new compilations Both data sets were eventually brought under control of a single authority, that of the Office of Geographic Data Co-ordination (OGDC). Key challenges for OGDC were to provide a common structure to the data and to standardise the maintenance. Government restructures have since seen administration changes through Geographic Data Victoria (GDV) to Land Victoria, but management of the data has remained stable. Throughout this time, significant changes to the data (its structure, quality, content and maintenance) have occurred, one of the most noteworthy being the out-sourcing of data maintenance to a non-government agency. Whilst full control and administration of the data remains with Information Services Branch (ISB), Vicmap Property is now maintained by an external provider. Other key changes to the property map base have included: · amalgamation of the two map bases; · translation into an Oracle® data base environment; · line cleaning and topological; · the identification and rectification of many "gaps" found in the data (for example, missing survey plan notings, and incomplete identification of Crown land). · Restructuring of the data to correctly map real world parcel and property relationships Improvements in the data continue, with improved input from local government and other key sources allowing faster turn-around of update information and added levels of attribution, for example Council property reference numbers. 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 BLOCK O N VARCHAR2 12 BLOCK SPI O N VARCHAR2 18 SPI UFI O N NUMBER 22 11 0 UFI PARISH_CODE O N VARCHAR2 4 PARISHC PARCEL_TASK_ID O N NUMBER 22 10 0 PAR_TASKID ALLOTMENT O N VARCHAR2 10 ALLOTMENT PLAN_NUMBER O N VARCHAR2 9 PLAN_NO PARCEL_PFI_CREATED O N DATE 7 PC_PFI_CR PARV_UFI_OLD O N NUMBER 22 10 0 PV_UFI_OLD PARV_PFI O N VARCHAR2 10 PARV_PFI PARV_UFI O N NUMBER 22 10 0 PARV_UFI P_NUMBER O N VARCHAR2 10 P_NUMBER PARV_UFI_CREATED O N DATE 7 PV_UFI_CR LOT_NUMBER O N VARCHAR2 12 LOT_NUMBER PARCEL_UFI_OLD O N NUMBER 22 10 0 PC_UFI_OL REG_DATE O N DATE 7 REG_DATE MULTI O N VARCHAR2 1 MULTI PART O N VARCHAR2 1 PART DESC_TYPE O N VARCHAR2 2 DESC_TYPE PARCEL_UFI O N NUMBER 22 10 0 PARCEL_UFI CREFNO O N VARCHAR2 15 CREFNO FURTHER_DESCRIPTION O N VARCHAR2 80 FUR_DESC SPI_CODE O N NUMBER 22 3 0 SPI_CODE Z_LEVEL O N VARCHAR2 2 Z_LEVEL SUBDIVISION O N VARCHAR2 12 SUBDIV PARCEL_UFI_CREATED O N DATE 7 PC_UFI_CR PARV_PFI_CREATED O N DATE 7 PV_PFI_CR UFI_CREATED O N DATE 7 UFI_CR PARCEL_PFI O N VARCHAR2 10 PARCEL_PFI POINT_ID O N VARCHAR2 36 POINT_ID PORTION O N VARCHAR2 12 PORTION CROWN_STATUS O N VARCHAR2 1 CROWN_STAT SEC O N VARCHAR2 12 SEC LGA_CODE O N VARCHAR2 3 LGA_CODE PARV_TASK_ID O N NUMBER 22 10 0 PARVTASKID TOWNSHIP_CODE O N VARCHAR2 5 TOWNSHIPC ROAD O N VARCHAR2 1 ROAD HORIZ_POS_UNCERTAINTY O N NUMBER 22 5 2 HZPOSUNCTY STATUS O N VARCHAR2 1 STATUS
About the Metadata Record
- Metadata identifier
- urn:uuid / b4abcf80-e2d3-51b4-a3c2-099f770a0b78
Processor
DEECA
-
Spatial, VDP
Contact
No information provided.
- Resource Type
- Dataset
- Date info ( Creation )
- 2023-03-27T14:48:19
- Date info ( Revision )
- 2024-03-22T14:22:47
- 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
b4abcf80-e2d3-51b4-a3c2-099f770a0b78
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