Electronic Data Guidelines - GEORGIA DEPARTMENT OF .
GDOTELECTRONIC DATA GUIDELINESGEORGIA DEPARTMENT OF TRANSPORTATIONELECTRONIC DATA GUIDELINESSecond EditionMarch 15, 2004Current Revision Date:March 15, 2006Previous Revision Date:December 14, 1998
GDOTELECTRONIC DATA GUIDELINES1-2 TABLE OF CONTENTSElectronic Data Guidelines (Section ronic Data Guidelines CoverTable of ContentsDisclaimerEDG Revision SummaryGeneral InformationCurrent DOT Software VersionsGuidelines for Submitting Electronic DataGraphic StandardsMinimum Text for Right of WayFile Conversion-Metric/EnglishSaving Plotted ViewsFile LocationsMiscellaneous ItemsDesign File Names and Level Schemes (Section 2)2-12-22-32-4Design File Names and Level Schemes CoverConstruction Plan AssemblyPlan Sheet LevelsConstruction Plan Assembly Sheets Sections(1) Cover(2) Index(3) Revision Summary(4) General Notes(5) Typical Sections(6) Summary Quantities(7) Quantities Amendment(8) Quantities (Construction)(9) Detailed Estimate(10) Traffic Diagram(11) Construction Layout(12) Misc. Maps(13) Mainline Plan(14) Crossroad Plan(15) Mainline Profile(16) Crossroad Profile
GDOTELECTRONIC DATA GUIDELINES2-4Construction Plan Assembly Sheets Sections (continued)(17) Driveway Profiles(18) Special Grading(19) Staging Plan(19) Staging Profiles(19) Staging Cross Sections(20) Staging Details(21) Drainage Area Map(22) Drainage Profiles(22) Drainage Xsections(23) Earthwork Cross Sections(24) Utility Plans(25) Lighting Plans(26) Signing and Marking Plans(27) Signal Plans(28) ATMS Plans(29) Landscaping Plans(30) Mitigation Plans(31) Retaining Wall Envelope(32) Retaining Wall Plans(33) Sound Barrier Envelopes(34) Sound Barrier Plans(35) Bridge Plans(36) Culvert Plans(37) Miscellaneous Structures(38) Special Construction Detail(39) Special Culverts(40) Construction Details(41) Georgia Standards(50) Erosion Cover(51) BMP General Notes(52) ERC Drainage Area Map(53) BMP Location Details(54) CMP General Notes(55) Watershed Map CMP Plan(56) Erosion Construction DetailRight-of-Way2-52-6Reference: File Names (List)Reference: Names and Level SchemesMAINDRNGREQDAlignment, edge of pavementDrainage (Plan View)Required Right-of-Way and easements
GDOTELECTRONIC DATA GUIDELINES2-6Reference: Names and Level Schemes Signing and Pavement markingSignalsAutomated Traffic Management SystemUtilities (Existing)Utilities (Proposed)Existing ContoursFinal ContoursConstruction LimitsStaging/Erosion Control (per stage #)Existing Property InformationExisting TopographyExisting Environmental and Cultural ResourcesProposed Environmental and Cultural ResourcesLandscapingLightingTraffic diagramRight of way and easement tablesTypical SectionsWalls (plan view)Walls (profile view)Construction LayoutSheet Layout LocationSupporting Files (Downloaded) (Section 3)3-13-2Supporting Files (Downloaded) CoverCell Libraries
GDOTELECTRONIC DATA GUIDELINES1-3 DISCLAIMERThe guidelines contained in this document are for reference only. Thematerial contained is provided without warranty or liability of any kind to theDepartment. Every effort has been made to make the documentation ascomplete and accurate as possible without errors.This information is provided on an "as is" basis. Updates to these guidelineswill be made as needed due to any errors found in the documentation, newprograms, changes in software, software enhancements, or as policy andmanagement dictate.As with any documentation or guidelines, improvements can and should bemade. Any additions, suggestions or comments for improvement areencouraged. This documentation is not meant to be a complete instructionaldocument. The intent is to provide guidelines that, if followed, will result inbetter quality and consistency for electronic plans and documents.Any recommendation for improvement to this documentation is welcomed.Any errors found should be brought to the attention of the DOT socorrections can be made. Any additional information or detailed explanationneeded to this documentation should be documented and mailed to:Director of PreconstructionGeorgia Department of TransportationNo. 2 Capitol Square S.W.Atlanta, Georgia 30334Attn: Plan Presentation CommitteeOr email to:PPC@dot.state.ga.us
GDOTELECTRONIC DATA GUIDELINES1-4 EDG REVISION SUMMARYGDOT EDG, Second Edition Creation Date: March 15, 2004Any subsequent revisions to this document shall be documented below.RevisionsDate3/15/06DescriptionLinestyles – modified and/or added various linestyles for Utilities,Erosion Control, Signing & Marking, etc “”Level assignments and menu functions– modified menu levelfunctions to correspond to EDG specifications“”Cells – updated and/or added various cells to existing libraries“”Menus – added/revised menu functions for several “FutureDevelopment” items
GDOTELECTRONIC DATA GUIDELINES1-5 GENERAL INFORMATIONTerm EDGIn places where EDG is mentioned in this document, unless otherwise stated, itrepresents an acronym for Electronic Data Guidelines and not the MicroStationEDG utility which is a graphics design file editor.English UnitsThis document and the supporting CADD Standard files were written based uponProjects with English Units. Metric versions of these items will only be producedif the Department decides to start new projects in the Metric format.Reference FilesThe use of MicroStation reference files is required to prevent duplicate designinformation. Therefore, project design elements should exist in only one designfile in most cases.TopographyOnly one topography file will exist for a project. Topography updates must becoordinated between the project manager and the SDE.As a general rule, topography files will remain independent files and should not bemodified. However, special situations may require manipulation of these files atthe discretion of the project manager and may require coordination with the projectSDE. Only topographic information should be included in topo files. Nocenterline information should be created or shown in the topography files.
GDOTELECTRONIC DATA GUIDELINESGDOT Root MenuThe GDOT Root Menu was developed to minimize common repetitive tasks of theplan sheet development process. This menu also aids with compliance to thecurrent GDOT EDG by automating many of the steps needed for reference file andlevel settings. Further development of this menu is ongoing and we welcome yourfeedback and suggestions.For help with using the GDOT Root Menu, please see the videos whichdemonstrate the creation of the following files: MATCHLINE.dgn,SHEETLAYOUT.dgn, and a Construction and Utility plan sheet.
GDOTELECTRONIC DATA GUIDELINES1-6 CURRENT DOT SOFTWARE VERSIONSThe current versions of major software used and accepted by the Georgia DOT areidentified on the R.O.A.D.S. tion/r-o-a-d-s/More recent versions than those identified on this website will not be accepted.All project deliverables must be submitted in CAiCE and Microstation softwareformat. Technical support and documentation for CAiCE and Microstationversions other than the version identified on the R.O.A.D.S. website will not besupported by the Georgia DOT. The INI files, sheet commands, grid files, menus,workspaces, etc., provided by the DOT may not work for other versions.Support for Microstation Software VersionsThe only accepted CADD software used by the Georgia DOT is MicroStation.Only the MicroStation J file format is acceptable for transmitting CADD filesto the department. The Microstation V8 file format will not be accepted bythe department. While Microstation V8 offers many new features that will assistthe department in the future, the department will not move to that format until ithas been adequately tested and methodology and procedures put in place totransition existing projects to the V8 file format.Translation tables, conversion tables, or special software programs have not beencreated or standardized for exchanging information between common file formatssuch as DXF, DWG, ICES, IGES, or software such as Autocad, ARCVIEW,ARCINFO, etc.MicroStation provides methods for exchanging select file types but data is oftenmodified during the process. Improvements have been made and are beingevaluated. If CADD software other than MicroStation J is used, those files shouldbe converted to MicroStation J file format and thoroughly reviewed prior totransmitting to the department.
GDOTELECTRONIC DATA GUIDELINES1-7 GUIDELINES FOR SUBMITTING ELECTRONIC DATA TOTHE DEPARTMENTAll electronic data furnished to the GA DOT shall use the appropriate namingscheme and format for the type of data to be transmitted. It is very important toclearly communicate what is being transmitted and to describe the format of thetransmitted files.A letter is to be attached to all submissions stating briefly:1.File content2.File Format (zipped, XP, 2000, MicroStation, CAiCE etc. and the utilityused)3.CAiCE or MicroStation version (as identified on R.O.A.D.S. website)4.Number of CDs .5.Files must be in the proper format before transmitting to the DOT. Notranslating of information by DOT personnel shall be required.6.If files are zipped or backed up, a brief explanation of the recommendedprocedure to extract the files should be included.7.Versions of software must be current to or fully compatible with that of theGA DOT.8.Each disk submitted shall be labeled and dated with a minimum of the PI#and date. If a series of disks are transmitted, the disk label shall also includethe disk number and the total disks of that set, (ex: 1 of 10). Othersubsequent disks shall be labeled so as to uniquely identify each group or setand shall include the sequence number followed by the total number in thegroup (ex: 2 of 10, 3 of 10, etc.)9.The DOT reserves the right to reject any file transmitted that does notconform to these guidelines.Deviation from FormatAny file to be submitted that deviates from the above mentioned format musthave prior DOT approval. The approval must be in writing with the name ofthe individual from the DOT who permitted the varying format.
GDOTELECTRONIC DATA GUIDELINESUsing Backup, Disks, and CompressionIn general, all files are to be furnished on one of the following in order ofpreference:1) CD’s2) FTPWinzipIf data compression is necessary, WINZIP will be the standard format used. TheWINZIP executable shall be included with the transmitted files. If a file or a groupof files is too large to be copied on a single diskette, then a zip disk or CD isrecommended.
GDOTELECTRONIC DATA GUIDELINES1-8 GRAPHIC STANDARDSMicroStationColor Tables:The Department has two acceptable Microstation color table formats:GDOTcolor.tblfor use in plan file production.GDOTDcolor.tblfor use in concept layouts (public ine Code:LC #01234567Æ RESULTING LINE STYLESOLIDDOTTEDMEDIUM DASHLONG DASHDOT DASHSHORT DASHDASH DOT DOTLONG DASH SHORT DASH
GDOTELECTRONIC DATA GUIDELINESMicroStationWeight Number:WT #ÆRESULTING WEIGHT / THICKNESS012345678910111213141510 5"WEIGHT VS. THICKNESS* NOTE: MicroStation weights range from 0 to 31. The resulting weight asshown above is not a MicroStation design file thickness value as viewed on themonitor screen, but is the measured width or thickness on a hardcopy plot from anoutput device such as a plotter. The resulting value may vary slightly inappearance or measured width due to plotter specific controls. A measured valueof width or thickness as shown above is desired and must be obtained within areasonable tolerance.Experience indicates there is no problem meeting the above guideline for thicknessand appearance. For that reason, a tolerance value is not specified. If upon reviewof plans submitted to the Department or submitted by another office of theDepartment, it is found that the line thickness, weight, or style does not meet theDepartments guidelines, the Department shall reserve the right to reject thoseplans.
GDOTELECTRONIC DATA GUIDELINESMicroStationUser Defined Line Styles:The Department has created over 450 user defined line styles for use in displayingUtilities, Erosion Control Items , Guardrail , Fencing and many other lineardisplayed features. The only acceptable line styles that the Department will acceptare those that the Department has provided. Any suggestions for future line stylesshould be submitted to the Plan Presentation Committee.Email to:PPC@dot.state.ga.usMicrostation - File FormatFrom the MicroStation (IGDS) file type, the number of units of resolution are:4,294,967,295 or 2 to the 32nd power 1.The English Seed file is noted as GDOT2D.DGN and is different than theSEED2D.DGN provided with the MicroStation software.The originalSEED2D.DGN file provided with MicroStation should not be used for creatingfiles for the DOT.English UnitsFOR ALL ENGLISH MICROSTATION FILESMicroStation J file format is to be used for all CADD files submitted using thefollowing working units:Master Units:Sub Units:Resolution:Positional Units:Working area ofFTth100014,294,967th per FT(Positional Units per th)FT squareThe GDOT2D.dgn seed file has been set with a Global Origin as follows:GO 0,0XY -2147483647,-2147483647This provides a design plane for a range in coordinate values (x,y) from(0,0) to (4,294,967.295,4,294,967.295). If coordinates are placed on or outside thedesign plane, a problem with the file will result.
GDOTELECTRONIC DATA GUIDELINES1-9 MINIMUM TEXT SIZE FOR RIGHT OF WAY PLANSEnglish Text Size GuidelinesThe minimum size for text on a set of English Right of Way plans and plans ingeneral is to be 0.15 inches on the final D size plot.Text information shown on Right of Way plan sheets should be placed at aminimum size of (0.15 X the scale for the plans). Plans are usually done at 1 inchequals fifty feet (1" 50') which would equal a text size of 7.5ft (0.15 x 50 7.5) orfor 1 inch equals twenty feet (1” 20’) which would equal a text size of 3.0ft (0.15x20 3.0).NOTE ON WEIGHT FOR TEXTIt is important on small text to keep the weight to a maximum of weight 2 andpreferably either weight 0 or 1. Heavier weights, especially numbers, whenreduced to a small document will appear as blurred objects and are not legible.Why the minimum size and weight for textA minimum text size on Right of Way plans must be followed for several reasons.The most important is the requirement for filing legible courthouse documents,deeds, etc. Plans, or selected areas of plans are often reduced to a letter sizedocument to provide the legal description to be filed in the courthouse as the finaldocument. The minimum text size guideline was established to meet the need ofthis requirement.There are situations where the text size may be smaller but this generally applies toconstruction plans. The final output is also dependent on the device used forgenerating the final plot or hardcopy. The above guideline for text size consideredthese factors and more when selecting the size.
GDOTELECTRONIC DATA GUIDELINES1-10 FILE CONVERSION -- Metric / EnglishWhen converting meters to feet and extreme accuracy is needed, use theconversion factor for U.S. Survey Feet rather than the slightly different factor forthe International Foot. The factors are as follows:U.S. Survey Feet (GA DOT plans)For conversion of meters to U.S. Survey Feet, multiply the meters by 39.37 dividedby 12 which is 3.28083333333 to 12 significant figures.To further explain: using 1 meter 39.37 inches, and converting to meters per feet,((1 m / 39.37 ") x (12 " / ft)) 0.3048006096012 m/ft or rounding for afactor of 0.3048International FeetFor conversion of meters to International Feet, multiply the meters by 100.0divided by 30.48 which is 3.28083989501 to 12 significant figures.To further explain: using 25.4 millimeters 1 inch, and converting to meters perfeet,((25.4 mm / 1 ") x (12 " / ft) x (m / 1000 mm)) 0.3048000000000 m/ft orrounding for a factor of 0.3048
GDOTELECTRONIC DATA GUIDELINES1-11 SAVING VIEWS IN MICROSTATION FOR PLOTTINGProblem:Recalling information to plotWhen design files are provided for review, modification, revision, etc., thepersonnel viewing or modifying the design files cannot easily determine whichreference files were attached or what levels were displayed in producing the finalhardcopy plot.Solution:Super Saved ViewsFor each sheet file and all major files for which a plot is created from, a SuperSaved View called GPLOT should be created that contains the exact levelsdisplayed for the active file and all reference files attached which produce the finalplot.Once the file is rotated on the screen correctly, view attributes set correctly, allfiles attached with appropriate levels displayed and all reference files clipped, theuser can either use the GDOT Root Menu command, Save Super View GPLOTor key-in MACRO SV GPLOT to save the view. This will create a file with theprefix the same as the design file plus the following extension GPLOT.svb.Example123456CP01 GPLOT.svbThese .svb files should be included in any submission of project plans todepartment personnel.For example, assuming the design file 123456CP01.DGN for mainline will beopened in MicroStation for review or modification and the plotting informationwas saved in a Super Saved View named GPLOT, the reviewer would open thedesign sheet file in MicroStation by either accessing the GDOT Root Menu andselecting Recall Super View GPLOT or by the key-in MACRO VI GPLOT. Thisshould display the file exactly as it appeared when the Super Saved View ofGPLOT was created.The two macros SV and VI are provided with the Georgia DOT Microstationdownload.
GDOTELECTRONIC DATA GUIDELINES1-12 FILE LOCATIONSUSING PI # FOR SUBDIRECTORYThe P.I.# less the first character followed by four characters shall be used todescribe the type of MicroStation design file.Assuming the drive letter C:\ is used as the root directory and a PI Number of0001234 is the active project, the first number of the PI number, 0 for this project,should be dropped and the appropriate file type added. The resulting file prefixwould now be the 6 digit number 001234 plus the 4 character description.Example: 001234MAIN.dgnfor the main design file.This naming convention allows many of the processes in attaching reference filesto be automated. The 6 digit number prefix must be used in order for theseautomation tools to function properly.All design file names must use the 6 digit PI Number as part of the file name withthe exception of the Sheetlayout.dgn and the Matchline.dgn files.All MicroStation files should be located in a subdirectory of the PI Number named\DGN\.Example:C:\001234\DGNNote: Microstation reference files should be attached without the Save Full pathoption on. By following the conventions set forth in the file names and theirlocations, the project will work whether or not a drive letter changes due to thetransfer of files.CAiCE Archive files should be stored in a subdirectory of the PI Number named\CAiCE\.Example:C:\123456\CAiCE
GDOTELECTRONIC DATA GUIDELINES1-13 MISCELLANEOUS ITEMSA clipped boundary should be placed so that a match line is created for theadjacent sheets to be plotted. This minimizes the possibility for duplication of databetween plan sheets.It is recommended to display levels on a final plot as illustrated later in theseguidelines. This will help ensure consistency as well as assist in the automation ofprocedures. As with any document there may be items that have not beenaddressed and the project designer will need to make the final determination oflevel display for each sheet. Documentation must be provided for informationplaced in Microstation files that are not listed in Sections 2-4 and 2-6.Documentation of procedures and project history should be maintained in a projectlog file.
GDOTELECTRONIC DATA GUIDELINESELECTRONIC DATA GUIDELINES2-1 Design File Names and Level SchemesThe following sections describe in a spreadsheet format the Design File Name andLevel Conventions that should be used on Georgia DOT plans.
Construction Plan AssemblyConstruction Plan AssemblySection Number and TypeDesign File Name(s)6 Digit PI Numberfollowed by TYPE andSheet NumberDescription(1)Cover123456CV01.DGNCover Sheet(2)Index123456IN01.DGNIndex Sheet(3)Revision Summary123456RV01.DGNRevision Summary Sheet(4)General Notes123456GN01.DGNGeneral Notes/Project Notes (may be included with Detailed Estimate Sheet)(5)Typical Sections123456TY01.DGNTypical Sections(6)Summary Quantities123456QN01.DGNSummary of Quantities (including Signing & Marking & Signal Quantities)(7)Quantities Amendment123456QA01.DGNQuantities Required by Amendment(8)Quantities (Construction)123456QC01.DGNQuantities Required on Construction(9)Detailed Estimate123456DT01.DGNDetailed Estimate(10)Traffic Diagram123456TR01.DGNTraffic Diagram(11)Construction Layout(12)Miscellaneous Maps (New LocationProjects only)123456CL01.DGNConstruction Layout Sheet (Stakeout Sheet)123456MM01.DGNMiscellaneous Maps and/or Aerial Photo Mosaics (New Location Projects only)(13)Mainline Plan123456CP01.DGNMainline Roadway Plan Sheets (plan & profile may be on same sheets)(14)CrossRoad Plan123456XR01.DGNCrossroad, Side Street, and Frontage Road Plans (plan & profile may be on same sheet)(15)Mainline Profile123456PR01.DGNMainline Roadway Profile Sheets(16)Crossroad Profile123456XP01.DGNCrossroad, Side Street, and Frontage Road Profile Sheets3/30/2006Construction Plan Assembly
Construction Plan AssemblyConstruction Plan AssemblySection Number and TypeDesign File Name(s)6 Digit PI Numberfollowed by TYPE andSheet NumberDescription(17)Driveway Profile123456DR01.DGNDriveway Profiles(18)Special Grading123456GR01.DGNSpecial Grading Sheets (Sediment/Detention Basins, Parking Lots, etc )(19)Construction Staging Plan Sheets123456ST01.DGNConstruction Staging Plan Sheets(19)Construction Staging Profile Sheets123456SP01.DGNConstruction Staging Profile Sheets(19)Construction Staging Cross-Sections123456SX01.DGNConstruction Staging Cross-Sections(20)Staging Details123456SD01.DGNStaging Details(21)Drainage Area Map123456DM01.DGNDrainage Area Map(22)Drainage Profiles123456DP01.DGNDrainage Profiles(22)Drainage Cross-Sections123456DX01.DGNDrainage Cross-Sections(23)Earthwork Cross Sections123456XS01.DGNEarthwork Cross Sections(24)Utility Plans123456UT01.DGNUtility Plans(25)Lighting Plans123456LT01.DGNLighting Plans and Details(26)Signing and Marking Plans123456SM01.DGNSigning and Marking Plans and Details(27)Signal Plans123456SG01.DGNSignal Plans(28)ATMS Plans123456AT01.DGNATMS/ITS Plans(29)Landscaping Plans123456LS01.DGNLandscaping Plans and Details3/30/2006Construction Plan Assembly
Construction Plan AssemblyConstruction Plan AssemblySection Number and TypeDesign File Name(s)6 Digit PI Numberfollowed by TYPE andSheet NumberDescription(30)Mitigation Plans123456WM01.DGNMitigation Plans (Wetland, etc )(31)Retaining Wall Envelopes123456WE01.DGNRetaining Wall Envelopes(32)Retaining Wall Plans123456WL01.DGNRetaining Wall Plans (MSE, Tie-Back, Cast-In-Place, etc )*(33)Sound Barrier Envelopes123456SE01.DGNSound Barrier Envelopes(34)Sound Barrier Plans123456SB01.DGNSound Barrier Plans*(35)Bridge Plans123456BR01.DGNBridge Plans and Bridge Standards*(36)Culvert Plans123456CU01.DGNCulvert Plans*(37)Miscellaneous Structures123456MS01.DGNMiscellaneous Structural Plans (Buildings, tollbooths, ice canopies, etc )*(38)Special Construction Detail123456DS01.DGNSpecial Construction Details - Project Specific (ADA, Special Design Drainage Structures, etc )(39)Special Culverts123456SC01.DGNSpecial Design Box Culverts(40)Construction Details123456CD01.DGNConstruction Details(41)Georgia Standards123456GS01.DGNGeorgia Standards* Structural Plans designed by the Office of Bridge and Structural Design or Structural Consultants3/30/2006Construction Plan Assembly
Construction Plan AssemblyConstruction Plan AssemblySection Number and TypeDesign File Name(s)6 Digit PI Numberfollowed by TYPE andSheet NumberDescription(50)Erosion Control Cover Sheet123456EC01.DGNErosion Control Cover Sheet(51)BMP General Notes123456EGN1.DGNBMP General Notes(52)Erosion Control Drainage Area Map123456EDM1.DGNErosion Control Drainage Area Map(53)BMP Location Details123456ER01.DGNBMP Location Details(54)CMP General Notes123456ECM1.DGNCMP General Notes(55)Watershed Map / CMP Plan123456EWM1.DGNWatershed Map / CMP Plan(56)Erosion Control Construction Details123456ECD1.DGNErosion Control Construction DetailsRight-of-Way Cover123456RC01.DGNRight-of-Way CoverRight-of-Way Plans123456RW01.DGNRight-of-Way PlansErosion Control PlansRight-of-Way Plans3/30/2006Construction Plan Assembly
ColorWeightDescriptionMicrostation LineStyle or CellCAiCE Feature CodeMicroStation LevelNamesMicroStation level(63 levels per designfile)Plan Sheet Levels4634Section Specific Levels1-41,50-56Section Specific Information Level Corresponds to Section(Level 13 Mainline Plan, Level 24 Utility Plan etc )Following Levels Apply to all Planimetric Sheets (examples include (13) Mainline Plan, (24) Utility Plan etc )42-444546474849494957-5960616263Empty (Available for future expansion) (Not Plotted)Miscellaneous Items,Notes etc. (Plotted)North ArrowMatch Line (Text)Match Line (Line)Scale Bar (10SC,20SC,50SC etc )LogoLegend InformationEmpty (Available for future expansion) (Not Plotted)Plot Substitution Text (Do Not Edit)Sheet Outline and Related TextLEAVE BLANKMiscellaneous Items,Notes etc. (Not Plotted)3/30/2006NARROWMATLIN#SCGPLNGPLNPlan Sheet Levels
GDOTELECTRONIC DATA GUIDELINESELECTRONIC DATA GUIDELINES2-4 Plan Assembly Sheet SectionsThe following sections describe in a spreadsheet format the Design File Name andLevel Schemes that should be used on Georgia DOT plan sheets.
(1)CoverDesign File Name(s)Reference File NameLogical NameLevels (See PPG 2,25,27,30,32,40,423/30/2006(1)Cover
(2)IndexDesign File Name(s)Reference File NameLogical NameLevels On123456IN01.DGNNANA2,45-49,60-62The files listed below should reside in each PI Project Number folder with the following naming conventions:Index.txtIndex standards.txtIndex details.txtThese files should be edited for each specific Project with Wordpad or other editor that retains the formatting for columns.This will allow for easier placement of the .txt file on Level 2 into the design file with the Automation Tools provided.3/30/2006(2)Index
(3)Revision SummaryDesign File Name(s)Reference File NameLogical NameLevels On123456RV01.DGNNANA3,45-49,60-62The file listed below should reside in each PI Project Number folder with the following naming convention:revison summary.txtThis file should be edited for each specific Project with Wordpad or other editor that retains the formatting for columns.This will allow for easier placement of the .txt file on Level 3 into the design file with the Automation Tools provided.3/30/2006(3)Revision Summary
(4)General NotesDesign File Name(s)Reference File NameLogical NameLevels On123456GN01.DGNNANA4,45-49,60-62See GDOT-GN-General-Notes.cel library for general notes.General Notes should be placed on Level 4.3/30/2006(4)General Notes
(5)Typical SectionsDesign File Name(s)Reference File NameLogical NameLevels S1-61See GDOT-GN-Typical Sections.cel library for Typical Sections.cells.3/30/2006(5)Typical Sections
(6)Summary QuantitiesDesign File Name(s)Reference File NameLogical NameLevels ry Quantities
(7)Quantities AmendmentDesign File Name(s)Reference File NameLogical NameLevels ities Amendment
(8)Quantities (Construction)Design File Name(s)Reference File NameLogical NameLevels ities (Construction)
(9)Detailed EstimateDesign File Name(s)Reference File NameLogical NameLevels On123456DT01.DGNNANA9,45-49,60-62The file listed below should reside in each PI Project Number folder with the following naming convention:Detailed estimate.txtThe output file from the Web Version of the Detailed Estimate program is used in the production of this design file.This will allow for easier placement of the .txt file on Level 9 into the design file with the Automation Tools provided.This will produce multiple sheets in the design file that should be copied in order to only have one sheet design file per respective sheet.3/30/2006(9)Detailed Estimate
(10)Traffic DiagramDesign File Name(s)Reference File NameLogical NameLevels On123456TR01.DGNNANA10,45-49,60-62 (See Plan Sheet Levels Section for Level Usage)123456TRDG.DGNTRDG1,23/30/2006(10)Traffic Diagram
(11)Construction LayoutDesign File Name(s)Reference File NameLogical NameLevels On123456CL01.DGNNANA11,45-49,60-62 (See Plan Sheet Levels Section for Level -10,36-383/30/2006(11)Construction Layout
(12)Misc. MapsDesign File Name(s)Reference File NameLogical NameLevels On123456MM01.DGNNANA12,45-49,60-62(See Plan Presentation Guide for Usage)3/30/2006(12)Misc. Maps
(13)Mainline PlanDesign File Name(s)Reference File NameLogical NameLevels On123456CP01.DGNNANA13,45-49,60-62 (See Plan Sheet Levels Section for Level ,34,35,47123456TOPO.DGNTOPO1,3,5,7,9,11,13,15,17,
ELECTRONIC DATA GUIDELINES 1-2 TABLE OF CONTENTS . 1-7 Guidelines for Submitting Electronic Data 1-8 Graphic Standards 1-9 Minimum Text for Right of Way 1-10 File Conversion-Metric/English 1-11 Saving Plotted Views 1-12 File Locations 1-13 Miscellaneous Items Design File Names and Level Schemes (Section 2) 2-1 Design File Names and Level .
Nurse-Midwives in Georgia: Value for Georgia Citizens Nicole S. Carlson PhD, CNM President, Georgia Affiliate of American College of Nurse-Midwives Assistant Professor Emory University School of Nursing . Birth in Georgia Georgia Births in 2013: . for Certified Nurse-Midwives in Law and Rule Data Current as of January 2014 MT WY MI ID .
Brian Kiepper, University of Georgia Wayne King, Georgia Green Industry Association Katie Kirkpatrick, Metro Atlanta Chamber of Commerce Ed Klaas, Georgia Irrigation Association Georgia Department of Georgia Department of
DCH At-a-Glance Board of Community Health Governor Georgia Department of Community Health Executive Assistant Commissioner Georgia Board for Physician Workforce Georgia Composite . Georgia Children* Served by the Department of Community Health in FY 2013 Accomplishments. Georgia Department of Community
Objective 1: Knows physical, human, and environmental geography of Georgia . The beginning Geography teacher: A. Knows the physical geography of Georgia B. Knows the human geography of Georgia C. Knows the regions and places in Georgia D. Knows the environmental geography of Georgia E. Knows the natural resource debates in Georgia
Donnie Smith, —Georgia Center of Innovation for Agriculture . . Paul Thompson—Georgia Department of Agriculture . Jason Deal—Georgia Department of Agriculture . Ruby Riesinger—Valdosta State University SBDC . Bill Boone—University of Georgia SBDC . Stan Moore—USDA/NRCS .
Digging into the Data. Richard Woods, Georgia's School Superintendent Georgia Department of Education Educating Georgia's Future We wonder How does this compare to last year? What data did 6th grade teachers have regarding the incoming 6th graders? Digging into the Data 2019 ELA Beginning Learner Developing
MIL-HDBK-454. GENERAL GUIDELINES FOR ELECTRONIC EQUIPMENT 1. Scope. 1.1 Guidelines appticable to electronic equipment. This handbook covers the common guidelines to be used in military specifications for electronic equipment. 1.2 Revision of guidelines.File Size: 6MBPage Count: 162Explore furtherDEPARTMENT OF DEFENSE HANDBOOKwww.dla.milMIL-STD-454 N REQUIREMENTS ELECTRONIC EQUIPMENTeveryspec.com/MIL-STD/MIL-S MILITARY HANDBOOK ELECTRONIC RELIABILITY DESIGN HA www.navsea.navy.milRecommended to you b
The SBSS-prepared A02 and A0B MILS transactions carry the expanded length descriptive data, which could contain various types of information for part-numbered requisitions in rp 67-80, and requires mapping to the DLMS transaction. This information is common to the YRZ exception data used by DLA, and so can be mapped to the generic note field as specified above. b. DLMS Field Length .
