Microstation Cadd Procedures

STATE OF NEW HAMPSHIRE
DEPARTMENT OF TRANSPORTATION
2012 CAD/D P ROCEDURES

AND R EQUIREMENTS
EFFECTIVE: APRIL 12, 2012
NHDOT CAD/D Procedures and Requirements
PART I GENERAL INTRODUCTION........................................................................... 1

Disclaimer.....................................................................................................................................................................1
About the Cover...........................................................................................................................................................1
Revision Summary.......................................................................................................................................................2
April2012 ..................................................................................................................................................................2
July2009 ....................................................................................................................................................................2
April2007 ..................................................................................................................................................................3
April2006 ..................................................................................................................................................................3
April2005 ..................................................................................................................................................................4
April2004 ..................................................................................................................................................................4
April2002 ..................................................................................................................................................................5
Introduction .................................................................................................................................................................6
Current NHDOT Software Versions..........................................................................................................................7
MajorSoftwareandCurrentProductionVersions ....................................................................................................7
FutureUpgrades ........................................................................................................................................................7
PART II GENERAL CAD/D INFORMATION ............................................................... 9

Documentation .............................................................................................................................................................9
Survey Datum ..............................................................................................................................................................9
Project Journal Files ...................................................................................................................................................9
ProjectJournalGuidelines .........................................................................................................................................9
SampleCAD/DProjectJournal ................................................................................................................................10
Directory Structure ...................................................................................................................................................14
PART III MICROSTATION......................................................................................... 15

MicroStation Workspace ..........................................................................................................................................15
File Naming ................................................................................................................................................................15
Level Assignments and Symbology ..........................................................................................................................15
Reference File Attachments ......................................................................................................................................16
Seed Files ....................................................................................................................................................................16
Imperial2DSeedFile(NHSEEDF2.DGN) ..................................................................................................................17
Imperial3DSeedFile(NHSEEDFT.DGN) ..................................................................................................................17
Fonts ...........................................................................................................................................................................18
Text Height and Spacing ...........................................................................................................................................19
April 2012
Table of Contents
Text Styles ..................................................................................................................................................................19

Line Styles ..................................................................................................................................................................20
NHDOTCustomLineStyleResourceFiles................................................................................................................20
TrueSizeLinestyles..................................................................................................................................................20
ScaledLinestyles ......................................................................................................................................................21
CustomLinestyleScalingCharts ..............................................................................................................................21
LinestylesCreatedat1:1 .........................................................................................................................................22
Color Table.................................................................................................................................................................22
Cross Hatching...........................................................................................................................................................22
Cell Files .....................................................................................................................................................................24
Dimensioning..............................................................................................................................................................25
Plotting .......................................................................................................................................................................25
Batch Print/Print Organizer.....................................................................................................................................25
Pen Tables ..................................................................................................................................................................26
PART IV MX............................................................................................................... 27
File Naming ................................................................................................................................................................27
Model Naming............................................................................................................................................................27
String Labeling ..........................................................................................................................................................27
Style Sets.....................................................................................................................................................................28
Feature Sets................................................................................................................................................................28
Drawing Macros ........................................................................................................................................................29
Cross-Section Settings Files ......................................................................................................................................29
Macro Symbols & Lines............................................................................................................................................29
Add-Ins .......................................................................................................................................................................29
PART V PROCEDURES............................................................................................ 31
Introduction ...............................................................................................................................................................31
Exchanging Right-of-Way Data ...............................................................................................................................31
Legacy Alignments ....................................................................................................................................................32
Roll Plans....................................................................................................................................................................32
Table of Contents
ii
April 2012
Cut Sheets...................................................................................................................................................................32
Cross-Section Drawings ............................................................................................................................................33
Bridge Detail Sheets...................................................................................................................................................33
PART VI OTHER PROJECT DATA........................................................................... 35

Drawing Quality Assurance / Quality Control........................................................................................................35
PART VII - ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS ......... 37

Overview.....................................................................................................................................................................37
File Format And Delivery .........................................................................................................................................37
RequirementsForSubmittingElectronicDataToNHDOT ......................................................................................37
DataSubmission ......................................................................................................................................................38
IntermediateSubmissions .......................................................................................................................................38
DeviationFromFormat............................................................................................................................................39
MicroStationOnlyDeliverable.................................................................................................................................39
MicroStationPlotFiles(FinalDesignConsultantsOnly)..........................................................................................39
FileConversion ........................................................................................................................................................39
NHDOT Design Process ............................................................................................................................................40
PlanPreparation ......................................................................................................................................................40
PreliminaryDesign...................................................................................................................................................41
FinalDesign..............................................................................................................................................................42
ProjectsDesignedusingInRoads .............................................................................................................................42
SpecializedDevelopmentbyDesignConsultants ....................................................................................................43
NHDOT Resources Available for Consultants........................................................................................................44
PART VIII - APPENDIX................................................................................................. 45

Appendix A - MicroStation Drawing Names...........................................................................................................45
BridgeDesignDetailDrawings.................................................................................................................................45
HighwayDesignContractPlandrawings .................................................................................................................46
OtherHighwayDesignContractPlandrawings.......................................................................................................46
HighwayDesignPlanDrawings................................................................................................................................46
Appendix B - Level Mapping Convention ...............................................................................................................49
Appendix C - NHDOT Custom Linestyles & Font .................................................................................................51
Appendix D MX Model Naming Convention .......................................................................................................55
PlanPreparationModels .........................................................................................................................................55
PreliminaryDesignModels......................................................................................................................................55
FinalDesignModels.................................................................................................................................................56
OTHERMODELS .......................................................................................................................................................56
Appendix D MX Data Transfer Formats..............................................................................................................57
LandXML ..................................................................................................................................................................57
April 2012
iii
Table of Contents
HALGN .....................................................................................................................................................................57
SampleHALGNInputData.......................................................................................................................................57
DescriptionofHALGNFormat .................................................................................................................................58
VERAT ......................................................................................................................................................................59
SampleVERATInputData........................................................................................................................................59
DescriptionofVERATFormat ..................................................................................................................................59
Appendix E Construction Reports .......................................................................................................................61
SampleAlignmentReport(COGOStyle)..................................................................................................................61
SampleAlignmentReport(Coordinates).................................................................................................................62
Appendix F Cross Section Set Labels ...................................................................................................................63
CrossSectionDetailFeatureStrings........................................................................................................................63
Table of Contents
iv
April 2012
PART I GENERAL INTRODUCTION
DISCLAIMER
Theproceduresdescribedinthisdocumentareforreferenceonly.Thisinformationisprovidedonan
"as is" basis. The material contained is provided without warranty or liability of any kind to the New
HampshireDepartmentofTransportation(NHDOT).
Updatingthismanualisintendedtobeacontinuousprocess.Astechnologyevolves,policieschange,
andprocessimprovementsarediscovered,thisdocumentwillbeupdatedtoreflectthosechanges.
As with any documentation, improvements can and should be made. Any additions, suggestions or
comments for improvement are encouraged. This documentation is not meant to be a complete
instructionaldocument.Theintentistoprovideguidelinesthat,iffollowed,willresultinbetterquality
andconsistencyforelectronicplansanddocuments.
This manual, in its entirety, may be freely copied and distributed for the purpose of providing a
consistentguidetothecomputeraideddesign&drafting(CAD/D)requirementsoftheNewHampshire
Department of Transportation. Copies of this manual along with CAD/D resource files (style libraries,
namingconventions,etc.)canbedownloadedathttp://nh.gov/dot/cadd/cadd.html.
Anyrecommendationsforimprovementstothisdocumentationarewelcome.Anyerrorsfoundshould
bebroughttotheattentionoftheCAD/DStaffsocorrectionscanbemade.Foradditionalinformation
ordetailedexplanationsofthestandardsdescribedwithinthisdocument,contact:
CAD/DSupportandDevelopment
NewHampshireDepartmentofTransportation
POBox483
Concord,NH033020483
Email:cadd@dot.state.nh.us
Tel:6032712171
ABOUT THE COVER

ThisyearscovershowsthedoubledeckerbridgeinSuncookcompletedin2007.Ontopisaphotoof
the completed structure taken by Jerry Zoller on November 30, 2007. Below it is a rendering of the
proposaldevelopedduringthedesignphasebyLysaBennetCrouchoftheCAD/DSection.
April 2012
Part I General Introduction
REVISION SUMMARY
APRIL2012
PartIGeneralIntroduction
Newsoftwareversions.
PartIIGeneralCAD/DInformation
TheprojectdirectorystructurewasmodifiedtoseparateMXdatafromcontractplandrawingdata.
PartIIIMicroStation
Updatestocellfilelisting.
Seedfileinformationnowincludesgeographiccoordinatesystembeingused.
InformationabouttheNHDOTpentablehasbeenupdated.
PartVProcedures
Theprocessforcreatingcutsheetshasbeenmodifiedalongwiththesheetnamingconvention.
PartVIOtherProjectData
NotesonQA_InputandotherGDMprogramshavebeenreplacedbydescriptionsoftaskmenus.
Appendix
ChangestoMicroStationdrawingnamesinAppendixA.
LinestylechartshavebeenupdatedinAppendixC.
AppendixD(MXmodelnames)hasbeenupdatedtoreflectcurrentpractices.
MXStringlabellistshavebeenupdated.
JULY2009
PartIIIMicroStation
Newcellfilesadded.Theseareidentifiedwithinthetext.
PartVProcedures
Newsectiontoremovedescriptionsofspecificproceduresfromsectionsdescribingsoftwareprograms.
InformationaboutLegacyAlignmentshasbeenadded.
Anadditionaloptionhasbeenaddedtotheprocessforcreatingcutsheets.
Appendix
MXStringlabellistshavebeenremovedseetheCAD/Dwebsiteforcurrentinformation.
April 2012
APRIL2007
PartIIGeneralCAD/DInformation
Newsection
PartIIIMicroStation
TheBrDdirectoryforBridgeDesignfileshasbeenrenamedtoBRC.
Detailsofchangestothenh_engineeringfont.
AdditionofBridgeDesigncrosshatchingdetails.
PartIVMX
TheERW8stylesethasbeenrenamedtoERL.
DocumentationofMXaddinshasbeenadded.
PartVIEngineeringConsultantRequirements
TheRightofWayprocesshasbeenrevised.
Appendix
AppendixAhasbeenexpandedtoincludeadditionaldrawinginformation.
AppendixCshowsupdatestothenh_engineeringfont.
AppendixJhasbeenupdatedtoreflectchangestotheMXaddinforaddingcrosssectiondetailsymbols.
APRIL2006
General
TheCAD/Dwebsiteaddresshasbeenchangedto:http://nh.gov/dot/cadd/
Theemailaddresshasbeenchangedtocadd@dot.state.nh.us
PartIIIMicroStation
UseofNHDOTdefinedMicroStationlinestylesisrequired.
Thetextstyleandlinestylesectionshavebeenexpandedandclarified.
Thelistsofdrawingnameshavebeenexpandedandclarified.
PartIVMX
AerialsurveydatahasbeenmergedintotheEXDstyleset.
LandXMLisnowthepreferredmethodofexchangingdesigndatabetweenMXandotherdesignsoftware.
Aprocessforexchangingrightofwaydatahasbeenadded.
FilesubmissionrequirementsforprojectsdesignedwithInRoadshavebeenupdated.
Appendix
AppendixAhasbeenexpandedtoincludeadditionaldrawinginformation.
April 2012
AppendixHhasbeenmodifiedtoencouragetheuseofLandXMLwhentransferringdesigndatabetween
MXandotherdesignsoftware.
APRIL2005
General
Nosignificantchanges.
PartIIIMicroStation
AddedNHDOTwebsitelocationofengineeringdetaildrawings.
Updatetodirectorystructureforprojectscontainingmultiplebridges.
AddedtextstyleinformationforBridgeDesignprojects.
PartIVMX
Styleset&featuresetlistingreformattedtoincludeadditionalinformation.
Appendix
ChangestoMicroStationdrawingnamesinAppendixA.
LinestylechartshavebeenupdatedinAppendixC.
Specialcharactersincludedinthenh_engineeringfont(font180)arelisted.
AppendixD(MXmodelnames)hasbeenupdatedtoreflectcurrentpractices.
MXStringlabellistshavebeenupdated.
AnewsectionAppendixJhasbeenaddedtodocumentMXCrossSectionSets.
APRIL2004
General
Nosignificantchanges.
PartIIIMicroStation
ReferencestoMicroStation/JfeatureshavebeenmodifiedtoreflecttheupgradetoMicroStationv8.
ReferencestoSettingsManagerhavebeenremoved.
Correctederrorsincustomlinestylescalingcharts.
Newcellfilesadded.Theseareidentifiedwithinthetext.
PartIVMX
StylesetshavebeenupdatedforMX2.6/MicroStationv8.
Appendix
ReferencestoMXversion2.5havebeenmodifiedtoreflecttheupgradetoMX2.6
ModificationshavebeenmadetotheMicroStationdrawingnamelist.Specificchangesareidentifiedin
thedrawinglist.
SomeMXstringlabelshavebeenaddedormodified.Theseareidentifiedwithinthestringlabeltables.
April 2012
APRIL2002
General
ConsultantdeliverablespecificationsrelocatedfromvariouspartsofthedocumentandcombinedasPART VII ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS
PartIIIMicroStation
Theprocessforcreatingcutsheetshasbeenmodifiedalongwiththesheetnamingconvention.
Theprojectdirectorystructurewasmodifiedtoincludesubdirectoriesforfrontsheetsandprofiles.The
bridgedirectorynowincludesadditionalsubdirectories.
Changestocellfilelistingtitles.celwasrenamedtostamps.cel,borders.cel,br_borders.cel,stnoffset.cel,
andturnrad.celhavebeenadded.
InformationabouttheNHDOTpentablehasbeenincluded.
BatchPlotinformationhasbeenadded.
PartIVMX
Additionalstylesetshavebeenlisted.
PartVOtherProjectData
Informationaboutthequalityassurance/qualitycontrolsoftwarehasbeenincluded.
Newsection.
NHDOTwillonlyacceptplandrawingsthatweredevelopedinMicroStationforprojectsthatwere
initiatedafterApril18,2002.
MicroStationplotfilereturnablechangedfromHPGLtoPDFformat.
Appendix
ModificationshavebeenmadetotheMicroStationdrawingnamelist.Specificchangesareidentifiedin
thedrawinglist.
InformationaboutMicroStationlevelcolors,styles,andcellnameshavebeenremovedtoavoidpotential
conflictswithdocumentationontheCAD/Dwebsite.
SomeMXstringlabelshavebeenaddedormodified.Theseareidentifiedwiththestringlabeltables.
April 2012
INTRODUCTION
ThisdocumentcontainstheNewHampshireDepartmentofTransportations(NHDOT)specificationsfor
electronic (computer) data as it relates to engineering design projects. It explains the minimum
requirementsthatmustbemetforallComputerAidedDesign&Drafting(CAD/D)dataproducedbyand
fortheNewHampshireDepartmentofTransportation.ThisistoensurethatCAD/Dfilescanbeusedby
the entire project team throughout all phases of project development. While the requirements
contained herein provide a basis for uniform CAD/D practice for NHDOT projects, precise rules that
wouldapplytoallpossiblesituationsthatmayarisearenotpossibletodescribe.Situationsmayexist
wherethesestandardswillnotapply.Ifvariancesfromthe"CAD/DPROCEDURESANDREQUIREMENTS"are
necessary for a project, they must be approved in writing by the NHDOT Project Manager and
documentedintheProjectJournalFileasdefinedherein.ThecreationofMicroStationdrawingsand/or
levelsforfeaturesthatarenotdescribedinthisdocumentshallbedocumentedintheProjectJournal
File. The creation of MX models that are not described in this document shall be documented in the
ProjectJournalFile.
As a minimum, NHDOT Design staff and engineering consultants are expected to adhere to the
standardsthatwereinforceatthetimethecontractwasinitiated.Althoughnotrequired,followingthe
lateststandardisrecommendedwheneverfeasible.
In addition to the traditional hardcopy delivery items, NHDOT requires supplementary electronic data
delivery items. This data shall be submitted in the formats specified by this document. In general,
designdataandDigitalTerrainModel(DTM)dataistobeprovidedintheMXmodelfile,LandXML,or3
D DXF file formats, and graphical data is to be provided in MicroStation's .DGN drawing format.
Organizations wishing to perform professional engineering services for NHDOT are required to deliver
electronic data as specified by this document. This specification also requires organizations to accept
andutilizepertinentelectronicinputdataasprovidedbyNHDOT.
TheseelectronicdeliveryitemsDONOTreplaceanyhardcopydeliveryitems.
Thisdocumentispublishedasanupdatetothe"CAD/DPROCEDURESANDREQUIREMENTS"documentdated
July2009andsupersedesallCAD/Dstandardspreviouslypublished.
Trademarks
MicrosoftandWindowsareregisteredtrademarksofMicrosoftCorporation.
MicroStation,MDL,InRoads,GEOPAK,MX,andMXROADareregisteredtrademarksofBentleySystems,Inc.
April 2012
CURRENT NHDOT SOFTWARE VERSIONS
NHDOTdesirestostaycurrentwithstateofthearttrendsinthemarket,however,budgetconstraints,
statewide implementation, impact on users, and providing support for the new features must be
consideredpriortoanychange.
AsNHDOTmakesachangethatresultsinmodifyingelectronicprocedures,the"CAD/DPROCEDURESAND
REQUIREMENTS"willbeupdatedwherenecessarytoreflectthechange.Alistofthemodificationswillbe
foundintherevisionsummary.Asarule,untildocumentationismodified,deviationfromthecurrent
datedrequirementsmustbeapprovedbytheProjectManager.
MAJORSOFTWAREANDCURRENTPRODUCTIONVERSIONS
1.
2.
3.
MicroStationV8i(SELECTseries2)(version08.11.07.443)
MXV8i(SELECTseries2)(version08.11.07.536)
MicrosoftOffice2000productswithExcel2002
FUTUREUPGRADES
BentleyreleasedMicroStationSELECTseries3asthisdocumentwasbeingpreparedandaSELECTSeries
3 version of MX is forthcoming. The Department will be testing those updates when time and
availabilitypermit.
April 2012
PART II GENERAL CAD/D INFORMATION
DOCUMENTATION
Documentation of NHDOT CAD/D practices and procedures can be found on the Internet at
http://nh.gov/dot/cadd/. Summaries of selected procedures will be found in PART V PROCEDURES beginningon
page31.
SURVEY DATUM
ForNHDOTprojects,theverticaldatumisbasedonNGVD29andthecoordinatesystemisNAD83/86.
PROJECT JOURNAL FILES

PROJECTJOURNALGUIDELINES
A Project Journal will be produced for each project. On consultantdesigned projects, a copy of the
journalfilewillbedeliveredwitheachelectronicprojectplansubmission.Thepurposeforthisjournalis
to aid downstream customers of the CAD/D data so they may utilize existing CAD/D work in their
processes. The format of the journal will be an electronic file, either in text format or a format
supportedbyMicrosoftWord2000.Asaminimum,thejournalwillcontainthefollowinginformation:
Alisting(Index)oftheprojectfiles,includingbriefdescriptionsofeachfileandwherethefileis
located.
Documentation about the CAD/D software used, special CAD/D decisions made, exceptions to
standardsthatweremade,problemsencounteredandworkaround,orotherimportantissues
thataroseduringthecourseoftheCAD/Dwork.Forexample,ifacustomlinestyleneededto
be created, the justification, resource file, and files where that line style was used would be
documented in the Journal. Other documentation would include the design software used
(includingversionnumber),particularsoftwaresettings,andotherinformationthatwouldhelp
adownstreamuserofthedataunderstandhowitwascreated.
ImportantdatathatshouldalsobecontainedintheJournalinclude:
Allinformationnecessaryfortheregenerationoruseofthosefilesbysubsequentcustomersof
theCAD/Ddata
Documentthedesigndata,controllingalignmentandprofilenamesandgeometryinput/output
files,relevantsurveyinformation,crosssectionsandthemethodologyusedtoobtainthefinal
geometriccontrolsintheCAD/Dproduct.
NHDOThasnotestablishedaspecificformatfortheJournalfile.Thesamplefileshownonthefollowing
pagesshouldbeusedaguidelineforthetypeofinformationtobeincludedandformatthatisexpected.
April 2012
Part II General CAD/D Information
TheprojectjournalmustbekeptuptodateastheCAD/Ddesignworkprogressesandbedeliveredwith
theprojectonthepreferredmediaforarchivalpurposes.
SAMPLECAD/DPROJECTJOURNAL
CAD/DPROJECTJOURNAL
(12345_project_index.doc)
4/13/00
PROJECTJOURNAL
Thisfilecontainsinformationabouttheproject12345andthecorrespondingelectronic
filescontainedintheprojectdirectory.Thisfileshouldbekeptuptodateandarchived
with the project's electronic files. When filling in the required information, please
deletetheinstructionsandexamplesinordertomaintainaconciserecord.
PROJECTDESCRIPTION
StateProjectNumber:12345
FederalAidNumber:N/A
County:Merrimack
ProjectManager:ProjectManager
ProjectDesigner:ProjectDesigner
ProjectDirectory:N:\CADD\pbt\town\12345\cadd\prj
SCOPEOFWORK
Thescopeofworkforproject12345goeshere.Includeasmuchdetailasnecessaryto
definetheworkdonefortheproject.
PROJECTFILES
Listanyfilesthatdonotfitintothestandardnamingconvention.Includeabriefdescriptionofthedata
containedineachone.
MICROSTATIONFILEINFORMATION
SeedFileUsedforthisProject: nhseedft.dgn,nhseedf2.dgn,nhseedm.dgn,nhseedm2.dgn
(selectone,deletetherest)
10
April 2012
NonStandardDrawings
Listanydrawingsthatarenotonthestandardnamingconventionlistwithabriefdescriptionofeach
one'scontents.
PlotInformation
Listinformationaboutbatchprintspecifications,pentables,orotherfeaturesusedtogeneratetheprint
files.
MXFILEINFORMATION
(orinformationforotherdesignprogramsused)
MXTopoinputfile:topo.inp
PreliminaryDesignEngineer:YourName
FinalDesignTeamLeader:TeamLeader
MXDesignInputFileNames
Description
pdesignmc0m.inp
ThefilethatcreatesthealignmentMC0Mand
designstringsuptoandincludingtheinterface
stage.
psectmc0m.inp
Createstheoldgroundandproposedcross
sectionsforalignmentMC0M
MXDesignOutputFileNames
Description
Topo.prn
OutputfromTopo.inpReportsassignedstring
labelsanderrors.ContainsX,Y,Zcoordinatesof
thesurveypoints.
Triangles.prn
OutputfromTriangles.inpReportscrossing
strings,minimumandmaximumelevationsand
planarea.
Sprofiles.prn
OutputfromSprofiles.inpReportsx,y,z
coordinatesofeachsurveyalignment.
April 2012
11
Ssections.prn
OutputfromSsections.inpReportsstring
assignmentsaswellaspointandoffset
informationforeachsurveyalignment.
TEXTFILES
Includeinformationaboutoutputfiles,geniofiles,orotherASCIIfilesprovidedwiththeproject
drawings.
NONSTANDARDMODELNAMES
Includeinformationaboutanymodelsthatdonotconformtostandardnamingconventions.These
couldbemodelsdevelopedasstudyalternativesorotherspecialuses.
SPECIALINFORMATION/COMMENTS
Includeanyinformationaboutspecialconsiderationsorproblemsdiscoveredduringthedesignprocess.
MAINLINE"MainStreet(NH25)"
Survey(PlanPrep)
MasterAlignmentModel: SALIGN
MasterAlignmentName: . MC1S
TriangleModel:................. Triangles
TriangleString:.................. TX00
CrossSectionModel: ........ SSECTMC1S
PreliminaryDesign
MasterAlignmentName: . MC1M
MasterAlignmentModel: PALIGN
DesignModel:................... PDESIGNMC1M
ProposedTriangleModel:
ProposedTriangleString: .
CrossSectionModel: ........ PDESIGNMC1MSECTIONS
FinalDesign
MasterAlignmentName: .
MasterAlignmentModel:
DesignModel:...................
CrossSectionModel: ........
12
April 2012
SIDEROADPleasantStreet
Survey(PlanPrep)
MasterAlignmentModel: SALIGN
MasterAlignmentName: . MC2S
TriangleString:.................. TX00
CrossSectionModel: ........ SSECTMC2S
PreliminaryDesign
MasterAlignmentName: . MC2A
MasterAlignmentModel: PALIGN
DesignModel:................... PDESIGNMC2A
CrossSectionModel: ........ PDESIGNMC2ASECTIONS
FinalDesign
MasterAlignmentName: .
MasterAlignmentModel:
DesignModel:...................
CrossSectionModel: ........
CrossSectionSettingsFile(CSU)
Description
mc1m.csu
CrosssectionsforMainSt.includingdrivesandskewedsections.
mc1m_all.csu
CrosssectionsforMainSt.cutateverypointonthealignmentfor
drainagestudy.
mc2a.csu
CrosssectionsforPleasantSt.includingdrivesandskewedsections.
April 2012
13
DIRECTORY STRUCTURE
The standard directory structure being used for CAD/D projects within NHDOT is shown below:
Directory and file names will only contain alphanumeric characters and underscores ("_"). No spaces
willbeincludedinnames.
CAD/DfilesarestoredindirectoriesundertheCaddfolder.
FilesthatareusedwithMicroStationorbymultiplebureausarestoredin
thePrjfolder.
FilesthatareusedwithMXv8iarestoredintheMXfolder.
Thefollowingfolderswillcontainfilesthatareonlypertinenttothat
particularbureau:
BRCBridgeDesign
EnvEnvironment
HwyHighwayDesign
RowRightofWay
TrfTraffic
TheBRCfoldercontainsthefollowingsubdirectories:
AbutA DetailplansdepictingAbutmentAfooting,masonry,and
reinforcing.
AbutB DetailplansdepictingAbutmentBfooting,masonry,and
reinforcing.
BrSite GeneralPlan,SitePlan,notes,andboringlogs.
DetailsMiscellaneousdetails,forexampleBridgeandApproachRail.
Pier DetailplansdepictingPierfooting,masonry,andreinforcing.
PrelimPreliminaryPlans.Afterpreliminaryplansareaccepted,pdffiles
oftheGenplan&Siteplandrawingsarecreated.Otherdrawings
arecopiedintothisdirectoryandrenamed.
Super Superstructuredetails.
TheCutSheetfolderunderPrjiswhereHighwayDesign'sfinalcontractplan
DGNfileswillbestored.FrontsheetsarestoredintheFrontSheetfolder
underPrj.BridgeDesigncontractplanfilesarestoredinthevariousBridge
directories.
Theimperial_macros,imperial_stylesandtheMxDatafoldersunderMX
arecreatedbyMX.Theimperial_macrosandimperial_stylesstoreproject
specificmacrosandstylesets.MXDataisusedtostoremiscellaneousMX
files.
Iftherearemultiplebridgesonaproject,theBRCdirectorystructureis
typicallymodifiedsothatdrawingsforeachbridgearekeptseparate.
The subdirectories under BRC can be named for the feature being
crossedorincaseswherethesamefeatureiscrossedmultipletimes,
thebridgenumberasshownhere.
14
April 2012
PART III MICROSTATION
MICROSTATION WORKSPACE
Through a collaborative effort, the NHDOT has made available a spreadsheet (nhdotdownloads.xls) to
clarifyhowtobestandmosteasilyutilizethefilesprovidedfordownloadontheDOTswebsite.The
spreadsheet and associated readme files found in nhdotmsv8iworkspace.zip should provide the
informationnecessarytoduplicatetheintentoftheMicroStationworkspaceusedatNHDOT.Thiswill
aidtheconsultantinproducingplansthatmeettheexpectationslaidoutintheDepartment's"CAD/D
PROCEDURESANDREQUIREMENTS"documentwithminimalinterferencetoasitesestablishedworkspace.
FILE NAMING
AnattemptshallbemadetohaveMicroStationfilesnamedusingonlyaneightcharacterfilenamewith
a.DGNextension.However,itisunderstoodthatthiswillnotalwaysbepossibleorpreferable.Drawing
names will only contain alphanumeric characters, "", and "_". No spaces or other special characters
shallbeused.SeeAppendixAMicroStationDrawingNamesbeginningonpage45formoredetails.
LEVEL ASSIGNMENTS AND SYMBOLOGY

ThefilesmentionedinthissectionareavailableontheCAD/Dwebsiteorcanberequestedthroughthe
ProjectManager.ThewebsiteaddressislistedintheDOCUMENTATIONsectiononpage9.
Levellibraryfilescontainlevelnamesandcolor/weight/styleinformationforMicroStation.DGNs.For
HighwayDesigntherearelevellibraryfilesavailableformostdetaildrawings.Thesefileshavethesame
3characternameasthedrawingwitha.csvextension.Forexample,thelevelnamingfilefordrawing
12345exd.dgnwillbeexd.csv.
Therearetwo*.CSVfilestobeutilizedwhencreating.DGNsfortheBureauofBridgeDesign.Thefirst
fileiscalledbrc.csv,andstandsforBRidgeCutsheet.Itcontainsthenamesrequiredtoaccuratelyplace
graphical elements on a cut sheet (also referred to as a detail sheet). The second file, called brd.csv,
containsthenamesrequiredtoplacegraphicalelementsina.DGNatprojectcoordinates.Manyofthe
namesinbrd.csvarerequiredinordertoconvertelementstoMXfromMicroStation.
Levelstandardsforfrontsheetsisfsh.csv,andforallothercutsheetsisthebxx.csv.Filtersfordisplaying
bordersareincludedinBorderFilters.dgnlib.
Standard plan drawings are maintained by the CAD/D Section and were revised and approved on
7/29/2010.TheyareavailableontheNHDOTwebsite(www.nh.gov/dotDoingBusinesswithDOT
Engineers/ConsultantsStandardPlansforRoadConstruction).Symbolsheetscanalsobefoundon
the NHDOT website (www.nh.gov/dot Doing Business with DOT Engineers/Consultants Detail
SheetsHighwayDesign)
April 2012
15
Part IV - MX
Lineweights,stylesandtextheightsshallconformtotheNHDOTlevelmappinglocatedontheNHDOT
CAD/D website. Use of NHDOTdefined MicroStation line styles is required. The consultant, with the
approvaloftheProjectManager,maycreatesymbolsthatarenotcoveredintheNHDOTDesignManual
or contained in NHDOT cell libraries that are needed to complete project plans. Resource files
containinganylinestylesand/orsymbolscreatedbytheconsultantforuseontheprojectdrawingswill
beprovidedtoNHDOT.
MicroStationsymbols,includingstandardborders,arecontainedinNHDOTsstandardcelllibrariesand
are available in MicroStation .CEL file format. A standard color table, line style resource files with
NHDOT line styles and font library with NHDOT fonts for use with MicroStation are available for
download.
REFERENCE FILE ATTACHMENTS

A reference file is a MicroStation drawing or other CAD/D file attached as a background to an active
designfile,thusallowingseveraldesigngroupstosharethesameinformationwithouttheneedtocopy
thefile(s).MicroStationandMXv8icanattachareferencefilebyoneofthreedifferentways:
1. Name only the path to the referenced file is resolved by the MicroStation configuration
variableMS_RFDIR.
2. Relativepaththereferencefilenameanditslocationrelativetothemasterfile.
3. URLaddressthefileisattachedintheformofaURLaddressusingrelativepaths.
InorderforaprojecttobedeliveredtoNHDOTinanelectronicformatthatwillallowfutureuseofthe
files for printing purposes without modification to the files, the reference files must be attached in a
waythatwillallowMicroStationorMXv8itoresolvethereferencefileattachmentpathsregardlessof
the drive or parent directory of the project. Option 1 above is the preferred method for NHDOT
projects, since it allows the files to be moved from drive to drive without losing the reference file
attachments.However,thisoptionrequirestheMicroStationconfigurationvariable,MS_RFDIR,beset
forallNHDOTprojects.
SEED FILES
MicroStationusesseedfilestocreatealldesignfiles.Theseseedfilesaretemplatesinwhichstandard
parameters are set according to what is needed to begin drafting for a specific type of work in
accordance with NHDOT standards. Seed files allow the user to begin work in a standard format and
maintain uniformity. The seed file defines the working units for the file, global origin, coordinate
system, view attributes, default color table, text settings, coordinate readout and several other
importantparameters.NHDOTsuppliesseedfilesforboth2Dand3Ddrawings.
Bydefault,NHDOTdesignteamsareworkingwith2DMicroStationdrawings.Ifaconsultantprefers
touse3DMicroStationdrawings,thisshouldbementionedpriortoobtainingsurveyordesigndata
fromtheDepartment.
Two of the most important settings in the seed file are the working units and global origin. Working
unitsareexpressedasmasterunitsandfractionalsubunits.Thenumberofpositionalunitspersubunit
iscalledtheworkingresolution.Theworkingresolutiondeterminestheprecisiontowhichelementsare
drawn.TheformatfortheworkingunitsinMicroStationisdefinedasMU:SU(masterunits,subunits).
Part IV - MX
16
April 2012
IMPERIAL2DSEEDFILE(NHSEEDF2.DGN)
WorkingUnits:
MasterUnits=ft
SubUnits=inches
GlobalOrigin: X=500
Y=500
Resolution
254/inch
IMPERIAL3DSEEDFILE(NHSEEDFT.DGN)
WorkingUnits:
MasterUnits=ft
SubUnits=inches
GlobalOrigin: X=500
Y=500
Z=10,000
Resolution
254/inch
The global origin has been set at 500, 500, 10000

using the NAD83 New Hampshire State Plane
coordinatesystem.Usingthesecoordinates,theseed
files can be used for both drawings based at State
Plane Coordinates and drawings, such as cross
sections, profiles, typicals and special details, using a
local coordinate base. The 10,000 unit offset allows
MX data with null elevations to be transferred
properly.
To reset the global origin for a drawing file, enter the keyin GO=500,500,10000 and use the right
mousebuttontoissuea"reset"command.
April 2012
17
Part IV - MX
FONTS
MicroStation font resource files are binary files created from font cells, TrueType, Postscript, or
AutoCADSHXfonts.MicroStationwillreadmultiplefontresourcefilesaccordingtothepathssetbythe
MS_SYMBRSCconfigurationvariableintheselectedworkspace.However,withinMicroStationtheyare
compiledintoalistofallthefontsfromalltheresourcefilesthatwerefound.Ifonefilecontainsafont
withthesamenumberassignedasanotherfontresourcefile,theuserwillseethelastonelocated.
TheNHDOTfontresourcefilesarecallednhcustomfont.rsc&nhttfont.rsc.AnyfontswithintheNHDOT
resource files that are no longer in use will be maintained for backward compatibility purposes. The
fonts contained within the NHDOT resource files are described below. Font numbers below 170 are
reservedforstandardMicroStationfonts.
NHCUSTOMFONT.RSC
FontDescription
180
nh_engineering(Engineeringw/bridgeanddraftingsymbols)Nonalphanumeric
characterscontainedwithinthisfontarepicturedinAPPENDIX C - NHDOT CUSTOM
LINESTYLES & FONTonpage51.
Thefollowinginformationisonlyincludedforhistoricalreference.Projectdrawingsshouldusethe
WindowstruetypefontsinsteadoftheMicroStationfontslistedbelow.
NHTTFONT.RSC
FontDescription
170
TrueTypefontArial
171
TrueTypefontArialBold
173
TrueTypefontCourier
174
TrueTypefontCourierBold
176
TrueTypefontTimesNewRoman
177
TrueTypefontTimesNewRomanBold
182
TrueTypefontComicSans
183
TrueTypefontComicSansBold
Part IV - MX
18
April 2012
TEXT HEIGHT AND SPACING

Standard text heights and fonts have been defined to ensure uniformity and legibility on all CAD/D
drawings. The correct text height is shown on the level mapping table and is dependent on the plot
scale. Note that the text height listed represents both the text height and width. Since, the most
important issue with text is that it should be legible, font and text height may vary if absolutely
necessary.Textlinespacingvariesbetweenhalfofthetextheightandthetextheightdependingonthe
use.
TEXT STYLES
Forbridgedrawings,textstylesareavailableatvariousengineeringandarchitecturalscales.Thestyles
arelocatedwithinnhdotTextandDimStyleLibraryFT.dgnlib(Imperial).
ThesedgnlibsshouldbedefinedbytheMS_DGNLIBLISTvariable.Thestylenamesincludetheintended
purposeofthetextandthescaleofthedrawingstheywillbeusedon.
nh_eng
Usedfornoteanddetailtext
Titlenh_eng
Usedfordetailtitletext
NoteTitlenh_eng
Usedforasmallerorsubtitletext
DimensionandtextstylelibrariesusedbyBridgeDesignareavailableontheNHDOTCAD/Dwebsite.
April 2012
19
Part IV - MX
LINE STYLES
LinestyleispartofthesymbologyofgraphicalelementsinMicroStation.Anelementcanbesettothe
standardMicroStationlinestyles(numbered07)ortoacustomlinestyledefinedinacustomlinestyle
resourcefile.Customlinestylesareuserdefinableresourcefilesforthedisplayofdifferentpatterns,
for example, a tree line, fence line, guardrail, etc. When an element is drawn in MicroStation with a
customlinestyle,thedefinitionofthelinestyleisnotcontainedwithinthedesignfile.Theresourcefile
fromwhichitwasselectedmustbepackagedwiththedesignfileanditmustbefoundbyMicroStation's
configuration in order to properly display the line. Therefore, users are strongly discouraged from
creatingtheirowncustomlinestyles.UsetheNHDOTsuppliedcustomlinestyleresourceswhenever
practical. Graphical depictions of NHDOT MicroStation linestyles are shown in APPENDIX C - NHDOT
CUSTOM LINESTYLES & FONTonpage51.
NHDOTCUSTOMLINESTYLERESOURCEFILES
StandardNHDOTCustomlinestylefiles
lineft.rsc
pipeft.rsc
As mentioned above, custom line styles are user definable in MicroStation. NHDOT linestyles are
created at two different scales (1:1 and 1=50) depending on the intended use. These settings are
included in the task menus. The task menus are described in more detail in DRAWING QUALITY
ASSURANCE / QUALITY CONTROLonpage35.
Cautionmustbeexercisedasthedefinitionforthelinestyleismaintainedinaresourcefileandadesign
file only contains links to custom line style resource files. If a new (nonstandard) custom linestyle is
developedbyauser,thoseresourcefilesmustbedeliveredwiththeproject.Usersshallnotmodifythe
NHDOTdeliveredstandardcustomlinestylefiles.
TRUESIZELINESTYLES
Linestylesthataredefinedtobeaspecificsize(suchaspipeandrailroadstyles)shouldalwaysbedrawn
atascaleof1.Stylesinthisgroupinclude:
PipeP#
CurbRt
BmGrDbl
Railroad
DrainPipe
BmGrLt
SheetPile
JerseyBarrier
BmGrRt
TrafBarls
PCurbLt
CblGrLt
UnderDrain
PCurbRt
CblGrRt
XPipE#
Pavemark
CblGrMed
XPipP#
PipeE#
CurbLt
Part IV - MX
20
April 2012
SCALEDLINESTYLES
Linestylesforplandrawingshavebeencreatedforuseona1=50'scaleImperialdrawing.Thisincludes
most of the linestyles available. When these linestyles are used on 1"=20' Imperial drawings, they
shouldbescaledby0.4.Chartsshowingscalevaluesforotherdrawingscalesareshownbelow.
CUSTOMLINESTYLESCALINGCHARTS
Imperial
April 2012
Scalefor
plotting
Ratio
1=1
6=1'
3=1'
2=1'
11/2=1'
1=1'
3/4=1'
1/2=1'
3/8=1'
1/4=1'
1"=5'
3/16=1'
1/8=1'
1=10'
3/32=1'
1/16=1'
1=20'
1=30'
1=50'
1=100'
1:1
1:2
1:4
1:6
1:8
1:12
1:16
1:24
1:32
1:48
1:60
1:64
1:96
1:120
1:128
1:192
1:240
1:360
1:600
1:1200
21
Custom
linestyle
scale
setting
0.0016
0.003
0.006
0.01
0.013
0.02
0.026
0.04
0.053
0.08
0.1
0.1066
0.16
0.2
0.2135
0.32
0.4
0.6
1
2
Part IV - MX
LINESTYLESCREATEDAT1:1
Thelineft.rscfilealsocontainscustomlinestylescreatedatascaleof1:1.Inorderfortheselinestobe
properlyproportioned,theusermustenterthescaleassociatedwiththeplotsizeofthedrawinginthe
LineStylesdialogboxforcustomlinestylesbeforeplacingtheline.Thelinestylesforwhichthisrule
appliesinclude:
LeaderBr
BreakBr
ArBegOpn
LedgeBr
BreakDimBr
ArBegSld
RocklineBr
DimBr
ArEndOpn
GroundBr
ArEndSld
ITSProp
ArrowBr
Therearemultiplewaystoalterthescaleoflinestylesonadrawing.Tosetthescale,selectElement
LineStyleCustom.Selectthelinestyle,checkthe"Scalefactor"boxandenterthedesiredscale.Click
onthegraphicrepresentationofthelinestyletoimplementthechange.Analternativewayistoissue
thekeyindwgceltscale#wherethe#isreplacedwiththedesiredscale.Futurelineswillbedrawnat
thenewscale.Toalterthescaleoflinestylesthathavealreadybeendrawn,selectalltheelementsto
bechanged.IssuetheChangeLinestyleScale#keyinreplacingthe#withthedesiredscale.
COLOR TABLE
A standard color table is necessary to provide visual consistency thus allowing users to easily identify
elements in shared files and for consistency in color plotting. NHDOT has its own default color table
callednhcolor.tbl.Thetabledefines256colorsfromwhichanactivecolorcanbeselectedandapplied
toanelement.NHDOTsblackandwhiteplottersareconfiguredtoprintallcolorsexcept1014inblack.
Colors1014willplotintheshadesofgraydisplayedinMicroStation.
CROSS HATCHING
CrosshatchingusedbyBridgeDesignisshownonthenextpage.
Part IV - MX
22
April 2012
April 2012
23
Part IV - MX
CELL FILES
ThefollowinggraphiccellfileshavebeencreatedforuseonNHDOTprojects.Itemsshowninitalics
havebeenaddedsincethepreviousedition.
alignment.cel
symbolsforalignmenttransfers
andmstasks
borders.cel
cutsheetborders(includingfront
sheets,ROWsummary,property
layoutandxsectionbordersand
theirtextcells)
br_Borders.cel
miscellaneousbridgeborders
br_bore.cel
boringsheetsymbols
br_Misc.cel
riprap,slopelines,waterstops,
sheetpiles,sectionAA,North
arrow,shearconnector,&RR
section
environ.cel
environmentaldetailcells
existin.cel
existingtopographycells
geotech.cel
geotechnicalcells
grdrail.cel
proposedguardraildetailcells
legends.cel
hearingplanlegends
logos.cel
NHDOTandotherlogos
notes.cel
projectbegin/endnotes
pavemark.cel
proposedpavementmarking
detailcells
profile.cel
cellsforprofiledrawings
br_pile.cel
HPsectionsandPileKey
row.cel
proposedrightofwaydetailcells
br_precast.cel
NewEnglandBulbTees(precast
concretebeams)
signals.cel
proposedsignalizationdetailcells
signs.cel
proposedsigndetailcells
br_Rail.cel
2bar,3baraluminumandT2,3,4
steelbridgeandapproachrails
stamps.cel
miscellaneousroll/plansheet
cells
StnOffset.cel
StationOffsetmacrocells
turnrad.cel
Imperialturningradiitemplates
br_Railmisc.cel existing/superseded,temporary,
andTexas101bridgeand
approachrails
br_weld.cel
weldsymbols
utility.cel
proposedutilitydetailcells
drainage.cel
proposeddrainagedetailcells
xsect.cel
crosssectiondetailcells
ThefollowingpatterncellfilehasbeencreatedforuseonNHDOTprojects.
nhpatern.cel
hearingplanremovalpatterns
CellsfromBentley'sarchpa.celmayalsobeused.
Part IV - MX
24
April 2012
DIMENSIONING
DimensionsshouldappearasshownintheHighwayDesignManualwiththefollowingexception:The
dimensionsforBridgedetaildrawingsshallbe
placedtohavetheappearanceofthosethatfollow:
TheuseofDimensionStylesisstronglyencouraged
for the placement of all dimensions on structural
design drawings, since, at a minimum, it will select
the proper text height. It is understood that in
ordertoachievethedimensionappearancesshown
above, the Dimension Style defaults will, at times,
needtobeoverridden.
Dimensionstylenamesreflectthescale.
Dimension and text style libraries are available on
theNHDOTCAD/Dwebsite.
PLOTTING
Theplotter configuration file(fileextension.PLTCFG)
isusedtosetdefaultplottersettings.Blackandwhite
plotconfigurationfileshavebeenmodifiedtoforceall
pen colors to black except pens 1014 which are
definedasvariousshadesofgrayintheNHDOTcolor
table. Line weights for full size plotters are as
indicatedinthegraphic.
Plotterdriverfilesshouldbeeditedforplotterspecific
adjustmentsonly.Changesintendedtoaffectallplots
shouldbemadeinthepentables.
BATCH PRINT/PRINT ORGANIZER

Toplotcutsheets,arectangularelementdrawnonlevelBorderandincolor84,style0,weight0has
been placed at the outer edge of NHDOT border cells. Batch Print looks for these elements when
plottingcutsheets.WhendevelopingCAD/Ddrawings,elementsofthiscolor,styleandweightshould
be avoided unless an element defining a batch print limit is being created. A print style
BorderLevelandColorwascreatedforPrintOrganizertousethissameelement.
April 2012
25
Part IV - MX
PEN TABLES
Apentableisusedtoalterthewayadrawingissenttotheplotter.Itcanbeusedtocontrolthelevels
thatareplotted,controltheorderinwhichtheyareplotted,maketextsubstitutions,orrunmacrosat
plottime.NHDOTusesapentablecallednhdotpen.tbltomakeanumberoftextsubstitutionsinplan
bordersandfrontsheets.Thevariablesthataresubstitutedaretypicallydefinedintheprojectcontrol
file(pcf).Currentlydefinedsubstitutionsinclude:
Drawingtext
Textsubstitution
Description
$PROJCLASS$
$STNO$
$SCALE$
$FEDNO$
$NHPROJ$
$ROUTENO$
$CSHTOT$
$LSHTOT$
$MRSHTOT$
$RSHTOT$
$SSHTOT$
$WSHTOT$
$BT$
$PBT$
$BRNO$
$BRDESCR$
$BRFILNO$
$BRDIR$
$TIME$
$FILE$
$USER$
$DATE$
$FILENAME$
$ROWTOWN$
$COUNTY$
$TOWN$
$MODELNAME$
$REVNUM$
$REVDATE$
$PROJNAMENUM$
$(PROJCLASS)
$(STNO)
$(NH_SCALE)
$(FEDNO)
$(NHPROJ)
$(ROUTENO)
$(CSHTOT)
$(LSHTOT)
$(MRSHTOT)
$(RSHTOT)
$(SSHTOT)
$(WSHTOT)
$(BT)
$(PBT)
$(BRNO)
$(BRDESCR)
$(BRFILNO)
$(lastdirpiece(_DGNFILE))
_TIME_
_FILE_
$(_USTN_USERNAME)
_DATE_
$(basename(_DGNFILE))
$(ROWTOWN)
$(COUNTY)
$(TOWN)
_MODELNAME_
$(REVNUM)
$(REVDATE)
$(PROJNAMENUM)
Projectclass
Stateprojectnumber
Projectscale
Federalprojectnumber
"N.H.PROJECTNO.12345"
Routenumberorroadname
Totalnumberofconstructionplansheets
TotalnumberofMaterials&Researchplansheets
Totalnumberofrightofwayplansheets
Totalnumberofshorelandplansheets
Totalnumberofwetlandplansheets
Totalnumberofbridgesheets
Totalnumberofpreliminarybridgesheets
Bridgeinventorynumber
Bridgedescription(roadoverfeaturecrossed)
Bridgefilenumber
Bridgedirectory
Currenttime
DGNfilename
Username
Currentdate
DGNfilenamewithoutdirectorypath
"TOWNOF"
Countyname
ProjectName(Town)
Modelname
RightofWayplanrevisionnumber
RightofWayplanrevisiondate
identifierforProjectExplorertofindV:/project
Part IV - MX
26
April 2012
PART IV MX
FILE NAMING
MXfilesshouldbenamedinsuchawaythatsomeoneunfamiliarwiththeprojectcanfigureoutwhat
the file is for. MX projects are typically given names beginning with the town name followed by the
stateprojectnumber.Forexample:Concord12345.mmd.Otherfiletypesarelistedinthetablebelow.
Type
Extension
Description
Input
.INP
UsedtostorelinemodecommandstocreateormodifyMXstrings
Output
.PRN
Usedtostoretheresultsofaninputfileorinteractivecommands
Draw
.DRW
Aninputfilethatisusedtocreateadisplayusingadrawingmacroormajor
optionDRAWand/orENHANCEcommands
Journal
.JOU
AjournalfilestorescommandsissuedduringanMXsessionsotheycanbe
rerunatalatertime
MODEL NAMING
SuggestedMXmodelnamesarelistedinAPPENDIX D MX MODEL NAMING CONVENTION,onpage55.Any
variationsfromthisconventionshallbenotedintheprojectjournalfile.
STRING LABELING
MXdataiscontainedinstringsandthestringsarecontainedinmodels.Eachstringhasauniquefour
character label. Typically the first two characters of the string label are used to identify the type of
string. NHDOT's string labeling convention can be found in the MX section of the CAD/D website at the
addresslistedintheDOCUMENTATIONsectiononpage9.
April 2012
27
Part IV - MX
STYLE SETS
A style set is a collection of styles which is used to draw a complete model or a selected part of it.
BeginningwithMXv8i,stylesetreferencestoMXmacrosymbolsandmacrolineshavebeenreplaced
with MicroStation cell and linestyle references. NHDOT style and features sets are stored on the
networkinMX'sPublicfoldersotheyareaccessibletoallusers.Thiseliminatestheneedtoupgrade
eachworkstationwhenchangesaremade.
FEATURE SETS
Feature sets are a means of grouping strings and identifying them with a description. They are used
throughoutMXtomakeiteasiertoselectstringsforsubsequentoperations.Thestringsbelongingtoa
featuresetarespecifiedusingapartialstringname,andaredrawnwithastyleset(usuallyhavingthe
same name as the feature set). For design detail, NHDOT uses a modified version of mxroad.fns to
conformtoMXdesignwizards.WhentransferringdetailbetweenMXandMicroStation,beawarethat
MicroStationelementsaredrawnbasedonthemodel'sdefaultstyleset.Thisshouldbethesamestyle
setthatwasusedtodrawtheMXDPW/DPF.
NHDOTDevelopedStylesetsforMXdrawings
StyleSets
FeatureSets
Description
Usedtotransferproposedbridgestructurestrings
betweenMXandMicroStation.
brd8.pss
brd8.fns
catchment.pss
catchment.fns
Usedtotransferdrainagecatchmentmodels.
ctr8.pss
ctr8.fns
Usedtodrawandtransfercontours.
env8.pss
env8.fns
Usedtodrawandtransferenvironmentalfeatures.
erl.pss
erl.fns
UsedtodrawandtransferexistingRightofWay
detail.
exd.fns
UsedtodrawexistingandaerialsurveydetailinMX
2.6thatwillbecomeMicroStationv8idetail
drawings.Thisstylesetisusedtocreatethe
project'sEXDandAIRdgnfiles.
exd.pss
UsedforMXdesignoptions.
Usedtodrawalignments.Alignmentstobe
transferredtoMicroStationaredrawnwiththe
NHAlignaddin.SeetheCAD/Dwebsiteformore
details.
mxroad.pss
mxroad.fns
ply8.pss
ply8.fns
Usedtodrawandtransferproposedroadwaydetail.
prw8.pss
prw8.fns
UsedtotransferproposedRightofWaystrings
betweenMXandMicroStation.
pvm8.pss
pvm8.fns
Usedtodrawproposedpavementdesign.
trav.pss
trav.fns
Usedtodrawsurveytraverses.
xsu.pss
xsu.fns
Tobesetasthemodeldefaultforcrosssection
models.Crosssectionstobetransferredto
MicroStationaredrawnwiththeXSMSmacro.
Part IV - MX
28
April 2012
DRAWING MACROS
Inadditiontothestyleandfeaturesetsmentionedabove,MXuserscanalsodrawdetailandsections
withdrawingmacros.Anumberofthesemacroshavebeendevelopedandareavailablefordownload
fromtheNHDOTwebsite.
CROSS-SECTION SETTINGS FILES

Cross sections and profiles can be generated in a number of different ways. Using the crosssection
wizard within MX allows the user to save parameters defining the crosssection set. These saved
settingsfileshavea.CSUextensionandarestoredintheprojectdirectory.Thesettingsfilewilldefine
thetypeofsectionscut(basedonthecrosssectionfeaturesetused),modelsselected,andinformation
aboutanyspecialstationsorskewedsections.Bydefault,thecrosssectionwizardusestheinformation
inthecrosssectionmodel'sdefaultstylesettodeterminethedifferenttypesofcrosssections.String
labelsforcrosssectionsarelistedin APPENDIX F CROSS SECTION SET LABELSonpage63.ForNHDOT
projects,thedefaultcrosssectionstylesetandfeaturesetarelistedinthetableonthepreviouspage.
MACRO SYMBOLS & LINES

SymbolsforusewithversionsofMXsoftwarebeforev8i,includingstandardlinepatterningsymbols,are
availableintheMX.MMSand.MMLfileformats.TheseMXsymbolsandlinesarebeingphasedoutin
favor of MicroStation cells and lines in the MX v8i style sets. This data is available on the NHDOT
websiteorcanberequestedthroughtheProjectManager.
ADD-INS
MX AddIns are applications such as Visual Basic programs that can interact with MX. NHDOT has
developedanumberoftheseprogramstosimplifysomeoperations.Theseprogramsareavailableon
theCAD/Dwebsite.
CONREPO
Usedtogenerateanoutputfileofstringpointsfromaspecifiedmodel.Thisreportiscommonly
usedtoprovide3dimensionalstringinformationtononMXconsultants.
DataImport ForimportingGPSdataorotherdelimited/formattedtextfilesintoMX.
NHAlign-v8i
UsedtocreateanalignmentdrawingthatcanbetransferredtoMicroStation.Improvedtohandle
spiralcurves.
NHAliReport
UsedtocreateaformattedreportofanMXalignment.Thisreportcanalsobeusedtoplotcurve
dataonaMicroStationalignment.
NHDraper
Usedtoaddelevationstooneormorestringsinamodel
NHProfile
UsedtodrawexistingandproposedprofilesthatcanbetransferredtoMicroStation.
PointScan
Usedtocreateareportofprojectfeaturesreferencedbystationandoffset.
RenameM
UsedtorenameMasterAlignmentstringsIteliminatestheneedtoaddressit'sSubreference,the
Geometrystring,andit'sSubreference.
XSDetail
Usedtocreatesectionsetsrepresentingdetailsymbolsplottedoncrosssections.Forbestresults,
crosssectionscreatedwiththisprogramshouldbedrawnwiththeXSMSdrawingmacro.
April 2012
29
Part IV - MX
PART V PROCEDURES
INTRODUCTION
ThissectionofferssummariesofsomeNHDOTCAD/Dprocedures.Itisnotintendedtoprovideanin
depthdiscussionofanyparticulartopic.Formoredetails,refertotheCAD/Dwebsite.
EXCHANGING RIGHT-OF-WAY DATA

Rightofway data is routinely updated during the project's lifetime. This information is typically
maintainedbytheNHDOTBureauofRightOfWayforbothinhouseandConsultantdesignedprojects.
Knowing that DOT staff and Consultants both need to work on the existing rightofway drawings, a
processhasbeendevelopedtoensurethatthisdataiskeptcurrentandaccurate.
Theexistingrightofwayinformationwillbedividedbetweentwodrawings.Onecontainsthelinework
(ERL) and the other will have the text information (ERT). It is intended that the Department will
maintainthemasterERLdrawing(abstracting)andsendtheconsultantacopywhenupdateshavebeen
made.
The Bureau of RightOfWay will continue to utilize Design History and that record will be maintained
throughoutthelifeoftheproject.Thisisinlinewithhowbusinesswasconductedwhentheprocess
includedtheROWAbstractingmylar.TheBureauofRightOfWaywillcontinuebusinessasusualwith
the ability to make changes at any time during the design process with the understanding that the
NHDOTConsultantReviewerwillbenotifiedwhenchangeshavebeenmade.
Theprocessshallbe:
ERTandERLdrawingsarecreatedbytheBureauofRightOfWayandDesignHistoryisturned
on. Under normal circumstances, only the NHDOT Bureau of RightOfWay should be making
changestotheERLdrawing.
TheConsultantreceivesacopyoftheERTdrawing.Attheirdiscretion,theConsultantisfreeto
adjusttextpositionormakeothercosmeticchangestoimproveappearanceofthedrawings.
Updates to parcel ownerships made by the NHDOT abstractors are revised on the ERT
drawingandacopyoftheupdatedERTdrawingissenttotheConsultant.TheConsultant
willberesponsibleforupdatingtheircopyoftheERTdrawing.DesignHistorycanbeused
tohighlightchangesandtextrevisionsmadetotheERTdrawingbyNHDOTstaff.
TheConsultantalsoreceivesacopyoftheERLdrawingwhichisreferencedintootherdrawings
(Notcopiedormerged).
Updates to property lines, ROW lines, easement lines etc. are made to the ERL.dgn by
NHDOT Bureau of RightOfWay staff and a copy is sent to the Consultant. The revised
ERL.dgnsupercedesallpreviousversions.
Updates to the ERL.dgn can be reviewed using the Design History to identify changes and
impactstothepropertylineandROWlinelocations
April 2012
31
Part V Procedures
RightofwaydataissubmittedinbothpaperandDGNformattoNHDOTBureauofRightofWay
forreviewandapprovalpriortotheproductionofrecordablemylars.
LEGACY ALIGNMENTS
PriortotheimplementationofaCAD/Dsysteminthe1980s,itwascustomarytoshowalignmentsof
former projects on plan drawings as a reference between the old and new projects. Computeraided
design, electronic survey equipment and advancement in GPS technology eliminated the need to
referenceformeralignmentswhencreatingnewones.Asaresult,formerprojectdatawasnolonger
shownontheplandrawings.
The Bureau of RightofWay has expressed a need to reference this historical information to facilitate
thelocatingofrightofwayboundariesthatwerelaidoutduringtheseformerprojects.Toassistthis
process, future projects are to include information about these legacy alignments. Whenever
possible,thisinformationshouldalsobeaddedtocurrentprojects.
Theprocessincludes:
Researching former projects to identify those within the limits of the current project. On
consultantprojects,theBureauofRightofWaywilldotheresearch.
Obtainingalignmentinformationfromtheasbuiltplans.
Draftingthatinformationontothealignmentdrawingofthecurrentproject.
ROLL PLANS
Projectrollplanfilenamesarecomposedofthreeparts;theNHDOTstateprojectnumber(firstfive
characters),drawingtype(lastthreecharacters),andthe.DGNfileextension.
AfurtherexplanationofstandardnamingconventionsanddrawingtypedesignatorsusedbyNHDOTis
containedinAPPENDIX A - MICROSTATION DRAWING NAMESbeginningonpage45.
CUT SHEETS
TheHighwayDesigngroupatNHDOTpresentlyusesamethodforpreparingcutsheetswhereasingle
drawing is created for an entire set of drawings (general plans, drainage plans, etc.) with each sheet
storedinadifferentmodelwithinthedrawingfile.
The drawing file names will be the project number followed by the type of drawing such as
12345genplans.dgn for the general plans of project #12345. Within this file there will be models for
each individual sheet using the naming convention outlined in the following table. For example, the
modelforthefirstgeneralplansheetwillbecalledGEN01.
For more details of the processes for developing cut sheets, see the documentation on the CAD/D
website.
Part V Procedures
32
April 2012
Realizing that there are a number of different ways to accomplish this same task, variations to the
methoddescribedabovemaybeacceptablewithpriorapprovalofNHDOT.Consultantswishingtouse
analternativemethodshouldcontacttheCAD/DDevelopmentStaff.Anydeviationsfromtheseformats
shall be noted in the Project Journal File. A listing of drawing type designators used by NHDOT is
containedinAPPENDIX A - MICROSTATION DRAWING NAMESbeginningonpage45.
CROSS-SECTION DRAWINGS
NHDOThasdecidedtostoreMicroStationcrosssectionsinoneormorefileseachcontaininganumber
ofcrosssections.ThismethodiscompatiblewithMXandallowsforasmallernumberofDGNfilestobe
createdfortheproject.Thesectionsareplottedusingabatchprintoptionthatprintsallinstancesofan
elementcontainedwithinthebordercell.
Realizing that there are a number of different ways to accomplish this same task, variations to the
method described above may be acceptable with prior approval. Consultants wishing to use an
alternativemethodshouldcontacttheCAD/Ddevelopmentstaff.
BRIDGE DETAIL SHEETS

A single detail sheet frequently requires the placement of several details of various scales. To
accomplishthis,alldetailsshallbedrawnatascaleof1:1whileusingtheNHDOTstandardworkingunits
definedwithintheNHDOTseedfiles.Thedetailsheetshallbecomposedbyapplyingscalefactorsto
the selfreferenced attachments of the detail drawing. The border of the detail sheet shall be a cell
placedonthedrawingatascaleof1.Detaildrawingsshallnotbecreatedbyeitherincreasingthescale
oftheborderorbytemporarilyadjustingtheworkingunitsofthefile,inanyway.
April 2012
33
Part V Procedures
PART VI OTHER PROJECT DATA
DRAWING QUALITY ASSURANCE / QUALITY CONTROL

To aid the consultant and inhouse staff in developing a set of
contract plans that conform to the requirements contained in
thisdocument,NHDOThasdevelopedaseriesoftaskmenusfor
working on MicroStation drawings. Using the task menus
providedwillensurethatelementsonthedrawingsarecreated
according to the established MicroStation standards. At this
time, use of the task menus is optional although their use is
stronglyencouraged.
The task menu system is composed of a collection of dgnlib

files.Thedgnlibfilescontaintheelementtemplates,tools,and
tasks for the particular drawing name. Separate task menus
have been created for each of the standard drawing names at
both 50scale and 20scale. Metric files will be created when
necessary. The task menu for 20scale alignment drawings is
shownhere.Themenuincludessectionsforthevarioustypes
of alignments, each containing commands to set the
level/color/stylefordraftingtheparticularfeature.
For NHDOT operators, a macro checks the dgn name and

project scale when a drawing is opened to determine the
appropriate task list to load. If the dgn name is nonstandard
theNH50bxxTasksareloadedassumingthedgnisacutsheet
typeofdrawing.
April 2012
35
Part VI Other Project Data
PART VII - ENGINEERING CONSULTANT DELIVERABLE

REQUIREMENTS
OVERVIEW
The purpose of this section is to establish the minimum acceptable criteria for electronic CAD/D
deliverables. Obtaining drawings and ground models in a common format will reduce the amount of
timespentbecomingfamiliarwiththedesignsiftheyaretransferredfromonedesignertoanotherand
allowsfortheirreuseinthefuture.
FILE FORMAT AND DELIVERY

REQUIREMENTSFORSUBMITTINGELECTRONICDATATONHDOT
AllelectronicdatafurnishedtotheNHDOTshallusetheappropriatenamingschemeandformatforthe
typeofdatatobetransmitted.Itisveryimportanttoclearlycommunicatewhatisbeingtransmitted
andtodescribetheformatofthetransmittedfiles.
Aletteristobeattachedtoallsubmissionsstatingbriefly:
1.
Filecontent
2.
FileFormat(zipped,MicroStation,MX,etc.andtheutilityused)
3.
MXand/orMicroStationversion
4.
NumberofCDs,DVDs,etc.
5.
Files must be in the proper format before transmitting to NHDOT. No translating of
informationbyNHDOTpersonnelshallberequired.
6.
Iffilesarezippedorbackedup,abriefexplanationoftherecommendedproceduretoextract
thefilesshouldbeincluded.
7.
VersionsofsoftwaremustbecurrenttoorfullycompatiblewiththatoftheNHDOT.
8.
EachdisksubmittedshallbelabeledanddatedwithaminimumoftheStateProject#anddate.
IfaseriesofCDs/DVDsaretransmitted,thedisklabelshallalsoincludethedisknumberandthe
totalCDs/DVDsofthatset,(ex:1of10).OthersubsequentCDs/DVDsshallbelabeledsoasto
uniquelyidentifyeachgrouporsetandshallincludethesequencenumberfollowedbythetotal
numberinthegroup(ex:2of10,3of10,etc.)
9.
NHDOT reserves the right to reject any file transmitted that does not conform to these
requirements.
April 2012
37
Part VII Deliverable Requirements
DATASUBMISSION
In addition to hard copy drawings specified by the contract, the consultant shall submit electronic
drawingfilesinMicroStation.DGNfileformat.Electronicfilesshallbedeliveredononeofthefollowing
inorderofpreference:
1) DVD
2) CDROM
3) PlacedonDOTFTPsite1
4) Flashdrive
The final submission shall include all files necessary to reproduce the cut sheet drawings as well as
copies of the original rollplan drawings used to generate the cut sheets. Documentation of
proceduresandprojecthistoryshallbemaintainedinaProjectJournalFile.Anindepthdescriptionof
theProjectJournalFileisin PART II GENERAL CAD/D INFORMATIONbeginningonpage9.TheProjectJournal
Filewillbeprovidedwiththesubmission.AnydrawingsnotincludedintheNHDOTstandarddrawing
listwillbeidentifiedandwillincludeadescriptionoflevelsusedoneachdrawing.
DetaileddescriptionsofthedatatobeprovidedbyNHDOTtotheconsultantandexpecteddeliverables
atvariousstagesoftheproject'sdevelopmentareincludedinthenextsection,NHDOT DESIGN PROCESS
onpage40.
IfMicroStationtablesforlinestyles,multilines,leveltables,symbologytables,database,specialfonts,or
anyspecialuserdefinedfeatureisused,thatinformationmustbeprovidedandshallbecomeproperty
of NHDOT. Similarly, any MX macro, symbol, linestyle, style set, or feature set developed by the
consultantthatisnecessarytoproperlydisplaytheprojectdatashallbecomepropertyofNHDOT.Any
MX input file developed to generate, enhance, or alter the project's design that the consultant feels
wouldbebeneficialtofuturedesignersoftheprojectshouldalsobeprovided.Anameanddescription
of each file must also be provided. NHDOT will not distribute these items to any other individual,
consultantorStateTransportationDepartmentwithoutpriorpermissionofthedeveloper.
INTERMEDIATESUBMISSIONS
The consultant shall be prepared to submit sample cut sheet, profile, typical or detail, and/or cross
section sheets for review of conformity to the NHDOT CAD/D specifications at various stages of the
project's development. As a minimum, the final design consultant should be prepared to submit
electronicprojectdrawingsatthePreliminaryPlans,Specifications&Estimate(PPS&E)andPS&Estages
oftheproject.Dependingontheproject,NHDOTmayrequestelectronicsubmissionsatamoreorless
frequentinterval.
Sincenumerousgroupsworktogetherduringtheproject'sdesign,itisimportantthateveryoneusesthe
samedata.Therefore,whenchangesaremadethatwouldaffectthedesign,updateddrawingsshallbe
providedtotheNHDOTConsultantReviewer.These,inturn,willbedistributedtoallaffectedparties.
1
TheNHDOTftpsiteislocatedatftp://nhftp.admin.state.nh.us/.ContactyourConsultantReviewerforusername
andpasswordinformation.
38
April 2012
DEVIATIONFROMFORMAT
Any file to be submitted that deviates from the abovementioned format must have prior NHDOT
approval. The approval must be in writing with the name of the individual from NHDOT who
permittedthevaryingformat.
MICROSTATIONONLYDELIVERABLE
For projects that were initiated after April 18, 2002, NHDOT will only accept plan drawings that were
developedinMicroStation'sDGNformat.TranslationsfromAutoCADoranyotherCAD/Dsoftwarewill
nolongerbeallowedonthoseprojects.Projectsinitiatedbeforethatdatewillcontinuetofollowthe
requirements in place at the time the project was initiated. Engineering consultants may, at their
discretion,choosetofollowasubsequentreleaseoftheserequirements.
MICROSTATIONPLOTFILES(FINALDESIGNCONSULTANTSONLY)
In addition to MicroStation format drawings, plot files of project cut sheets in PDF format will be
required at the completion of the project. Plot files should be named with the convention for plan
sheets outlined Appendix A - MicroStation Drawing Names beginning on page 45 using a .PDF file
extension. The purpose of this requirement is to provide a viewable and reproducible copy of the
drawingasitexistedattheendoftheconsultantcontract.
FILECONVERSION
ThisinformationonlyappliestoprojectsinitiatedpriortoApril18,2002.
Translation tables, conversion tables, or special software programs have not been created or
standardizedforexchanginginformationbetweencommonfileformatssuchasDXF,DWG,ICES,IGES,
orsoftwaresuchasAutoCAD,ARCVIEW,ARCINFO,GDS,etc.
MicroStation provides methods for exchanging select file types but data is often modified during the
process. The Consultant is solely responsible for any translation and verification required to convert
nonMicroStation graphics files to the current NHDOT MicroStation design file format. All translated
designfilesshallconformtothestandardsadoptedbyNHDOTforelectronicplansandthespecifications
requiredinthisdocument.ThosefilesshallbeconvertedtoMicroStationandthoroughlyreviewedprior
totransmittingtoNHDOT.
April 2012
39
NHDOT DESIGN PROCESS

This section is intended to describe the data that is to be provided when a project moves from one
design phase to the next. There are two major transition points where Highway Design CAD/D data
needstobetransferred:theturnoverfromthePlanPreparationSectiontoPreliminaryDesignandthe
onefromPreliminaryDesigntoFinalDesign.TheBridgeDesignsectionisresponsiblefordevelopingthe
preliminaryand/orfinalplansand,asaresult,BridgeDesignfallswithinboththePreliminaryandFinal
Designsectionsdefinedbelow.
PLANPREPARATION
The Plan Preparation section is responsible for taking project survey and preparing the digital terrain
model(DTM)andbasedrawingsthatwillbeusedduringthedesignprocess.Theyshouldalsobethe
onestoinitiatetheProjectJournalFiledescribedin PART II GENERAL CAD/D INFORMATIONbeginningonpage
9.
By default, NHDOT design teams are working with 2D drawings. If a consultant prefers to use 3D
drawings,thismustbementionedpriortoobtainingsurveyordesigndatafromtheDepartment.
ElectronicdatatobeprovidedbyPlanPreparationto:
NHDOTPreliminaryDesignSectionandconsultantsusingMXsoftware:
1. CopyoftheMXmodelfile
2. Copy of the topo input file (TOPO.INP) containing survey data and Plan Preparation
modifications/enhancements.
3. CopyofannotatedMicroStation.DGNfilesdevelopedfortheproject.
4. CopyoftheProjectJournalFilecontainingallpertinentinformationabouttheproject.
ConsultantswithoutMXsoftware:
1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromtheMXmodelfile
2. CopyofannotatedMicroStation.DGNfilesdevelopedfortheproject.
40
April 2012
PRELIMINARYDESIGN
The Preliminary Design section is responsible for taking the data provided by the Plan Preparation
section and designing the project up to the Public Hearing stage. This includes gathering all data
necessary to prepare designs to be presented at the Public Officials Meeting, Public Informational
Meetings,andPublicHearing.
ElectronicdeliverablesexpectedatthecompletionofthePreliminaryDesignprocess:
NHDOTPreliminaryDesignStaffandConsultantsusingMXsoftware:
2. Copyofanyinputfilesavailabletorecreatethesubmitteddesign
3. CopyofMicroStation.DGNfilesdevelopedfortheproject
5. CopiesofanyMicroStationcellfilesandlinestyleresourcefilesusedontheprojectthatare
notincludedintheNHDOTstandards.
1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromthedesignsoftware
2. Copy of project horizontal and vertical alignments and associated design features in
LandXML formats. Descriptions of file transfer formats can be found in APPENDIX D MX
DATA TRANSFER FORMATSbeginningonpage57
ElectronicdatatobeprovidedbyNHDOTPreliminaryDesignsectionto:
NHDOTFinalDesignSectionandconsultantsusingMXsoftware:
2. Copy of the topo input file (TOPO.INP) containing survey data and Plan Preparation
modifications/enhancements
5. CopyoftheProjectPublicHearingPlaninPDFformat
2. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromtheMXmodelfile
April 2012
41
5. CopyoftheProjectPublicHearingPlaninPDFformat
FINALDESIGN
TheFinalDesignsectionisresponsiblefortakingthedataprovidedbythePreliminaryDesignSectionor
PreliminaryDesignConsultantanddesigningtheprojectuptotheContractPlansstage.Thisincludes
refining the project design as approved at the Public Hearing, preparing a project estimate, bid
documents,andobtainingnecessaryconstructionpermits.
Electronicdeliverablesexpectedattheproject'scompletion:
AllConsultantsandNHDOTFinalDesignStaff
3. COGO and coordinate reports of each alignment similar in format to the ones shown in
APPENDIX E CONSTRUCTION REPORTSonpage61
4. Stationandoffsetlistingofproposedbounds
5. PlotfilesinPDFformatofeachcontractplansheet
ConsultantsusingMXsoftware:
2. Copyofanyinputfilesavailabletorecreatethesubmitteddesign
1. 3DDXFfilesofexistingdetailandtriangulationgeneratedfromthedesignsoftware
3. IftheprojectwasdesignedwithInRoads/SelectCAD,includefilesmentionedbelow
PROJECTSDESIGNEDUSINGINROADS
If a project is designed with InRoads the following files should be delivered as part of the electronic
deliverable:
Surfacedata:(*.dtm):Thesefileswillcontainexistingandproposedsurfaceinformation. This
information will include but is not limited to the surface triangulation. Other information
that will potentially be found in the dtm include planemetric features like: breaklines
42
April 2012
representing existing and proposed objects, feature lines for entities like R.O.W. or
easements,aswellasrandompointinformationthatcandepictfeatureslikecatchbasins,
mailboxes,orothersinglepointfeatures.
Alignment data (alg): This will contain all coordinate geometry and alignment information for
theprojectalignments.
Roadway designer files (*.ird): The roadway designer file will include the templates (Typical
sections) in addition to the roadway model definition, this is the recipe to build your
design.Itemsinthisfileinclude:superelevation,linkstothealignmentsusedinthedesign,
aswellasthelimitsofdesign.
Survey data (*.fwd or other formats): If the survey for the project was completed by people
outside the department all data used to create the existing conditions plans should be
provided.IfthesurveywasdoneinInRoadsSurveythe.fwdfilesthatwereimportedinto
InRoads Survey should be provided. If the survey was done with a different software the
databroughtintoInRoadsshouldbeprovidedinitsoriginalformat.
StyleSheets (*.xsl):InRoadsreportstylesheetsusedforreportsincludedinthedesignshould
alsobedeliveredwiththeproject.
InRoads Preferences (*.xin): This file will contain the settings used to control the display of
information as well as the default values displayed in InRoads dialogs for generating the
designgraphics.
Storm & Sanitary files (*.sdb): The design information entered into InRoads Storm & Sanitary
should also be included for the Departments use. This will include location, sizes and
structuretypesforthedrainagedesign.
QuantityManagerfiles(*.mdb):Thisfileisthedatabasecontainingtheautomaticallygenerated
quantitiesfromInRoadsfortheproject.
SPECIALIZEDDEVELOPMENTBYDESIGNCONSULTANTS
Any specialized programs, macros, utilities, symbology, etc., developed by the consultant that are
necessary to properly display drawings submitted to NHDOT shall be included with other project
deliverables.
Submission of copies of other specialized programs, macros, utilities, symbology, etc. developed to
improve MicroStation and MX drafting and design processes is encouraged. It is understood that
NHDOT accepts these items without any guarantee of usefulness or expectations of support by the
developer. In addition, NHDOT will not distribute these items to any other individual, consultant or
StateTransportationDepartmentwithoutpriorpermissionofthedeveloper.
April 2012
43
NHDOT RESOURCES AVAILABLE FOR CONSULTANTS

To assist in the production of the required CAD/D files, NHDOT has provided MX and MicroStation
support files available from the Department's web site. The website address is listed in the
DOCUMENTATION section on page 9. Many of the files that are available are described in the LEVEL
ASSIGNMENTS AND SYMBOLOGYsectiononpage15.
44
April 2012
PART VIII - APPENDIX

APPENDIX A - MICROSTATION DRAWING NAMES
MicroStationdrawingnameswillbeginwiththeNHDOTstateprojectnumberfollowedbythedrawing
type.Thetablesbelowshowthetextthatwillfollowtheprojectnumberalongwithadescriptionofthe
drawing.
Forexample:12345ALI.DGNwouldcontainalignmentdataforproject12345.
BRIDGEDESIGNDETAILDRAWINGS
For projects that contain multiple bridges the six digit bridge inventory number shall be used after the names
below.Forexample:12345AAbut123_456.DGNwillcontaintheabutmentAmasonryforthe12345projectfor
bridgenumber123/456.
AbutA
Frame
AAbut
ARebar
AWings
AReWings
AFoot
AReFoot
AbutmentAMasonry
AbutmentAReinforcement
AbutmentAWings
AbutmentAWingsReinforcement
FootingAMasonry
FootingAReinforcement
FRDetls
FRFoot
FRReFoot
FRALeg
FRReALeg
FRBLeg
FRReBLeg
FRDeck
FRReDeck
FRWings
FRReWings
FrameDetails
FrameFooting
FrameFootingReinforcement
FrameLegA
FrameLegAReinforcement
FrameLegB
FrameLegBReinforcement
FrameDeck
FrameDeckReinforcement
FrameWings
FrameWingsReinforcement
PrelimPlans
PreGen
PreSite
PreliminaryGenplan
PreliminarySitePlan
BrSite
Genplan
Siteplan
Borings
BorReq
DevlView
BrNotes
BrDetour
Genplan
Siteplan
BoringLogs
BoringRequest
DevelopedViews
BridgeNotes
BridgeDetour
Super
DeckDetls
DeckBars
DeckSect
Girder
FramePlan
SSDetls
Shoes
Joints
DeckDetails
DeckReinforcing
DeckSection
GirderLayoutandDetails
FramingPlan
SuperStructureDetails
BridgeShoes
FixedJointsandExpansionJoints
AbutB
BAbut
BRebar
BWings
BReWings
BFoot
BReFoot
AbutmentBMasonry
AbutmentBReinforcement
AbutmentBWings
AbutmentBWingsReinforcment
FootingBMasonry
FootingBReinforcement
Pier
Pier1
RePier1
Pier2
RePier2
Pier1Masonry
Pier1Reinforcement
Pier2Masonry
Pier2Reinforcement
Box
BXDeck
BXReDeck
BXFoot
BXReFoot
BXWings
BXReWings
BXWalls
BXReWalls
BXDetls
BoxDeck
BoxDeckReinforcement
BoxFooting
BoxFootingReinforcement
BoxWingsMasonry
BoxWingsReinforcement
BoxWalls
BoxWallsReinforcement
BoxDetails
April 2012
45
Part VIII Appendix
HIGHWAYDESIGNCONTRACTPLANDRAWINGS
Drawing(DGN)Name
12345crbplans
12345drnplans
12345detplans
12345eroplans
12345genplans
12345geoplans
12345lndplans
12345pvtplans
12345plplans
12345rowplans
12345shrplans
12345sgnplans
12345sigplans
12345trfplans
12345wetplans
Content
Curbing
Drainage
Detour
Erosion
General
Geotechnical
Landscaping
PavementMarking
PropertyLayout
RightofWay
Shoreland
Signing
Signalization
TrafficControl
Wetland
PrefixforModelNames*
CRB
DRN
DET
ERO
GEN
GEO
LND
PVT
PL
ROW
SHR
SGN
SIG
TRF
WET
*modelnamefollowedby#or##indicatingasequentialnumber
OTHERHIGHWAYDESIGNCONTRACTPLANDRAWINGS
Forexample:12345FSC.DGNwouldbetheconstructionplanfrontsheetforproject12345.
FSC
FSR
FSW
FSS
P##
FrontSheetConstruction
FrontSheetsROW
FrontSheetWetland
FrontSheetShoreland
Profiles
RS#
SG#
SM#
ST#
TY#
RowSummarySheet
Signalization
SummarySheet
SignTextLayout
Typical
HIGHWAYDESIGNPLANDRAWINGS
(Namesinitalicshavebeenaddedsincethepreviousversionofthisdocument)
Whenattachingthesedrawingsasreferencefiles,itisrecommendedthatthethreecharacterdrawingnamebe
usedasthelogicalname.
Drawing
Content
LevelLibrary
AdditionalDetails
Name
(CSV)
AIR
AerialSurveyData
EXD
Allgrounddataobtainedfromaerialsurveys.
ALI
Alignment
ALI
Existingandproposedroadwayalignments&
surveytraverses
BOR
Borings
BOR
Geotechnicalboringlocations
BRD
BridgeInformation
BRD
TheBRDdgncontainsabutments,wings,deck,
approachslab,railandstonelayoutinthebridge
areaatprojectcoordinates.
Part VIII Appendix
46
April 2012
Drawing
Name
CLR
Content
ColorPlan
LevelLibrary
(CSV)
HER
CTR
DET
EDD
EDU
ExistingContours
Detour
ExistingDigitizedDetail
ExistingDigitizedUtilities
CTR
DET
EXD&TXT
EXD&TXT
ENV
Environment
ENV
ERL
ERL
EXD
EXF
EXL
ExistingRightofWay
Lines
ExistingRightofWay
Text
ExistingDetail
FieldCheckData
Exceldata
HER
HHO
HearingPlan
InformationalHandout
LLC
LargeLocationMap
LND
LOC
Landscaping
ProjectLocationMap
LND
LOC
MTH
MatchLines
MTH
PCN
PDR
PGR
PLY
PNT
PRO_MC##
ProposedContours
ProposedDrainage
ProposedGuardrail
ProposedLayout
ProposedNotes
Profile
CTR
PDR
PGR
PLY
PNT
PRO
PRW
PSG
PSN
PUT
PVM
ProposedRightofWay
ProposedSignalization
ProposedSigning
ProposedUtilities
PavementMarkings
PRW
PSG
PSN
PUT
PVM
ERT
April 2012
ERT
EXD
EXD&TXT
HER
HER
AdditionalDetails
Colorfillpatternstypicallyusedforproject
meetingsandpresentations.Thisisnotthesame
astheHERdrawingdevelopedforthePublic
Hearingwhichhasaclearlydefinedformatand
colorlegend.
Detours,DiversionsandTrafficcontrolitems
Detailcreatedbytracingoldplansoraerialphotos
Informationreceivedfromutilitycompaniesthat
wasaddedtothedrawingbyDOTorConsultant
staff.
Wetlandorfloodzonedelineations,identifications
ofhistoricproperties,andotherenvironmental
concerns
RightofWaylines,propertylines,civilboundaries
Propertyownernames,taxmap&lotinformation,
otherassociatednotes.
Dataobtainedbygroundsurvey.
Grounddataandtextpickedupduringfieldchecks
ContainslinkstoExceldata,generallyusedfor
summarysheets.
TheInformationalHandoutispreparedforthe
PublicHearing.
LLCistypicallyusedatmeetingsonlargerprojects.
Itshowstheprojectlocationinrelationtothe
surroundingarea.
TheLOCdrawingshowstheproject'slocationin
relationtothesurroundingarea.Itisoneofthe
drawingsusedindevelopmentoftheFrontSheet.
Partofthecutsheetprocess.Thisdrawing
containsoutlinesrepresentingtheareastobe
displayedoneachsheet.
Profiledrawingswillbenamedwith"PRO_"
followedbythefourcharacteralignmentlabelfor
projectsdesignedinMX.ProjectsnotusingMXwill
needsomeothermethodofidentification.
47
Part VIII Appendix
Drawing
Name
PWT
PXB
PXBM
Content
LevelLibrary
(CSV)
PWT
PXR
PXT
SSD
ProposedWetlands
PicturesBridgeDesign
PicturesBridge
Maintenance
PicturesEnvironmental
PicturesHighway
Design
PicturesMaterials&
Research
PicturesRightofWay
PicturesTraffic
SupercededDetails
TXT
XS_MC##
ExistingText
Crosssection
TXT
XSU
XSU
SectionDetails
XSU
PXE
PXH
PXM
AdditionalDetails
Includesshorelandanderosioncontrolitems.
ThePXseriesofdrawingsareusedforstoring
rasterphotographs.Thereareseparatedrawings
foreachdesignbureautoindicatewhoaddedthe
images.
TheSSDdrawingcanstoredetailsthathavebeen
changedandarenolongervalid,butwanttobe
keptincasetheyareneededinthefuture.
Text from survey books annotated by plan prep.
Crosssectiondrawingswillbenamedwith"XS_"
followedbythefourcharacteralignmentlabelfor
projectsdesignedinMX.ProjectsnotusingMXwill
needsomeothermethodofidentification.
Part VIII Appendix
48
April 2012
APPENDIX B - LEVEL MAPPING CONVENTION

Note: MicroStationlevelinformationwasincludedinpreviouseditionsofthisdocument.Toreduce
thepotentialforerrorsandconflictingdata,thisinformation hasbeenremoved.Thelatest
mapping convention can be found on the NHDOT website at the address listed in the
DISCLAIMER section of this document. Previous versions of the level mapping will be
maintainedonthewebsite.
April 2012
49
Part VIII Appendix
APPENDIX C - NHDOT CUSTOM LINESTYLES & FONT
April 2012
51
Part VIII Appendix
Part VIII Appendix
52
April 2012
April 2012
53
Part VIII Appendix
nh_engineering(Font180)SpecialCharacters
Character245isusedindimensionswhereacharacterappearingasan*isneeded.Thenormal*willshowthe
dimensionvalue.
Part VIII Appendix
54
April 2012
APPENDIX D MX MODEL NAMING CONVENTION

Note: These are the most commonly encountered models on a project. When creating additional
models,usenamesthateasilyandaccuratelyreflecttheinformationcontainedinthemodel.
(Namesinitalicsarechangedorhavebeenaddedsincethepreviousversionofthisdocument)
PLANPREPARATIONMODELS
(Modelsappearinapprox.orderofcreation)
RAxxxxxModelcontainingafieldsurveyedtraversestringPSSA.Traversesmaybereceivedasseparatedumpfiles
(eg. RAxxxxx.SDR, RBxxxxx.SDR, etc. where xxxxx is the project number). Individual traverses are typically
combined to create a single traverse in this model. The Survey Section is responsible for closing/adjusting
traverses.
TOPOModelcontainingexistingprojectdetail/topostringsasrecordedinthefieldbysurveydatacollectors.This
modeliscreatedbyeditingthenmergingindividualtopodumpfiles(eg.TAxxxxx.SDR,TBxxxxx.SDR,etc.xxxxxis
theprojectnumber).
AERIALDETAILModelcontainingexistingaerialsurveydetailobtainedfromanoutsideagency.
BOUNDARYAmodelcontainingoneormoreboundarystrings(BDRY,BY01,etc.)Boundarystringsmaybeusedin
mergingmodelsorcontrollingcreationandtrimmingofthetrianglestring(althoughPBRKstringshavegenerally
supercededboundarystringneedsintriangulation).
TRIANGLESModelcontainingthetriangulationstring(TRIA)createdbyusingselecttopodetailstringinformation.
Triangulation interpolates points on and between strings, creating a surface from which elevations can be
extractedatanylocation.
CONTOURS Model containing the existing ground contour strings (0 [zero] = major, D = minor) created by
surfacing(contouring)theTRIANGLESmodel.
PPALIGN Model containing reference master alignments (MCxS) created using center of road shots (CO) to
establishtangentsandaddingapproximatecurves(tonearest15').Referencealignmentsareusedtocutprofiles
and cross sections which assist in verifying the accuracy of the TOPO & CONTOURS models via a field check.
Existing ground elevations are attached to the master strings by sectioning them over the TRIANGLES model.
Stringsinthismodelmustberefined(drivepointsadded,etc.)iftheyaretobeusedfordesignpurposes.
PPSECTMCxSModelcontainingexistinggroundcrosssectionscutreferencingthemasterstringMCxSinSALIGN.
Existing ground sections are cut over the TRIANGLES model at each point along the master string and assigned
stringlabelsbeginningwith'E'.Separatesectionmodelsaremaintainedforeachuniquemasterstring.
NOTE:THESEMODELSARERECORDFILES!NOMODIFICATIONSARETOBEMADEWITHOUTTHEPRIORAPPROVAL
OFPLANPREP.
PRELIMINARYDESIGNMODELS
LEGACY Model for storing Legacy Alignments. Legacy alignments are used by the Bureaus of Highway Design,
Maintenance and RightofWay to determine where the existing roadway and structures are located, to better
defineourROWassets.
April 2012
55
Part VIII Appendix
PALIGN Model for storing all master (MC) and geometry (GC) strings with proposed elevations, as well as the
correspondingExistingGround'OC'strings.Duringearlystagesofaproject,alargenumberofalignmentsmaybe
created.Sideroadalignmentsaresometimesstoredinamodelnamedaftertheroad.
Note:Master'MC'andtheassociatedexistingground'OC'stringsmustresideinthesamemodeltobedrawnup
orplottedtogetheronaprofile.
PDESIGNMCxxThismodelcontainsthemasterstring'MCxx'withproposedelevations(copiedfromPALIGN),and
the associated template (created with DESIGN options) and Earthworks (INTERFACe options) strings. Separate
designmodelsaremaintainedforeachmasterstring.
PDRIVESModelforstoringalldrivewayalignments.
PCONTOURS Model to contain the proposed preliminary design contours.
PSECTMCxxModelcontainingallcrosssectionsformasterstringMCxx.SectionSetsarelistedinCrossSection
SetLabels.Separatecrosssectionmodelsaremaintainedforeachmasterstring.
Forthemostaccurateresults,existingcrosssections'E'shouldbecutovertheTRIANGLESmodel.
SIGHT LINES MCxx Model intended to store sight lines and visibility envelope strings resulting from Visibility
Analysis.Separatesightlinemodelsaremaintainedforeachmasterstring.
NOTE:THESEMODELSAREINTENDEDFORPRELIMINARYUSEONLYANDARETECHNICALLYCONSIDERED'RECORD'
FILES.NOMODIFICATIONSARETOBEMADEWITHOUTTHEAPPROVALOFTHEPRELIMINARYDESIGNENGINEER.
FINALDESIGNMODELS
Whenaprojectisturnedover,thepreliminarydesignengineershallprovidetheteamwithalistofthemodelsand
pertinentstringsineach.ThefinalteamwillcopythepertinentstringsintotheappropriateFinalDesignmodels.
FinalworkshouldnotbedoneonPreliminaryDesignmodels.
FALIGN
FDESIGNMCxx
FSECTMCxx
ModeldescriptionsareidenticaltoPreliminaryDesignmodelswiththeexception
thattheyareforFinalDesignuse.
FTRIANGLES Model containing the final triangulation string (TRIP) based on the proposed design template and
interface strings contained in the FDESIGN MCxx model. A PBRK or boundary stringmay be created to prevent
contoursfrombeinggeneratedoutsidethelimitsoftheinterface(slope)lines.Thesestring(s)wouldbestoredin
theappropriateFDESIGNMCxxmodel.
FCONTOURSModeltocontainthefinalcontoursgeneratedbysurfacingtheFTRIANGLESmodel.
NOTE:THESEARETHEMOSTCOMMONLYENCOUNTEREDMODELSONAPROJECT.WHENCREATINGADDITIONAL
MODELS,USENAMESTHATEASILYANDACCURATELYREFLECTTHEINFORMATIONCONTAINEDINTHEMODEL.
OTHERMODELS
MICROSTATIONALIGNMENT AtemporarymodelusedtostorealignmentstransferredfromMicroStationtoMX.
XSDETAILMCxx Surveydetailpointsasfeaturestringstobeusedfordevelopingcrosssections.
Part VIII Appendix
56
April 2012
APPENDIX D MX DATA TRANSFER FORMATS
LANDXML
TheuseofLandXMLisencouragedfortransferringdesigndata.LandXMLwasestablishedtoexchangedesigndata
utilizing a nonproprietary data standard. LandXML is the easiest avenue for transferring alignments between
designsoftwares,including(butnotlimitedto)MX,InRoads,andGeopak.
SurveydataandsurfacetriangulationsmayalsobetransferredviaLandXML.Howeveratthistime,therearestill
limitations when transferring large models (surfaces). Therefore, it is strongly recommended to translate only
essentialdata.
ImportingLandXMLdatatoMXandexportingMXdatatoLandXMLaredocumentedonthedepartmentswebsite.
Also,learnmoreaboutLandXMLatwww.LandXML.org.
TraditionalformatsusedforimportingalignmentdatatoMXarealsodescribedbelow.
HALGN
HALGNshouldonlybeusedfortransferringalignmentdatabetweentwogroupswhobothuseMX.LandXML
shouldbeusedtotransferalignmentdatabetweendifferentdesignsoftware.HALGNisanASCIIformatthatcan
beusedtodefineahorizontalalignmentinMXusingstraightandcircularelements.
Amaximumof500elementsmaybeprocessed.
Singleelementalignmentsmaybedefined.
SAMPLEHALGNINPUTDATA
MOSS
EDIT,PALIGN
004,3=MC4A
004,3=GC4A
999
HALGN,PALIGN,PALIGN
300,LB=MC4A,SC=10000.000,CF=10000.000,CE=25.000,TL=0.100
301,1,SX,X1=1074148.120202,Y1=386094.810662,X2=1074100.198409,Y2=386000.78602
6
301,2,LE,RA=150.000000
301,3,SX,X1=1074100.198409,Y1=386000.786026,X2=1074173.873438,Y2=385776.46549
7
301,4,RE,RA=150.000000
301,5,SX,X1=1074173.873438,Y1=385776.465497,X2=1074187.614075,Y2=385623.90322
2
301,6,LE,RA=150.000000
301,7,SX,X1=1074187.614075,Y1=385623.903222,X2=1074439.853660,Y2=384526.11973
9
April 2012
57
Part VIII Appendix
301,8,RE,RA=675.000000
301,9,SX,X1=1074439.853660,Y1=384526.119739,X2=1074076.050658,Y2=384210.19930
7
999
FINISH
DESCRIPTIONOFHALGNFORMAT
MOSS .............................................................MXfilesbeginwiththislinetoclearanypreviouserrors
EDIT,PALIGN.............................................TellsMXtoEDITthemodelcalledPALIGN.Forsimplicityalwaysuse
thismodelnameinfilesgeneratedfromotherdesignpackages.
004,3=MC4M ...............................................The004optiontellsMXtodeletethestringlabeledMC4Mifit
currentlyexists.MXalignmentsarenamedwith4characterlabels
beginningwith"MC".Thethirdcharacterisselectedbytheuserand
canbeanyalphanumericcharacter.However,theselectedcharacter
cannotbeusedformorethanonealignment.SeetheDesignstring
labelingconventionontheCAD/Dwebsitefortheappropriatefourth
character.
004,3=GC4M ...............................................DeletethecorrespondingGeometryString.Usethelabelabove
changingtheinitialcharacterto"G"
999................................................................TellsMXtoendtheEDITcommand
HALGN,PALIGN,PALIGN..........................BegintheHALGNoption.Includethemodelnametwice.
300,LB=MC4M,SC=10000.000,CF=10000.000,CE=25.000,TL=0.100
Initiatethealignment.
LB=Alignmentlabel
SC&CFarestartstation.Thesenumbersshouldmatch
CE=Stationinterval.Typically25forImperialprojects,10formetric
TLisacurvetolerance,use0.1
301,1,SX,X1=1074148.120202,Y1=386094.810662,X2=1074100.198409,Y2=386000.78602
6
Tangentandcurvesectionsaredefinedusingoption301.Thefirst
fieldafterthe301recordisasequencenumberbeginningat1.The
followingcodetellsthetypeofelement;SX=Tangent,LE=Lefthand
curve,RE=Righthandcurve.
X1,Y1arecoordinatesatthebeginningofthetangentsection
X2,Y2arecoordinatesattheendofthetangentsection
301,2,LE,RA=150.000000...................Thislinecreatesalefthandcurvebetweenthetangentintheline
aboveandtheonebelowwitharadiusof150.
301,3,SX,X1=1074100.198409,Y1=386000.786026,X2=1074173.873438,Y2=385776.46549
7
301,4,RE,RA=150.000000
301,5,SX,X1=1074173.873438,Y1=385776.465497,X2=1074187.614075,Y2=385623.90322
2
301,6,LE,RA=150.000000
301,7,SX,X1=1074187.614075,Y1=385623.903222,X2=1074439.853660,Y2=384526.11973
9
301,8,RE,RA=675.000000
301,9,SX,X1=1074439.853660,Y1=384526.119739,X2=1074076.050658,Y2=384210.19930
7
999
FINISH.........................................................Indicatestheendofinputdata
Part VIII Appendix
58
April 2012
VERAT
VERATshouldonlybeusedfortransferringalignmentdatabetweentwogroupswhobothuseMX.LandXML
shouldbeusedtotransferalignmentdatabetweendifferentdesignsoftware.VERATisanASCIIformatthatcan
beusedtodefinetheverticalcomponentsofapreviouslycreatedMXalignment.
SAMPLEVERATINPUTDATA
MOSS
VERAT,PALIGN,PALIGN
MC4M,10000.000000,10145.714000,7=9
10000.000000,328.220000
10003.600000,328.097000,0.010000
10004.800000,328.037000,0.010000
10010.800000,327.867000,0.010000
10041.000000,327.500000,40.000000
10095.000000,327.875477,30.000000
10118.624000,329.271000,0.010000
10135.902000,330.756000,0.010000
10145.714000,331.789000
999
FINISH
DESCRIPTIONOFVERATFORMAT
MOSS .................................................................................. MXfilesbeginwiththislinetoclearanypreviouserrors

VERAT,PALIGN,PALIGN............................................... BegintheVERAToption.Includethemodelnametwice.
MC4M,10000.000000,10145.714000,7=9 ........... Begintheprofiledefinitionintheformat:
Stringlabel,startstation,endstation,7=numberofprofile
pointsdefined
10000.000000,328.220000 ..................................... StartdataBeginningstation,elevation
10003.600000,328.097000,0.010000................ VerticalPIpointStation100+03.6,elevation328.097,
0.01curvelength
The0.01curvelengthisusedtoindicateagradebreak.
Inthiscasethealignmentiscrossinganotherroadwayat
anintersection.Station100+03.6isthepointwherethe
alignmentcrossestheedgeoftravelledwayonthe
intersectingroad.
10004.800000,328.037000,0.010000
10010.800000,327.867000,0.010000
10041.000000,327.500000,40.000000 ............. thislineshowsaverticalcurvewithalengthof40atVPI
station100+41,elevation327.5
10095.000000,327.870000,30.000000
10118.624000,329.271000,0.010000
10135.902000,330.756000,0.010000
10145.714000,331.789000 ..................................... Endofprofilestationandelevation.
999..................................................................................... TellsMXtoendtheVERATcommand
FINISH.............................................................................. Indicatestheendofinputdata
April 2012
59
Part VIII Appendix
Part VIII Appendix
60
April 2012
APPENDIX E CONSTRUCTION REPORTS

SAMPLEALIGNMENTREPORT(COGOSTYLE)
Description of ALIGNMENT M101
-----------------------------*ELEMENT
1 TANGENT
PBT
156+00.00
PC
500899.844
98356.927
500899.844
98356.927
500747.591
98532.771
158+45.26
1909.860
462.917
232.598
14.112
14.008
160+75.58
April 2012
03 00 00
13 53 15
461.784
S 56 03 22.5 E
500641.993
98740.017
500641.993
98740.017
1993.548
180+69.13
499736.941
100516.282
499736.941
100516.282
499670.171
100647.325
182+16.20
DIRECTION
2864.789
293.889
147.073
3.773
3.768
183+63.02
*ELEMENT
5 TANGENT
PT
183+63.02
PAT
DEGREE=
DELTA=
L CHORD=
L CH BRG=
DISTANCE
RADIUS=
LENGTH=
TANGENT=
EXTERNAL=
MID ORD=
PT
S 49 06 45 E
LEFT
*ELEMENT
4 CURVE RIGHT
PC
180+69.13
PI
DIRECTION
98347.355
156+12.66
*ELEMENT
3 TANGENT
PT
160+75.58
PC
12.662
RADIUS=
LENGTH=
TANGENT=
EXTERNAL=
MID ORD=
PT
500908.132
DISTANCE
*ELEMENT
2 CURVE
PC
156+12.66
PI
S 63 00 00 E
DEGREE=
DELTA=
L CHORD=
L CH BRG=
02 00 00
05 52 40
293.760
S 60 03 40 E
499590.333
100770.842
499590.333
100770.842
DISTANCE
1550.624
199+13.64
DIRECTION
498748.578
61
S 57 07 20 E
E
102073.104
Part VIII Appendix
SAMPLEALIGNMENTREPORT(COORDINATES)
Point
North
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
500004.15
500008.48
500010.22
500012.81
500017.14
500021.47
500025.80
500026.69
500030.13
500034.46
500038.79
500043.12
500047.45
500051.78
500052.40
500056.11
500060.45
500064.79
500069.13
500073.47
500077.82
500082.17
500086.52
500090.88
500095.24
500099.60
500103.97
500108.34
500112.71
500117.09
500121.47
500125.85
500130.24
500134.63
500139.02
500143.42
500147.81
500152.21
500156.62
500161.03
500165.44
500169.85
500174.27
500178.69
500183.11
500187.54
500191.97
500196.40
500200.83
500205.27
500209.71
Part VIII Appendix
East
Elevation
Station
636.90
637.00
637.04
636.99
636.89
636.79
636.69
636.67
636.51
636.32
636.13
635.95
635.78
635.62
635.60
635.47
635.33
635.20
635.08
634.97
634.87
634.77
634.69
634.61
634.55
634.49
634.44
634.41
634.38
634.36
634.35
634.35
634.36
634.37
634.40
634.44
634.48
634.54
634.60
634.66
634.72
634.78
634.84
634.90
634.96
635.02
635.08
635.14
635.20
635.26
635.32
70100.00
70105.00
70107.01
70110.00
70115.00
70120.00
70125.00
70126.02
70130.00
70135.00
70140.00
70145.00
70150.00
70155.00
70155.72
70160.00
70165.00
70170.00
70175.00
70180.00
70185.00
70190.00
70195.00
70200.00
70205.00
70210.00
70215.00
70220.00
70225.00
70230.00
70235.00
70240.00
70245.00
70250.00
70255.00
70260.00
70265.00
70270.00
70275.00
70280.00
70285.00
70290.00
70295.00
70300.00
70305.00
70310.00
70315.00
70320.00
70325.00
70330.00
70335.00
99991.85
99994.35
99995.36
99996.85
99999.35
100001.85
100004.35
100004.86
100006.85
100009.35
100011.85
100014.35
100016.85
100019.35
100019.71
100021.85
100024.34
100026.83
100029.31
100031.79
100034.26
100036.72
100039.18
100041.63
100044.08
100046.52
100048.95
100051.38
100053.81
100056.23
100058.64
100061.04
100063.45
100065.84
100068.23
100070.61
100072.99
100075.36
100077.73
100080.09
100082.45
100084.80
100087.14
100089.48
100091.81
100094.13
100096.45
100098.77
100101.08
100103.38
100105.68
62
April 2012
APPENDIX F CROSS SECTION SET LABELS

(Itemsinitalicshavebeenaddedsincethepreviousversionofthisdocument)
SectionSet
0,1
2
3
4,5,6,7
8,9
A,B
C
D
E
F
G,H,I,N,O,P,Q,S,T,U.V
J
K
L
M
R
W
X
Y
Z
FeatureName
*available*
Environmentlines
Rightofwaylines
*available*
Buildingsills
*available*
Other
Design
ExistingGround
Subgrade
*available*
MiscSectionJ
MiscSectionK
MiscSectionL
MiscSectionM
DrainagePipes
DetailFeatures
OldGroundElevations
General
Temporary
MXLabel
VB,VH,VO,VT,VZ,WD
BC,BN,BP,BR,BS,BT
BD
Determinedbyuser
Designmodel
Triangulation
XC*seetablebelow
*seetablebelow
OC
UsedbyMXwizards
CROSSSECTIONDETAILFEATURESTRINGS
April 2012
MXLabel
FeatureName
X0,X1
Coniferous&DeciduousTrees
X2
Environmentlines
X3
Rightofwaylines
X4,X5
JointPole
X6,X7
Hydrant
X8,X9
Buildingsills
XA,XB
GuyPole
XC,XD
DrainagePipes
XE
DrainageStructureSumps
XG,XH
LightPole
XI,XJ
JointPolewithLight
XK,XL
PowerPolewithLight
63
Part VIII Appendix
XM,XN
Pole
XO,XP
PowerPole
XQ,XR
TelephonePole
XS
CatchBasin
XT
DropInlet
XU
DrainageManhole
XV
UtilityManholes
Part VIII Appendix
64
April 2012

Microstation Cadd Procedures

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Microstation Cadd Procedures

Hochgeladen von

Copyright:

Verfügbare Formate

STATE OF NEW HAMPSHIRE

2012 CAD/D P ROCEDURES

EFFECTIVE: APRIL 12, 2012

NHDOT CAD/D Procedures and Requirements

PART I GENERAL INTRODUCTION........................................................................... 1

PART II GENERAL CAD/D INFORMATION ............................................................... 9

PART III MICROSTATION......................................................................................... 15

NHDOT CAD/D Procedures and Requirements

Text Styles ..................................................................................................................................................................19

NHDOT CAD/D Procedures and Requirements

PART VI OTHER PROJECT DATA........................................................................... 35

PART VII - ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS ......... 37

PART VIII - APPENDIX................................................................................................. 45

NHDOT CAD/D Procedures and Requirements

PART I GENERAL INTRODUCTION

ABOUT THE COVER

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

ConsultantdeliverablespecificationsrelocatedfromvariouspartsofthedocumentandcombinedasPART VII ENGINEERING CONSULTANT DELIVERABLE REQUIREMENTS

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

CURRENT NHDOT SOFTWARE VERSIONS

Part I General Introduction

NHDOT CAD/D Procedures and Requirements

PART II GENERAL CAD/D INFORMATION

PROJECT JOURNAL FILES

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

Part II General CAD/D Information

NHDOT CAD/D Procedures and Requirements

PART III MICROSTATION

LEVEL ASSIGNMENTS AND SYMBOLOGY

NHDOT CAD/D Procedures and Requirements

REFERENCE FILE ATTACHMENTS

NHDOT CAD/D Procedures and Requirements

The global origin has been set at 500, 500, 10000

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

TEXT HEIGHT AND SPACING

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements

BATCH PRINT/PRINT ORGANIZER

NHDOT CAD/D Procedures and Requirements

NHDOT CAD/D Procedures and Requirements