Technical specifications accessible [MS Word Document

advertisement
Technical specifications
Vicmap Transport
Document version 1.0 – November 2013
Applies to delivered data model version 3.3
Published by the Victorian Government Department of Environment and Primary Industries Melbourne,
June 2013
© The State of Victoria Department of Environment and Primary Industries 2013
This publication is copyright. No part may be reproduced by any process except in accordance with the
provisions of the Copyright Act 1968.
Authorised by the Victorian Government, 8 Nicholson Street, East Melbourne.
Print managed by Finsbury Green. Printed on recycled paper.
ISBN 978-174287-815-7
For more information contact the DEPI Customer Service Centre 136 186
Standard
This document is based on the AS/NZS ISO 19131:2008 Geographic information
Acknowledgments
The Department of Environment and Primary Industries acknowledge the assistance of PSMA Australia in the
preparation of this guide.
Disclaimer
This publication may be of assistance to you but the State of Victoria and its employees do not guarantee that the
publication is without flaw of any kind or is wholly appropriate for your particular purposes and therefore disclaims all
liability for any error, loss or other consequence which may arise from you relying on any information in this publication.
DEPI does not warrant that this Product Description and the data are free from errors or omissions. Also, DEPI shall not
be in any way liable for any loss, damage or injury suffered by the licensed user of the data of this Product Description or
any other person or organisation consequent upon or incidental to the existence of errors or omissions in the data or this
Product Description.
Accessibility
If you would like to receive this publication in an accessible format, such as large print or audio, please telephone
136 186, or email customer.service@depi.vic.gov.au
Deaf, hearing impaired or speech impaired? Call us via the National Relay Service on 133 677 or visit
www.relayservice.com.au
This document is also available in PDF format on the internet at www.depi.vic.gov.au/vicmap/vicmap
Department of Environment and Primary Industries
Contents
Overview
5
Vicmap Transport
Feature Identification and Tracking
Spatial services PFI /UFI Applications
5
5
5
Data Quality
6
Accuracy
Feature and attribute accuracy (Thematic accuracy)
Quality
6
8
9
General information
20
Feature representation
23
Reference tables
37
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
1
Overview
Vicmap Transport
Vicmap Digital is the foundation that that underlies most spatial information in Victoria. This set of
spatial related data products, made from individual datasets, is developed by Information Services
Victoria, DEPI.
VSIS framework information datasets have been delivered into the following Vicmap Products, identified
below.
Feature Identification and Tracking
Feature identification is managed through the use of two identifier attributes, the Persistent Feature
identifier (PFI) and the Unique Feature Identifier (UFI).
The PFI is a sequential number allocated to new features at creation and remains with the feature
throughout all editing actions. Over time the PFI itself will not be unique within the database as edit
actions result in splitting and merging of features.
The UFI attribute will be assigned to new or edited features as maintenance occurs. The UFI attribute
will always be unique.
Spatial services PFI /UFI Applications
The following incremental update attributes are required with behaviour as described:
 PFI – a sequential number applied across the whole VDRT database.
A new PFI is assigned in the following instances:
1. Creation of a new feature, i.e. when a new object is added to the database.
2. When two or more existing features are merged, the final merged feature assumes a new PFI.
The old PFIs of the features making up the merged feature are retired.
When a feature is split into two or more new features. Each of the new features is assigned a new PFI.
The PFI of the original feature is retired.
PFIs do not change when a feature is edited in any other way. i.e. when the following edits are
undertaken on features :3. Attributes of a feature are modified
4. Physical or spatial representation of a feature is modified.

UFI - a unique sequential number applied across the whole VDRT database. New UFIs are
created on a feature whenever edits are undertaken on the feature.

Create_date_UFI, The date that a UFI is created on a feature

Retire_date_UFI, The date that a feature is retired. A feature is retired when any physical
change, attribute change, or deletion of a feature occurs.

Superceded_UFI; This is the UFI of a feature prior to the last edit of the feature

create_date_pfi, (format dd-mmm-yyyy hh:mm:ss) is the date/time stamped against each
feature when it is originally created and remains with the feature through all editing actions to
attributes or modification of feature spatial representation.

‘retire_date_pfi, (format dd-mmm-yyyy hh:mm:ss) is the date/time stamped against each
feature when it is retired as a result of merge, split or deletion actions.
Vicmap data is never deleted, only retired. All key features are tagged with the above attributes to
enable an audit trail to be maintained and to facilitate incremental updating.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
5
Data Quality
DEPI is reviewing its Quality Assurance practices to ensure they conform to those proposed by
Australian Standards (AS). Proposed AS/NZS and ISO documents include;
Quality Control ‘Guidelines for Quality Control in ISO/TC211’
ISO/CD 15046-5: Geographic Information – Part 5: Conformance and Testing
ISO/CD 15046-13: Geographic Information – Part 13: Quality Principles
ISO/CD 15046-14: Geographic Information – Part 14: Quality Evaluation.
AS/NZS 4819: Rural and Urban Addressing 4819:2011.
Accuracy
Positional
The positional accuracy of spatial data is a statistical estimate of the degree to which planimetric
coordinates and elevations of features agree with their real-world values.
The minimum positional accuracy attainable will be the sum of errors from three sources:

The positional accuracy of source material;

Errors due to the conversion process;

Errors due to the manipulation process.
The positional accuracy of the source material - Sm
This specification cannot prescribe a figure for the positional accuracy of much of the source material as
it had already been produced. For example, the Vicmap Transport road centre lines are primarily
derived from the following sources:
1. Vicmap Property – cadastral base data
2. Vicmap’s ‘Topographic’ themes
There is an expectation that the source data complies with the following statements.
Topographic mapping-derived data:
Not more than 10% of well-defined points shall be in error by more than 0.5 mm measured on
the source material.
Statistically, this relates to a standard deviation on the source map (Sm) of 0.31 mm.
Cadastral mapping-derived data:
This data has generally been derived via plotting onto the topographic base, and therefore is of
significantly lower accuracy than the topographic base.
Not more than 10% of well-defined points shall be in error by more than 1.0 mm measured on
the source material.
Statistically, this relates to a standard deviation on the source map (Sm) of 0.62 mm.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
6
Errors due to the conversion processes – Sdata
The errors due to the digitising process depend on the accuracy of the digitising table set-up or the
scanner resolution, systematic errors in the equipment, errors due to software and errors specific to the
operator. An accepted standard for digitising is that the line accuracy should be within half a line width.
The majority of features derived from topographic maps have a line width of 0.2 mm or greater. The
half-line width is taken as 0.1 mm and this in interpreted as one standard deviation S data for the
distribution of errors.
Linear Features:
As well as the errors in the conversion process, linear features are also subject to filtering as part of the
point density reduction process. If the filtering parameters are not carefully selected the resulting linear
feature may not retain sufficient likeness with the source material. To ensure linear features are faithful
to the shape and length of the source material, the specification below will be satisfied:
The separation between the feature instance on the source material and its Vicmap Transport digital
representation shall not be greater than 0.2 mm at source material scale, i.e. 5m for 1:25,000 data.
Errors due to the manipulation processes - Sman
The processes used during data editing and structuring processes will introduce an error S man not
greater than 10% of the Sdata.
Other errors due to cartographic generalisations and data model simplifications are referred to in the
section on Generalisations Within The Data.
Absolute positional accuracy
The total statistical error from the source material and digitising process (Sabsolute) discussed above is
given by the following formulae:
Topographic base-derived data
sa b so lu te
=
( sm ) 2  ( sd a ta) 2  ( sma n) 2
( 0. 31) 2  ( 0. 10 ) 2  ( 0. 03) 2
= 0. 33 mm
This represents an error of 8.3 m on the ground for 1:25,000 data. Typically, rural areas outside the
metropolitan area would be sourced from 1:25,000 Spatial Information Infrastructure Vicmap
topographic data giving a worst case of 8.3m.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
7
Cadastral Base-derived data
sa b so lu te
=
( sm ) 2  ( sd a ta) 2  ( sma n) 2
( 0. 62 ) 2  ( 0. 10 ) 2  ( 0. 03) 2
= 0. 63 mm
This represents an error of 0.32 m for 1:500 data and 1.6m for 1:2,500 data.
Typically, within the area covered by Spatial Information Infrastructure Vicmap metro cadastral data,
source mapping scales of between 1:500 and 1:2,500 are used giving a worst case of 1.6 m.
Generally, rural areas outside the metropolitan area would be sourced from 1:25,000 topographic data.
However, most rural townships would be sourced from 1:2,500 Spatial Information Infrastructure
Vicmap cadastral data giving a worst case of 1.6 m.
A conservative estimate of 5 m and 20 m for the standard deviation of the Vicmap Transport
within the Melbourne Metropolitan area and Rural areas respectively will be used in any data
quality information.
Alternative and equal ways of expressing this error are:

Not more than 10% of well-defined points will be in error by more than 8.2 m for the Melbourne
Metropolitan area and 33 m for rural areas.

The worst case error for the data is ±15 m for the Melbourne Metropolitan area and ±60 m for
Rural areas.
It should be noted that the limited field checks for positional accuracy so far undertaken have shown the
data to be well within 12 metres of surveyed position.
The positional accuracy of each feature instance (stated as a source scale) is given in the Data Quality
Table. A value of 9999 is used when the positional accuracy of the feature is not definable or not
applicable. For example the coordinates of a connector feature do not carry any meaning with respect
to positional accuracy and so the value of positional accuracy given is 9999.
Feature and attribute accuracy (Thematic accuracy)
DEPI is continually improving and extending the quality and content of the base. It is proposed to
undertake a series of ongoing post-production validation checks to confirm content and spatial
accuracies. Proposals include :

Ongoing - Property Information Program (PIP) – reconciliation of property/parcel/road
information held by local government against Vicmap;

Information Infrastructure Initiative (III), the purpose of which is to improve the quality and
performance of land information infrastructure for Victoria.
Positional, relative & planimetric accuracy

Ongoing – Customer feedback. Data anomalies identified by Vicmap users may be lodged in
the Notification for Editing System (NES) for investigation and, where required, rectification

Data Anomaly Investigation/Edits
Anomalies identified during the data capture process were flagged for future investigation.
Although most have been corrected, the balance may be reviewed as resources permit.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
8
Attribute accuracy

Checks on existing data attribution is continuing and inconsistencies are being systematically
identified, removed and omissions added, e.g. name attributes, construction and structure
type. For example, ISB seeks the latest authoritative list of road names from all road managers
and road naming authorities as well as Victorian councils. ISB reviews VT road name content
against these road name authority listings through the annual Property Information Quality
Audit (PIQA). – It should be noted that this work has raised inconsistencies within local
government’s management systems and names may cycle as they are reaffirmed or revised.
Quality
To conform as far as possible to the national (ICSM) topographic data model, some specific
requirements were identified by DEPI, with respect to the handling of cartographic text, unformed
polygon based features, and temporal and status management.
Vicmap Transport data will comply with the following rules for spatial data integrity. (The maximum
allowable errors are described in the ‘Data Quality’ section. The rules will be enforced with a 95% or
better confidence level when full Vicmap Transport compliance has been reached.)

The spatial data will have no overshoots, undershoots, broken lines, pseudo nodes or other
artefacts of the data capture process.
These possible errors in the data and their correct structure are illustrated below.
Correct Representation
Incorrect Representation
Undershoot in data
Correct Representation
Incorrect Representation
Overshoot in data
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
9
Pseudo node
Same feature with identical attribute values
Pseudo-node in data
Correct Representation
Incorrect Representation
Broken line in data
Correct Intersection
Correct Linear Feature
Incorrect Intersection
Incorrect Intersection
Spike in Linear Feature
Artefacts
Artifacts such as spikes and deviations of a linear feature from its expected position are removed from
the data to the extent that they will not be visible when the data is plotted or displayed at half its nominal
scale i.e. 1:12 500 for 1:25 000 data.

All linear features within the same layer are broken by a node at intersections, or at the point
where an attribute of the feature changes. A node will exist at these intersection points.

Within a layer there will be no coincident features.
Coincident features
There will be no coincident polygons, lines (whole or in part) or points of the same feature type in the
data (also frequently known as double digitising). Differing features may be coincident, as may be the
case where a dam wall also forms part of a dam polygon, (in these cases, the common data repeats for
each feature type, and is appropriately tagged and supplied as part of each feature type)
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
10
Point Density Reduction
Data point reduction filters linear spatial objects so that the locational information is conveyed by the
minimum number of points while still retaining the smooth shape of the source data.
The following specifications have been adopted:

The length of a line segment should be equal to, or greater than 2.5 metres.

The length of a line segment should not be greater than 10,000 metres.
Resolution of coordinates
Co-ordinates of all spatial objects will be quoted to the nearest 0.001 metres
Unique Feature Identifier Attribute
Feature identification is managed through the use of two identifier attributes, the Persistent Feature
identifier (PFI) and the Unique Feature Identifier (UFI).
The PFI is a sequential number allocated to new features at creation and remains with the feature
throughout all editing actions. Over time the PFI itself will not be unique within the database as edit
actions result in splitting and merging of features. Old PFI’s are retired after merge and split edits. A
PFI does not change when edits are undertaken on attributes or modifications done to spatial
representation of a feature.
A Unique Feature Identifier (UFI) will be an alphanumeric string attached to each feature instance as an
attribute. The UFI will be unique on a State basis (depending on systems adopted by other States), and
is expected to facilitate the efficient incremental update of Vicmap Transport features.
The UFI attribute will be assigned to new or edited features as maintenance occurs. The UFI attribute
will always be unique.
Both PFI and UFI items are numeric by definition and will be managed with the same domain across all
themes in Vicmap Digital.
Class: spatial_feature
Definition: A spatial feature within the dataset
Features: Spatial
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
11
Name
Definition
Data Type
Key
Mandatory
PFI
VICMAP Digital
unique identifier for a
feature over time
(common to all
versions of a single
feature)
number
yes
yes
UFI
VICMAP Digital
unique identifier for a
feature
Number
yes
yes
feature_type_code
feature code to
identify feature type
Character
named_feature_id
Feature Name
Identifier for the
feature
number
feature_quality_id
Identifier for the
feature quality record
number
yes
Create_date_pfi
Date the PFI
originally created
date
yes
Superceded_pfi
PFI of feature before
merge or split
operation
number
create_date_ufi
Date the ufi was
created on
date
Unique
yes
yes
yes
Spatial Feature Class Common Attributes
FEATURE CODING CONVENTIONS
Meaningful alphanumeric feature codes are held directly on the spatial features to assist in data
maintenance. In a number of instances, feature codes are expanded to inherently hold some ‘type’
attributes, that are normalized in the Spatial Information Infrastructure Unified Data Store model. Type
attributes in the Transport Theme have been absorbed using this approach as per the following Table.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
12
Aggregated Feature
Type Attribute
Entities
Feature Type Codes
Road Infrastructure
Road
Infrastructure_type
Ford
ford
Bridge
bridge
Tunnel
tunnel
Gate
gate
Barrier
barrier
Level Crossing
level crossing
Intersection
int_admin
int_attribute
int_coast
int_locality
int_nosignal
int_signal
roundabout
road_end
Transport Feature Codes incorporating type
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
13
GENERAL REFERENCE CLASSES
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
14
Feature Quality Class Attributes
Class: feature_quality
Definition: Defines accuracy and other quality information pertaining to this spatial feature
Features: Aspatial
Name
Definition
Data Type
Id
Identifier for the feature quality
record
number
feat_reli_date
reliability date for spatial
features
date
yes
attr_reli_date
reliability date attribute
date
yes
plan_accuracy
plan accuracy
real
yes
elevation_accuracy
elevation accuracy
real
yes
data_sour_code
Source Code
number
yes
Scale
VICMAP Digital data scale
indicating position accuracy
number
yes
create_date
Date the record was created on
date
yes
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
15
Code
List
Key
Mandatory
yes
yes
DATA SOURCE CODE
Data Source Class Attributes
Source
Source Description
1
MMBW
10
MELWAYS/UBD
20
VICROADS
21
VICROADS - DESIGN
30
DNRE
31
DNRE - TOPOGRAPHIC
32
DNRE - PROPERTY
40
LOCAL GOVERNMENT AUTHORITIES
50
EMERGENCY SERVICES/BEST
60
WATER AUTHORITIES
70
FIELD DATA CAPTURE
80
SATELLITE IMAGERY
81
AERIAL PHOTOGRAPHY
90
NSW – LAND INFORMATION CENTRE
999
UNKNOWN
REFERENCE TABLE CODELISTS APPLICABLE:
Derivation of Planimetric Accuracy
The proposed derivation of planimetric accuracy is based on the SDRN ( State Digital Road
Network)specification absolute accuracy definitions (Refer SDRN Technical Specification version 5.0).
Standard deviations proposed to be adopted as detailed below:-
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
16
Scale
source
theoretical plan_acc
Formula Used
adopted plan_acc
40
1, 32 (cadas)
0
scale*0.00063
0.5
480
1, 32
0.3
0.5
500
1, 32
0.3
0.5
1000
1, 32
0.6
1
2500
1, 32
1.6
2
5000
1, 32
3.2
4
7500
1, 32
4.7
5
10000
1, 32
6.3
10
20000
1, 32
12.6
15
25000
1, 32
15.8
20
50000
1, 32
31.5
35
40
31 (topo)
0
480
31
0.2
0.5
500
31
0.2
0.5
1000
31
0.3
0.5
2500
31
0.8
2
5000
31
1.7
3
7500
31
2.5
4
10000
31
3.3
6
20000
31
6.6
11
25000
31
8.3
14
50000
31
16.5
28
scale * 0.00033 0.5
All other sources scale * 0.00033
9999999
9999
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
17
Round up to appropriate whole
metre
9999
Class: data_source
Definition: The source of the data in this dataset
Features: Aspatial
Name
Definition
Data Type
Code List
Key
Mandatory
Code
Source code
number
yes
yes
Name
Data source name
character
yes
description
Source description
character
no
DATA LAYER CLASS ATTRIBUTES
Class: Layer
Definition: The layer to which the features belong
Features: Aspatial
Name
Definition
Data Type
Code
Layer code
number
Name
Layer name
character
yes
Description
Layer description
character
no
theme_code
Theme code
character
yes
DATA THEME CLASS ATTRIBUTES
Class: Theme
Definition: The Theme to which the features belong
Features: Aspatial
Name
Definition
Data Type
Code List
Code List
Key
Mandatory
yes
yes
Key
Mandatory
yes
yes
Code
Theme code
number
Name
Theme name
character
yes
Description
Theme description
character
no
NAMED FEATURE CLASS ATTRIBUTES
Class: named_feature
Definition: The list of all names of features used within Victoria, with linkages to the official Place Names Register
maintained by Spatial Information Infrastructure.
Features: Aspatial
Name
Definition
Data Type
Code List
Id
Unique name id within Vicmap
Digital (Roads & Topographic)
number
Name
Name
character
yes
Place_name_pid
Foreign key to Victorian Place
Names Register
number
yes
create_date
Date the record was created on
date
yes
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
18
Key
Mandatory
yes
yes
ALTERNATE NAME CLASS ATTRIBUTES
Class: alternate_name
Definition: The list of alternative names applicable to features. Names may or may not occur in the Place Names
Register.
Features: Aspatial
Name
Definition
Data Type
Code List
Id
Unique name id for features with
a unique combination of primary
and alternate names
number
Name
Name
character
yes
create_date
Date the record was created on
date
yes
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
19
Key
Mandatory
yes
yes
General information
History

Vicmap Transport is derived from topographic series mapping instigated in the early 1970’s.

The State commenced its mapping program in 1970 with the aim of producing hardcopy series mapping across
Victoria. Preliminary compilation was at 1:10,000 scale and produced 1:10,000 base maps in town and urban
areas and 1:25,000 topographic maps in rural areas.

An accelerated program was instigated in 1980 to step up production over the State with printed double format
Topographic maps. Graphical capture of the State was completed in 1994.
Methodologies used included
photographic scale reduction of available 1:10,000 mapping, photogrammetric plotting, digital scanning and
digitising.

Whilst initial compilation was oriented to the creation of repromat material for the publication of paper maps, a
conversion program and continuing capture to digits was commenced. Between 1985 and 1994, a mandatory
‘digital’ data set (Roads, Hydrography and Relief) was created using processes such as raster scanning of
negative separations and vectorising, together with a small amount of direct digitising from source
photogrammetric compilation plots and mapping artwork.

A second stage program was undertaken between 1994 and 1997 to capture the balance of topographic data
covering infrastructure, vegetation, spot heights, contour values and text.

This new ‘digital’ data was held as ‘spaghetti’ Microstation design files in individual 1:25,000 single or double
mapsheet tiles. The data had no topological structure. Features were given limited intelligence through line and
symbol styles and colours, attribution using AS2482 feature coding and separation into 63 levels. Contours and
spot heights were tagged with respective height values. This data was known as the State Digital Map Base
(SDMB) – Topographic.

In 1995, the State Government required the establishment of a multi agency emergency services Computer Aided
Dispatch system (CAD) under the Bureau of Emergency Services Telecommunications group (BEST). Initial
implementation required the establishment of a digital road network for the metropolitan area and slightly beyond
(Best CAD map area). The State Digital Road Network (SDRN) was established utilising the road detail of
topographic roads product over rural locations, supplemented with the more accurate and current cadastral road
centre lines for towns. Address points were created from Melbourne Water’s POLARIS mail address data base.
The SDRN was created with full model specifications, data structure rules, topology, unique identification and
extended descriptive attribution.

Meanwhile, the original SDMB - Topo data whilst cartographically correct, lacked the connectivity (overshoots &
undershoots), attribution and topology required for modern GIS environments. The data had to be cleaned and
polygonised. All data underwent a process of cleaning, topological structuring and attribution to make it GIS
ready. Additional data was captured where required. This new GIS data has been separated into themes and
Custodians assigned to each with responsibilities to maintain and further develop their products. As part of the
VGIS Victorian Geospatial Information Strategy (2000-2004), key elements of the data were grouped into the eight
framework data sets.

Vicmap Transport is now a theme of the SDMB. The data has undergone considerable quality assurance to verify
accuracy and content via update projects such as ESI and ongoing validation against local government data via
the Property Information Project (PIP).

As part of the VGIS 2000 – 2004 geospatial information initiative, framework data was grouped into eight
“Framework” data sets one of which is TRANSPORT.

Vicmap data has undergone considerable quality assurance to verify accuracy and content via update projects
and ongoing validation against local government data via the Property Information Program (PIP).

Since 2005 considerable effort has been made to eliminate redundant data and verify existing data. This has been
aided by DEPI’s Coordinated Imagery Program (CIP). Extensive statewide projects have been completed
investigating Paper Roads, Roads on freehold land, DEPI managed roads, Road seals and proposed roads.
Standards and Specifications
Conformity is sought with relevant portions of existing and draft standards and specifications. For example,
Relevant Australian (AS/NZS) standards.
ISO 19100 series as they become adapted by Standards Australia and the user community.
The outputs of Working Groups under the auspices of ICSM, ANZLIC and other industry organisations.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
20
ICSM Roads Working Group Road Model 2010
DEPI has adopted the recommended ICSM Guidelines for incremental update (Ref. Policy and Guidelines for
Incremental Update – ICSM Harmonization Working Group, October 2000).
Where these Standards have been found to be deficient to DEPI ISB requirements (e.g. attribute field size insufficient)
suitable modifications will have been made. A table of variations is documented and will be available via the Internet
on www.depi.vic.gov.au/spatial.
Legislative requirements

This dataset has not been constructed as the requirement of any Commonwealth or State legislation.

Under the auspices of the Subdivision Act, local government must provide subdivision information to the Registrar
of Titles.

The use and distribution of Vicmap Transport must comply with the Information Privacy Act 2000 (Victoria) and the
Privacy Act 1988 (Commonwealth).

The 2004 Road Management Act requires all Victorian road managers to maintain a list of public roads under their
management. Since this was enacted Vicmap Transport has benefitted from improved road management
practices and records being available from authoritative sources.
Current Data Development
Fitness for Purpose establishment: A series of workshops are being held with industry groups to establish what their
business requirements of the data are. Armed with this information a ‘fitness for purpose’ specification will be
developed and a migration program determined.
Notification for Editing Service: The Notification for Editing Service (NES) is an initiative that is crucial to supporting
government delivering outcomes by aiding in the provision of authoritative location based services across business for
users of all levels of expertise. The objectives of NES are to:

Improve spatial data quality

Provide simple, efficient, effective, low cost maintenance processes

Create a fully transparent maintenance process for all participants

Enable maintenance process availability to any potential maintainer
Access to NES application is restricted to selected customers. Enquiries can be directed to NES Administrator at
www.depi.vic.gov.au/NES
Future plans
Further enhancement and development of this Vicmap product will be achieved through various projects:
Quality Reporting Tool Identified Data Deficiencies: IBT has developed a Quality Reporting Tool (QRT) to test
the conformity of the data held in our Vicmap Products against product specifications and reference files. These
scripts are run following the receipt and loading of each Incremental Update. The QRT identifies deficiencies in the
data and provides documented evidence of non-conformance of the data. This will be used to justify data upgrade
projects to improve the conformity of the data.
Fulfillment of strategic aims:

Integration with other Vicmap data sets (Transport, Admin & Address): As part of the VSIS spatial
data framework strategy, work will continue to bring all Vicmap products into closer alignment, particularly in terms
of vertical topology.
Vicmap Transport is being further enhanced and developed through the implementation of the following projects:

‘Anomaly Advice Notices’ (Internet-based forms for feedback) are received from knowledgeable notifiers
through the Notification and Edit Service. Work is being undertaken to further encourage client input and the
processing of such information including: clearer and easier-to-use advice notices and facility for electronic
submission.

Upgrade feature attribution - Some features lack full descriptive attribute values. As sources are identified, they
are used to populate appropriate null attributes. E.g. walking track names, road restriction information.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
21
Database

Association between coincident features when appropriate;


Some form of relationship should be able to be maintained between features that are in effect occupying the
same space in the real world. E.g. Many road centre lines also form administrative boundaries or are
coincident with other features; for example dam wall.
Existing Vicmap Digital data to be accommodated without loss of information;
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
22
Feature representation
Road Feature representation
Roads as chains
Generally, with the exception of cases noted below, all roads, including multiple lane and minor dual carriageway
roads, will be simplified into a single-line bi-directional representation. That is, a single chain will represent roadways
between intersections, regardless of traffic direction – as per the example below.
Single line representation of a minor dual carriageway road
Painted or unsubstantial median strip
Dual Carriageway
Vicmap road
representation
Connector features (pseudo roads)
To allow linear analysis of road networks to be carried out, an artificial feature called a 'connector' may be added to
the data. ‘Connector' or pseudo road features will allow reduction of substantial roundabouts to a single node feature
for network computational purposes. They may also be used to form an implied intersection where a local road does
not directly intersect a highway but may be considered to do so as entry via a service road is possible. For example:
service road exit
Main Road
roundabout
feature
Connector or
pseudo road
Connector or
pseudo road
Substantial Roundabout
Service road
Jones Road
Implied Intersection
The connector feature is composed of one or more chains, providing a topologically correct representation of the
feature for analysis purposes. The points that make up this chain cannot be given any value for planimetric accuracy
and this is indicated in the Data Quality attribute for the feature by a value of 9999999 (not applicable) for the
planimetric accuracy scale attribute. The general rule for the attribution of connectors is that connectors carry the
attributes of the road they represent.
Dual carriageways
All known divided roads are attributed as ‘divided_road’.
To be represented as separated carriageways in Vicmap Transport, a road must meet the following criteria:
 There exists a physical divider (for example, a raised concrete/asphalt strip, kerb and channel, planted or
grassed median, etc.) between carriageways.

The centre-line of each carriageway is separated by at least 20 metres.

The length of the dual carriageway is greater than 100 metres.
A small number of yet to be identified minor “local” roads with separate carriageways and divided sections of road that
fail to meet the above criteria are represented as single line features.
Carriageways of Freeways and Motorways
A separate road chain for each carriageway will represent all freeways and motorways. For example, Tullamarine
Freeway, Western Ring Road, City Link, East Link).
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
23
Carriageways with different names
Differently named carriageways are represented separately. That is, separate roads of differing names, running
parallel or in close proximity to each other will be depicted and attributed as separate chains.
Locality boundaries along dual carriageways
Where a divided road defines a locality boundary, one half of the dual carriageway is represented to the left of the
locality boundary and the other to the right of the locality boundary.
Service roads
Service roads are separately captured and identified. Unless a service road is identified as having its own individual
road name, the road_name will that of the main road it services.
Cross roads and cross-overs
Where crossovers occur, the names of any crossing roads are included as alternate names to cater for the
identification of the intersecting roads (see example figures below).
Road Class will reflect the appropriate level of the road to which it is assigned. E.g.
Cross-overs joining opposing dual-carriageways of a highway are by necessity low speed and therefore a
lower class (Class = 5).
Crossing road segments reflect the lower classification of any intersecting roads …
…. Highway / Collector:
crossing road segment = 4
…. Highway / Local:
crossing road segment = 5
…. Collector / Highway / Local:
crossing road segment = 5
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
24
Cross roads and cross-overs are named using road name aliases to ensure that user systems can form logical
intersects of both carriageways with all adjoining roads.
SERVICE ROAD
HIGHWAY
PRINCES
SERVICE ROAD
HIGHWAY
Primary name = FRED STREET
1st Alias HARRY ROAD
2nd Alias = PRINCES HIGHWAY
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
25
HIGHWAY
SERVICE ROAD
HARRY ROAD
Primary name = NEW STREET
Alias name = PRINCES HIGHWAY
HIGHWAY
NEW STREET
PRINCES
FRED STREET
NEW STREET
Where two roads of differing names intersect a dual carriageway road, the primary name used for the crossing will be
that of the highest classification. The name of the lesser class road will be used for the first alias. The name of the
dual carriageway will be used as a final alias to indicate that opposing carriageways are also linked. For example:
JONES STREET
HIGHWAY
Primary name = SMITH STREET
Alias name = PRINCES HIGHWAY
PRINCES
HIGHWAY
Primary name = JONES STREET
1st Alias = MARKET LANE
2nd Alias = PRINCES HIGHWAY
MARKET LANE
PRINCES
SMITH STREET
SERVICE ROAD
HIGHWAY
Crossovers on Freeways
Individual chains will represent emergency vehicle crossovers on freeways.
Freeway Carriageways
Crossover
Emergency Access Gat e
Bike paths
Bike paths sharing roadway with vehicular traffic are inclusive features. Road classification will reflect the road they
are part of.
Bike paths existing off-road for the specific purpose of bike riding will have a road classification of 12.
Bike paths existing as shared pathways with pedestrians will have a road classification of 11.
Walking Tracks
Walking tracks existing off-road for the principal purpose of walking or hiking have a road classification of 11.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
26
Bridge and tunnel connecting feature identification system.
Longer bridges and tunnels of span greater than 50 metres are represented by chains. Tunnels and Bridges shorter
than the above spans are represented by nodes. Feature codes possible for bridge and tunnel features are bridge
(chain), bridge (node), and tunnel_road (chain), tunnel (node). A feature is a bridge when the length of the upper
feature exceeds its width. A feature is a tunnel when the width of the upper feature exceeds its length. (The direction
of traffic flow on the upper feature defines the dimension of length).
In order to allow systems to logically model traffic flow and not see bridge/tunnel nodes as any other four-way linked
intersection, it is important to identify which chains a bridge/tunnel node links. This is achieved by adding attributes to
show connecting PFI values (conpfi1 and conpfi2). In this manner, user systems can determine which road chains
join and go over (bridge) or join and go under (tunnel). This methodology has not been applied to rail bridges and
tunnels.
Typical representations include:
Tunnel greater than 50 metres length
Example - a road tunnel of greater than 50 metres length joining single line road under dual carriageway (double line)
road.
Road passing under freeway
(CONPFI1 = c, CONPFI2 = b)
PFI = c
Node = 'tunnel'
Feature 'tunnel'
PFI = b
Dual
Carriageways
Node = 'tunnel'
(CONPFI1 = a, CONPFI2 = b)
PFI = a
Chain representation of Bridge/Tunnel feature over dual carriageway
In this
example, the tunnel feature passes beneath the dual carriageways of a freeway. As it is greater than 50 metres in
length is represented by two tunnel nodes (at the points where roads intersect) and a tunnel chain representing the
roadway passing under the freeway.
Attributes conpfi1 and conpfi2 for the tunnel node features are populated with the PFI’s of their respective connecting
road and tunnel chains. That is:
NODE 1 ….
conpfi1 = PFI value ‘c’ and conpfi2 = PFI value ‘b’
NODE 2 ….
conpfi1 = PFI value ‘b’ and conpfi2 = PFI value ‘a’
Bridge less than 50 metre span
Example - single line road bridge of less than 50 metres length over a single line road.
(PFI = c)
(PFI = a)
(CONPFI1 = a, CONPFI2 = b)
Node = 'bridge'
Road1
(PFI = b)
(PFI = d)
In this example the logical intersection of the
two features is represented by a bridge
node. ‘Road1’ passes over ‘Road2’.
Consequently, attributes conpfi1 and conpfi2
for the bridge node feature are populated
with the PFI’s of the connecting ‘Road1’
chains, i.e.
conpfi1 = PFI value ‘a’ and conpfi2 = PFI
value ‘b’.
Road2
Node representation of a Bridge/Tunnel feature
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
27
Bridge greater than 50 metres span
Example - Linear Bridge - single line road over single line road.
feature 'int_attribute'
PFI = a
feature 'bridge_rd_p'
(conpfi1 = a, conpfi2 = b)
feature 'bridgel'
PFI = b
road1
feature 'int_attribute'
Chain representation of a bridge/tunnel
feature over single carriageway
road2
In this example, a bridge chain feature represents the bridge. The extent of the bridge (the span, causeway, etc.) will
be bounded by attribute nodes. The logical intersection of the upper/lower features will be the location of a bridge
node, the conpfi attributes of which will enable user systems to determine which road chains join and pass over.
Case 1: Bridge over non road feature (e.g. Watercourse, rail line etc.)
The bridge point will have a conpfi1 and conpfi2 equal to the pfi values of the two adjoining road arcs.
Case 2: Road bridge over another road
The bridge point will have four intersecting arcs. The conpfi1 and conpfi2 values will equal the pfi values of the two
road arcs that the bridge is located on.
Naming of Structures
Line Representation
Where the road arc is greater than 50 metres in length:
The feature type code shall be the structure type i.e. bridge, tunnel.
The primary road name will be populated within that arcs road name field. The structure name will be populated in the
structure name field where it is known. Structure Name sources include Geographic Names Register, Local
Government Authorities, Vicroads, DEPI Road Management as well as other road and asset managers.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
28
Road Name = Road Name
1
Feature Type = Road
Road Name = Road Name
2
Feature Type = Road
Example:
Feature Type =
Bridge
Primary Road =
Road Name1
Alias Road Name = Road Name 2
(If relevant)
Structure Name = Bridge Name
Advantages:
This approach has two advantages:
All bridge / tunnel names are named within the Transport data model.
The structure name is separated from the road name(s).
Point Representation
Where the feature is less than 50 metres in length the feature shall be depicted as a point within Tr_
road_infrastructure.
Bridge and tunnel exist as feature types. No road name fields exist within the point as these are present in the
connecting road arcs.
The name field will be populated by the structure name
TR Road
Feature Type =
Road
Road Name 1
TR Road
Feature Type = Road
Road Name = Road
Name2
TR_Road Infrastructure:
Feature Type =
Bridge
Name =
Bridge Name
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
29
Intersections
Road junctions will be represented as a single node. Multi-junction intersections may comprise a series of nodes.
Simplification will occur in the following cases.
Single Logical (or ‘bent line’) Intersections
Intersections formed on a through road by slightly offset side roads (less than ten metres apart), will be considered to
be a single logical intersection. Single logical intersections will be forced by bending the arms (within the intersection
area), to a single node. For example:
Adopted
Intersection
<10 m
Small Roundabouts
Roundabouts that can be included within a circle of 20 metres diameter are generalised to a single node.
20 metres
Small Roundabout (< 20m diameter)
Transport Representation
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
30
Substantial Roundabouts
Substantial roundabouts are those that have a nominal diameter of 20 metres or greater.
These roundabouts are constructed from road arcs representing the equivalent of their actual road centre lines on the
ground. To facilitate connectivity for network analysis, the intersection of the converging roads are represented by
‘connector’ (or pseudo) arcs joined at a ‘roundabout’ node at the approximate centroid of the roundabout.
Complex roundabouts may be generalised as per the rules for generalisation for slip lanes and forked intersections,
etc.
Feature_type = int_nosignal
traffic direction
MIDLAND HWY
Feature_type = connector
traffic direction
Feature_type = connector
Feature_type = int_nosignal
MIDLAND HWY
Feature_type = road
Feature_type = roundabout
MAIN STREET
MAIN STREET
Feature_type = int_nosignal
Feature_type = road

Where converging and diverging road arcs intersect the roundabout proper, they meet at ‘int_nosignal’ nodes.

‘Connector’ or pseudo-road arcs join these converging and diverging road arcs from the point where they
meet the roundabout proper to a ‘roundabout’ node at a nominal centre of the roundabout.

The road name/type/suffix of converging and diverging road arcs meeting the roundabout proper are
continued along the roundabout arc in a clockwise direction from the point of intersection to the next point of
intersection.

The road class of the entire outer ring of road arcs representing the roundabout is that of the highest class
road entering the roundabout.

The road class of the ‘connectors’ extending to the centre ‘roundabout’ node is that of the roads they extend
from.

The road arc vector direction of the entire outer ring arcs representing the roundabout is clockwise around the
roundabout.

The road traffic direction of the entire outer ring arcs representing the roundabout is forward (F) in a clockwise
direction.

The road name/type/suffix of the ‘connectors’ extending to the centre ‘roundabout’ node is that of the roads
they extend from.

The road arc vector direction of the ‘connectors’ extending to the centre ‘roundabout’ node is that of the road
arcs they extend from.

The road traffic direction of the ‘connectors’ extending to the centre ‘roundabout’ node is that of the roads they
extend from.

Although the ICSM Road Working Group data model 2010 http://www.icsm.gov.au/icsm/roads/index.html
recommends a 20 meter diameter this is yet to be fully adopted across the Vicmap Transport data model.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
31
Forks
Forks at Intersections
Intersections will be depicted ‘as built’ with the exception of short legs of less than 50 metres.
Short legs of less than 50 metres are to be deleted – for example:
’as-built’
Vicmap Transport
Slip Lanes
Left turn slip lanes less than 50 metres in extent will be omitted
< 50m
’as-built’
Vicmap Transport
Road ends
Logical ends of roads
Logical road endings (as reflected on the ground by cul-de-sacs, court bowls, track ends, etc.), will be
represented by a “road_end” node. For example:
ARC - road
(road)
NODE - road end
(road_end)
NODE - intersection-non signalised
(int_nosignal)
Artificial road ends
There will be occurrences where a non-real or artificial road ending has to be created, for example, at tile
edges or at State Borders. These will not be true road endings, existing on the ground. Rather, they will be
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
32
the end of the data in a particular file, the roads logically extending in the next file, on the next sheet, or
across the border into the next State. Any nodes created here will subsequently be dissolved when the
abutting data file is adjoined. At these points, a temporary node may be added. These nodes will be termed
“edge”. Pictorially, they could be represented as:
CONTRACT EDGE
Road alignment
beyond contract limit
NODE - State border/tile edge/contract edge
(edge)
Roads on Private Land
Roads on private land are valuable to emergency services to show property access to dwellings, water
bodies and assets. To delineate these from local roads default settings are being assigned. These are road
class = 6 (2wd), road seal = 2 (unsealed) and road restriction = 5 (private access). These roads are generally
UNNAMED. Cartographically it is recommended that these roads appear less prominently than local roads.
Proposed Roads
Proposed Roads created from proposed subdivisions are supplied from the Vicmap Land Administration
Themes maintainer on a weekly basis to the Vicmap Topographic Themes maintainer. These are assigned a
class code = 9 (Proposed Road) and a road seal of 3 (Unknown).
The road name provided on the proposed plan is included at the same time. If no road name is present the
road name is assigned UNNAMED.
Where the proposed road is within a common parcel or not within the road casement this road may also be
given a road restriction of 5 (private access only)
Under the Planning and Subdivisions Act 1988 subdivisions can exist as a proposal for five years.
Consequently proposed roads can also exist with this status for five years in Vicmap Transport.
Periodic investigations are undertaken to verify the existence of proposed roads within Vicmap Transport
beyond five years. These are given an appropriate road class if required, with appropriate attribution.
Redundant data verified from aerial imagery is deleted.
As Vicmap Address points are approved these are periodically compared to Vicmap Transport Roads. Where
required roads are changed from proposed to approved status.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
33
EZI Road Name and EZI Road Name Label
These fields are concatenations of Road Name / Road Type abbreviation and Road Suffix to provide a string
useful for labelling within a GIS environment or to produce map products.
These are generated to take advantage of the road attribute data and reduce the reliance upon a separate
text layer for road labelling.
EZI ROAD NAME LABEL has each word capitalized, uses VMREFTAB.ROAD_TYPE.ROAD_TYPE
ABBREVIATION and separates hyphens with a space.
EZI ROAD NAME LABEL displays the text string in both upper and lower case.
Both label fields are applied to the primary road name only.
VMREFTAB.ROAD_TYPE.ROAD_TYPE ABBREVIATION provides a definitive list of road type
abbreviations.
Suffixes OFF and ON are not included in the concatenation.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
34
Rail and Tram feature Representation
Railway, Light rail and Tramway are treated as common features. They can be separately identified by
means of their feature codes and structure types.
Generalisation of rail features
Rail features are generalised within Vicmap Transport. Up to three adjacent tracks (usually representing an
up-line, down-line and express passing line) may be represented in Vicmap Transport by a single line
feature.
Marshalling yards are generalised using a similar multiple track relationship, the intent being to indicate the
density and extent of the yards and the direction and layout of sidings and crossings.
Relationship of rail features with roads
Tram, train and light rail lines are tagged as being on-road, off-road or underground as appropriate. Tracks
will be identified as being ‘on road’ where they run coincident with road carriageways. Within Vicmap
Transport, these lineal features will be coincident with corresponding road line features. Where tracks run in
their own reserve separate to a road, even where the reserve acts as a median strip to dual carriageway
roads, the rail features will be tagged as ‘off road’. Below ground rail lines are tagged as ‘underground’.
Ferry feature Representation
Vehicular ferry routes only included where facilities exist for the transportation of road vehicles over water.
Ferry routes are shown as lineal features, approximating the shortest likely route between nominated landing
points. Passenger only ferries and formal shipping channels/routes are not defined in Vicmap Transport.
Air feature Representation
Vicmap Transport includes the ground location of air infrastructure. It does not include air routes.
AIRPORT_AREA
Civil Aviation Safety Authority (CASA) registered and certified airports are depicted within Vicmap Transport
(Air) as both airport_area and air infrastructure polygons. All airports are named.
The International Civil Aviation Organisation Code has been populated for airports in Vicmap Transport. E.g.
YMCO Mallacoota
Sealed runways at larger airports are also captured as polygons.
Hierarchy
To assist with mapping / categorisation a hierarchy has been adopted for airports. Vicmap Lite also uses
hierarchy 1 to 3 below to depict airports as points.
The hierarchy is as follows:
1. CASA airport certified with CASA id and ICOA code
2. CASA airport registered with CASA id and ICOA code
3. Other CASA airport with ICAO code
4. Non CASA airport.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
35
CASA classifications are taken from the CASA website http://casa.gov.au/aerodromes
There is no identified need to add hierarchy to TR_AIR_INFRA_AREA_POLYGON which show the actual
airstrips as the CASA information will be held in the parent TR_AIRPORT_AREA_POLYGON.
The attributes

AUTH_ORGANISATION_CODEVARCHAR2(4)

AUTH_ORGANISATION_ID VARCHAR2(30)
hold CASA as the authoritative organization and the CASA certification/registration number as the
authoritative organization identifier.
AIR_INFRASTRUCTURE_ AREA_POLYGON
Airstrips both sealed and unsealed, within an airport or not are depicted as a polygon within
Air_Infrastructure_Area_Polygon. Where possible these airstrips are named from authoritative sources.
AIR INFRASTRUCTURE LINE
This depicts the airfield centreline and includes all airstrips depicted within Air Infrastructure Area. These also
include airstrips sourced from New South Wales Land and Property Management Authority (NSW LPMA)
and reflect the source data. I.e. the NSW data is supplied as centreline linework only.
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
36
Reference tables
Vicmap Transport should be used in conjunction with the following reference tables to fully utilise the information it
contains. These reference tables are available in the Vicmap Reftab product and are listed below:
VMREFTAB. FEATURE_TYPE_TOPO
VMREFTAB. FT_AUTHORITATIVE_ORGANISATION
VMREFTAB.LOCALITY
VMREFTAB.ROAD_SUFFIX
VMREFTAB.ROAD_TYPE
VMREFTAB. TP_FEATURE_QUALITY
VMREFTAB.TR_AIRPORT_HIERACHY
VMREFTAB.TR_BRIDGE_CONSTRUCTION_TYPE
VMREFTAB.TR_BRIDGE_PHYSICAL_CONDITION
VMREFTAB.TR_DIVIDED_ROAD
VMREFTAB.TR_FERRY_TYPE
VMREFTAB.TR_RAIL_GAUGE
VMREFTAB.TR_RAIL_PHYSICAL_CONDITION
VMREFTAB.TR_RAIL_ROAD_RELATIONSHIP
VMREFTAB.TR_RAIL_STATION_STRUCTURE_TYPE
VMREFTAB.TR_RAIL_ STRUCTURE_TYPE
VMREFTAB.TR_RAIL_TOURIST_TYPE
VMREFTAB.TR_ROAD_CLASS
VMREFTAB.TR_ROAD_DIRECTION
VMREFTAB.TR_ROAD_RESTRICTION
VMREFTAB.TR_ROAD_SEAL
VMREFTAB.TR_ROAD_STRUCTURE_TYPE
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
37
VMREFTAB. FEATURE_TYPE_TOPO
FEAT
SUBT
YP
UFI
PFI
FTYPE
10107692
10107693
10107694
10107695
10107696
10107697
10107698
10107703
10107704
10107707
10107709
10107711
10107712
10107713
10107714
10107715
10107716
10107717
10107718
10107719
10107720
10107721
10107722
10107724
10107725
10107726
10107731
10107732
10107733
10107734
10107735
10107736
10107737
10107740
10107741
10107742
10107743
10107744
10107745
10107746
10107747
10107748
10107749
10107752
10107753
10107754
10107755
1215
1217
1218
1219
1220
1221
1222
1232
1233
1236
1238
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1253
1255
1256
1262
1263
1264
1265
1266
1267
1268
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1283
1284
1285
1286
airport
barrier
beach
beacon
breakwater
bridge
bua
causeway
cave
cliff
coast
connector_structure
contour
contour_approx
contour_dep
contour_dep_approx
contour_dep_index
contour_index
cutting_both
cutting_one
dam_batter
dam_wall
dam_wall_road
dse_region
embankment_both
embankment_one
fence
ferry_route
flat_sti
foot_bridge
ford
forest
gate
helipad
int_attribute
int_coast
int_locality
int_nosignal
int_signal
island
island_marine
island_terrestrial
junction
launching_ramp
levee
level_crossing
lga
FEATSTAT
US
VMADDPFILK
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
38
D
E
S
C
PFI_CR
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
UFI_CR
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
UFI
PFI
UFI
10107758
10107759
10107760
10107761
10107762
10107763
10107764
10107767
PFI
1289
1290
1291
1292
1293
1294
1295
1298
10107768
10107769
10107773
10107774
10107777
10107778
10107779
10107780
10107781
10107782
10107783
10107786
10107787
10107788
10107789
10107790
10107791
10107792
10107793
10107794
10107796
10107797
10107798
10107799
10107800
10107801
10107802
10107803
10107804
10107805
10107807
10107808
10107809
10107810
10107811
10107812
10107814
1299
1300
1304
1305
1308
1309
1310
1311
1312
1313
1314
1317
1318
1319
1320
1321
1322
1323
1325
1326
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1339
1340
1341
1342
1343
1344
1346
FTYPE
FTYPE
locality
lock
lookout
mainland
mapsheet
marine_place
marshalling_yard_rail
mountain
named_natural_regio
n
observatory
pass
peninsula
pipe_water_uground
plateau
pondage
pondage_saltpan
pondage_sewerage
postcode
public_land
rail_dismantled
rail_disused
rail_light
rail_siding
rail_station
rail_tourist
rail_trail
railway
rapid
reef
research_station
ridge
road
road_end
rock_bare
rock_outcrop
rock_terrestrial
roundabout
route_marker_nat
runway
sand
sand_dune
scrub
sea
shoreline
sign_post
FEAT
SUBT
YP
FEATSTAT
US
FEAT
SUBT
YP
FEATSTAT
US
VMADDPFILK
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
VMADDPFILK
N
N
N
N
N
N
N
N
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
39
D
E
S
C
D
E
S
C
PFI_CR
UFI_CR
PFI_CR
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
UFI_CR
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
UFI
PFI
FTYPE
10107816
10107817
10107821
10107822
1348
1349
1353
1354
sinkhole
spillway
spot_height
spring
UFI
10107823
10107826
10107827
10107828
10107830
10107831
10107833
10107834
10107836
10107839
10107840
10107841
10107842
10107843
10107844
PFI
1355
1358
1359
1360
1362
1363
1366
1367
1369
1373
1374
1375
1376
1377
1378
10107845
10107846
10107847
10107848
10107849
10107850
10107851
10107852
10107853
10107856
10107857
10107858
10107860
10107861
10107862
10107863
10107864
10107865
10107866
10107867
10107868
10107869
10107870
10107871
10107872
10107873
1379
1380
1381
1382
1383
1384
1385
1386
1387
1390
1391
1392
1394
1395
1396
1439
1440
1498
1490
1491
1493
1494
1495
1496
1497
1499
FEAT
SUBT
YP
FTYPE
state_border
survey_beacon
tank
tank_water
timber
timber_scattered
tram_dismantled
tramway
tunnel
valley
vegetation
vicgov_region
vicmap_boundary
watercourse_area
watercourse_channel
watercourse_channel
_drain
watercourse_drain
watercourse_river
watercourse_stream
waterfall
watering_place
wb_dam
wb_lake
wb_lake_salt
well
well_water
wetland_swamp
windbreak
windpump
wreck
bay
brickyard
bridge_rail_du
wharf
tunnel_rail_o
buoy
marina
pipe_water
rail_uground_o
bridge_rail_dm
bridge_rail_o
FEAT
SUBT
YP
FEATSTAT
US
VMADDPFILK
ACTIVE
ACTIVE
ACTIVE
ACTIVE
N
N
N
N
FEATSTAT
US
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
VMADDPFILK
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
40
D
E
S
C
PFI_CR
12/01/2010
12/01/2010
12/01/2010
12/01/2010
D
E
S
C
PFI_CR
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
12/01/2010
15/11/2011
21/01/2011
30/08/2011
30/08/2011
30/08/2011
21/10/2011
21/10/2011
15/11/2011
15/11/2011
UFI_CR
1/02/2012
1/02/2012
1/02/2012
1/02/2012
UFI_CR
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
1/02/2012
FEAT
SUBT
YP
UFI
PFI
FTYPE
10110849
1516
10110850
10110851
10110852
10110854
10110857
1517
1518
1519
1520
1521
connector_channel
connector_channel_
drain
connector_drain
connector_stream
connector_river
connector
D
E
S
C
FEATSTAT
US
VMADDPFILK
ACTIVE
N
1/02/2011
14/02/2012
ACTIVE
ACTIVE
ACTIVE
ACTIVE
ACTIVE
N
N
N
N
N
1/02/2011
1/02/2011
1/02/2011
1/02/2011
1/01/2000
14/02/2012
14/02/2012
14/02/2012
14/02/2012
14/02/2012
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
41
PFI_CR
UFI_CR
UFI
PFI
10127689
1522
10127690
1523
10127691
1524
10127693
1525
FEAT
SUBT
YP
FTYPE
watercourse_area_c
hannel_drain
watercourse_area_ri
ver
watercourse_area_dr
ain
watercourse_area_c
hannel
FEATSTAT
US
INACTIV
E
INACTIV
E
INACTIV
E
INACTIV
E
VMADDPFILK
D
E
S
C
PFI_CR
UFI_CR
N
1/05/2012
28/05/2012
N
1/05/2012
28/05/2012
N
1/05/2012
28/05/2012
N
1/05/2012
28/05/2012
VMREFTAB. FT_AUTHORITATIVE_ORGANISATION
AUTHORGC AUTH_ORG
AUTHORGNAM
Department of Sustainability and
Environment - Spatial information
100
DSE-SII
Infrastructure
Department of Education and
101
DEECD
Early Childhood Development
103
AMBULANCE VIC
Ambulance Victoria
105
MFB
Metropolitan Fire Brigade
106
CFA
Country Fire Authority
107
VICPOL
Victorian Police
108
DOJ
Department of Justice
Department of Justice Emergency Services Policy and
109
DOJ-ESP&S
Support
115
SPAUSNET
SP Ausnet
110
NSW
New South Wales
111
SA
South Australia
112
CASA
Civil Aviation Safety Authority
300
ALPINE
Alpine Shire
301
ARARAT
Ararat Rural City
302
BALLARAT
Ballarat City
303
BANYULE
Banyule City
304
BASS COAST
Bass Coast Shire
305
BAW BAW
Baw Baw Shire
306
BAYSIDE
Bayside City
307
BOROONDARA
Boroondara City
308
BRIMBANK
Brimbank City
309
BULOKE
Buloke Shire
310
CAMPASPE
Campaspe Shire
311
CARDINIA
Cardinia Shire
312
CASEY
Casey City
AUTHORGC
AUTH_ORG
100
DSE-SII
101
103
105
106
107
108
DEECD
AMBULANCE VIC
MFB
CFA
VICPOL
DOJ
109
115
110
111
112
300
301
302
303
304
305
306
307
308
309
310
311
312
DOJ-ESP&S
SPAUSNET
NSW
SA
CASA
ALPINE
ARARAT
BALLARAT
BANYULE
BASS COAST
BAW BAW
BAYSIDE
BOROONDARA
BRIMBANK
BULOKE
CAMPASPE
CARDINIA
CASEY
CENTRAL
GOLDFIELDS
COLAC OTWAY
CORANGAMITE
DAREBIN
EAST GIPPSLAND
FRANKSTON
GANNAWARRA
GLEN EIRA
GLENELG
GOLDEN PLAINS
GREATER
BENDIGO
313
314
315
316
319
320
321
322
323
324
CENTRAL GOLDFIELDS
COLAC OTWAY
CORANGAMITE
DAREBIN
EAST GIPPSLAND
FRANKSTON
GANNAWARRA
GLEN EIRA
GLENELG
GOLDEN PLAINS
Central Goldfields Shire
Colac Otway Shire
Corangamite Shire
Darebin City
East Gippsland Shire
Frankston City
Gannawarra Shire
Glen Eira City
Glenelg Shire
Golden Plains Shire
313
314
315
316
319
320
321
322
323
324
325
GREATER BENDIGO
Greater Bendigo City
325
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
42
AUTHORGC
AUTHORGC
AUTH_ORG
AUTH_ORG
AUTHORGNAM
AUTHORGNAM
AUTHORGC
AUTHORGC
326
GREATER DANDENONG
Greater Dandenong City
326
327
GREATER GEELONG
GREATER
SHEPPARTON
HEPBURN
HINDMARSH
HOBSONS BAY
HORSHAM
HUME
INDIGO
KINGSTON
KNOX
LATROBE
LODDON
Greater Geelong City
327
Greater Shepparton City
Hepburn Shire
Hindmarsh Shire
Hobsons Bay City
Horsham Rural City
Hume City
Indigo Shire
Kingston City
Knox City
Latrobe City
Loddon Shire
328
329
330
331
332
333
334
335
336
337
338
MACEDON RANGES
MANNINGHAM
MARIBYRNONG
MAROONDAH
MELBOURNE
MELTON
MILDURA
MITCHELL
MOIRA
MONASH
MOONEE VALLEY
MOORABOOL
MORELAND
MORNINGTON
PENINSULA
Macedon Ranges Shire
Manningham City
Maribyrnong City
Maroondah City
Melbourne City
Melton Shire
Mildura Rural City
Mitchell Shire
Moira Shire
Monash City
Moonee Valley City
Moorabool Shire
Moreland City
339
340
341
342
343
344
345
346
347
348
349
350
351
Mornington Peninsula Shire
352
MOUNT ALEXANDER
MOYNE
MURRINDINDI
NILLUMBIK
NORTHERN
GRAMPIANS
PORT PHILLIP
PYRENEES
QUEENSCLIFFE
Mount Alexander Shire
Moyne Shire
Murrindindi Shire
Nillumbik Shire
353
354
355
356
Northern Grampians Shire
Port Phillip City
Pyrenees Shire
Queenscliffe Borough
357
358
359
360
SOUTH GIPPSLAND
SOUTHERN
GRAMPIANS
STONNINGTON
STRATHBOGIE
SURF COAST
SWAN HILL
TOWONG
WANGARATTA
WARRNAMBOOL
WELLINGTON
WEST WIMMERA
WHITEHORSE
WHITTLESEA
WODONGA
WYNDHAM
South Gippsland Shire
361
Southern Grampians Shire
Stonnington City
Strathbogie Shire
Surf Coast Shire
Swan Hill Rural City
Towong Shire
Wangaratta Rural City
Warrnambool City
Wellington Shire
West Wimmera Shire
Whitehorse City
Whittlesea City
Wodonga City
Wyndham City
362
363
364
365
366
367
368
369
370
371
372
373
374
375
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
43
AUTH_ORG
AUTH_ORG
GREATER
DANDENONG
GREATER
GEELONG
GREATER
SHEPPARTON
HEPBURN
HINDMARSH
HOBSONS BAY
HORSHAM
HUME
INDIGO
KINGSTON
KNOX
LATROBE
LODDON
MACEDON
RANGES
MANNINGHAM
MARIBYRNONG
MAROONDAH
MELBOURNE
MELTON
MILDURA
MITCHELL
MOIRA
MONASH
MOONEE VALLEY
MOORABOOL
MORELAND
MORNINGTON
PENINSULA
MOUNT
ALEXANDER
MOYNE
MURRINDINDI
NILLUMBIK
NORTHERN
GRAMPIANS
PORT PHILLIP
PYRENEES
QUEENSCLIFFE
SOUTH
GIPPSLAND
SOUTHERN
GRAMPIANS
STONNINGTON
STRATHBOGIE
SURF COAST
SWAN HILL
TOWONG
WANGARATTA
WARRNAMBOOL
WELLINGTON
WEST WIMMERA
WHITEHORSE
WHITTLESEA
WODONGA
WYNDHAM
AUTHORGC
376
377
AUTHORGC
378
AUTHORGNAM
Yarra City
Yarra Ranges Shire
AUTHORGNAM
Yarriambiack Shire
AUTHORGC
376
377
AUTHORGC
378
379
AUTH_ORG
YARRA
YARRA RANGES
AUTH_ORG
YARRIAMBIACK
FRENCH ISLAND
(UNINC)
French Island (Unincorporated)
379
380
381
382
UNINCORPORATED
BENALLA
MANSFIELD
Unincorporated
Benalla Rural City
Mansfield Shire
380
381
382
383
MOUNT BAW BAW
ALPINE RESORT (U
Mount Baw Baw Alpine Resort
(Unincorporated)
383
384
MOUNT BULLER ALPINE
RESORT (UN
Mount Buller Alpine Resort
(Unincorporated)
384
385
LAKE MOUNTAIN
ALPINE RESORT (U
Lake Mountain Alpine Resort
(Unincorporated)
385
FALLS CREEK ALPINE
RESORT (UNI
MOUNT STIRLING
ALPINE RESORT (
Falls Creek Alpine Resort
(Unincorporated)
Mount Stirling Alpine Resort
(Unincorporated)
Mount Hotham Alpine Resort
(Unincorporated)
Unknown
388
999
389
317
318
MOUNT HOTHAM
ALPINE RESORT (UN
UNKNOWN
ALPINE RESORTS
(UNINC)
DELATITE
DOCKLANDS
Alpine Resorts (Unincorporated)
Delatite Shire
Docklands
389
317
318
998
113
114
PORT OF MELBOURNE
(PLANNING ON
CEO
IndependantDEECD
Port Of Melbourne (Planning
Only)
Catholic Education Office
Independant Schools DEECD
998
113
114
116
AUSTRALIAN CAMPS
ASSOCIATION
Australian Camps Association
116
Scouts Australia
117
Girl Guides Australia
Athletics Victoria
Life Saving Victoria
Alpine Resorts Commission
Department of Sustainability and
Environment - Fire Management
Australian Pipeline Trust Group
State Emergency Service
Emergency Services
Telecommunication Authority
Baseball Victoria
Confederation of Australian Motor
Sport
Croquet Victoria
CycleSport Victoria
Football Federation Victoria
Motorcycling Victoria
Royal Victorian Bowls Association
118
125
119
120
AUTH_ORG
YARRA
YARRA RANGES
AUTH_ORG
YARRIAMBIACK
FRENCH ISLAND
(UNINC)
UNINCORPORATE
D
BENALLA
MANSFIELD
MOUNT BAW BAW
ALPINE RESORT
(U
MOUNT BULLER
ALPINE RESORT
(UN
LAKE MOUNTAIN
ALPINE RESORT
(U
FALLS CREEK
ALPINE RESORT
(UNI
MOUNT STIRLING
ALPINE RESORT (
MOUNT HOTHAM
ALPINE RESORT
(UN
UNKNOWN
ALPINE RESORTS
(UNINC)
DELATITE
DOCKLANDS
PORT OF
MELBOURNE
(PLANNING ON
CEO
IndependantDEECD
AUSTRALIAN
CAMPS
ASSOCIATION
SCOUTS
AUSTRALIA
GIRL GUIDES
AUSTRALIA
ATHLETICS VIC
LSV
ARC
121
122
123
DSE-FIRE
APA
SES
124
126
ESTA
BV
127
128
129
130
131
132
CAMS
CV
CSV
FFV
MV
RVBA
386
387
388
999
117
118
125
119
120
SCOUTS AUSTRALIA
GIRL GUIDES
AUSTRALIA
ATHLETICS VIC
LSV
ARC
121
122
123
DSE-FIRE
APA
SES
124
126
ESTA
BV
127
128
129
130
131
132
CAMS
CV
CSV
FFV
MV
RVBA
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
44
386
387
AUTHORGC
133
AUTH_ORG
VRA
AUTHORGNAM
Victorian Rifle Association
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
45
AUTHORGC
133
AUTH_ORG
VRA
AUTHORGC
AUTH_ORG
AUTHORGNAM
Department of Planning and
Community Development - Local
Government Victoria
Tourism Victoria
Hockey Victoria
Victorian Caravan Parks
Association
To Be Confirmed
AUTHORGC
AUTH_ORG
134
135
136
DPCD-LGV
TV
HV
134
135
136
DPCD-LGV
TV
HV
137
200
VCPA
TBC
137
200
Midway Afforestation
Department of Health and Aging
Central Highlands Water
148
102
140
141
142
143
144
MIDWAY-AFFOREST
DHA
CHW
DEMETER FARMING
AUS
FORESTRYSA
GPFL
GTFP
Demeter Farming Aus
ForestrySA
GPFL
Green Triangle Forest Products
141
142
143
144
145
HVP PLANTATIONS
HVP Plantations
145
146
104
139
149
162
151
152
153
ELDERS FORESTRY
DHS
PFO
PTG
NFAM
S.E.F.E
AUSTGUM
WF
146
104
139
149
162
151
152
153
154
158
159
157
155
156
160
138
150
161
147
163
164
MFPM
ABG
SPL
SERIC
GRP
APP
CALCO
AKD
MIDWAY
SMF
MCEWAN
DOHA
TP
Elders Forestry
Department of Human Services
PF Olsen Australia
Plantation Timbers Group
New Forest Asset Management
S.E.F.E
AUSTGUM
Willmott Forest
Macquarie Financial Products
Management
Australian Blue Gum
Southern Plantation Forest
SERIC
GRP
APP
CALC Trusses and Timber
AKD Softwoods
Midway Limited
Snowy Mountain Forests
McEWAN
Department of Health and Ageing
Timberlands Pacific
VCPA
TBC
MIDWAYAFFOREST
DHA
CHW
DEMETER
FARMING AUS
FORESTRYSA
GPFL
GTFP
HVP
PLANTATIONS
ELDERS
FORESTRY
DHS
PFO
PTG
NFAM
S.E.F.E
AUSTGUM
WF
148
102
140
154
158
159
157
155
156
160
138
150
161
147
163
164
MFPM
ABG
SPL
SERIC
GRP
APP
CALCO
AKD
MIDWAY
SMF
MCEWAN
DOHA
TP
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
46
VMREFTAB.LOCALITY (sample only – there are over 2500 localities in total)
LOCUNIQUE
ABBEYARD
ABBOTSFORD
ABERFELDIE
ABERFELDY
ACHERON
ADA
LOCALITY
VICNAMESID
ABBEYARD
ABBOTSFORD
ABERFELDIE
ABERFELDY
ACHERON
ADA
UFI
100117
100118
100119
100120
100121
100122
10026296
10026297
10026298
10026299
10026300
10026301
UFI_CR
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
VMREFTAB.ROAD_SUFFIX
RD_SUF
N
S
E
W
LR
UP
NE
NW
SE
SW
CN
EX
ML
OT
IN
OF
ON
A
B
C
DV
BR
LONGNAME
North
South
East
West
Lower
Upper
North East
North West
South East
South West
Central
Extension
Mall
Outer
Inner
Off
On
A
B
C
Deviation
Branch
UFI
UFI_CR
10012581
10012582
10012583
10012584
10012585
10012586
10012587
10012588
10012589
10012590
10012591
10012592
10012593
10012594
10012595
10012596
10012597
10012598
10012599
10012600
10014961
10015101
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
47
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
28/02/2008
27/05/2008
18/07/2008
VMREFTAB.ROAD_TYPE
ROAD_TYPE
ALLEY
ARCADE
AVENUE
BAY
BEND
BOULEVARD
BOWL
BRAE
BREAK
BYPASS
CHASE
CIRCLE
CIRCUIT
CLOSE
CONCOURSE
COURSE
COURT
COVE
CRESCENT
CREST
CROSS
DALE
DELL
DIVIDE
DRIVE
EDGE
ESPLANADE
FIRELINE
DASH
FORD
FREEWAY
GARDENS
GATE
GATEWAY
GLADE
GLEN
GRANGE
GREEN
GROVE
HEATH
HEIGHTS
HIGHWAY
HILL
HUB
JUNCTION
LANE
LINK
MALL
MEWS
NOOK
OUTLOOK
PARADE
PARKWAY
PASS
PATH
PLACE
PLAZA
RDTYPEABB
ALLY
ARC
AV
BAY
BEND
BVD
BOWL
BRAE
BRK
BYPA
CH
CIR
CCT
CL
CON
CRSE
CT
COVE
CR
CRST
CRSS
DALE
DELL
DIV
DR
EDGE
ESP
FLNE
DASH
FORD
FWY
GDNS
GTE
GTWY
GLDE
GLEN
GRA
GRN
GR
HTH
HTS
HWY
HILL
HUB
JNC
LANE
LINK
MALL
MEWS
NOOK
OTLK
PDE
PWY
PASS
PATH
PL
PLZA
GNR_APPROV
Y
Y
Y
N
N
Y
N
N
Y
Y
Y
N
Y
Y
Y
N
Y
N
Y
Y
N
N
N
N
Y
N
Y
N
N
N
Y
N
N
N
Y
N
Y
N
Y
N
N
Y
N
N
N
Y
N
Y
Y
N
N
Y
Y
N
Y
Y
Y
UFI
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
48
UFI_CR
10151321
10151360
10151334
10151378
10151379
10151335
10151380
10151381
10151336
10151337
10151322
10151382
10151338
10151315
10151339
10151383
10151316
10151384
10151340
10151323
10151385
10151386
10151387
10151388
10151341
10151389
10151343
10151390
10151391
10151392
10151345
10151393
10151394
10151395
10151324
10151396
10151346
10151397
10151325
10151398
10151399
10151347
10151400
10151401
10151402
10151326
10151403
10151362
10151368
10151404
10151405
10151375
10151374
10151406
10151363
10151318
10151319
3/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
3/10/2012
ROAD_TYPE
RDTYPEABB
GNR_APPROV
UFI
ROAD_TYPE
POCKET
POINT
PURSUIT
QUADRANT
QUAY
REACH
RETREAT
RETURN
RIDE
RIDGE
RISE
RISING
ROUND
ROW
RUN
SLOPE
SQUARE
STREET
STRIP
TERRACE
THROUGHWAY
TRACK
TRAIL
TURN
VALLEY
VIEW
VIEWS
VISTA
WALK
WATERS
WAY
WOODS
ACCESS
AMBLE
COMMON
CONNECTION
CUTTING
GULLY
HOLLOW
ISLAND
REST
APPROACH
BOARDWALK
BRIDGE
CENTRE
CENTREWAY
CIRCUS
CLUSTER
CORNER
CROSSING
DEVIATION
CRUISEWAY
DIP
ELBOW
END
ENTRANCE
EXTENSION
FAIRWAY
RDTYPEABB
PKT
PNT
PRST
QDRT
QY
RCH
RTT
RTN
RIDE
RDGE
RISE
RSNG
RND
ROW
RUN
SLPE
SQ
ST
STRP
TCE
THRU
TRK
TRL
TURN
VLLY
VIEW
VEWS
VSTA
WALK
WTRS
WAY
WDS
ACCS
AMBL
CMMN
CNTN
CUTT
GLY
HLLW
ISLD
REST
APP
BWLK
BDGE
CTR
CNWY
CRCS
CLR
CNR
CRSG
DEVN
CUWY
DIP
ELB
END
ENT
EXTN
FAWY
GNR_APPROV
N
N
N
N
N
N
Y
N
N
Y
Y
N
N
N
N
N
Y
Y
N
Y
N
Y
Y
N
N
Y
N
Y
Y
N
Y
N
N
N
N
N
N
N
N
N
N
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
UFI
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
49
UFI_CR
UFI_CR
10151407
10151408
10151410
10151411
10151412
10151413
10151320
10151414
10151415
10151353
10151327
10151416
10151417
10151418
10151419
10151420
10151328
10151354
10151421
10151329
10151422
10151356
10151357
10151423
10151424
10151330
10151425
10151331
10151371
10151426
10151359
10151427
10151428
10151429
10151430
10151431
10151432
10151433
10151434
10151435
10151436
10151333
10151361
10151437
10151439
10151440
10151441
10151442
10151443
10151444
10151445
10151446
10151447
10151448
10151449
10151342
10151450
10151451
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
ROAD_TYPE
INTERSECTION
KEY
RDTYPEABB
INTN
KEY
GNR_APPROV
Y
N
UFI
ROAD_TYPE
LANDING
LANEWAY
LINE
LOOP
PATHWAY
PASSAGE
PARK
QUAYS
RAMP
RESERVE
ROUTE
ROAD
SUBWAY
STEPS
WYND
SPUR
WOOD
WHARF
WALKWAY
VALE
UNDERPASS
TUNNEL
TOP
TOLLWAY
DOMAIN
DENE
BOULEVARDE
KEYS
OUTLET
FORK
MANOR
FIRETRAIL
CROOK
FIREBREAK
FLATS
TWIST
TRAVERSE
ARTERIAL
MAZE
CAUSEWAY
PROMENADE
RDTYPEABB
LDG
LNWY
LINE
LOOP
PWAY
PSGE
PARK
QYS
RAMP
RES
RTE
RD
SBWY
STPS
WYND
SPUR
WD
WHRF
WKWY
VALE
UPAS
TUNL
TOP
TLWY
DOM
DENE
BVDE
KEYS
OTLT
FORK
MAN
FTRL
CRK
FBRK
FLTS
TWST
TVRS
ARTL
MAZE
CSWY
PROM
GNR_APPROV
N
N
N
Y
N
Y
N
Y
Y
N
N
Y
Y
Y
N
N
N
Y
N
N
Y
N
N
Y
N
N
N
N
N
N
N
Y
N
N
N
N
N
N
N
Y
Y
UFI
UFI_CR
10151349
10151452
UFI_CR
10151453
10151454
10151455
10151369
10151456
10151364
10151457
10151351
10151352
10151458
10151459
10151370
10151366
10151365
10151460
10151461
10151462
10151332
10151463
10151464
10151358
10151465
10151466
10151355
10151467
10151468
10151469
10151470
10151471
10151472
10151473
10151344
10151474
10151475
10151476
10151477
10151478
10151479
10151480
10151376
10151377
VMREFTAB. TP_FEATURE_QUALITY
FEATRELDT
ATTRELDT
SCALE
DATAS
RCC
UFI
ID
11323704
1
1/07/1994
1/07/1994 9999999
999
11323705
2
1/07/1994
1/07/1994 40
1
11323706
3
1/07/1994
1/07/1994 40
1
11323707
4
1/07/1994
1/07/1994 40
1
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
50
3/10/2012
4/10/2012
DESC
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
4/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
3/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
3/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
4/10/2012
VMREFTAB.TR_AIRPORT_HIERACHY
CODE
1
2
HIER_FNAME
CASA
CERTIFIED
CASA
REGISTERED
Description
Regular Public Transport (RPT) operation or frequent charter
with more than 30 passengers certified by CASA
Same physical standards as certified aerodrome registered
by an approved person and recognised by CASA
Not certified or registered but served by Regular Public
Transport (RPT) operation or by charter operations at least
once per week and recognised by CASA
Not recognised by CASA
3
CASA OTHER
4
NON-CASA
VMREFTAB.TR_BRIDGE_CONSTRUCTION_TYPE
CONSTNTYPC
1
2
3
4
5
6
7
8
9
10
11
CONST_TYPE
BICYCLE
BRIDGE
COVERED
BRIDGE
DRAW BRIDGE
FOOT BRIDGE
LIFT BRIDGE
OVERPASS
PONTOON
BRIDGE
SUSPENSION
BRIDGE
SWING BRIDGE
VIADUCT
CONVENTIONAL
BRIDGE
DESC
Bicycle Bridge
Covered Bridge
Draw Bridge
Foot Bridge
Lift Bridge
Overpass
Pontoon Bridge
Suspension Bridge
Swing Bridge
Viaduct
Conventional Bridge
VMREFTAB.TR_BRIDGE_PHYSICAL_CONDITION
PHYSCONDC
DESC
1
2
Operational
Closed
VMREFTAB.TR_DIVIDED_ROAD
DIVRDCODE
DS
ND
U
DD
DIV_RD
Divided
Single
Not Divided
Unknown
Divided
Double
DESC
Divided Single Centreline Representation
Not Divided
Unknown
Divided Double Line (one line per carriageway) Representation
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
51
VMREFTAB.TR_RAIL_GAUGE
RAILGAUGEC
RAIL_GAUGE
DESC
1
2
3
4
5
STANDARD
BROAD
BOTH
VRNARROW
NARROW
4ft 8.5in Gauge
5ft 4in Gauge
Both 4ft 8.5 in and 5ft 4in Gauge
2ft 6in Victorian Railways Narrow Gauge
3ft 6in Narrow Gauge
VMREFTAB.TR_RAIL_PHYSICAL_CONDITION
PHYSCONDC
PHYS_COND
DESC
1
2
3
DISMANTLED
DISUSED
OPERATIONAL
Dismantled
Disused
Operational
VMREFTAB.TR_RAIL_ROAD_RELATIONSHIP
RDRELC
RDREL
DESC
1
2
3
ON ROAD
OFF ROAD
UNDERGROUND
On Road
Off Road
Underground
VMREFTAB.TR_RAIL_STATION_STRUCTURE_TYPE
STR_TYPEC
1
2
3
STRUC_TYPE
RAILWAY
STATION
LIGHT RAIL
STOP
TRAM STOP
ISDEPREC
DESC
No
Railway Station
No
No
Light Rail Stop
Tram Stop
VMREFTAB.TR_RAIL_ STRUCTURE_TYPE
STR_TYPEC
STRUC_TYPE
DESC
1
2
3
4
5
6
LIGHT RAIL
TRAMWAY
MONO RAIL
NORMAL RAIL
HEAVY RAIL
UNDERGROUND
Light Rail
Tramway
Mono Rail
Normal Rail
Heavy Rail
Underground
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
52
VMREFTAB.TR_RAIL_TOURIST_TYPE
TOURIST_T
YPE_CODE
TOURIST_TYPE
DESC
Y
N
YES
NO
VMREFTAB.TR_ROAD_CLASS
RDCLASSC
ROAD_CLASS
DESC
0
1
2
3
4
5
6
7
9
FREEWAY
HIGHWAY
ARTERIAL
SUB-ARTERIAL
COLLECTOR
LOCAL
2WD
4WD
PROPOSED
WALKING
TRACK
BICYCLE
TRACK
FERRY ROUTE
Freeway
Highway
Arterial
Sub-Arterial
Collector
Local
2wd
4wd
Proposed
11
12
14
Walking Track
Bicycle Track
Ferry route
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
53
VMREFTAB.TR_ROAD_DIRECTION
DIR_CODE
DIRECTION
F
FORWARD
R
B
REVERSE
BOTH
DESC
Forward Direction of traffic with respect to digitized direction of
feature
Reverse Direction of traffic with respect to digitized direction of
feature
Traffic possible in both directions
VMREFTAB.TR_ROAD_RESTRICTION
RDRESTC
1
2
3
4
5
6
7
RDREST
MAINTENANCE
VEHICLES
SEASONAL
CLOSURE
HT OR WT LIMIT
PERMANENTLY
CLOSED
PRIVATE
UNMAINTAINED
DWO
DESC
Maintenance Vehicles Only
Subject To Seasonal Closure
Subject To Height Or Weight Limits
Road Permanently Closed
Private Access
Road Unmaintained
Dry weather only
VMREFTAB.TR_ROAD_SEAL
RDSEALC
ROAD_SEAL
DESC
1
2
3
SEALED
UNSEALED
UNKNOWN
Road Sealed
Road Unsealed
Unknown
VMREFTAB.TR_ROAD_STRUCTURE_TYPE
STR_TYPEC
STRUC_TYPE
DESC
1
2
3
BOOM GATE
BUSH GATE
CATTLE GRID
CROSSING
GATE
SLIP RAIL
TOLL BARRIER
TURNSTILE
GATE
Boom Gate
Bush Gate
Cattle Grid
4
5
6
7
8
Crossing Gate
Slip Rail
Toll Barrier
Turnstile
Gate
Vicmap Transport - Technical Specifications Version 1.0
Department of Environment and Primary Industries
54
Download