Technology and Environment Directorate
Road and Traffic Engineering Branch
Document No. 67/08/121
Issue Date 20/06/2005
DIGITAL SERVICES MODELS
This document is owned and controlled by the Survey & Mapping Manager.
The Data Manager is the delegated custodian.
All comments for revision should be submitted to the Data Manager.
Authorisation
As Executive Director of the Technology and Environment Directorate of Main Roads, I
authorise the issue and use of this standard.
..............………………........................................................
EXECUTIVE DIRECTOR TECHNOLOGY AND ENVIRONMENT
Date: ___/ ___/ ___
No controlled copies are issued for this standard.
The latest copy of this standard is located on the Main Roads Internet site.
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 1 of 15
REVISION STATUS RECORD
Page
No
Latest
Revision
No
Latest
Revision
Date
Revision
Description/Reference
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Authorised by : ________________________________
Survey & Mapping Manager
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Date
____/____/____
Page 2 of 15
CONTENTS
1.
PURPOSE................................................................................................................. 4
2.
SCOPE ...................................................................................................................... 4
3.
REFERENCES ........................................................................................................ 4
4.
DEFINITIONS AND INTERPRETATIONS ....................................................... 4
5.
DIGITAL SERVICE MODELS ............................................................................. 5
5.1
Coordinate System and Datum .............................................................................. 5
5.2
MX Genio files. ........................................................................................................ 5
5.3
String Compression ................................................................................................. 5
5.4
Verification of Services ........................................................................................... 6
5.5
Services Extent Data File ........................................................................................ 6
5.6
Entry onto Land if service location verification is required................................ 6
5.7
Service Report .......................................................................................................... 7
5.8
MX Services Data file labels. .................................................................................. 7
6.
MEDIUMS FOR DIGITAL DATA ....................................................................... 8
APPENDIX A ....................................................................................................................... 9
APPENDIX B ..................................................................................................................... 10
APPENDIX C ..................................................................................................................... 15
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 3 of 15
1.
PURPOSE
The purpose of this Standard is to establish the requirements of all work related to the
capture of Digital Service Models for Main Roads. All work must be performed and
presented in accordance with the following standard to ensure that Main Roads has
continuity in standard, quality and procedure.
2.
SCOPE
This Standard must apply to all work related to the supply of Digital Service Models.
Advice and further information on this standard can be obtained by contacting the Data
Manager, Road and Traffic Engineering Branch, Main Roads.
3.
REFERENCES
The following documents relate to this procedure:
Guide to the Design of Relocation Protection of Services
67-08-33 Data License/Copyright
67-08-43 Digital Ground survey
67-08-44 Digital Photogrammetric Mapping
“Entry onto Land Process Guidelines”
4.
DEFINITIONS AND INTERPRETATIONS
The following terms used in this procedure have the specific meanings indicated:
Contractor - the party named in the Contract to perform the Services
Main Roads - Main Roads Western Australia
AHD - Australia Height Datum.
3D - Three Dimensional
2D - Two Dimensional
MX - MOSS software
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 4 of 15
5.
DIGITAL SERVICE MODELS
The purpose of this standard is to establish the minimum requirements for digital service
models for Main Roads. All services data must be supplied digitally, and must be
accompanied with a report and metadata.
To search for existing services data, dial before you dig (Ph 1100) or web site
http://www.dialbeforeyoudig.com.au must be used.
All data and reports generated from the use of this standard must be lodged with the Data
Manager within the Road and Traffic Engineering Branch, Main Roads.
5.1
Coordinate System and Datum
All services data must be compiled into the local Main Roads approved project zone. All
3D services data must relate to the Australian Height Datum (AHD). The local project
zone will be provided by the Main Roads project manager or the Senior Geodetic Surveyor.
5.2
MX Genio Files.
All services information must be presented digitally as MX genio files.
Only Main Roads feature codes detailed at Appendix A can be used. Any additional codes
required must be obtained from the Data Manager, Road and Traffic Engineering Branch,
Main Roads. All additional codes must be clearly noted within the services report.
All services without levels must be given a null level of –999.000
5.3
String Compression
All service strings supplied in MX Genio files must be compressed to ensure that the
number of captured labels do not exceed the permutation of possible labels available.
Compression software can be obtained from the Data Manager, Road and Traffic
Engineering Branch, Main Roads. Acknowledgement must be written within the services
report that the MX Genio files supplied to Main Roads have been compressed.
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 5 of 15
5.4
Verification of Services
Underground services are not to be verified unless specified in the Main Roads request.
If a services model is being captured in conjunction with a digital ground survey or
photogrammetric mapping survey, then all above ground services data must be upgraded to
the same standard as the requested ground survey standard (ie 67-08-43 Digital Ground
Survey or 67-08-44 Digital Photogrammetric Mapping standard.)
If a verified services model is requested and there is no ground survey request, then all
service data must be picked up in accordance with the 67-08-23 Digital Ground Survey
standard.
All services data must have their positional accuracy stated within the services report.
5.5
Services Extent Data File
An outline of the services investigation area must be supplied in a single file and labelled
as a two-dimensional “B” string. The string must form a closed polygon.
5.6
Entry onto Land
It will be the contractor’s responsibility to obtain permission from landowners, custodians
and governing bodies before entering any property to investigate or coordinate the capture
of any services. The Main Roads project manager, on request, will supply the contractor
with an appropriate letter to facilitate entry for this purpose. If a problem with accessing
property arises, then entry onto land must follow Main Roads Corporate Policy “Entry onto
Land Process Guidelines”.
The contractor will maintain a written record of all contact made with landowners when
performing fieldwork. These records shall be supplied as part of the services report.
Where any land or property proposed for inspection or investigation is on a Crown
Reserve, National Park, designated Aboriginal Site, protected under Native Title or any
other encumbrance, the contractor must obtain all necessary clearances from the
appropriate authorities and/or occupiers of the land to effect such inspection, investigation
or work.
All queries by the landowners with respect to the project work, are to be referred to the
Main Roads project manager.
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 6 of 15
5.7
Service Report
A Digital Services Model report must be supplied.
The report must contain the following headings:







Scope of work.
Contact names and numbers for services providers.
Services faxes and information received from the services provider.
Project issues. (Including a statement that string compression was used on the MX
Genio service file.)
If there were any field verifications performed, what was done and the location of
the works.
Metadata for all lodged information. A sample metadata statement is detailed at
Appendix C. This must include an expected accuracy for each service.
Any issues relating to entry onto land and / or contact with landowners.
All service reports must be lodged in both hard copy and soft copy (Microsoft Office 2000
compatible) formats.
5.8
MX Services Data File Labels.
All supplied data must be provided to Main Roads in a digital services file.
Digital files shall be named in accordance with Main Roads Document 67-08-87 Data
Model and String Naming Guideline.
For example, if the Great Northern Highway (Road number H6) had services collected
within the road reserve corridor from SLK 25 – 55 then the data files will be labelled
H6_25_55_serv.gen.
This data file must be accompanied with the extent data file. This data file will be labelled
H6_25_55_ext.gen.
Relevant Road Numbers are available from the project manager.
Genio format must be as per Appendix B and are to be in accordance with Main Roads
feature codes detailed at Appendix A.
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 7 of 15
6.
MEDIUMS FOR DIGITAL DATA
Digital Data must be presented on either of the following mediums:
CDs
-
CD-R or CD-RW
700 MB
Windows XP compatible.
and / or
DVDs
MAIN ROADS WA
106746373
-
DVD-R or DVD-RW
4.7 GB
Windows XP compatible.
Services
Standard 67-08-121
Page 8 of 15
APPENDIX A
FEATURE CODES
NOTE:
(RHR) - Right Hand Rule for Data Capture
(LHR) - Left Hand Rule for Data Capture
(ie Object on right or left of string defined in direction of capture)
MULTIPLE LIGHT POLE
LMØ1
WATER BORE
PWB1
ELP
ELØ1
STANDPIPE
PST1
ELP (MRWA)
EMØ1
WATER PIPE
WPØ1
POWER POLE
PPP1
RETICULATION SPRINKLER
PRT1
TRANSFORMER (SINGLE)
PET1
TAP
PWT1
TRANSFORMER (DOUBLE)
ETØ1
WELL
PWL1
STAY POLE
PSP1
WATER MAIN MARKER
PWR1
STEEL WIRE ANCHOR
PWA1
RETICULATION CONTROL VALVE
PSU1
HIGH MAST LIGHTING
PHL1
GAS MARKER
PGM1
ELECTRIC CABLE MARKER
PSC1
GAS VALVE
PGV1
MRWA CABLE MARKER
PCM1
GAS MANHOLE
EGØ1
MRWA ELECTRIC CABLE BOX
PRE1
GAS LINE
EHØ1
ELECTRIC CABLE BOX
PEC1
GAS TEST VALVE
PGU1
HIGH TENSION PYLON
EPØ1
MRWA DISTRIBUTION BOARD
PDB1
WAWA DRAINAGE MANHOLE
DWØ1
OVERHEAD POWER LINES
EAØ1
MRWA DRAINAGE MANHOLE
DRØ1
HIGH TENSION POWER POLE
PHT1
SIDE ENTRY PIT
DXØ1
MRWA ELECTRIC SUPPLY POLE
PPE1
UNDEFINED MANHOLE
DUØ1
GROUND FLOODLIGHT
PGF1
GULLY
DGØ1
MRWA ELECTRIC MANHOLE
EUØ1
LGA DRAINAGE MANHOLE
DLØ1
DRAINAGE PIPE
DPØ1
TELECOM MANHOLE
VMØ1
SEWERAGE PIPE
DVØ1
TELECOM PIT OR BOX
PPB1
SEWERAGE MANHOLE
DSØ1
TELECOM PILLAR
PTP1
SEWER VENT
PSW1
TELECOM MARKER
PTM1
SEWER LINE MARKER
PSX1
TELECOM POLE
PPT1
TELEPHONE BOOTH
PFB1
RAILWAY PLATFORM
RZØ1
EMERGENCY PHONE
PEP1
ON RAIL
RYØ1
TELECOM TOWER
VTØ1
RAIL TRAFFIC SIGNALS
PRS1
TELECOM CABLE
VCØ1
RAIL TRAFFIC CONTROL BOX
PRC1
ANTENNA
PAN1
RAIL TELEPHONE BOX
PPR1
TELECOM ELEVATED JOINT
PTJ1
RAIL CABLE PIT OR BOX
PRB1
WATER METER
PWM1
RAIL BOOM GATE
GXØ1
STOP VALVE
PSV1
RAIL CABLE MARKER
PRX1
HYDRANT (GROUND)
PHG1
RAIL CABLE MANHOLE
DZØ1
HYDRANT (PILLAR)
PHP1
RAIL UNDERGROUND CABLE
ERØ1
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 9 of 15
APPENDIX B
MX GENIO FORMAT
REQUIREMENT FOR GENIO OPTION
All data must be suitable for input via the generalised input and output (GENIO) option of MX,
and labelled in accordance with the MX Codes given at Appendix A. All point features (those
commencing with P) within the project, are to be grouped and supplied as a single string for each
point feature type used. The specific formats required are as follows.
MX HEADER
Each digital file must be headed by a DELETE, CREATE and GENIO statement with the project
name, followed by the appropriate ORDR (minor option 003) and FORMAT (minor option 00 )
statements, as per the example below.
Only alphanumeric values can be used for a project name with the project name meeting the
definition requirements as defined in the Survey and Mapping Guideline available at the following
website address
http://www.mainroads.wa.gov.au/standards/guidelines_survey_&_mapping/data_management/con
ventions/index.html
MOSS, EXAMPLE OF GENIO HEADERS FOR DATA FILES
DELETE,PROJECT NAME
CREATE,PROJECT NAME
GENIO,PROJECT NAME
003,ORDR,4=3,1,2
001,FORMAT (6F13.3)
} Header
> GENIO project name
> Order statement
> Format Statement
Note:
1. 003,ORDR,4=3,1,2 defines 3 points per line each having an easting (1) and northing (2). This is
the format for special 2D strings (contours) with the contour height detailed in field 4 of the
080 option.
For 3D strings the presence of an RL is denoted by the minor option 003,ORDR,4= 2,1,2,3
which defines two points per line with each point having an easting (1), Northing (1) and an RL
(1).
The ORDR statement precedes the initial format statement in the file and from there only
requires defining where (before the 080 option) a string dimension changes. Eg: 2D changes to
a 3D string
2. 001FORMAT(6F13.3) defines 6 fields of 3 characters (9 integer, 1 decimal point and 3
decimal places).
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 10 of 15
APPENDIX B … cont
MINOR OPTION 080 General input of strings
Minor option 080 stores string information created external to MX, such as ground survey
information.
All strings must be headed by the input minor option 080. Additive constants for easting and
northing origin may be included if required, in which case they automatically are added to each
first and second dimension of the point information.
080 header records can be supplied in fixed format as per the defined columns (), or in comma
delimited format including shortcuts [ie. Field 4 defined by 4=], as shown in the following:
Minor Option 080
Field 1
(4-7)
Field 2
(8-11)
Field 4
(12-23)
Field 5
(24-33)
Field 6
(34-43)
Field 7
(44-51)
Field 8
(52-61)
&9 &(62-71)
Field 10
String Label
Sub Reference (if required)
Contour Level for a 2D string
Origin Easting (Optional)
Origin Northing (Optional)
Dimension of string being created
Number combination to be used to signify the end of the
string - The default values are 0.0, 0.0. If a string is to input
with the coordinates (0.0, 0.0) then another combination such
as 999999.9, 999999.9) or -1.0, -1.0 must be used.
Horizontal optimising tolerance (code a negative
number).
(72-80)
Or
080,Label,4=RL,Easting Constant,Northing Constant, 2
080,Label,5=Easting Constant,Northing Constant, 3
> For 2D
> For 3D
2D strings - 3 points per record
The main use of 2D strings is for the supply of contours.
The default ORDR (ORDR,4=3,1,2) for 2D detail strings is shown below, represented as 3 points
per record in the format (6F13.3). The Level is supplied in the 080 statement.
If the string has a null level value (unknown or not required), -999 is shown in field 4 of the 080
option.
Columns
1-13
14-26
27-39
40-52
53-65
66-78
MAIN ROADS WA
106746373
) First Point
)
) Second Point
)
) Third Point
)
Easting
Northing
Easting
Northing
Easting
Northing
Services
Standard 67-08-121
Page 11 of 15
APPENDIX B … cont
EXAMPLE
003,ORDR,4=3,1,2
001FORMAT(6F13.3)
080RBØ2
30.00
54264.317
259402.308
54273.334
259380.103
-9999.000
-9999.000
0.000
0.000
2.00
54265.852 259399.058
54276.229 259370.331
-9999.000 -9999.000
54269.857
259389.684
54276.984
259367.398
3D strings - 2 points per record
3D strings are used for the definition of most detail features.
The default ORDR (ORDR, 4=2,1,2,3) for a 3D detail string is shown below, represented as 2
points per record in the format (6F13.3).
Columns
1 -13 Easting
14-26 Northing
27-39 3rd Dimension (Level)
40-52 Easting
53-65 Northing
66-78 3rd Dimension
) First Point
)
) (-999 for null level)
) Second Point
)
) (-999 for null level)
EXAMPLE
003,ORDR,4=2,1,2,3
100 FORMAT(6F13.3)
080RBØ3
53631.377
260047.804
53694.647
259985.595
-9999.000
-9999.000
0.000
0.000
3.00 -9999.000
29.580
53660.767
260019.494
29.905
53726.864
259951.926
-9999.000
-9999.000
29.823
29.857
Minor option 080 Input of Alphanumeric (Text) Strings
For text strings the input format is: 001FORMAT(4F 3.3,/,40A4)
The oblique (/) defines that each string consists of 2 lines with the character information contained
in the second line.
Alphanumeric text strings are input with 080 header lines and differ from other strings in that they
can be of different dimensions, however the initial string label character must be "*". The content
of the 080 strings is as defined in MINOR OPTION 080 General input of strings and utilises
fields 1, 5, 6, 7, 8 and 9.
The dimension of the string (as defined by field 7 of the 080 option) is based on the number of
characters and is calculated as follows:
Dimension = 4 + Number of Characters
4
NOTE: Spaces within text are included as characters. If the number of characters is not strictly
divisible by 4 then the dimension must be rounded up to the next whole number.
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 12 of 15
APPENDIX B … cont
For example, the characters
GREAT would have dimension 4 + 5/4 = 6 whereas
GREAT NORTHERN would have dimension 4 + 14/4 = 8 and
GREAT NORTHERN HIGHWAY would have 4 + 22/4 = 0.
The first line following the 080 statement contains the following four dimensions in a format of 4F
3.3.
1.
2.
3.
4.
X coordinate of bottom left of first character.
Y coordinate of bottom left of first character.
Height of characters.
Whole circle bearing of the baseline of characters stored as radians.
The next line contains the text to a maximum 44 characters. A standard terminating line follows
this with the terminator number in fields 1 and 2 of 4F 3.3.
A blank line must be inserted before the commencement of the next string.
 After generating an alphanumeric string, the string elements cannot be modified. The string
can only be deleted as a whole.
 The dimension of the string needs to be defined in relation to the maximum number of
characters to any one point on the string.
EXAMPLE
00 FORMAT(4F13.3,/,40A4)
080*001
0.000
0.000
54286.037
259396.996
0.300
GREAT NORTHERN HIGHWAY
-9999.000
-9999.000
080*001
0.000
0.000
54286.037
259396.996
0.300
GREAT EASTERN HIGHWAY
-9999.000
-9999.000
999
FINISH
MAIN ROADS WA
106746373
10.00
-3.950
-9999.000
0.00 -9999.000
-3.950
Services
Standard 67-08-121
-9999.000
-9999.000
Page 13 of 15
APPENDIX B … cont
EXAMPLE OF A FILE CONTAINING EACH LINE TYPE
DELETE,MX EXAMPLE
CREATE,MX EXAMPLE
GENIO,MX EXAMPLE
003,ORDR,4=3,1,2
001FORMAT(6F13.3)
080RBØ2
30.00
0.000
0.000
2.00 -9999.000 -9999.000
54264.317
259402.308
54265.852 259399.058
54269.857
259389.684
54273.334
259380.103
54276.229 259370.331
54276.984
259367.398
-9999.000
-9999.000
003,ORDR,4=3,1,2,3
001FORMAT(6F13.3)
080RBØ3
0.000
0.000
3.00 -9999.000 -9999.000
53631.377
260047.804
29.580
53660.767
260019.494
29.823
53694.647
259985.595
29.905
53726.864
259951.926
29.857
-9999.000
-9999.000
-9999.000
00 FORMAT(4F13.3,/,40A4)
080*001
0.000
0.000
0.00 -9999.000 -9999.000
54286.037
259396.996
0.300
-3.950
GREAT NORTHERN HIGHWAY
-9999.000
-9999.000
001FORMAT(4F13.3,/,40A4)
080*001
54286.037
259396.996
NORTHERN HIGHWAY
-9999.000
-9999.000
0.000
0.000
0.300
8.00 -9999.000
-3.950
-9999.000
999
FINISH
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 14 of 15
APPENDIX C
SERVICES METADATA SHEET
Metadata Category
Dataset
Core Metadata Element
Project Title
Custodian
MRWA Contract number
Description
Contact Address
Organisation
Contact Position
Mail Address
Service Description
Telephone
Facsimile
Electronic Mail
Type of service
Custodian of servicee
Contact name
Contact number
Positional Accuracy
Date
Type of service
Custodian of servicee
Contact name
Contact number
Positional Accuracy
Date
Services Projection
Coordinate System
Metadata Date
Metadata Date
Further Information
Approved non standard codes
Problems encounted
Description
Great Eastern Highway SLK 25 – 55
Survey and Mapping Branch
9999/99
1.5 km wide mapping corridor over Great
Eastern Hwy for preliminary design. Including
services and road reference marks.
John Smith utilities Inc.
John Smith
99 Smithdale Court
East Perth WA 6005
9666 6666
9666 6665
John.smith@util.com
Water Main
Water authority
Splash Waters
9123 4567
2m
Electicity
SECWA
High Voltage
9123 4567
2m
Perth Coastal Grid 94
None
Fred Bloggs refusing entry to land (see
attachment)
Any relevant information or
comment
Further Information
MAIN ROADS WA
106746373
Services
Standard 67-08-121
Page 15 of 15