Contacts

Identifiers and Keywords

ANZLIC Id

ANZVI0803009256 

Victorian Spatial Data Library (VSDL) Schema

VMPROP:TASK 

Jurisdiction

Victoria 

Topic category

• Planning cadastre
• Environment
• Boundaries

Resource Constraints

Use limitation

Access through www.delwp.vic.gov.au/vicmapdata o As above. 

Classification

Limited Distribution  

Other Dataset Details

Date ( Revision )

2022-08-02

Date ( Publication )

2023-03-18T01:18:05

Status

Completed  

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 https://www.land.vic.gov.au/maps-and-spatial/spatial-data/vicmap-catalogue 

Maintenance and update frequency

Continual  

Maintenance date ( Publication )

2023-03-18T01:18:05

Spatial

Spatial representation type

Text, table  

Description

General - Victoria 

Reference system identifier

4283

N

S

E

W

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
TASK_DATA_LOCATION	O	N	VARCHAR2	255						TASKDATALN
BATCH_ID	O	N	NUMBER	22	10	0				BATCH_ID
DATE_RELEASED	O	N	DATE	7						DTRELEASED
OPERATOR_ID	O	N	NUMBER	22	10	0				OPERATORID
DOCUMENT_NO	O	N	VARCHAR2	255						DOC_NO
SOURCE_AGENCY	O	N	VARCHAR2	50						SRC_AGENCY
DATE_RECEIVED	O	N	DATE	7						DATERECVD
STOPPED_CLOCK_REASON	O	N	VARCHAR2	255						STOPCLOCKR
STATUS	O	N	VARCHAR2	20						STATUS
DATE_COMPLETED	O	N	DATE	7						DATECOMPLT
TASK_ID	O	N	NUMBER	22	10	0				TASK_ID
UFI_OLD	O	N	NUMBER	22	10	0				UFI_OLD
DATA_SUPPLY_METHOD	O	N	VARCHAR2	20						DATASUPMET
PFI_RETIRED	O	N	DATE	7						PFIRETIRED
UFI_CREATED	O	N	DATE	7						UFI_CR
TASK_EFFORT_ESTIMATE	O	N	NUMBER	22	10	1				TASKEFFEST
SOURCE_TASK_ID	O	N	VARCHAR2	255						SRC_TASKID
UFI	O	N	NUMBER	22	10	0				UFI
LGA	O	N	VARCHAR2	45						LGA
DOCUMENT_VERSION	O	N	VARCHAR2	20						DOC_VERSN
TASK_ACTUAL_TIME	O	N	NUMBER	22	10	1				TASKACTTIM
DATE_ONHOLD	O	N	DATE	7						DATEONHOLD
DOCUMENT_STAGE	O	N	VARCHAR2	20						DOC_STAGE
TASK_COMMENTS	O	N	VARCHAR2	500						TASKCOMMT
PLAN_STATUS	O	N	VARCHAR2	50						PLANSTATUS
DATE_REVISED	O	N	DATE	7						DTREVISED
LGA_CODE	O	N	VARCHAR2	3						LGA_CODE
PFI_CREATED	O	N	DATE	7						PFI_CR
DESCRIPTION	O	N	VARCHAR2	255						DESC
DATE_TARGET	O	N	DATE	7						DTTARGET
TASK_TYPE	O	N	VARCHAR2	50						TASK_TYPE
NUMBER_LOTS	O	N	NUMBER	22	4	0				NUM_LOTS

About the Metadata Record

Metadata identifier

urn:uuid / a821d759-b378-571f-8978-a10ba3420bad