PRODUCT DESCRIPTION
[TRANSPORT
Version 3.2
Information Services Branch
PRODUCT DESCRIPTION
Vicmap Transport
Information Services Branch
Department of Sustainability and Environment
Document version 3.2 - July 2012
Applies to delivered data model version 3.1
Vicmap Transport Prod Desc V3_2 for PDF.doc
ii
PRODUCT DESCRIPTION
[TRANSPORT
Version 3.2
Information Services Branch
TABLE OF CONTENTS
1.
PRODUCT DESCRIPTION ............................................................................................................... 5
CUSTODIAN ...............................................................................................................................................................5
JURISDICTION ............................................................................................................................................................5
CONTACT INFORMATION ...........................................................................................................................................5
DESCRIPTION .............................................................................................................................................................6
PRODUCTION AND/OR ACQUISITION METHODS...........................................................................................................9
SOURCE OF INPUT INFORMATION .............................................................................................................................10
GENERALISATIONS WITHIN THE DATA .....................................................................................................................11
CURRENCY & STATUS .............................................................................................................................................11
DATA CREATION DATES ...........................................................................................................................................12
MAINTENANCE AND UPDATE FREQUENCY...............................................................................................................12
STANDARDS AND SPECIFICATIONS ..........................................................................................................................12
LEGISLATIVE REQUIREMENTS ..................................................................................................................................13
CURRENT DATA DEVELOPMENT ..............................................................................................................................13
FUTURE PLANS ........................................................................................................................................................13
DATA SCHEMA ........................................................................................................................................................14
DATA MODEL ..........................................................................................................................................................18
ROAD FEATURE REPRESENTATION...............................................................................................................20
RAIL AND TRAM FEATURE REPRESENTATION ...........................................................................................33
FERRY FEATURE REPRESENTATION .............................................................................................................33
AIR FEATURE REPRESENTATION ...................................................................................................................34
DATABASE DESIGN..................................................................................................................................................35
DATA DICTIONARY..................................................................................................................................................36
BUSINESS REQUIREMENTS .......................................................................................................................................41
AREAS OF APPLICATION ..........................................................................................................................................42
2A. QUALITY OF VICMAP TRANSPORT ................................................................................................ 43
LINEAGE/HISTORY ...................................................................................................................................................43
DATA QUALITY STATEMENT...................................................................................................................................44
SPATIAL ACCURACY ................................................................................................................................................45
COMPLETENESS .......................................................................................................................................................47
LOGICAL CONSISTENCY ..........................................................................................................................................47
POST-PRODUCTION VALIDATION..............................................................................................................................47
2B. MINUMUM QUALITY STANDARD ..................................................................................................... 49
PROPOSED/REQUIRED QUALITY ASSURANCE APPLICATIONS ....................................................................................49
POSITIONAL, RELATIVE & PLANIMETRIC ACCURACY....................................................................... 49
ATTRIBUTE ACCURACY ......................................................................................................................... 49
COMPLETENESS...................................................................................................................................... 49
3.
METADATA..................................................................................................................................... 50
4.
PRICING.......................................................................................................................................... 50
5.
ACCESS.......................................................................................................................................... 50
APPENDIX A- REFERENCE TABLES...................................................................................................... 51
LAYER – ENTITY RELATIONSHIPS ............................................................................................................................51
LAYER TABLE STRUCTURE ......................................................................................................................................53
AIRPORT AREA (POLYGON) ....................................................................................................................................53
AIRPORT INFRASTRUCTURE AREA (POLYGON) ....................................................................................................54
AIRPORT INFRASTRUCTURE (LINE) .......................................................................................................................55
AIRPORT INFRASTRUCTURE (POINT).....................................................................................................................56
FERRY ROUTES (LINE) ............................................................................................................................................57
Vicmap Transport Prod Desc V3_2 for PDF.doc
iii
PRODUCT DESCRIPTION
[TRANSPORT
Version 3.2
Information Services Branch
RAIL (LINE).............................................................................................................................................................58
RAIL INFRASTRUCTURE (POINT)..............................................................................................................................61
ROAD (LINE) ...........................................................................................................................................................62
TR_CLASS_CODE .................................................................................................................................... 65
PHYSICAL CONDITION ............................................................................................................................ 66
TR_ROAD_SEAL....................................................................................................................................... 67
TR_ROAD_RESTRICTION........................................................................................................................ 67
TR_DIVIDED ROAD................................................................................................................................... 67
TR_ROAD SUFFIX .................................................................................................................................... 68
ROAD INFRASTRUCTURE (POINT)............................................................................................................................68
TR_PHYSICAL_CONDITION .................................................................................................................... 71
ROAD INFRASTRUCTURE (POINT)............................................................................................................................73
TR_PHYSICAL_CONDITION .................................................................................................................... 75
APPENDIX B- DATA MODEL ................................................................................................................... 77
DEFINITION: A SPATIAL FEATURE WITHIN THE DATASET................................................................ 78
FEATURES: SPATIAL .............................................................................................................................. 78
GENERAL REFERENCE CLASSES ..............................................................................................................................80
DEFINITION: DEFINES ACCURACY AND OTHER QUALITY INFORMATION PERTAINING TO THIS
SPATIAL FEATURE .................................................................................................................................. 80
DEFINITION: THE SOURCE OF THE DATA IN THIS DATASET............................................................ 82
DEFINITION: THE LAYER TO WHICH THE FEATURES BELONG ........................................................ 83
DEFINITION: THE THEME TO WHICH THE FEATURES BELONG ....................................................... 83
FEATURES: ASPATIAL ............................................................................................................................ 84
GLOSSARY ............................................................................................................................................... 86
Vicmap Transport Prod Desc V3_2 for PDF.doc
iv
PRODUCT DESCRIPTION
VICMAP TRANSPORT Version 2.4
1.
Information Services Branch
PRODUCT DESCRIPTION
CUSTODIAN
Information Services Branch (ISB)
Department of Sustainability and Environment (DSE)
JURISDICTION
State of Victoria
CONTACT INFORMATION
Custodian
Information Services Branch (ISB)
Department of Sustainability and Environment (DSE)
Level 13, 570 Bourke Street
MELBOURNE Victoria 3000
Australia
PO Box 500
East Melbourne 3002
Victoria Australia
General information
George Mansour
Emil Skender
phone +61 3 8636 2333
facsimile +61 3 8636 2813
phone +61 3 8636 2333 facsimile +61 3 8636 2813
Technical details
David Blain
phone +61 3 8636 2339
facsimile +61 3 8636 2813
Supply enquiries
Vicmap Products are available through:
•
for purchase of small packets/areas of selected products online, go to
www.dse.vic.gov.au/vicmapdata
or
•
for larger quantities of Vicmap, refer to one of our Data Service Providers, listed at
http://www.dse.vic.gov.au/vicmapdsp
•
E-mail enquiries
vicmap.info@dse.vic.gov.au
Internet site for information
http://www.dse.vic.gov.au/spatial
http://www.dse.vic.gov.au/vicmap
http://www.dse.vic.gov.au/maps-imagery-data
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
5
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
DESCRIPTION
Vicmap Transport is made up of point, line and polygon area features in a seamless and
topologically structured data set. It is comprised of a basic framework of linear features
supplemented by related point and node and polygon features providing the supplementary data
supporting the transport network over the topographic and demographic landscape. Further
classification and description of real world features is provided by attribute tables, which add
specific description and definition to each feature supported by code lists that can be used for
analysis and individual identification.
The following transport features are fundamental to this data set:
•
Road network;
•
Road related structures – including fords, bridges, tunnels, gates, intersections, roundabouts,
barriers, rail crossings;
•
Ferry routes;
•
Rail network, railway yard, tramway, railway bridge, railway tunnel;
•
Rail related structures – including railway sidings, stations, railway bridges, railway tunnels;
•
Tramway network;
•
Air related structures – including (major) airport extents, runways, landing strips, helipads
Geographic Extent
Vicmap Transport coverage extends across the whole of Victoria as well as 100 kilometres into New
South Wales and 1 x 1:100 000 tile into South Australia.
Content
Theme Description
Vicmap Transport is made up of point, line and polygon area features in a seamless and
topologically structured data set. It is comprised of a basic framework of linear features
supplemented by related point and node and polygon features providing the supplementary data
supporting the transport network over the topographic and demographic landscape. Further
classification and description of real world features is provided by attribute tables, which add
specific description and definition to each feature supported by code lists that can be used for
analysis and individual identification.
The following transport features are fundamental to this data set:
•
Road network;
•
Road related structures – including fords, bridges, tunnels, gates, intersections, roundabouts,
barriers, rail crossings
•
Ferry routes
•
Rail network, railway yard, tramway, railway bridge, railway tunnel
•
Rail related structures – including railway sidings, stations, railway bridges, railway tunnels
•
Tramway network
•
Air related structures – including (major) airport extents, runways, landing strips, helipads.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
6
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Attribution
Every entity in this dataset is attributed, including detail both specific to the individual entity (eg.
road name) and generalised information about the feature (eg. feature type). Generalised classes
of common attribution are coded and indexed in separately maintained reference tables.
Attribute Class Tables include :
•
Spatial Feature – Description of a spatial feature within the dataset including feature ID, date
stamping and type;
•
Feature Quality - Defines accuracy and other quality information pertaining to this spatial feature;
•
Capture Method - The method used to capture this data;
•
Data Source - The source of the data in this dataset;
•
Layer - The layer to which the features belong;
•
Theme - The Theme to which the features belong;
•
Named Feature - The list of all names of features used within Victoria, with linkages to the official
Geographic Place Names Register maintained by Information Services Branch;
•
Alternate Name - The list of alternative names applicable to features. Names may or may not
occur in the Geographic Place Names Register.
•
Feature Type - The holding of all the different feature types that are applicable and their
relationship to the original Vicmap IGDS Data Dictionary.
See Appendix B, Data Model – (not all tables populated).
Structure
•
Topologically structured
•
Seamless across full extent
•
Conforms to national data models ie. ANZLIC, ICSM
•
Consists of vector data lines, points and polygons
•
Additional information about features contained in attribute tables eg. data quality, feature type.
Linear layers : Linear features such as roads and railways can be considered as linear networks and
are of special interest in GIS for network analysis processes such as shortest path computations.
Linear Networks are composed of nodes and chains. Nodes may be distinct features in their own right
and are used in Vicmap Transport to represent such features as a road end or an intersection with
other linear features.
Point layers : Relatively small area features, less than 50m in length, may be generalised as entity
points such as the centroids of bridges, tunnels, gates, railway stations and helipads, etc. Some
larger area features, eg. helipads are represented as entity points.
Polygon layers : Some larger area features have been captured in more detail and will be
represented as entity polygons. Examples include airport perimeters and sealed runways at major
airports.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
7
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Features
•
Unique Feature Identification managed through the use of two identifier attributes. The
Persistent Feature Identifier (PFI) and the Unique Feature Identifier (UFI); each feature uniquely
identified for change management.
•
Direction code to indicate forward or reverse direction of roads with respect to each vector, the
digitised direction of feature.
•
Connectors or pseudo roads are used to provide topologically correct representation to allow for
linear analysis of road networks through roundabouts or implied intersections,
•
Feature attribution to further describe or classify features eg. Name, locality, route number,
class, road seal, road restriction, bridge construction type, structure type, physical condition.
•
Updates provided as whole file replacement or via Incremental Updating (change only
replacement files).
•
Feature_Quality_ID attribute is the pointer to a Feature Quality Table that provides data quality
information (feature reliability dates, plan accuracy and data source).
•
Seamless storage of the data across full extent (non-tiled).
•
Adoption of ICSM guidelines for incremental updates - to assist in temporal data management
(features are date-stamped – data is retired rather than deleted).
•
Meaningful alphanumeric feature codes are held directly on spatial features to facilitate data
maintenance eg. rail_cross, bridge.
•
Ramp naming convention employed to uniquely identify freeway interchange ramps using a
derived logical traffic flow of either INbound or OUTbound ramps relative to Melbourne.
•
Road chain features carry locality (suburb) left and right as attributes, helping orientate users
and the differentiation of roads with duplicate or ambiguous names.
•
National and State Road Route Numbers.
•
Public Land managed roads indicated by the NRE Route Number.
•
Alternate/alias road names.
•
Under regular maintenance cycle - Data supplied by authoritative sources.
•
Weekly data refresh from maintainer
Reference systems
The datum used in the construction and maintenance of Vicmap data is the Geocentric Datum of
Australia. Data is held in geographicals (latitude/longitude) computed in terms of the GDA at 01
January 1994 (GDA94).
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
8
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Related data sets
These Vicmap Product are part of the State of Victoria’s framework information. VSIS framework
information datasets have been delivered into the following Vicmap Products, identified below :
• Vicmap Index
• Vicmap Address
• Vicmap Lite
• Vicmap Admin
• Vicmap Planning
• Vicmap Crown Land Tenure
• Vicmap Position
• Vicmap Elevation
• Vicmap Property
• Vicmap Features of Interest
• Vicmap Topographic
• Vicmap Hydro
• Vicmap Transport
• Vicmap Imagery- Aerial Photography
• Vicmap Imagery- Satellite
• Vicmap Vegetation.
Reference tables
Reference tables are used in the production and maintenance of this data set. They have been
established to provide a ‘real world’ picture of the features and attributes to which they pertain. They
illustrate the layer - entity relationships and specify attribute detail pertinent to each.
Copies of these tables are downloadable from http://dse.vic.gov.au/Vicmap . Copies may also be
obtained directly from DSE. They are held as ‘Oracle’ tables and are available in most database,
spreadsheet and delimited formats. Some of the tables are dynamic, with changes being incorporated
as new entries are determined. Users should regularly check the web site.
PRODUCTION AND/OR ACQUISITION METHODS
Original construction of the data sets
•
It was not until 1994 that a whole-of-state standard topographic mapping coverage of Victoria was
attained. Capture scale was at 1:25,000. 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
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
9
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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 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 DSE’s Coordinated Imagery Program (CIP). Extensive statewide
projects have been completed investigating Paper Roads, Roads on freehold land, DSE managed
roads, Road seals and proposed roads.
Ongoing maintenance of datasets
Only authoritative sources are used in the creation and maintenance of Vicmap data. DSE updates
its Road and Address data through its direct links with local government and other authoritative
sources in and out of government. For example, Local government provides new and change data
through its links with Property Information Program (PIP). Update data may come in the form of
subdivision information containing road alignments and name attribution. Other data comes in the
form of plans or textual information. Similarly update information is sourced from the Department of
Transport, Vicroads, Parks Victoria, Melbourne Water and the Department of Sustainability and
Environment’s own crown land and forest management groups. Feedback from users, including
emergency services dispatch ensures that the highest standards are maintained. Any reported
errors or omissions must be verified against the authoritative source before any change is made.
SOURCE OF INPUT INFORMATION
Content may be supplemented and /or verified with information supplied by:
•
Local Government Authorities
•
VicRoads
•
Licensed Surveyors
•
Regional Water Authorities
•
Street Directories
•
Melbourne Water
•
Victoria’s Emergency Services
•
Emergency Services Telecommunications Authority (ESTA)
•
Parks Victoria
•
Fire Management - Department of Sustainability and Environment
•
Forests and Lands - Department of Sustainability and Environment
•
Land Registry – Department of Sustainability and Environment
•
Registrar of Geographic Names – Department of Sustainability and Environment
•
Data capture and verification using aerial imagery
•
Victorian Government Gazette
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
10
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
GENERALISATIONS WITHIN THE DATA
Much of Vicmap data was primarily been captured to 1:25,000 scale topographic specifications from
compilations or negative separations. Conversion and manipulation processes have contributed to
the degradation of positional accuracy of the real world spatial data. Some features may have been
subjected to cartographic generalisation (when compared to their true relative location on the
earth’s surface). When one or more adjacent features would have resulted in over-printing at
publication scale, one feature will have been held in its true position and the rest marginally
displaced. A hierarchy determined which features were held in correct position. Natural features
were placed higher in the hierarchy. The hierarchy was as follows:
1. Hydrographic lines (coastline, watercourses and water bodies)
2. Railways
3. Principal roads
4. Secondary roads
5. Minor roads, tracks
6. Buildings and other point symbols
7. Vegetation boundary
Examples of cartographic generalisation include,
•
Where a river and road coincide at the scale of compilation, the road would have been marginally
displaced.
•
Where two or three features were close and adjacent, the one lowest in the hierarchy could be
displaced by as much as 25 metres at ground scale. Such displacement was required to maintain
the correct alignment of each feature to the other.
•
Multi track rail lines have been generalised. See later references to rail features.
•
Point features such as buildings in close proximity to linear features were displaced in a way that
retained their positional relationship relative to other features.
•
Minor divided carriageway roads represented as single road centerlines.
•
Smaller bridge and tunnel features represented by nodes.
•
Intersection features such as slip lanes and road forks less than 50m in length omitted.
•
The generalisation of some offset road intersections by the process of 'bent lining' resulted in a
loss of absolute accuracy for these features.
•
Line string-vector specifications stipulate maximum distance between two points (0.25mm) and
thinning of arcs applied according to the degree of curvature of the line strings. For three
successive points, if the mid-point is less than 0.10mm off-line it was discarded.
General rules associated with data capture were applied to determine whether features were to be
drawn to scale to form polygons or were to be symbolised as a point. After displacement, symbolised
features did not remain within accuracy tolerances according to their dimension and therefore were
not included in accuracy tests.
CURRENCY & STATUS
All features are tagged with a pointer (feature_quality_id) to the feature quality table with the following
attributes to determine currency:
•
‘feat_reli_date’
(format dd-mmm-yyyy hh:mm:ss) the date of source information for new or
modified spatial feature.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
11
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
•
Information Services Branch
Department of Sustainability and Environment
‘attr_reli_date’
(format dd-mmm-yyyy hh:mm:ss) the date of source information for new or
modified aspatial object attributes of the feature.
DATA CREATION DATES
Vicmap data is never deleted, only retired. All key features are tagged with the following attributes to
enable an audit trail to be maintained and to facilitate incremental updating :
•
‘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.
•
‘create_date_ufi’ (format dd-mmm-yyyy hh:mm:ss) is the date/time stamped against each feature
when it is created.
•
‘retire_date_ufi’
(format dd-mmm-yyyy hh:mm:ss) is the date/time stamped against each
feature when it is retired due to physical change, attribute change or deletion.
MAINTENANCE AND UPDATE FREQUENCY
Primary maintenance sources are local government for new and changed road information (supplied
via the PIP), Vicroads for major roads, the Registrar of Geographic Names for locality and topographic
feature name detail and the DSE for roads on public land.
The above responsible authorities supply detail and change information to ISB on a priority basis
subject to various agreements. Such data is incorporated into Vicmap according to agreed
maintenance schedules (maintained daily, updates supplied weekly to DSE for distribution as Vicmap
Transport).
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.
•
ICSM Roads Working Group Road Model 2010
•
DSE 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 DSE ISB requirements (eg 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.dse.vic.gov.au/spatial.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
12
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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 are their business requirements of the data. 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.dse.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 nonconformance of the data. This will be used to justify data upgrade projects to improve the conformity
of the data.
Fulfilment 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:
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
13
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
•
Information Services Branch
Department of Sustainability and Environment
Integration with other Vicmap Digital products (Hydro, Property and others). As part of DSE
ISB’s spatial data framework strategy, work will continue to make all Vicmap products more
closely aligned, particularly in terms of vertical topology.
•
Under Consideration: Tram stops, Bus routes, Bus stops, identification of Public Roads,
Responsible Road Authorities and overarching Coordinating Road Authority, oversize load
routes
•
Under Consideration for inclusion : Turn restrictions, speed limits
• ‘Anomaly Advice Notices’ (Internet-based forms for feedback) are received from knowledgable
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. Eg. walking track names, road
restriction information.
DATA SCHEMA
Data Structure
Vicmap Transport uses a feature-based data model described by the following definitions:
Entity : A real world phenomenon not divided into phenomena of the same kind, eg. bridge.
Feature instance : An abstraction of an entity. The description of a feature instance encompasses
only selected properties of that entity. Feature instances can also be referred to as features.
The feature structure of the feature based data model can be summarised as
feature instance = [spatial object + attribute object]
eg. ROAD = [ Line + Class: Freeway ]
Attribute : An attribute is a particular property of an entity. Attributes can be spatial (or locational) and
aspatial (or non-locational).
Attribute value : The value assigned to an attribute for a specific feature instance.
Attributes can be spatial (locational) and aspatial (non-locational) eg. Feature-type_code (ford, road,
bridge), UFI, create_date, retire-date, feature_quality_id, construction.
Feature class : A group of feature instances defined by a set of rules and having common attributes
and relationships that are the properties of the corresponding real world phenomena.
Within the Oracle tables that comprise Vicmap Transport, classes may refer to “link” tables, which
establish direct relationships between the point and/or line and/or polygon structures that may be used
as spatial objects eg. Rail.
Each feature instance reflects only selected properties of an entity type. The object types below are
the primitive components of data contained in Vicmap Transport. These data objects are grouped
together to form a hierarchy ie. theme, layer, included entity and attributes, which is used for the
capture and transfer of data.
The data is topologically structured (spatially related to adjoining objects) and classified into a variety
of categories of additional information about the feature as represented by attributes, which are held in
attribute tables. Attributes will only reflect selected characteristics of their feature. For example, the
name of a railway line (line) is recorded in the name attribute.
Polygons are used to represent formally bounded area features, eg. an airport area (Landing ground).
Lines or Chains are used to represent the boundaries defining such area features. They also provide
the graphical definition of linear features such as roads, bridges, railways and connectors.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
14
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Points are used to locate symbols, eg. bridge, barrier, gate, intersections, and as paracentroids within
polygons, holding information about the polygon. They also define the extent of all lines.
The feature structure of the feature-based data model can be summarised as:
Feature instance = [spatial object + attribute object]
Where:
Spatial Object: It is the addition of all the locational attributes of the feature instance and may
comprise geometrical objects such as points, lines and polygons. Spatial objects carry a
spatial address that consists of one or more couplets (x, y) or triplets (x, y, z) of coordinates.
In the feature based data model topological relationships will be carried as part of the spatial
object whenever the transfer formats support them.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
15
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
POINT
Geometric representation defined by a single 'x, y'
coordinate couplet or an 'x, y, z' triplet. Three
special points are used in the data model.
Entity Point – used to locate point features or area
features represented by a point.
Paracentroid – point within a polygon used to hold
information about that polygon.
This point is
topologically linked to the bounding chains of the
polygon.
Every polygon will contain a paracentroid. This point
type is sometimes known as a centroid or as a
polygon label point in proprietary GIS software
packages.
Node - A point that is a junction of two or more
chains or an end point of a chain. Nodes may carry
attribute information.
Note: For supply purposes, some node features may be extracted and supplied as point features.
LINE or CHAIN
A line composed of a sequence of non-intersecting
line segments bounded by nodes (not necessarily
distinct) at each end.
Chains will reference their start and end nodes.
Assigned attributes (including PFI and UFI) will relate
to the entire chain (i.e. between nodes)
When a chain is defining a polygon boundary it will
reference the polygons to the left and right of the
chain with respect to the direction of digitisation.
POLYGON
A bounded, continuous region consisting of an
interior area, an outer boundary defined by a set of
chains, and zero or more, non-nested inner
boundaries also defined by sets of chains, and a
paracentroid that holds information about the
polygon.
Within a layer the polygons are mutually exclusive
and are generally digitised in a clockwise direction.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
16
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Attribute Object: The addition of the non-locational information about a feature instance. These data
identify the feature class and the aspatial attributes of a specific instance of the feature type. The
attribute object is composed of one or more attributes.
Spatial Object
Example 1
Line (x1, y1…. xn, yn)
Attribute Object
Attribute
Attribute Value
Feature_type_code:
Road
Road_name:
Calder
Road_type:
Highway
Class_code:
1 (Highway)
Road_seal:
Sealed
Direction_code:
B (both ways)
Route_No:
A79 (Vicroads system)
Restrictions:
Physical_condition:
Operational
Construction_type:
Example 2
Polygon
Feature_type_code:
Airport
Name:
Sale Aerodrome
Runway_number:
The spatial object and attribute object as defined above are the primitive components of data
contained in Vicmap Transport. These data objects are grouped together to form a hierarchy, which is
used for the capture and transfer of the data.
All Vicmap Transport data share a number of common characteristics, which are set out below.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
17
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
DATA MODEL
This Vicmap Products Data Model has been developed in S-Designer Modelling tool and can be
located on the Victorian Government website www.dse.vic.gov.au/vicmap
Vicmap Transport data will comply with the following rules for spatial data integrity. (The maximum
allowable errors are described in section 2A. Quality of Vicmap Transport. 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
Pseudo node
Same feature with identical attribute values
Pseudo-node in data
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
18
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Correct Representation
Incorrect Representation
Broken line in data
Correct Intersection
Incorrect Intersection
Correct Linear Feature
Incorrect Intersection
Spike in Linear Feature
Artefacts
Artefacts 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 ie 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)
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
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
19
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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. (see Appendix B)
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
Connector features (pseudo roads)
representation
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:
ser v ic e ro ad e x it
M a in R o ad
ro u nd ab o u t
fea t ure
C o n nec to r o r
p seud o ro ad
C o n necto r o r
p seud o ro a d
S u b sta n ti a l R o u n d a b o u t
S erv ice ro ad
Jo ne s R o ad
Im p li e d In t e rse c ti o n
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.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
20
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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).
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. Eg.
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 Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
21
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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.
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:
SERVICE ROAD
PRINCES
FRED STREET
Primary name = NEW STREET
Alias name = PRINCES HIGHWAY
HIGHWAY
NEW STREET
PRINCES
HIGHWAY
Primary name = FRED STREET
1st Alias HARRY ROAD
2nd Alias = PRINCES HIGHWAY
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
SERVICE ROAD
HARRY ROAD
SERVICE ROAD
22
JONES STREET
PRINCES
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
SERVICE ROAD
HIGHWAY
Information Services Branch
Department of Sustainability and Environment
SMITH STREET
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Crossovers on Freeways
Individual chains will represent emergency vehicle crossovers on freeways.
Freeway Carriageways
Crossover
Emergency Access Gate
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 Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
23
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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’
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
24
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Bridge less than 50 metre span
Example - single line road bridge of less than 50 metres length over a single line road.
(PFI = c)
(CONPFI1 = a, CONPFI2 = b)
(PFI = a)
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, ie
conpfi1 = PFI value ‘a’ and conpfi2 =
PFI value ‘b’.
Road2
Node representation of a Bridge/Tunnel feature
Bridge greater than 50 metres span
Example - Linear Bridge - single line road over single line road.
f e a tu r e 'in t_ a t t r ib u t e '
PFI = a
f e a tu r e 'b r id g e l'
f e a tu r e 'b r id g e _ r d _ p '
( c o n p f i1 = a , c o n p f i2 = b )
PFI = b
ro a d 1
f e a tu r e 'in t_ a t t r ib u t e '
C h a in r e p r e s e n t a t i o n o f a b r i d g e / t u n n e l
f e a tu r e o v e r s i n g l e c a r r ia g e w a y
ro a d 2
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 (eg. 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:
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
25
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
The feature type code shall be the structure type ie 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, DSE Road Management as well as other
road and asset managers.
Road Name = Road Name 1
Feature Type = Road
Road Name = Road Name 2
Feature Type = Road
Example:
Feature Type =
Primary Road =
Alias Road Name =
Structure Name =
Bridge
Road Name1
Road Name 2
(If relevant)
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
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
26
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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
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 :
A d o p ted
In tersectio n
< 10 m
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
27
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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
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.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
28
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
•
‘Connector’ or psuedo-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.
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 Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
Vicmap Transport
29
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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)
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
30
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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 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 Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
31
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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 labeling 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 labeling.
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 definitative list of road
type abbreviations.
Suffixes OFF and ON are not included in the concatenation.
Cross Border Data Incorporation
In December 2006 a data exchange agreement was signed between Land and Property Management
Authority (LPMA), New South Wales and the Department of Sustainability and Environment (DSE),
Victoria. This exchange allows for the provision of mapping datasets for a distance of 100 kilometers
into each jurisdiction.
This meets expectations of emergency service organisations who regularly respond to incidents
beyond Victorian borders.
In Victoria this jurisdictional topographic data is incorporated into the relevant topographic Vicmap
data themes so that the Vicmap topographic data models now extend across the Victorian border into
New South Wales by 100 kilometers.
Data sets sourced from the South Australian Department of Environment and Natural Resources
(DENR) have been incorporated into Vicmap since 2007.
The extent into SA is one 1:100 000 tile or approximately 40km.
Jurisdictional transport themes are incorporated into Vicmap Transport on an annual basis subject to
funding availability. Data is sourced in January / February of each year and incorporation is complete
May / June of the same year.
It is worth noting that jurisdictional data does not necessarily meet Vicmap standards and accuracies.
Both NSW and SA capture data to support base mapping of 1:50,000 with associated accuracies.
Road classifications differ to Vicmap along with road attribute completeness. For example NSW roads
only hold one road name and no aliases.
However, the advantage of holding this information is to allow a standard view beyond Victoria for
Vicmap users.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
32
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Where more regular supplies of NSW and SA topographic data are required it is recommended that
the relevant state agencies are contacted separately to arrange these additional supplies.
RAIL AND TRAM FEATURE REPRESENTATION
Railway, Light rail and Tramway are treated as common features.
identified by means of their feature codes and structure types.
They can be separately
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.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
33
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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. eg. 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 the same hierarchy 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.
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 centerline 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. ie the NSW data is supplied
as centerline linework only.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
34
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
DATA MODEL
A copy of the Vicmap Transport data model developed in S-Designer Modelling tool is attached as
Appendix B.
The general model was constructed with the following objectives:
To conform as far as possible to the national (ICSM) topographic data model, some specific
requirements were identified by DSE, with respect to the handling of cartographic text, unformed polygon
based features, and temporal and status management.
Temporal Data Management
All data has temporal attributes for the management of different versions of the database. These
attributes include date stamps such as Created, Retired and Extracted for Edit (data management tool
only).
Implementation Status
The implementation status of a feature may include Proposed and Constructed stages.
DATABASE DESIGN
The database design enables:
•
Seamless storage of the data across full extent (non-tiled);
•
Versioning of features;
•
−
No features are deleted from or altered in the database.
−
If features need to be modified they are tagged with a retirement date and replaced with a new
modified feature.
−
Features removed from the active database are tagged with a retirement date.
Incremental updates are consistent with the Vicmap Property database incremental update format
specification;
−
A temporal slice from the database should be able to be extracted for any range of dates and
reformatted into a file suitable for update of supply or client databases.
•
Extraction of the data in a structure suitable for population of the layers in the Spatial Information
Infrastructure Unified Data Store;
•
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;
•
Management reporting on database maintenance activities to assist with contract management;
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
35
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
DATA DICTIONARY
The data dictionary applicable to this Vicmap Products model is also located on the Victorian
Governments website www.dse.vic.gov.au/spatial.
A copy of the data dictionary applicable to the Vicmap Transport model is attached as Appendix A.
Named features are attributed with the name in full. Abbreviations are not used except in the cases
noted below or unless the field length is too small to accommodate the full name.
Feature attribute rules
Assignment of road names
Road names in Vicmap Transport are assigned according to the following rules :
Local Government Authority assigned road names are assigned as the primary Vicmap Transport road
name. The extent of a road is indicated by formally assigned street addresses.
Where a council has formally defined the name and extent of a road section (such as may be found on
a council issued/endorsed lodged plan or council listing of roads for the respective LGA), that road
name is used as the primary Vicmap Transport road name. Where no council endorsed name
appears evident, a road name may be adopted as a primary road name in Vicmap Transport if
evidence appears to support its common use. For example, roads in national parks and on crown
land or a Vicroads “from-to” name or any other Vicroads assigned name. Sources may include the
Vicroads Country Street Directory, local maps or directories or CFA Regional map books. Other
names found for the same road or section of road are recorded as alias/secondary names.
A council may assign a local name to a segment of a major through road (eg Black Stump-Woop
Woop Road) and refer to it as such on its official maps, plans and road records (eg. Main Street).
Council may later assign addresses to this same segment of road and use the through road name (not
the local name) for the address assignments – particularly in cases of rural addressing. In such
cases, the primary road name will be that of the street addressing, ie. the through road name (Black
Stump-Woop Woop Road) and the alias will be the local road name (Main Street).
Where a “from-to” name is used for a major road controlled by Vicroads, the order of names
(towns/localities) will be that given in the most current Vicroads Country Street Directory. Where
evidence suggests that the reverse order is also frequently used (eg. CFA regional map books, etc.), it
shall be included as an alias/secondary name.
The determination that council names take priority over other naming authorities such as Vicroads and
Department of Sustainability and Environment is based on the power to name roads given to Local
Government under the Local Government Act 1989 and the principles espoused in the leaflet “A Guide
to Road Naming in Victoria published by the Registrar of Geographic Names (Victoria) 2002
Road name content
Road name content will be determined according to the following rules:
•
The only characters permitted are; A..Z, 0..9, - , (space).
Apostrophes, commas, and periods are removed, eg Ross', Ross's will be coded as ROSS,
O'Brien's as OBRIENS, A’Beckett as ABECKETT.
•
All names are in UPPER CASE, eg McClure will be coded as MCCLURE.
•
No characters are permitted in superscript or subscript, eg McDuff is coded as MCDUFF.
•
No spaces are allowed to be embedded within words, single spaces only are allowed between
words and no spaces are allowed to surround hyphens, eg GEMBROOK-LAUNCHING PLACE
ROAD.
•
Origin–Destination roads names as primary road names reflect addressing road name within Vicmap
Address. The reverse origin-destination road name is added as an alias road name.
•
Initials are separated by a single space, eg A.I.F. Street becomes A I F STREET and A. H. CAPP
SCENIC DRIVE becomes A H CAPP SCENIC DRIVE.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
36
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
•
Road type is spelt in full.
•
(Primary) Road names are recorded as actually used. Numbers are not converted into words unless
they are used that way (see note below where aliases are created for ease of use).
•
Road name prefixes Saint and Mount are to be abbreviated to ST and MT respectively where in
common use, eg ST KILDA ROAD, MT DANDENONG ROAD. Other cases of possible but,
uncommonly used abbreviation, including POINT (PT), will continue to be coded in full, eg MOUNT
VUE ROAD, MOUNT VIEW COURT, VIEW POINT AVENUE, VIEW MOUNT ROAD, MOUNTAIN
VIEW ROAD, LONG POINT ROAD, POINT COOK ROAD, POINT ORMOND AVENUE.
•
Only where limitations in field size make it necessary, will truncation of road name or road type be
accepted. Such abbreviations are to be at the right-hand end and should comply with the provisions
of Australian Standard AS4590.
•
The road name field is to be non-null. Where the name of a road is not known or the road is
unnamed, the name 'UNNAMED' is to be used.
•
Road type and suffix fields may, or may not be, null.
•
Bridge and tunnel features inherit the road description of the linked road they service.
•
Rights of Way, where included, are to have the road name 'R O W Y'.
•
Road type suffixes are to be abbreviated to one or two characters as per the following;
•
N
….. North
CN
….. Central
S
….. South
U
….. Upper
E
….. East
L
….. Lower
W
….. West
EX
….. Extension
NE
….. North East
ML
….. Mall
NW
….. North West
ON
….. On (ramp)
SE
….. South East
OF
….. Off (ramp)
SW
….. South West
Road suffixes are to be recorded in the Road-Suffix field, eg Vincent Street North would have N in
the road suffix field. Where no suffix exists, this field is to be ‘null’.
Note that a suffix is not a directional or similar element derived from a locality name. Directions or
similar devices occurring in a locality name that has subsequently been used in a road name, will
remain unchanged in the road name field. For example, Wandin East Road is recorded as roadname - WANDIN EAST, road-type - ROAD, suffix - “”.
•
Validation files of currently-accepted road types and road suffixes are held by and are available from
Spatial Information Infrastructure. Any types or suffixes found not to conform to these lists should be
brought to the attention of Spatial Information Infrastructure, for validation and incorporation into
such validation files.
•
Where two road types exist in a road description, the first is included in the Road Name field and the
second in the Road Type field. For example, High Street Road will contain HIGH STREET in the
Road Name field and ROAD in the Road Type field. For the purposes of this definition, 'Mall' is
considered to be a Road Type suffix. For example, 'Bourke Street Mall' will have 'Bourke' in the
Road Name field, STREET in the Road Type field, and 'ML' in the Road Suffix field.
•
Where the first word of a road description is 'The', the subsequent word is included in the road name.
If the Road Type is not used then any suffix is recorded wholly within the Road Name field. For
example, 'The Pass' contains 'THE PASS' in the Road Name field and the Road Type and Road
Suffix fields are null. `The Parade West' contains 'THE PARADE WEST' in the Road Name field and
Road Type and Road Suffix fields are null.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
37
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
•
Roads having two or more names have their more usual description as the primary road description.
The second or next most popular name, should there be more than two, form Alias Road Name
descriptions.
•
Connecting ramps linking roads, freeways, highways and major arterial roads are named according
to the Spatial Information Infrastructure convention for the unique naming of ramps.
•
All Road Attribute fields, (excepting feature codes), are upper case only.
Maintenance of road names with inclusive numeric characters
A number of road names include numeric characters. Many are fire or access tracks and are unlikely
to have property addresses assigned to them. However, some are urban roads and do have
associated addresses. It is known that some computer systems have difficulty in deciphering a house
number from a road name with an embedded number. For example, “10 MILE ROAD” could be
interpreted both as house number 10 located in Mile Road or as no house number and road name Ten
Mile Road. In some cases, a number has a distinct association with an existing feature. For example,
3CV LANE is named after the radio station at the end of the lane. Spelled out as THREE CV LANE it
would lose that link. Similarly, HARPERS NUMBER ONE NORTH TRACK is long winded. It is unlikely
to be signposted in full or shown on maps or in directories as such.
Road names are recorded as advised by the overarching responsible authority. All such authorities
were informed of the Australian addressing standard; AS/NZS4819 Rural and urban addressing, and
in particular the associated guidelines that recommend that “numbers included as all or part of a road
name should be written in full” (exceptions include the case of 3CV Land cited above).
Where the use a numeric is still to be the authoritative form of the road name, then an alias road name
is created with the number spelled out in full. Eg. BSEVENTY ONE ROAD.
•
No spaces are inserted between an alpha prefix, a number and/or an alpha suffix. Eg. 4W
FIRETRAIL.
•
If an abbreviation for the word “number” is used then no space is inserted after the abbreviation.
Eg. NO6 TRACK.
•
Similarly, abbreviations for second, third, fourth or other like numbers will have no space inserted.
Eg. 5TH AVENUE.
•
Where spelled out in full, formats will be as follows :
D3 TRACK:
…. road_name
=
DTHREE
road_type
=
TRACK
10 MILE ROAD
…. road_name
=
TEN MILE
road_type
=
ROAD
3RD AVENUE:
…. road_name
=
THIRD
road_type
=
AVENUE
NO5 FIRETRAIL
…. road_name
=
NUMBER FIVE
road_type
=
FIRETRAIL
3CV LANE
…. road_name
=
THREE CV
road_type
=
LANE
In the case of conflicting names for a road feature or for features matching across different source
map boundaries, the incompatibility should have been resolved and the features uniquely named.
Alias ‘Numeric’ Road names
All road names with inclusive numerics have an associated alias with the number spelt out in full to
assist in easy road identification.
Alias ‘From – To’ Roads
In the case of ‘From – To’ road names, alias names with the ‘From – To’ road name reversed have
been created to assist in easy road identification. Eg.
ROAD NAME = MELTON HIGHWAY
ALIAS NAME = KEILOR-MELTON ROAD
ALIAS NAME = MELTON-KEILOR ROAD
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
38
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
ROAD NAME = GISBORNE-MELTON ROAD
ALIAS NAME = MELTON-GISBORNE ROAD
Height_limit
Where vehicular height restrictions of below seven metres apply along road segments, at bridges or at
tunnels, the height limit, in metres to one decimal place, is recorded.
Direction_code
Direction of traffic flow is indicated, related to the vector depicting the road segment:
ONE WAY TRAFFIC -
F .... forward
R .... reverse
TWO WAY TRAFFIC -
B .... both
As a general rule, vectors are flipped to tag one way traffic as having a direction of Forward.
Class_code
A road classification code has been applied to indicate function and condition of each road. For
details refer Appendix A
Road_seal
An attribute indicating whether the road surface is fully sealed (asphalt, concrete, etc.) or unsealed is
included. For details refer Appendix A
Route_ no
The route number assigned by VicRoads under their system indicating road condition and suitability is
included. Eg. C146. For details refer Appendix A
Divided Road
Column is DIV_RD
DD
DS
ND
U
Divided Double Line (one line per carriageway) representation
Divided Single Centreline Representation
Not Divided
Unknown
Node types
The following road node types may be found in the data :
administrative
at the intersection of roads and administration boundaries (eg. LGA,
locality, etc)
attribute
where a change of road attribute/s occur (eg source scale, name,
class)
barrier
at the location of permanent traffic barriers
connector
as an artificial device to indicate roads connect within a given
distance
drainage
road/stream intersection where crossing type is unknown (eg.
Bridge, culvert?)
edge
at the edge limit of the data or tile to indicate that the road does
physically continue beyond this point
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
39
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
ford
where the average vehicle can cross an intersecting stream under
normal conditions
gate
where a gate limits passage
signalised intersection
where electronically controlled traffic lights control an intersection
non-signalised intersection
at road intersections not controlled by traffic lights
level crossing
where roads intersect with rail/tramway lines in current use
road bridge
at points where the road is carried by a structure across some other
physical feature
road end
where a road is discontinued, other than the edge of the data or at a
barrier or gate
road tunnel
at points where a road is continued via an underground or under
water passage
roundabout
at intersections characterised by a central median feature and
circular road arrangement
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
40
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
BUSINESS REQUIREMENTS
Usage or availability restrictions
Product/s will be provided under the terms and conditions of an annual licence.
Licence restrictions/conditions
Vicmap products are supplied under Licence. The Licensee may use the Data only for internal
business use. There is no transfer of title or ownership in the Data, and the copyright and intellectual
property in the Data remains the property of the State.
Vicmap products are protected by copyright under the Copyright Act 1968 (Commonwealth). The
dataset is appropriately labelled with copyright information and the removal or degradation of this
labelling is an offence under the Copyright Amendment (Digital Agenda) Act 2000 (Commonwealth).
Access constraints
All digital data issued to customers is subject to licence conditions. A copy of the terms and conditions
of the Licence can be viewed at www.dse.vic.gov.au/vicmap under Products and then under Licence
for use of Vicmap
In general, the User Licence allows licensees to use the data within their own business but does not
permit data to be provided to third parties. There is no transfer of intellectual property in the data to
customers.
Exclusion of Liability
Information Services Branch (ISB) makes every effort to provide and maintain accurate, complete,
useable and timely digital land information. However, some product versions may be preliminary in
nature and presented prior to final review and approval by Manager Spatial Services. The data and
information are provided with the understanding that they are not guaranteed to be correct or
complete. Users are cautioned to consider carefully the provisional nature of the data before using it
for decisions that concern personal or public safety or the conduct of business that involves
substantial monetary or operational consequences. Conclusions drawn from or actions undertaken on
the basis of this data are the sole responsibility of the user.
Privacy Statement
Where any use of this Product is linked or related to other data causing the identification of an
individual the user must comply with appropriate state or federal legislation.
Supply format
Supply format will be by negotiation with your supplier. Examples may include :
Example
• DXF File
• Intergraph .DGN
• ESRI ‘SHAPE’ files
• DWG (AutoCAD)
• MapInfo
•
Incremental Update - (Refer to the Victorian Government website dse.vic.gov.au/spatial for
details regarding the IUF Model and supporting documentation.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
41
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Media format
• CD-ROM
• DVD
• Email (less than 10Mb)
Other formats and media available upon application.
Projections
Native projection- Geocentric Datum of Australia – 1994 Adjustment (GDA94)
•
− Degrees and decimals of a degree - GDA94 latitude/longitude
Others on request
•
AREAS OF APPLICATION
See Marketing & Product Development Plan
•
•
•
•
•
•
•
•
•
•
•
•
•
Property Identification/Property Ratings
Infrastructure/facilities location and management
Strategic planning
Project planning
Reference framework
Research systems
Geocoding
Asset management
Real Estate management
Valuations analysis
Property analysis
Graphical index
Mailing list validation, Mail outs.
Note: Many applications will require the input of user specific data, eg. property polygons, planning
polygons, land use information, sales and/or valuation figures, etc
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
42
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
2A. QUALITY OF VICMAP TRANSPORT
LINEAGE/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.
•
Graphical detail was compiled photogrammetrically from 1:40,000 scale aerial photography and plotted
onto stable base film or digitally captured using software (Micromap) and converted to design file format
(CAD).
•
Field verification per mapsheet established data currency and completion of map content.
•
Control for photography was created using field survey techniques and then extrapolated to individual
photo models via aerial triangulation and mathematical block adjustment.
•
Stable base repromat generated initially as mechanical film plots progressed to direct digital repromat
(scribe coats) and were then cartographically enhanced to produce print ready film negatives.
•
Map currency remained stagnant at print date without a formal revision program. Project based
revision occurred in selected areas due to specific problems discovered ie. older areas - use of
unsuitable mapping control or major urban development. Client feedback instigated partial
revision in particular mapsheets using uncontrolled photography.
•
1st Stage Digital Capture 1985-94. A mandatory data set (Hydrography, Relief, Roads ) was
first captured using raster scanning of negative separations and vectorising, together with some
direct digitising from source material ( compilation plots, mapping artwork).
•
2nd Stage Digital Capture 1994-97. Capture of the balance of data features covering text,
infrastructure, vegetation, spot heights and contour values was carried out by scanning or hand
digitising from compilations, negative separations and printed map source material.
•
Mapbase data was stored in (CAD environment) microstation design file format data as
individual 1:25,000 single or double mapsheet tiles. Features were separated into 63 levels
and attributed with feature coding (AS2482) and symbol style specification to facilitate
separation and classification but was still only “spaghetti” data. Topographic data had no
attribution with the exception of contours and spot heights that were tagged with respective
height values. This data set was not suited to GIS applications, not being ‘clean’ in terms of line
work or topologically structured or holding any significant degree of ‘intelligence’. The main
level of ‘intelligence’ linked to the data being through line style, colour, level, etc. and a feature
coded data link which defined the scale origins and type of boundary represented.
•
The first attempt at producing an intelligent topologically structured data base occurred in 1996
driven by a need for a Computer Aided Dispatch System for the Bureau of Emergency Services
Telecommunications group (BEST). As a result a road network database (SDRN) model based
on an area centred on Melbourne was created. The State Digital Road Network (SDRN) model
was a blend of cadastral centre lines and topographic roads and hydrographic overlay data.
Topologically structured and consisting of linear and point feature layers attributed with unique
feature identification, feature coding, classification and quality pointers and this was held in a
seamless relational data base.
•
State Digital Map Base 1996-97. This data covering Victoria, was cartographically correct but
lacked the connectivity (due to the existence of overshoots and undershoots), attribution and
topology required for modern GIS environments. The data had to be cleaned and polygonised.
The migration of the rest of the SDMB was set to integrate the existing data bases; Cadastral,
Road Network and Topographic.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
43
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
•
To make the SDMB GIS ready with full attribution, topology and unique identification, Spatial
Information Infrastructure developed a model using the GEOCASE modeling tool to create a
feature based seamless information set across Victoria. This was stored in an Relational Data
Base Management System (RDBMS) conforming to national (ICSM) data model standards. It
was designed to populate layers in the Spatial Information Infrastructure’s Unified Data Store
(Oracle/SDE base) without loss of any existing Vicmap Digital data.
•
Data within this map base is scale dependant (1:25,000), based on various accuracy standards
of source information, conversion and manipulation processes resulting in degradation of the
positional accuracy of the real world spatial data. The planimetric accuracy maximum of this
data set is a statistical estimate based on the cumulative error and Topographic Mapping
Standard applied that is equivalent to 17.5m for 90% of well defined points (0.7mm at 1:25,000
scale).
•
Vicmap Digital Topographic resided under the control of Office of Geographic Data Coordination (OGDC). Key challenges for OGDC were to provide a common structure to the data
and to standardise the maintenance. The result of this was out-sourcing of data maintenance to
a non-government agency. While full control and administration of the data remained with
Spatial Information Infrastructure, Vicmap Digital Topographic is now maintained by external
contractors
•
Other key changes have included; incorporation of the metropolitan SDRN roads and address
base, translation into an Oracle data base environment, line cleaning and topological structuring
(including the formation of various administrative boundary and area polygons) and the
identification and rectification of many anomalies found in the data, eg. edge joining of updated
contract areas, border mapping.
•
Improvements in the data continue, with a major update of selected topographical features over
Victoria eg. the ESI project, improved input from local government and other key sources,
allowing faster turn-around of update information and added levels of attribution, eg. automatic
update of road and address information from council supplied data via PIP.
•
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.
DATA QUALITY STATEMENT
Fitness for purpose
Although some higher order accuracy occur in pockets, the data is primarily derived from mapping
compiled at 1:480 and 1:500 (metropolitan Melbourne), 1:2,500, 1:10,000 and 1:25,000 scales. Use
of the data is therefore logically suited to applications at the same or smaller scale to that of the
source. Any enlargement or extrapolation of the data will result in proportionally increased visual
displacement and/or errors of the same order of magnitude in any analytical outcomes.
Proposed / Required Quality Assurance Applications
ISB is continually improving and extending the quality and content of the base. ISB will continue to
undertake and improve its Quality Assurance processes to ensure that they conform to Australian and
International Standards, and continue to improve the quality of the data within the Products.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
44
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
SPATIAL ACCURACY
Positional Accuracy
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 planimetric 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.
It is expressed as the standard deviation of the horizontal position of the feature that is +/-17.5 metres
for scanned 1:25,000 scale topographic data. It is generally estimated that 90% of well defines
features are within 0.7mm at 1:25,000 map scale of their true position.
Cartographic generalisation of features to facilitate presentation has been employed based on a
hierarchy as mentioned in “Generalisations within the Data.” It is believed that all generalisations fall
within the remaining 10% at 1.0mm or less at plot scale.
The positional accuracy of the source material
This specification cannot prescribe a figure for the planimetric 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 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 map (Sm) of 0.62 mm.
Errors due to the conversion processes
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 Sdata for the
distribution of errors.
Linear Features:
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
45
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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, ie 5m for 1:25,000 data.
Errors due to the manipulation processes
The processes used during data editing and structuring processes will introduce an error Sman not
greater than 10% of the Sdata.
Other errors due to cartographic generalisations and data model simplifications are referred to in
section on Generalisations Within The Data.
Absolute planimetric 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
s absolute =
=
=
( s m ) 2 + ( s data ) 2 + ( s man ) 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
topopgraphic data giving a worst case of 8.3m.
Cadastral Base-derived data
s absolute =
=
=
( s m ) 2 + ( s data ) 2 + ( s man ) 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.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
46
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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 planimetric 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 planimetric accuracy given is 9999.
COMPLETENESS
Completeness is measured by carrying out a visual comparison of symbolised plots of the data over
plots of the source material.
Various projects ie. ESI, SDRN, ESMAP, CFA mapping, PIP maintenance, Vicmap Topographic
Mapping Program, selected area updates, undertaken over certain years have contributed to
validation and update of data content bringing about a level of confidence in the completeness of
various feature items. ISB continuously reviews its data against the latest information available
from respective authoritative sources.
Reliability figures indicating completeness of content between the data set and real world.
Estimated completeness of content with respect to Layers:
•
Road infrastructure ( ford, bridge, tunnel, gate, intersection points)
Victoria ……
96%
•
Road ( road, bridge, tunnel, ford)
Victoria ……
96%
•
Ferry Route
Victoria ……
90%
•
Rail (railway, tramway, station, bridge, tunnel, yard )
Victoria ……
90%
•
Airport Infrastructure ( runway, helipad )
Victoria ……
95%
•
Airport Area (airport )
Victoria ……
95%
*The above figures are believed to be reasonable estimates of accuracy. They are anecdotal,
sometimes supported by limited feature and/or attribute comparisons with other data sets. They
have not been confirmed through statistical methodologies and/or large scale field trials.
LOGICAL CONSISTENCY
The allowable error in logical consistency ranges between 1% (new data additions) to 5% (premaintenance contract data). Logical consistency is a measure of the degree to which data complies
with the technical specification. The test procedures are a mixture of software scripts and onscreen, visual checks.
POST-PRODUCTION VALIDATION
All VicMap Transport data is rigorously tested using a number of formal validation routines including
software, manual and visual checks. Spatial Information Infrastructure holds a number of validation
tables used as the measure of valid data content or exceptions therefrom.
Various procedures are undertaken as normal update/maintenance routines, to ensure conformity of
the data to Specification. Example validation tests include checking to ensure that:
•
Data sets contain valid text case and character types specific to each field
•
Data sets comply with establishment rules, eg single spaces only to be used in road names
•
Road extension field contains only standard abbreviations
•
There are no “null” values in prescribed coverages, eg road names, etc
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
47
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
•
All entities have a PFI and UFI, and that within each table PFI and UFI is valid and unique
•
All entities have a Data Quality Pointer, that only valid DQ tables are used and that all DQ tables
are unique
•
All line drawing specifications adhered to, ie all lines are equal to or greater than the minimum line
length of 2.5 metres; (Cross border data may not comply with this standard)
•
All node types are valid, ie roundabout, signalised intersection, etc.
•
All line types are valid according to approved reference tables ie road, bridge, tunnel, etc.
•
All lines are delineated by nodes
•
There are no artefacts in the data, ie no overshoots, no undershoots, no duplicated line work, etc.
•
Software application to confirm topology and form polygons
•
There are no invalid structures (polygon, line, node, point only)
•
Virus-check software for digitally-supplied input data
•
Input check-list to prompt operator
•
Use of operator ‘pick-lists’ for standard inputs
•
5% of all maintenance Advice Notices processed are separately audited by DSE to confirm
accuracy, completeness and correctness in the capture process
•
Ongoing - Property and road details are being extensively validated against local government
records through the Property Information Program (PIP)
•
Ongoing – Customer feedback. Data anomalies identified by Vicmap users may be noted
(preferably using the PIP M1 and M2 forms developed for client feedback and forwarded to ISB
for investigation and, where required, rectification
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
48
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
2B. MINUMUM QUALITY STANDARD
PROPOSED/REQUIRED QUALITY ASSURANCE APPLICATIONS
Information Services Branch 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 Project (PIP) – reconciliation of property/parcel/road
information held by local government against Vicmap Digital Property;
•
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
•
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.
Attribute accuracy
•
Checks on existing data attribution is continuing and inconsistencies are being systematically
identified, removed and omissions added, eg. 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.
Completeness
•
Ongoing – review of features such as walking tracks, helipads, airports, ferry routes, fords and
bridges due to limited authoritative sources.
Information Services Branch 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:2003.
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
49
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
3.
Information Services Branch
Department of Sustainability and Environment
METADATA
Metadata at Page 0, and Page 1 levels has been created using a compliant metadata entry tool, and
has been added to the Victorian Spatial Data Directory (VSDD). VSDD entries may be viewed via
Information Services Branch’s website at www.dse.vic.gov.au/spatial or via the Australian Spatial Data
Directory site at http://www.erin.gov.au/net/asdd/.
The metadata complies with the Geospatial Information Metadata Guidelines for Victoria – part of the
Victorian Geospatial Information Strategy 2000-2003.
4.
PRICING
Under the Government pricing policy, data is supplied to customers on an annual access right to use
basis for an annual licence fee. The licence fee is aimed to recover the cost of maintenance and thus
ensure product continuity. The pricing of the data is dependent on the volume of data required,
measured by geographical area and intensity of use of the data, measured by the number of userseats/terminals upon which the data may be simultaneously used/viewed. The Government pricing
policy also contains provision for subsidies and credits.
•
Credits may be granted on licence fees in recognition for substantive contributions to the data set
by licensed users.
•
Subsidies may be applied to meet community or social objectives determined by government or
arising from agreed outcomes.
5.
ACCESS
Small packet/small geographical area of selected Vicmap Products can be accessed directly from the
Land Channel website on http://www.dse.vic.gov.au/vicmapdata. Customers wishing to access larger
areas or with special requirements should contact a Data Service Provider (DSP).
To facilitate more widespread and ready access, Vicmap Products are distributed by Data Service
Providers, with Department of Sustainability and Environment (DSE) taking a wholesale role. The
objective of this approach is to promote industry development, allowing DSE to focus on production
and development while DSPs focus on marketing and sales. There is a small group of users who
obtain Vicmap products directly from DSE, generally as a result of an existing contractual arrangement
or agreement. Multiple DSPs have been engaged to provide a competitive market. DSP’s are listed
on the Land Channel website on http://www.dse.vic.gov.au/vicmapdsp
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
50
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
APPENDIX A- REFERENCE TABLES
LAYER – ENTITY RELATIONSHIPS
Vicmap – TRANSPORT is maintained under contract to Spatial Information Infrastructure. The data
set is held in Oracle®, the spatial component of which is managed by ESRI’s ArcSDE®.
OVERVIEW OF TABLES AND THEIR INCLUDED FIELDS
This document sets out the layers, entities, attribute tables, and fields within these tables that
comprise the Vicmap Transport product data set. Those tables containing information are indicated
below. It should be recognised that not all fields may be populated at this time. Similarly, not all
‘types’ listed in the tables may necessarily be found in the data. The completion of any specific field
varies depending on information availability and capture program.
For update information access www.land.vic.gov.au/spatial under Vicmap Products.
This table details the feature types, entity types and attributes applicable to each of the layers within
the Transport theme.
Transport Theme Layer Entity Attribute Relationships
Aggregated Feature
Geometric Type
Road Infrastructure
Point
Included Entities
Class Specific
Attributes
related_feature_ufi
rotation
Ford
class_code
route_no
nre_route
Bridge
class_code
height_limit
road_id
route_no
nre_route
physical_condition
construction_type
Tunnel
class_code
height_limit
route_no
nre_route
Gate
structure_type
Intersection
Barrier
Level Crossing
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
51
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Aggregated Feature
Geometric Type
Included Entities
Class Specific
Attributes
Road
Line
Road Segment
road_name
Ford
road_type
Bridge
road_suffix
Tunnel
class_code
direction_code
route_no
nre_route
structure_height_limit
restrictions
road_seal
structure_
physical_condition
structure_
construction_type
left_locality
right_locality
structure name
Ferry Route
Line
Ferry Route
ferry_type
Rail
Line
Railway
structure_
Tramway
physical_condition
Railway Tunnel
road_rel
Railway Bridge
track_number_of
Railway Yard
structure_construction_ty
pe
rail_gauge
tourist_type
Rail Infrastructure
Point
Railway Exit
Point
Railway Station
Railway Tunnel
Railway Bridge
structure_physical_conditi
on
rotation
user_type
Airport
Infrastructure Area
Polygon
Runway
runway_number
Airport
Infrastructure
Line
Runway
runway_number
Point
Helipad
Airport
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
52
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Aggregated Feature
Geometric Type
Included Entities
Airport Area
Polygon
Airport
Class Specific
Attributes
Airport void
LAYER TABLE STRUCTURE
AIRPORT AREA (POLYGON)
Summary information
Description
A facility, either on land or water, where aircraft can take off and land;
usually consists of hard surfaced landing strips a control tower, hangars,
and accommodations for passengers and cargo.
Entity
Airport
Included terms
Aerodrome, Seadrome, Seaplane base, Landing Area, Apron, Taxiway
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE: TR_AIRPORT_AREA_POLYGON
COLUMN NAME
DATA TYPE
FIELD
SIZE
NULL
COLUMN DESCRIPTION
AUTH_ORG_CODE
VARCHAR2
4
Y
The code of the Authoritative
Organisation where the record is
sourced.
AUTH_ORG_ID
VARCHAR2
50
Y
The identifier of the Authoritative
Organisation where the record is
sourced.
HIERARCHY
VARCHAR2
4
Y
CASA hierarchy of Airports
ICAO CODE
VARCHAR2
4
Y
International
Civil
Aviation
Organisation unique identifier
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
RUNWAY_NUMBER
VARCHAR2
6
Y
Number of Runways associated with
the Airport
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality
record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
53
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
LOOK UP TABLE CODELISTS APPLICABLE:
TABLE:
TR_AIRPORT_HIERARCHY
Code
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
1
2
3
4
FEATURE CODES RANGES:
Feature_Type_Code
Description
airport
Aerodrome, Seadrome, Seaplane base, Landing Area, Apron, Taxiway
airport_void
Airport area void
AIRPORT INFRASTRUCTURE AREA (POLYGON)
Summary information
Description
A straight path used for landing and take-off of aircraft.
Entity
Runway
Included terms
Airstrip,Landing strip,Landing area
Entity Type
Spatial
ICSM Conformance
Conforms
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
54
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
TABLE:
Information Services Branch
Department of Sustainability and Environment
TR_AIR_INFRA_AREA_POLYGON
COLUMN NAME
DATA TYPE
FIELD
SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
RUNWAY_NUMBER
VARCHAR2
6
Y
Number of Runways associated with the
Airport
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
FEATURE CODES RANGES:
Feature_Type_Code
Description
runway
Runway perimeter, taxiways and parking areas
airport_void
Runway area void
AIRPORT INFRASTRUCTURE (LINE)
Summary information
Description
A straight path used for landing and take-off of aircraft.
Entity
Runway
Included terms
Airstrip,Landing strip,Landing area
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE:
TR_AIRPORT_INFRASTRUCTURE
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD
SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
55
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
RUNWAY_NUMBER
VARCHAR2
6
Y
Number of Runways associated with
the Airport
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality
record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
FEATURE CODES RANGES:
Feature_Type_Code
Description
runway
Linear runway
AIRPORT INFRASTRUCTURE (POINT)
Summary information
Description
An area set aside or designated for the landing of helicopters
Entity
Helipad
Included terms
Helicopter landing pad, helipad, heliport
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE:
TR_AIR_INFRA_POINT
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD
SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
RUNWAY_NUMBER
VARCHAR2
6
Y
Number of Runways associated with
the Airport
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality
record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
56
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
FEATURE CODES RANGES:
Feature_Type_Code
Description
helipad
Helipad
LOOK UP TABLE CODELISTS APPLICABLE: NONE
FERRY ROUTES (LINE)
Summary information
Description
A route across a river, lake or sea used by a vessel for the regular
transport of vehicles or passengers from one terminal point to another.
Entity
Ferry Route
Included terms
Hovercraft route, Hydrofoil route, Punt crossing point
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE:
TR_FERRY_ROUTE
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD
SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
FERRY TYPE
VARCHAR2
1
Y
Type of Ferry
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality
record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
FEATURE CODES RANGES:
Feature_Type_Code
ferry_route
Description
Ferry or Punt
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
57
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
LOOK UP TABLE CODELISTS APPLICABLE:
Ferry_type
Code
Description
1
Hovercraft
2
Hydrofoil
3
Punt
4
Boat
RAIL (LINE)
Summary information
Description
A permanent way having one or more rails which provide a track for trains
or trams.
Entity
Railway
Included terms
Abandoned railway, Disused railway, Double track railway, Light rail,
Monorail, Siding, Single track railway, Spur line, Tramway, Underground
railway
Entity Type
Spatial
ICSM Conformance
Conforms
Description
An underground or underwater passage.
Entity
Tunnel
Included terms
Cattle underpass,Pedestrian underpass,Subway,Underground railway
tunnel,Underpass
Entity Type
Spatial
ICSM Conformance
Conforms
Description
An area of land with one or more sidings or spur lines to allow trains to be
parked, serviced, assembled or unloaded
Entity
Railway yard
Included terms
Railroad yard, Marshalling yard
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE:
TR_RAIL
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
58
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
PHYSICAL_CONDITION
VARCHAR2
1
Y
Condition of Rail Infrastructure
ROAD_REL
VARCHAR2
1
Y
Code to indicate relationship of Rail to roads
[on road / off road or underground]
TRACKS_NUMBER_OF
VARCHAR2
1
Y
number of tracks
STRUCTURE_TYPE
VARCHAR2
1
Y
Type of Railway
STRUCTURE_NAME
VARCHAR2
45
Y
Name of the Structure
RAIL_GAUGE
VARCHAR2
1
Y
Rail track gauge
TOURIST_TYPE
VARCHAR2
1
Y
Flag to indicate tourist railway
FROM_UFI
NUMBER
(20,0 )
Y
UFI of Node Feature from which Rail Segment
starts
TO_UFI
NUMBER
(20,0 )
Y
UFI of Node to which the segment is going
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
FEATURE CODES RANGES:
Feature_Type_Code
Description
railway
Railway Line
rail_dismantled
Railway Dismantled
rail_disused
Disused Railway
marshalling_yard_rail
Marshalling Yard
rail_siding
Railway Siding
Bridge_rail_dm
Bridge – Rail Dismantled
bridge_rail_du
Bridge – Rail Disused
bridge_rail_o
Bridge – Rail Operational
rail_uground_dm
Underground Rail Dismantled
rail_uground_du
Underground Rail Disused
rail_uground_o
Underground Rail Operational
rail_trail
Rail Trail
rail_light
Light Rail
Tramway_o
Tramway
tram_dm
Tramway Dismantled
tram_du
Tramway Disused
Tunnel_o
Tunnel Operational
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
59
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Feature_Type_Code
Description
Tunnel_dm
Tunnel dismantled
Tunnel_du
Tramway Disused
LOOK UP TABLE CODELISTS APPLICABLE:
Road_Rel
Road Relationship
Code
Description
1
On Road
2
Off Road
3
Underground
Physical_condition
Code
Description
1
Dismantled
2
Disused
3
Operational
Rail_gauge
Code
Description
1
4' 8.5" Gauge (Standard)
2
3
5' 4" Gauge (Broad)
Both 4ft 8.5 in and 5ft 4in Gauge
4
2’ 6” Victorian Railways Narrow Gauge
5
3’ 6” Narrow Gauge
Structure_type
Code
Description
1
Light Rail
2
Tramway
3
Mono Rail
4
Normal Rail
5
Heavy Rail
6
Underground
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
60
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
RAIL INFRASTRUCTURE (POINT)
Summary information
Description
A point on a railway designated as a stopping place to set down or pick up
passengers or freight.
Entity
Railway Station
Included terms
Train stop, Light rail stop
Entity Type
Spatial
ICSM Conformance
Conforms
Description
Emergency exit from underground railway
Entity
Railway Exit
Included terms
Entity Type
Spatial
ICSM Conformance
New entity
TABLE:
TR_RAIL_INFRASTRUCTURE
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
PHYSICAL_CONDITION
VARCHAR2
1
Y
Condition of Rail Infrastructure
ROAD_REL
VARCHAR2
1
Y
Code to indicate relationship of Rail to roads
[on road / off road or underground]
USER_TYPE
VARCHAR2
1
Y
Type of Rail Station
ROTATION
NUMBER
(7,2 )
Y
Rotation angle [in degrees]
cartographic placement
FROM_UFI
NUMBER
(20,0 )
Y
UFI of Node Feature from which Rail Segment
starts
TO_UFI
NUMBER
(20,0 )
Y
UFI of Node to which the segment is going
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
of
symbol
for
FEATURE CODES RANGES:
Feature_Type_Code
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
Description
61
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
bridge_rail
Bridge - Rail
rail_station
Rail Station
tunnel_rail
Tunnel - Rail
rail_exit
Railway Exit
LOOK UP TABLE CODELISTS APPLICABLE:
TR_User_type
Code
Description
1
Railway Station
2
Light Rail Stop
3
Tram Stop
TR_Physical_condition
Code
Description
1
Dismantled
2
Disused
3
Operational
ROAD (LINE)
Summary information
Description
An open way for the passage of vehicles, persons or animals on land.
Entity
Road
Included terms
Access road, Alley, Boardwalk, Boulevard, Cart track, Causeway, Cul de
sac, Cycle path, Divided highway, Driveway, Elevated highway, Express
way, Farm track (N),Fire line, Fire track, Foot track, Footpath, Freeway,
Highway, Horse trail, Maintenance track, Path, Pedestrian mall, Private
road, ramp, Road on causeway, Service road, Ramp, Slipway, Bicycle
Track, Shared Pathway
Entity Type
Spatial
ICSM Conformance
Conforms
Description
An underground or underwater passage.
Entity
Tunnel
Included terms
Cattle underpass, Pedestrian underpass, Subway, Underground railway
tunnel, Underpass
Entity Type
Spatial
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
62
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
ICSM Conformance
Conforms
Description
A shallow or flat portion of the bed of a watercourse where a crossing may
be effected.
Entity
Ford
Included terms
Entity Type
Spatial
ICSM Conformance
Conforms
Description
A structure erected over a depression or obstacle to carry traffic or some
facility such as a pipeline.
Entity
Bridge
Included terms
Bicycle bridge, Covered bridge, Draw bridge, Foot bridge, Lift bridge,
Overpass, Pontoon bridge, Suspension bridge, Swing bridge, Viaduct
Entity Type
Spatial
ICSM Conformance
Conforms
TABLE:
TR_ROAD
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
EZI ROAD NAME
VARCHAR2
65
EZI ROAD NAME LABEL
VARCHAR2
65
Y
Combination of ROAD_NAME, ROAD_TYPE_
ABBREVIATIONS & ROAD_SUFFIX (where
appropriate) in title case
ROAD_NAME
VARCHAR2
45
N
Road name (Primary)
ROAD_TYPE
VARCHAR2
15
Y
Road name type (Primary)
ROAD_SUFFIX
VARCHAR2
2
Y
Road Name Suffix (Primary)
ROAD_NAME_1
VARCHAR2
45
Y
Road name (Alternate or Secondary)
ROAD_TYPE_1
VARCHAR2
15
Y
Road name type (Alternate or Secondary)
ROAD_SUFFIX_1
VARCHAR2
2
Y
Road Name Suffix (Alternate or Secondary)
ROAD_NAME_2
VARCHAR2
45
Y
Road name (Tertiary)
ROAD_TYPE_2
VARCHAR2
15
Y
Road name type (Tertiary)
ROAD_SUFFIX_2
VARCHAR2
2
Y
Road Name Suffix (Tertiary)
…………………………..
……………..
……….
………
…………………………………
ROAD_NAME_x
VARCHAR2
45
Y
Road name (x)
ROAD_TYPE_x
VARCHAR2
15
Y
Road name type (x)
ROAD_SUFFIX_x
VARCHAR2
2
Y
Road Name Suffix (x)
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
Combination of ROAD_NAME, ROAD_TYPE &
ROAD_SUFFIX
63
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
LEFT_LOCALITY
VARCHAR2
40
Y
Left of road locality name
RIGHT_LOCALITY
VARCHAR2
40
Y
Right of road locality name
CLASS_CODE
NUMBER
(2,0 )
Y
Code to indicate Road Classification
DIRECTION_CODE
VARCHAR2
1
Y
Direction Code to indicate possible traffic direction
ROUTE_NO
VARCHAR2
5
Y
VicRoads Route Number
STRUCTURE_NAME
VARCHAR2
45
y
Name of Structure
STRUCTURE
_HEIGHT_LIMIT
NUMBER
(3,1 )
Y
Height limit applicable to road section
ROAD RESTRICTIONS
CHAR
1
Y
Code to indicate any restrictions that apply to the
road section
STRUCTURE_PHYSICAL
_CONDITION
VARCHAR2
1
Y
Code to indicate the physical condition of a bridge
STRUCTURE_CONSTRU
CTION_TYPE
VARCHAR2
2
Y
Code to indicate construction type of bridges
ROAD_SEAL
VARCHAR2
1
Y
Code to indicate the Road surface type
NRE_ROUTE
VARCHAR2
5
Y
Department
of
Natural
Environment Route Number
FROM_UFI
NUMBER
(20,0 )
Y
UFI of Node Feature from which Road Segment
starts
TO_UFI
NUMBER
(20,0 )
Y
UFI of Node to which the segment is going
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
Resources
and
FEATURE CODES RANGES:
Feature_Type_Code
Description
road
Road Segment
roundabout
Road along Roundabout
connector
Road Connector
ford
Road along Ford
bridge
Bridge (to scale) #
foot_bridge
Foot Bridge (to scale)
tunnel
Road along Tunnel
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
64
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
LOOK UP TABLE CODELISTS APPLICABLE:
TR_Class_Code
Code
Description
0
Freeway
1
Highway
2
Arterial
3
Sub-Arterial
4
Collector
5
Local
6
2wd
7
4wd
9
Proposed
11
Walking Track
12
Bicycle Path
Road Class Code Definitions
Class Code
Class
Definition
0
Freeway
Hard surface formation, high volume, high speed roads
declared as “Freeway”; comprising dual carriageway and full
access control and grade separated intersections; ie no direct
access from adjoining properties or side roads and all
crossings are by means of overpass or underpass bridges with
traffic entering or leaving carriageways by means of ramps.
Single carriageway sections forming part of declared freeways
may be included within this category.
1
Highway
Hard surface roads which:
Are of importance in a national sense, and/or
Are of a major interstate through route, and/or
Are principal connector roads between capitals and/or major
regions and/or key towns.
2
Arterial
Well maintained and widely used hard surface formation roads
which are major connectors between:
Freeways and/or National Highways, and/or
Major centres, and/or key towns, or
Have major tourist importance or
Which main function is to form the principle avenue of
communication for metropolitan traffic movements, not catered
for by freeways.
3
Sub-Arterial
Hard surface formation road, which acts as:
A connector between highways and/or arterial roads, or
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
65
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
An alternate route for class 2 roads, or
A principal avenue for massive traffic movements.
4
Collector Road
Hard surface or improved, loose surface formation road acting
to:
Provide for traffic movement (connects class 3 to class 5), or
To distribute traffic to local street systems.
5
Local Road
Hard surface or improved, loose- surface formation road
providing property access.
6
Track 2-Wheel Drive
Unimproved roads which are generally only passable in two
wheel drive vehicles during fair weather and are used
predominately by local traffic.
Also included are driveways regardless of construction.
7
Track 4-Wheel Drive
Unimproved roads which are generally only passable with four
wheel drive vehicles.
9
Proposed
Road centreline alignments have been received from plans of
subdivision or VicRoads and are yet to be constructed or
construction is not complete.
11
Walking Track
A pathway designed for traffic on foot.
12
Bicycle Path
A pathway allowing bicycle traffic in the main. This is not a
shared road way with vehicular traffic.
TR_Direction_Code
Code
Description
F
Forward Direction of traffic with respect to digitized direction of feature
R
Reverse Direction of traffic with respect to digitized direction of feature
B
Traffic possible in both directions
Physical Condition
TR_Bridge_Physical_Condition
Condition relating to bridges
Code
Description
1
Operational
2
Closed
Construction
TR_Bridge_Construction_Type
Construction relating to bridges
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
66
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Code
Description
1
Bicycle Bridge
2
Covered Bridge
3
Draw Bridge
4
Foot Bridge
5
Lift Bridge
6
Overpass
7
Pontoon Bridge
8
Suspension Bridge
9
Swing Bridge
10
Viaduct
11
Conventional Bridge
Information Services Branch
Department of Sustainability and Environment
TR_Road_Seal
Road Surface description
Code
Description
1
Road Sealed
2
Road Unsealed
3
Unknown
TR_Road_Restriction
Road usage restriction description
Code
Description
1
Management Vehicles Only
2
Subject To Seasonal Closure
3
Subject To Height Or Weight Limits
4
Road Permanently Closed
5
Private Access
6
Road Unmaintained
7
Dry Weather Only
TR_Divided Road
Code
Description
DD
Divided Double Line (one line per carriageway) Representation
DS
Divided Single Centreline Representation
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
67
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
ND
Not Divided
U
Unknown
TR_Road Suffix
Code
A
B
BR
C
CN
DV
E
EX
IN
LR
ML
N
NE
NW
OF
ON
OT
S
SE
SW
UP
W
Description
A
B
Branch
C
Central
Deviation
East
Extension
Inner
Lower
Mall
North
North East
North West
Off
On
Outer
South
South East
South West
Upper
West
ROAD INFRASTRUCTURE (POINT)
Summary information
Description
A structure erected over a depression or obstacle to carry traffic or some
facility such as a pipeline.
Entity
Bridge
Included terms
Bicycle bridge, Covered bridge, Draw bridge, Foot bridge, Lift bridge,
Overpass, Pontoon bridge, Suspension bridge, Swing bridge, Viaduct
Entity Type
Spatial
ICSM Conformance
Conforms
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
68
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Description
An underground or underwater passage.
Entity
Tunnel
Included terms
Cattle underpass, Pedestrian underpass, Subway, Underground railway
tunnel, Underpass
Entity Type
Spatial Point
ICSM Conformance
Conforms
Description
A structure to prevent entrance or passageway.
Entity
Gate
Included terms
Boom gate, Bush gate, Cattle grid (N),Crossing gate, Gate
Toll barrier (N),Turnstile
Entity Type
Spatial Point
ICSM Conformance
Conforms
Description
A shallow or flat portion of the bed of a watercourse where a crossing may
be effected.
Entity
Ford
(N),Slip rails,
Included terms
Entity Type
Spatial
ICSM Conformance
Conforms
Description
road segment endpoint not at an intersection
Entity
Road end
Included terms
Entity Type
Spatial Point
ICSM Conformance
New entity
Description
The junction of roads or tracks.
Entity
Intersection
Included terms
Clover leaf interchange, Crossing, Diamond intersection, Grade crossing,
Interchange, Level crossing, Pedestrian crossing, Railroad crossing, Traffic
circle, Roundabout, signalized and non signalized intersection, intersection
with coast, drainage or administration boundaries
Entity Type
Spatial Point
ICSM Conformance
Conforms
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
69
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Description
Pseudo node delineating differences in line attributes ie.
change road to bridge.
Entity
Road node
Included terms
Int_attrubute
Entity Type
Spatial Point
ICSM Conformance
Conforms
TABLE:
Feature type
TR_ROAD_INFRASTRUCTURE
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
HEIGHT_LIMIT
NUMBER
(3,1 )
Y
Height limit applicable to road point
feature
PHYSICAL_CONDITION
VARCHAR2
1
Y
Code to indicate the physical condition
of a bridge
CONSTRUCTION_TYPE
VARCHAR2
2
Y
Code to indicate the type of dam wall
construction type
ROTATION
NUMBER
(7,2 )
Y
Rotation angle [in degrees] of symbol
for cartographic placement
STRUCTURE_TYPE
VARCHAR2
1
Y
Code to indicate type of barrier
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
70
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
FEATURE CODES RANGES:
Feature_Type_Code
Description
bridge
Bridge
tunnel
Tunnel
roundabout
Roundabout Road Intersection
level_crossing
Level Crossing (Road/Rail (tram) intersection)
ford
Ford
gate
Gate
barrier
Road Barrier
road_end
Logical road endings
int_admin
Road intersection by Administration boundary feature
int_attribute
Pseudo node resulting from differences in line attributes on either side of
node feature
int_coast
Road intersection by coast line feature
int_locality
Road intersection by Locality Boundary feature
int_nosignal
Roads Intersection – non signalised
int_signal
Roads Intersection – signalised
LOOK UP TABLE CODELISTS APPLICABLE:
TR_Physical_Condition
Condition relating to bridges
Code
Description
1
Operational
2
Closed
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
71
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
TR_Construction_Type
Bridge construction type
Code
Description
1
Bicycle Bridge
2
Covered Bridge
3
Draw Bridge
4
Foot Bridge
5
Lift Bridge
6
Overpass
7
Pontoon Bridge
8
Suspension Bridge
9
Swing Bridge
10
Viaduct
11
Conventional Bridge
TR_Structure_Type
Code
Description
1
Boom Gate
2
Bush Gate
3
Cattle Grid
4
Crossing Gate
5
Slip Rails
6
Toll Barrier
7
Turnstile
8
Gate
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
72
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
ROAD INFRASTRUCTURE (POINT)
Summary information
Description
A structure erected over a depression or obstacle to carry traffic or some
facility such as a pipeline.
Entity
Bridge
Included terms
Bicycle bridge, Covered bridge, Draw bridge, Foot bridge, Lift bridge,
Overpass, Pontoon bridge, Suspension bridge, Swing bridge, Viaduct
Entity Type
Spatial
ICSM Conformance
Conforms
Description
An underground or underwater passage.
Entity
Tunnel
Included terms
Cattle underpass, Pedestrian underpass, Subway, Underground railway
tunnel, Underpass
Entity Type
Spatial Point
ICSM Conformance
Conforms
Description
A structure to prevent entrance or passageway.
Entity
Gate
Included terms
Boom gate, Bush gate, Cattle grid (N),Crossing gate, Gate
Toll barrier (N),Turnstile
Entity Type
Spatial Point
ICSM Conformance
Conforms
Description
A shallow or flat portion of the bed of a watercourse where a crossing may
be effected.
Entity
Ford
(N),Slip rails,
Included terms
Entity Type
Spatial
ICSM Conformance
Conforms
Description
road segment endpoint not at an intersection
Entity
Road end
Included terms
Entity Type
Spatial Point
ICSM Conformance
New entity
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
73
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Description
The junction of roads or tracks.
Entity
Intersection
Included terms
Clover leaf interchange, Crossing, Diamond intersection, Grade crossing,
Interchange, Level crossing, Pedestrian crossing, Railroad crossing, Traffic
circle, Roundabout, signalized and non signalized intersection, intersection
with coast, drainage or administration boundaries
Entity Type
Spatial Point
ICSM Conformance
Conforms
Description
Pseudo node delineating differences in line attributes ie.
change road to bridge.
Entity
Road node
Included terms
Int_attrubute
Entity Type
Spatial Point
ICSM Conformance
Conforms
TABLE:
Feature type
TR_ROAD_INFRASTRUCTURE
TABLE DESCRIPTION:
COLUMN NAME
DATA TYPE
FIELD SIZE
NULL
COLUMN DESCRIPTION
PFI
NUMBER
(20,0 )
Y
Persistent Feature Identifier
UFI
NUMBER
(20,0 )
Y
Unique Feature Identifier
FEATURE_TYPE_CODE
VARCHAR2
30
Y
Feature Code
NAME
VARCHAR2
50
Y
name of a feature
NAMED_FEATURE_ID
NUMBER
(9,0 )
Y
Unique identifier for feature name
HEIGHT_LIMIT
NUMBER
(3,1 )
Y
Height limit applicable to road point
feature
PHYSICAL_CONDITION
VARCHAR2
1
Y
Code to indicate the physical condition
of a bridge
CONSTRUCTION_TYPE
VARCHAR2
2
Y
Code to indicate the type of dam wall
construction type
ROTATION
NUMBER
(7,2 )
Y
Rotation angle [in degrees] of symbol
for cartographic placement
STRUCTURE_TYPE
VARCHAR2
1
Y
Code to indicate type of barrier
FEATURE_QUALITY_ID
NUMBER
(9,0 )
Y
Identifier for the feature quality record
CREATE_DATE_PFI
DATE
7
Y
Date of original Creation of Feature
SUPERCEDED_PFI
NUMBER
(20,0 )
Y
PFI of feature prior to merge or split
operation
CREATE_DATE_UFI
DATE
7
Y
Date of Creation of Feature
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
74
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
FEATURE CODES RANGES:
Feature_Type_Code
Description
bridge
Bridge
tunnel
Tunnel
roundabout
Roundabout Road Intersection
level_crossing
Level Crossing (Road/Rail (tram) intersection)
ford
Ford
gate
Gate
barrier
Road Barrier
road_end
Logical road endings
int_admin
Road intersection by Administration boundary feature
int_attribute
Pseudo node resulting from differences in line attributes on either side of
node feature
int_coast
Road intersection by coast line feature
int_locality
Road intersection by Locality Boundary feature
int_nosignal
Roads Intersection – non signalised
int_signal
Roads Intersection – signalised
LOOK UP TABLE CODELISTS APPLICABLE:
TR_Physical_Condition
Condition relating to bridges
Code
Description
1
Operational
2
Closed
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
75
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
TR_Construction_Type
Bridge construction type
Code
Description
1
Bicycle Bridge
2
Covered Bridge
3
Draw Bridge
4
Foot Bridge
5
Lift Bridge
6
Overpass
7
Pontoon Bridge
8
Suspension Bridge
9
Swing Bridge
10
Viaduct
11
Conventional Bridge
TR_Structure_Type
Code
Description
1
Boom Gate
2
Bush Gate
3
Cattle Grid
4
Crossing Gate
5
Slip Rails
6
Toll Barrier
7
Turnstile
8
Gate
Vicmap Transport Prod Desc V3_2 for PDF.doc
Data Dictionary
Appendix A
76
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
APPENDIX B- DATA MODEL
Please refer to the data models on the DSE website:
http://www.dse.vic.gov.au/property-titles-and-maps/maps-imagery-and-data/data/vicmap/vicmapproducts/vicmap-transport
Version 3.1 February 2010
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
77
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Class: spatial_feature
Definition: A spatial feature within the dataset
Features: Spatial
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
Identifier
feature
Name
the
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
created on
date
for
ufi
was
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.
Aggregated Feature
Type Attribute
Entities
Feature Type Codes
Road Infrastructure
Road
Infrastructure_type
Ford
ford
Bridge
bridge
Tunnel
tunnel
Gate
gate
Barrier
barrier
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
78
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Aggregated Feature
Information Services Branch
Department of Sustainability and Environment
Type Attribute
Entities
Feature Type Codes
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
Refer to Appendix A DATA DICTIONARY, for a full list of feature codes adopted for the Vicmap
Transport database.
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 Information Infrastructure 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 :1. Attributes of a feature are modified
2. 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.
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
79
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
•
Information Services Branch
Department of Sustainability and Environment
Superceded_UFI; This is the UFI of a feature prior to the last edit of the feature
Incremental Update Attributes:
The following Attributes for the new Incremental Update Model for VDRT are:
Attribute
Data Type
Description
PFI
Number
Persistent Feature Identifier
Create_date_PFI
Date
Date that PFI originally created
Retire_date_PFI
Date
Date that PFI retired as a result of merge, split, or feature
discontinuance (deletion)
Superceded_PFI
Number
PFI of feature before merge or split operation
Create_Type_code
Varchar
Type of action that caused creation of feature
UFI
Number
Unique Feature Identifier – assigned at every feature creation
or edit
Create_date_UFI
Date
Date that UFI created
Retire_date_UFI
Date
Date that UFI retired
Superceded_UFI
Number
Value of UFI on the feature prior to last edit
Change_Type_code
Varchar
Type of edit undertaken on feature at last edit
Proposed VDRT Incremental Update Attributes – Spatial Tables
In addition all LINKAGE tables will have the following items:
Attribute
Data Type
Description
UFI
Number
Unique Feature Identifier – assigned at every feature creation
or edit
Create_date_UFI
Date
Date that UFI created
Retire_date_UFI
Date
Date that UFI retired
GENERAL REFERENCE CLASSES
Feature Quality Class Attributes
Class: feature_quality
Definition: Defines accuracy and other quality information pertaining to this spatial feature
Features: Aspatial
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
80
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Name
Data Type
Definition
id
IDENTIFIER FOR THE FEATURE
number
Code
List
Key
Mandatory
yes
yes
QUALITY RECORD
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
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
LOOK UP 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:Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
81
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
scale
40
source
Information Services Branch
Department of Sustainability and Environment
theoretical plan_acc
Formula Used
adopted plan_acc
0
scale*0.00063
0.5
1, 32 (cadas)
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
scale * 0.00033
0.5
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
All other
sources
scale * 0.00033
9999999
Round up to appropriate whole
metre
9999
9999
Data Source Class Attributes
Class: data_source
Definition: The source of the data in this dataset
Features: Aspatial
Name
Definition
Data Type
code
Source code
number
name
Data source name
character
yes
description
Source description
character
no
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
Code List
Key
Mandatory
yes
yes
82
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
Data Layer Class Attributes
Class: Layer
Definition: The layer to which the features belong
Features: Aspatial
Name
Definition
Data Type
Code List
Key
Mandatory
Code
Layer code
number
yes
yes
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
Key
Mandatory
Code
Theme code
number
yes
yes
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
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
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
Code List
Key
Mandatory
yes
yes
83
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Information Services Branch
Department of Sustainability and Environment
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
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
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
Code List
Key
Mandatory
yes
yes
84
PRODUCT DESCRIPTION
VICMAP TRANSPORT
Version 3.2
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
Information Services Branch
Department of Sustainability and Environment
85
PRODUCT DESCRIPTION
[PRODUCT NAME]
APPENDIX
Version ?.?
Information Services Branch
GLOSSARY
[Subject/Term]
[Definition]
Source (if applicable)
Area Feature
A feature which is portrayed as a region or surface. An area feature is bounded by one or more
polygons.
AS2482
Australian Standard 2482 defines Geographic information systems – Geographic data – Interchange of
feature-coded digital mapping data.
Attribute
A particular characteristic or property of an entity. Attributes can be spatial (or locational) and aspatial
(or non-locational).
Attribute Object
The addition of non-locational information about a feature instance. These data identify the feature
class and the aspatial attributes of a specific instance of the feature type. The attribute object is
composed of one or more attributes.
Attribute Value
The value assigned to an attribute for a specific feature instance.
CAD
Computer-Aided Design is the production of drawings, specifications, parts lists, and other designrelated elements using special graphics- and calculations-intensive computer programs. CAD systems
originally merely automated drafting but now often include three-dimensional modelling and computersimulated operation of the model.
Chain
A line composed of a sequence of non-intersecting line segments bounded by nodes. Chains reference
the polygons to the left and right of the chain.
Data
The base level of information stored in electronic databases. Generally, “raw” data has not been valueadded.
AUSISB at www.ausISB.gov.au
Entity
A real world phenomenon not divided into phenomena of the same kind.
Feature Instance
An abstraction of an entity. The description of a feature instance encompasses only selected properties
of that entity. Feature instances can also be referred to as features.
Feature Type
A class of real world phenomena with common properties.
A group of feature instances defined by a set of rules and having common attributes and relationships
that are properties of the corresponding real world phenomena. Within the Oracle tables that comprise
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
86
PRODUCT DESCRIPTION
[PRODUCT NAME]
APPENDIX
Version ?.?
Information Services Branch
Vicmap Digital Property, classes may refer to “link” tables, which establish direct relationships between
the point and/or line and/or polygon structures that may be used as spatial objects.
The feature structure of the feature based data model can be summarised as:
feature instance = [spatial object + attribute object]
GDA94
The Geocentric Datum of Australia 1994 is based on the Australian Fiducial Network (AFN) which fits
into a global geodetic framework. The AFN comprises eight highly accurate survey marks across
Australia each with a permanently tracking Global Positioning System (GPS) receiver. It has been
established by AUSISB for geodetic surveying and scientific purposes.
GeoCASE
The modelling tool is a proprietary computer-aided software engineering product called GeoCASE. It is
based on the entity–relationship (E–R) model extended to suit an object-oriented approach to
representing the real world. (See Ross Honeyman)
GIS
Geographic Information System. A spatial database which is manipulated with a set of spatial operators
or commands.
ICSM
Intergovernmental Committee on Survey and Mapping. ICSM's role is to provide leadership through
coordination and cooperation in surveying, mapping and charting. ICSM's core function is to coordinate
and promote the development and maintenance of key national spatial data including geodetic,
topographic, cadastral, street addressing, tides, topographic information & sea level, and geographical
names.
IUF : “Incremental Update Format”
A system whereby maintenance updates are provided as change only, add/modify/delete incremental
update files, between nominated dates/times.
Information Services Branch
A body within Department of Sustainability & Environment, responsible for spatial policy for the State
and for providing and maintaining a statewide spatial infrastructure, including the Victorian Geodetic
Framework and Vicmap Digital.
Layer
Subdivision of a theme into one or more layers of data on the basis of topological relationships. Linear
networks, polygons and point/line features are placed in separate layers.
Linear Network
A theme layer consisting of linear features which are connected forming a pathway along which
movement is possible.
Metadata
Metadata, defined as ‘information about information’, provides fundamental information management
tools at three levels:
• Discovery: enabling users to locate and evaluate information.
• Management: enabling custodians to better manage their spatial information.
• Utilisation: enabling users to access and manipulate information by means of automated /
distributed systems.
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
87
PRODUCT DESCRIPTION
[PRODUCT NAME]
APPENDIX
Version ?.?
Information Services Branch
MGA94
Map Grid Australia. A cartesian coordinate system based on the Universal Transverse Mercator
projection on the Geocentric Datum of Australia 1994. The unit of measure is the metre.
Node
A point that is a junction of two or more chains or which is the end point of a chain.
Node/Chain Structure
The structuring of linear features in a theme layer so that they consist of chains broken by nodes at
intersections or at the point where an attribute of the feature changes.
Persistent Feature identifier (PFI)
Unique Feature Identification (each feature is uniquely identified for change management) is managed
through the use of two identifier attributes; namely the Persistent Feature identifier (PFI) and the Unique
Feature Identifier (UFI).
See also Unique Feature Identifier(UFI)
Polygon
A set of chains used to define the boundaries of an area. There is one external polygon and there may
be one or more internal, non-nested polygons.
Positional Accuracy
Statistical estimate of the degree to which planimetric coordinates and elevations of features agree with
their real world values.
SDE
Spatial Data Engine – an ESRI product
Software used by Information Services Branch to manage the spatial component of it’s Unified Data
Store, which includes copies of the whole of the Vicmap Digital product suite.
SDTS
The United States Spatial Data Transfer Standard. This standard is to be the basis of the new
Australian Standard for the transfer of spatial digital data.
Segment
A direct line between a pair of points, or a point and a node.
Sliver
Long, thin triangle or polygon of very small area formed by overlaying of almost-coincident lines. Often
a result of twice-digitising the same linear feature.
Spatial Object
The addition of all of the locational attributes of the feature instance and may comprise geometrical
objects such as points, lines and polygons. Spatial objects carry a spatial address that consists of one
or more couplets (x, y) or triplets (x, y, z) of co-ordinates. In the feature based data model topological
relationships will be carried as part of the spatial object whenever the transfer formats support them.
Theme
The information contained in the map production material can be divided into themes which contain
logically-related geographic information, each theme capable of being used as a data set in its own
right. Vicmap Transport contains a single theme: “Roads”
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
88
PRODUCT DESCRIPTION
[PRODUCT NAME]
APPENDIX
Version ?.?
Information Services Branch
Unique Feature identifier (UFI)
Unique Feature Identification (each feature is uniquely identified for change management) is managed
through the use of two identifier attributes; namely the Persistent Feature identifier (PFI) and the Unique
Feature Identifier (UFI).
See also Persistent Feature Identifier (PFI)
VSIS 2011-14
In 2008, the Victorian Spatial Council’s Victorian Spatial Information Strategy 2008-101 introduced the
strategic goal of creating a ‘spatially enabled Victoria’.
The role of the Strategy is to create the frameworks that enable all sectors of the spatial information
community2 to be highly engaged and their efforts integrated towards delivering a spatially enabled
Victoria.
Development of this 2011-14 Strategy has allowed the Council to review the landscape it painted in
2008 and set out the requirements for continuing to respond to the challenges associated with meeting
this goal.
VSIS 2011-2014 incorporates four integrated strategic directions:
• Creating a framework in which the use of spatial information can flourish.
• Adopting an inclusive approach to the management of spatial information
• Developing the spatial information community through collaboration and partnerships
• Maintaining the foundations for spatial information management.
Further information http://victorianspatialcouncil.org/
Vicmap
Vicmap is a set of spatially related data products made up from individual datasets. They are the
underlying foundation to Victoria's primary mapping and geographic information systems.
Vicmap products are produced and managed by Information Services Branch, Department of
Sustainability and Environment. Further Information- www.dse.vic.gov.au/lvicmap
Transport_Prodesc_2.4.doc
Data Dictionary
Appendix A
89