9/23/2016 https://www.mainroads.wa.gov.

au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St

Home BuildingRoads StandardsandTechnical

Data,ModelandStringNaming

RoadandTrafficEngineering

TypicalProjectProcesses

Data, Model and String Naming

DocumentNo:D08#24171

Revision:5

Dateamended:03Dec2015

TheinformationbelowisintendedtoreflectthepreferredpracticeofMainRoadsWesternAustralia("MainRoads").MainRoadsreserves
therighttoupdatethisinformationatanytimewithoutnotice.IfyouhaveanyquestionsorcommentspleasecontactAndrewBerrybyemail
oron(08)93234137.
Totheextentpermittedbylaw,MainRoads,itsemployees,agents,authorsandcontributorsarenotliableforanylossresultingfromany
actiontakenorreliancemadebyyouontheinformationhereindisplayed.

RevisionRegister

<>tr>
Ed/VersionNumber
1

ClauseNumber

DescriptionofRevision

Date

All

GuidelineDeveloped.

30Nov2001

All

CombinedwithSurveyandMappingDataNamingConventions.
Guidelinerevisedandapproved.

25Mar2003

All

Guidelinerevisedandapproved.

28Mar2007

UpdateLinkforMetadataStatement.

04Sep2007

4A

Header

GuidelineContactamended.

13Dec2007

4B

Header

GuidelineContactchanged.

07Aug2010

4C

Header

ContactpersonamendedtoAndrewBerry.

17May2013

All

Guidelinerevisedandapproved

03Dec2015

TableofContent
1.INTRODUCTION
2.FILENAMINGCONVENTION
3.MODELNAMINGCONVENTION
3.1DesignModels
3.2SurveyandMappingModels
4.STRINGNAMINGCONVENTION
4.1DesignStrings
4.2SurveyandMappingStrings
4.3MainRoadsStringNamingConvention
5.TYPICALEXAMPLESOFMAINROADSSTRINGNAMINGCONVENTION

1.INTRODUCTION
Thisguidelinedefinesthestringandmodelnamingconventionsforallsurvey,mappinganddesigndatausedordevelopedforprojects
undertakenforMainRoads.
MXisthestandarddesignsoftwarepackageusedwithinMainRoads.A"genio"asciifileisthegeneralformatusedforthetransferofdata.
Theinitialheaderswithinthisgeniofile(delete,createandgenio)enableuserstoassignamodelnamethatdescribestheprojectlocation
andcoordinategrid.WhenimportedintoMXtheseheaderscreatethemodelnameandtheassociatedgeniostringsareplacedinthe
definedmodel.Inadditionthenameofthegeniofileistoalsoreflecttheprojectlocationandcoordinategrid.AsampleMXgeniofileanda
guidelineonthenamingconventionforthemodelnameandassociatedstringsaredetailedbelow.
Thelogicalnamingoffilesisparticularlyimportantwherealternateformatsareusedtoprovideinformation(Microstation,AutoCAD,Arcinfo
exportetc.),thatdon'thavethefunctionalityofdefiningamodelname.
Inadditiontotheuseoflogicalnamingconventionsallsurvey,mappinganddesigndatashallbeaccompaniedbyaMetadataStatement,
whichwillincludesufficientinformationtoadequatelydefine:
Lineage
PositionalAccuracy
AttributeAccuracy
LogicalConsistency
CompletenessofData

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

1/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St

2.FILENAMINGCONVENTION
Logicalfilenamesinconjunctionwithasuitablemetadatastatementshouldbeusedtoprovidesufficientinformationtoclearlyidentifythe
data.
Anexamplewherealogicalnameisnotusedwouldbe:
survey.genTheonlyinformationauserislikelytoimpartfromthisnameisthatitisanMXgeniofile(extension.gen)ofasurvey.
Amorelogicalnamewouldbe:
GNH_200_220.genLogicallythiswouldidentifythatitisafilecontainingdigitalinformationforGreatNorthernHighwayfrom200220
SLK.Theassociatedmetadatastatementwouldidentifywhetheritissurvey,designetc.

3.MODELNAMINGCONVENTION
Carefulselectionofmodelnamesshallbetakentoavoidconfusionwhenworkingonlargeprojectswithmultipleinterchangesor
intersections.Uniformnamingconventionswillenabledesignerstomoveeasilyfromoneprojecttoanother.Modelnamesshallcontainno
morethan28lettersincludingspaces.Whereverpossiblethenameofaprojectzoneshallbeincludedinthemodelname.

3.1DesignModels
Fordesignpurposes,separatemodelsshallbecreatedforintersectionsoreachinterchange.Themainalignmentandrelatedstringsshall
bedesignedinaseparatemodel.
Oncompletionofthedesignprocessallrelevantstringsshallbecopiedintoamasterdesignmodelforsectioning,volumescalculations,
reportingforconstructionandpreparationoffinaldrawings.Allredundantstringsshouldbedeletedandallrelevantstringsshouldhave
discontinuitiesintroducedwherenecessary,afterbeingcopiedintothemasterdesignmodel.Themasterdesignmodelshallcontainonly
stringsrequiredforconstruction.
Namingconventionformatsfortypicaldesignmodelsshouldbeasperthefollowingexample,wherePCG94isthelocalgridused:
DESIGNCONCEPTPCG94Conceptdesignmodel
DESIGNFINALPCG94Finaldesignmodel
DESIGNULTIMATEPCG94Ultimatedesignmodel
DESIGNCONCEPT"intersection/interchangename/number"PCG94Conceptintersection/interchangedesign
SECTIONSCONCEPTPCG94Conceptsectionsmodel
SECTIONSFINALPCG94Finalsectionsmodel
SECTIONSULTIMATEPCG94Ultimatesectionsmodel
SECTIONSCONCEPT"name/number"PCG94Conceptintersection/interchangesections
CADASTRALPCG94Cadastralmodel
SERVICESPCG94Servicesmodel
Thesemodelnamesareprovidedasaguideandcanbevariedtosuittherequirementsofparticularprojects.Modelnamesshould
howeverbeselectedlogicallyenablingotherdesignerstoaccessthedataeasily.

3.2SurveyandMappingModels
3.2.1DetailSurveyModels
CareshouldbetakenwhendefiningMXmodelnamestoensurethatthenameisrelevanttothedatacontent,surveylocationandproject
zone.
ForexampleadetailsurveyoftheintersectionofWellingtonStreetandWilliamStreet,Perth,wherePCG94isthelocalgridusedcouldbe
called:
WELLINGTONWILLIAMSURVEYPCG94
WhereasastrippedgroundsurveyforasectionoftheGrahamFarmerFreeway,wherePCG94isthelocalgridusedcouldbecalled:
GFFLAKETOWILLIAMSTRIPPCG94
Toassistinthedesignprocess,individualdetailsurveysandthusmodelnamesshallbecreatedforthefollowing:
TopographicSurvey
BoundaryPolygon
ForMappingProjects(670844DigitalPhotogrammetricMapping)
Detail
Relief
SpotHeights
Text
BoundaryPolygon
Cadastral
Services
Contours
Audit
Wheredigitalinformationissuppliedtootherinternalorexternalareas,documentationmustalsobeprovidedtoclearlyidentifywhatis
beingsupplied.Forfurtherinformationpertainingtothisrefertothefollowingguideline:DataPurchaseorSupplyGuidelines.
Detailsurveymodelsshallhaveattheminimum,thecoordinatezoneusedinthemodelname.
Namingconventionformatsfortypicalsurveyandmappingmodelswhere,PCG94isthelocalgridused,shouldbeasperthefollowing
example:

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

2/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St
"PROJECTNAME"SURVEYPCG94
"PROJECTNAME"BOUNDARYPCG94
"PROJECTNAME"CADASTRALPCG94
"PROJECTNAME"SERVICESPCG94
"PROJECTNAME"CONTOURSPCG94
"PROJECTNAME"AUDITPCG94
Thesemodelnamesareprovidedasaguideandcanbevariedtosuittherequirementsofparticularprojects.Modelnamesshould
howeverbeselectedlogicallyenablingotherdesignerstoaccessthedataeasily.

4.STRINGNAMINGCONVENTION
4.1DesignStrings
Surfacesandfeaturesarerepresentedasagroupofstringswithstringlabelsconsistingoffouralphanumericcharacters.
MainRoadshasadoptedtheNationalMXstringnamingconventionandfeatureset.Thestringnames,detailedatsection4.3shallbe
usedforallMainRoadsdesignprojectsandarecompatiblewiththedefaultMXRoadstringnamingconventionandfeatureset.Thelabels
detailedatsection4.3arethefirsttwocharactersofthestringlabel.
Considerationshouldbegiventodefiningthe3rdcharacterofstringlabelstoparticularintersectionsand/orinterchanges.
Forexample"ES10"wouldrefertoashoulderstringlocatedatintersectionnumber1onthelefthandside.Thisparticularnaming
conventionallowsstringstobegroupedaccordingtotheintersection(s)wheretheyaresituated,makingiteasierforotherMXusersand
designerstolocateadesignstringwhennecessary.
Stringlabel"TTTT"isaspecialstringandshouldnotbeused.
TheRoadandTrafficEngineeringBranchhasdevelopedafeaturedesignstylesetmeetingtherequirementsoftheNationalString
NamingConvention.ThisfeaturesetalsoconformstotheMainRoadsDrawingPresentationGuideline.

4.2SurveyandMappingStrings
Adigitalterrainmodelcanberepresentedbyanumberofstringorpointfeatureswitheachfeaturelabelconsistingoffouralphanumeric
characters.
MainRoadshasdevelopedadetailedlistofstringnamingconventionstobeusedinallMainRoadssurveyandmappingprojects.
Thefeaturecodingfortopographicalsurveysaredetailedinthe670843DigitalGroundSurvey.Allfeaturelabelsshallbeusedinstrict
accordancewiththislist.
Undergroungutilitiessurveyscodesaredetailedin6708121.
Inthecaseofmappingprojects,notallcodesareused.ForalistoffeaturecodesapplicableformappingprojectsrefertoAppendixBof
670844DigitalPhotogrammetricMapping.
Whereaparticularuniquefeaturedoesnothaveacorrespondingfeaturecodeandisconsideredtobesignificant,itshallbecapturedand
suppliedinanappropriateMXformat,withauniquefeaturecode.Onregistrationandlodgementofthedigitaldata,theassociated
documentationshallincludeasummaryofallnonstandardstringscaptured,includingtheMXcodeused.

4.3MainRoadsStringNamingConvention
TheMainRoadsStringNamingConventionhasbeenbasedontheNationalStringNamingConvention.Thefollowingtablegives
standardstringlabelsusedfornamingofstringsindesignmodels.Thecharacterslistedbelowrepresentthefirsttwostringlabel
characters.
TheMainRoadsStringNamingConventionadoptsdifferentalphanumericcharactersforleftandrightoffsets.Thesecharactersareplaced
inthe4th fieldofthestringlabel:
Lefthandside0to9andAtoH
RighthandsideItoZ

MAINROADSSTRINGNAMINGCONVENTION

DESCRIPTION

LABEL

GENERALDESIGNSTRINGS
Carriageway(Taper)

C0

Carriageway(MedianEdge)

C1

Carriageway(BitumenEdge)

CE

Carriageway(GutterInvert)

CF

Carriageway(Hinge)

CH

Carriageway(MaterialEdge)

CM

Carriageway(WingKerbReturn)

CR

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

3/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St
Carriageway(HardStrip)

CS

Carriageway(TopofKerb)

CT

Carriageway(MedianEdge6D)

MA

Shoulder(BackofKerb)

EB

Shoulder(GutterInvert)

EF

Shoulder(EarthworksDatum)

EH

Shoulder(HighSideTurnDown)

ER

Shoulder(Edge)

ES

Shoulder(Verge)

EV

Shoulder(FrontofFootpath)

EW

Shoulder(BackofFootpath)

EX

Earthworks(Interface)

IA

Earthworks(CutBerm)

IB

Earthworks(Intermediate)

IC

Earthworks(FrontofDitch)

ID

Earthworks(BackofDitch)

IE

Earthworks(BottomofDitch)

IF

Earthworks(NoiseBund)

IN

Earthworks(FillBerm)

IS

Earthworks(BrokenHinge)

IZ

RoadReferenceLine(NaturalSurface)

NC

RoadReferenceLine

MC

RoadReferenceLine(Geometry)

GC

Carriageway(FilletMString)

MR

TrafficIslands(TopofKerb)

TT

TrafficIslands(6D)

MT

Fence

FN

BridgeAbutments

BA

BridgePiers

BP

BridgeDeck

BB

ConcreteBarrier

BC

SafetyFence

BS

SafetyFence(WBeam)

BW

ConstructionJoint/CutonExisting

NJ

SubgradeStrings

VolumeStrings

VO

RetainingWallBottom

WB

RetainingWallTop

WT

Boundary

BD

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

4/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St
TextString

DRAINAGESTRINGS
Culvert

DB

Canal

DC

Pipe(Invert)

DI

Pipe(Top)

DT

HydraulicGradeLine

DH

Pipe(DesignSurface)

DD

Pipe(SurveySurface)

DS

Headwall

SH

Drain(Centreof)

DR

LINEMARKINGSTRINGS
Line9x3

L3

Line1x1

L1

ContinuityLine

LA

BarrierLineDoubleUnbroken

LD

Edgeline

LE

HoldLineupto0.3Wide

LH3

HoldLineupto0.45Wide

LH4

HoldLineupto0.6Wide

LH6

BarrierLineLeftBroken

LL

DiagonalMarkingOutline

LO

PedestrianCrossing

LP

BarrierLineRightBroken

LR

StopLineupto0.3Wide

LS3

StopLineupto0.45Wide

LS4

StopLineupto0.6Wide

LS6

TurningLine

LT

PaintedLineUnbroken

LU

Typicalexamplesoftheapplicationoftheabovestringnamingconventionsareshownonthefiguresbelow.

5.TYPICALEXAMPLESOFMAINROADSSTRINGNAMINGCONVENTION

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

5/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St

FIGURE5.2MXSTRINGLABELSDUALCARRIAGEWAY(KERBED)

FIGURE5.3MXSTRINGLABELSDUALCARRIAGEWAY/FREEWAY

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

6/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St

FIGURE5.4MXSTRINGLABELSPLANVIEW

FIGURE5.5MXSTRINGLABELSPROFILEVIEW

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

7/8

9/23/2016 https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_St

FIGURE5.6MXSTRINGLABELSINTERCHANGEPLANVIEW

https://www.mainroads.wa.gov.au/BuildingRoads/StandardsTechnical/RoadandTrafficEngineering/TypicalProjectProcesses/Pages/Data,__Model_and_String_N

8/8