ridot cad standards manual - cell phones, mobile...

RIDOT CAD Standards Manual

i

TABLE OF CONTENTS

1. Introduction and Application

1

2. Documentation and Review 2.1 Associated Documentation 2.2 Applicability

3

3. File Preparation 3.1 File Format 3.2 File Submission 3.3 Recordable Disk Security 3.4 Contractual Obligation

4

4. Sheet Layout and Basic Drawing Parameters 4.1 Specifications 4.2 Sample Sheets

Cover Sheets Standard Notes Standard Symbols Job Specific Notes Border Layout Dimensions

6

5. AutoCAD™ Objects and Graphic Quality Standards 5.1 Overview

7

6. Units, Coordinate System and Map Coordinate Reference 6.1 Specifications 6.2 Mapping Company Guidance

6.3 RI State Plane Coordinates and RIGL

8

7. Drawing Features and Layers 7.1 Overview 7.2 Existing vs. Proposed Features 7.3 Text Annotation Associated with Features 7.4 Leader Lines

10

8. Layer Naming Conventions 8.1 Overview 8.2 Layer Names 8.3 Layer Name Sub-Fields 8.4 Color and Line Weights

12


ii

9. Using XREFs 9.1 XREF Best Practices 9.2 Binding XREFs

15

10. Using Images 10.1 Images Best Practices

16

Appendices

A-1 B-1

C1-1 C2-1 D-1

Appendix A: RIDOT.CTB File Appendix B: Symbols, Layer Names and Preferred Linetypes Appendix C-1: Master Layer List (Alpha by “Major Category” Sub-Field) Appendix C-2: Master Layer List (Alpha by “Description” Sub-Field) Appendix D: Drawing Samples


Page 1

1. Introduction and Application

This document was created to standardize features shown on construction plans and State Highway Plats created with AutoDesk™ AutoCAD™ software (hereafter, “AutoCAD”) for the Rhode Island Department of Transportation (RIDOT). Utilization of these standards by all Designers (Consultants and Subconsultants) will promote uniformity of process and presentation across differing projects, and will empower the use of emerging technologies such as geographic information systems (GIS). This manual requires the use of associated files. These files are available on the official RIDOT website at http://www.ridot.us/PMP, under “DOCUMENTS”, “Manuals – CAD Standards” and include the following:

RIDOT.CTB

RIDOT.LIN

RIDOT.SHX

RIDOT-DIMENSION.DWT Variation from these standards may be necessary for special or unusual circumstances. Consequently, good engineering and drafting judgment should be used in reaction to specific or unusual project conditions. When questions regarding adherence to specific recommendations of this manual arise, they should be addressed to the appropriate RIDOT Project Manager (PM).

This document outlines the requirements and procedures for the final digital submittal to RIDOT. These requirements provide the basis for common exchange of AutoCAD-related digital files among Designers and submissions to RIDOT. Any or all of these standards may be superseded by subsequent RIDOT policies. It is the responsibility of the Designer to check the RIDOT website http://www.ridot.us for current regulations, requirements and policy documentation, and to implement as necessary. Questions regarding potentially conflicting instructions between existing RIDOT Policy documentation and this manual shall be brought to the immediate attention of the RIDOT Project Manager and CAD Standards Coordinator at [email protected]. All submitted CAD files, formats and naming conventions (Text Style, Layer Name, Etc.) shall conform to the RIDOT CAD Standards Manual. The preparation of base mapping files shall utilize the symbols as shown in Appendix B. Guidance regarding preferred symbols, linetypes and dimensions, as provided by this Manual and its Appendices will be followed. In the case where additional symbols are required, the RIDOT CAD Standards Manual format (refer to Section 7.2 “Existing vs. Proposed Features”) shall be employed. Additional symbols may be evaluated for adoption as a standard.

http://www.ridot.us/PMP

http://www.ridot.us/

mailto:[email protected]


Page 2

If you have any questions about the use of these standards or suggestions for changes to be considered in future revisions, you may contact:

RIDOT CAD Standards Committee 2 Capitol Hill Providence, RI 02903 [email protected]


Page 3

2. Documentation and Review

2.1 Associated Documentation These standards define specific digital drawing parameters and shall apply to all RIDOT Construction Plans, Profiles, Cross-Sections and ROW Plans and Plats. These standards do not alter or imply any revision of standing RIDOT Project specifications, regulations and/or policies, as documented in such publications as:

• RIDOT Design Policy Memorandums (DPMs) • RIDOT “To All Consultant” (TAC) and “To All Project Engineers” (TAPE)

documents • RIDOT Bridge Design Manual • RIDOT Maintenance Manual • RIDOT Traffic Design Manual • RIDOT Highway Design Manual • RIDOT Standard Details • Any RIDOT Project specifications and associated documents referenced by

specifications In cases where content of the above documents differ from or are in apparent conflict with those set forth in this manual, this manual shall be considered to supersede. In the interest of maintaining consistency among an array of RIDOT manuals, specifications, processes and methodologies, any potential conflict/contradiction should, upon initial discovery, be immediately brought to the attention of the RIDOT PM responsible for the project, in writing. The PM should adjudicate whether the issue warrants further escalation and review by the CAD Standards Coordinator. The PM will forward the necessary details via the address in Chapter 1. 2.2 Applicability These standards only define digital format standards for creation and submittal of engineering drawings for construction Projects in the *.DWG (commonly called “Drawing”) file format. The submittal of digital CAD drawings to the Plan Room applies to all Design Projects and recorded Real Estate Plats.


Page 4

3. File Preparation

3.1 File Format Final electronic record drawings submitted to RIDOT shall be provided by the Designer in both TIF (Tagged Image File) and DWG (AutoCAD Drawing File) format. AutoCAD-generated DWG files should adhere to the standards defined in this document for the generation of Plan and Plat sheets. TIF files should be generated from the corresponding DWG file, which in turn corresponds to each Plan and Plat sheet in a particular Project submittal. Further guidance is found in related DPM 460.11. TIF files shall be 400 DPI (dots per inch) resolution. DWG files shall be compatible with the latest AutoCAD version as approved by the latest official RIDOT “To All Consultants” documentation but in no cases will be earlier than AutoCAD 2004-compatible. Digital drawings shall be submitted, with appropriate signatures on each corresponding TIFF file, per DPM 450.01 Project Submission Identification. 3.2 File Submission Final electronic record drawings shall be submitted to the RIDOT Plan Room following the requirements set forth by DPM 460.11, a portion of which has been re-created below for reference purposes:

1. A read-only compact disk in a plastic protective case labeled appropriately for identification. Hand-written CD labeling is not permissible. The following must be included on the CD label:

a. Project Title b. FAP Number c. Contract Number d. Submission Date (dd/mm/yyyy) e. Designer/Contractor Name f. Volume Number g. Total Number of Sheets

2. One TIF and one DWG file for each individual sheet within the submittal. Files shall

be named according to DPM 450.06 “Plan Sheet File Names” 3. A text file or Microsoft Excel file named “Contract Number_Trsnmtl”. This Excel

file should be saved as the latest version per RIDOT internal standards and/or per RIDOT TAC documentation. This file provides summary information about the transmittal. The following is required:

a. Project Title b. FAP Number c. Contract Number d. Submission Date e. Designer/Contractor Name f. Total number of Files and Pages in the Submittal


Page 5

g. Name, Sheet Number and Description of each drawing file in the Submittal h. Any layer-naming standards used on the Project which are not specifically

defined in this document. 3.3 Recordable Disk Security Submitted disks may not be re-writable; submission of “CD-RW” disks is prohibited. The contents of each disk must be scanned to ensure that the disk is free of malware (i.e. virii, Trojans, worms, spyware, rootkits, executable code, etc) prior to submission. As variants of existing threats and new threats emerge constantly, designers must use the most current file-scanning methodologies to ensure that each CD is free from infection. 3.4 Contractual Obligation Rules and policies regarding the fulfillment of the contractual obligations are determined by the RIDOT Contracts and Specifications Office, existing RIDOT policy and procedures in effect at the time of submission.


Page 6

4. Sheet Layout and Basic Drawing Parameters 4.1 Specifications Drawings will adhere to all standards defined in RIDOT specifications and DPMs for the preparation of drawing plans including Real Estate Plats and Plans. Submittals are required to adhere to standard sheet layouts that define drawing dimensions and format for border, title blocks, legends, margin information text, and other standard content as detailed in DPM 450.06 and DPM 450.02. AutoCAD™ DWG templates depicting sheet format and layout requirements for the standard Plan and Plat sheets are detailed in associated DPMs 450.01, 450.02 and 450.06. Requisite information to appear on each plan is determined by DPM 450.02. Questions regarding potentially conflicting instructions, including but not limited to plotting (CTB) files and symbols, between existing RIDOT Policy documentation and this manual should be brought to the immediate attention of the RIDOT Project Manager and CAD Standards Coordinator. 4.2 Sample Sheets Sample sheets include the Cover Sheet, Standard Symbols, Standard Notes and Job Specifics. Both the template (PDF) and AutoCAD (DWG) files are available for downloading from the PMP website: http://www.ridot.us/PMP, Documents – DPM. The following are available which are prefixed by “DPM 450.02 <>”:

File name Plan Sheet Name (PDF) (DWG)XXXXX_V1_001_COVER Plan Cover Sheet XXXXX_V1_002_STDSYM Standard Symbols XXXXX_V1_003_STDNOTES01 Standard Notes – 1 XXXXX_V1_004_STDNOTES02 Standard Notes – 2 XXXXX_V1_005_JSNOTSYM Job Specific Notes Plat Cover Sheet Border Layout

Dimensions


Page 7

5. AutoCAD™ Objects and Graphic Quality Standards 5.1 Overview The types of AutoCAD™ graphic objects used should follow accepted engineering design practices. For all features to which precise parametric measurements apply (arcs, spline curves, fillets, etc.), these features should be created using appropriate AutoCAD™ Draw commands. Proper connectivity between features should be maintained. Linework should graphically snap together, with no gaps, overshoots or undershoots, unless they are part of the design. Line objects should also snap to the center of associated point features (e.g., sewer mains to manholes) to ensure graphic connectivity. Arcs and splines should connect properly (along tangent) to line objects. In most cases, point features will be represented by an AutoCAD™ block. In these cases, snapping of linework should use the insertion point (normally the center) of the feature. Appropriate AutoCAD™ commands (e.g. OSNAP) or custom tools to ensure proper graphic connectivity and quality will be used.


Page 8

6. Units, Coordinate System and Map Coordinate Reference 6.1 Specifications Unless specifications for a particular Project define different rules and standards, these basic requirements for units and coordinate system reference will be followed:

1. The paper space origin of a drawing will be defined as 0,0 and will be placed in the lower left outside the drawing border.

2. Drawings shall be created in two-dimensional space unless a Project specification calls for 3-dimensional coordinates. Mapping companies should provide information including Z-axis information which may be brought into 2-dimensional drawings by the consultant.

3. The default compass orientation for plan drawings calls for the Y-axis (vertical axis) to have a North-South orientation and the X-axis to have an East-West orientation. Drawings may deviate from this sheet orientation standard if it results in greater readability or sheet handling.

4. A magnetic north arrow should always be provided and should precisely define the north-south orientation of the drawing.

5. For profile views or cross-sections, the Y-axis will represent elevation or height (as called for in the design specifications), and the X-axis will represent horizontal distance or length.

6. For all Highway plans, cross sections, typical sections and profiles, and all Bridge general layout plans, AutoCAD Units will be defined as Decimal Feet (1 drawing unit = 1 foot). Other drawing types such as structural and architectural details may be set at 12 drawing units = 1 foot.

7. Angles will be defined as Degrees/Minutes/Seconds. 8. All designed or measured features should be dimensioned as called for in RIDOT

Road and Bridge Project specifications. Appropriate AutoCAD™ dimension annotation commands should be used, pursuant to the RIDOT.DWT file provided with this manual.

9. Text annotation and dimension annotation may be either placed on the same layer as the feature being labeled or in a separate layer (properly named) at the discretion of the Designer. See “Appendix B Notes”.

6.2 Mapping Company Guidance Mapping companies should use Symbols, Linetypes and Layer Naming conventions found in Appendix B for guidance when preparing files for submission to the RIDOT Prime or Sub-Contractor. Mapping and surveying contractors should attempt to incorporate all standards found in this manual. Coordination with the recipient of the mapping contractors’ CAD files should precede submission of said files, specifically file-naming, Symbol and Linetype usage, with regard to impact on cost and schedule. Mapping companies should consult the “Existing Features” symbols, linetypes and layer names as shown in Appendix B.


Page 9

6.3 RI State Plane Coordinates and RIGL As required by DPM 450.02, a minimum of two State Plane Coordinate points shall be included in each plan drawing as separate AutoCAD™ point objects stored in their designated layer. These locations shall be placed as an AutoCAD™ point object and shall be symbolized as defined herein and annotated with the x,y coordinates. They shall correspond to known features (e.g., manhole) or a physically placed monument. These coordinates should be in reference to the Rhode Island State Plane Zone according to the NAD 83. They should be placed using a survey technique (GPS recommended) that ensures a local horizontal accuracy of 2 centimeters or better. In Projects where elevation is required, local vertical accuracy shall be 5 centimeters or better. Signs associated with Signing Contracts should be tied into the State Plane Coordinate system. These and all references to the State Plane Coordinate System shall be followed, pursuant to the General Laws of the State of Rhode Island (a.k.a. RIGL) as follows:

TITLE 34 Property; CHAPTER 34-8 Rhode Island Coordinate System; SECTION 34-8-4 (b) For the purposes of more precisely defining the Rhode Island coordinate system of 1983, the following definition by the national ocean survey/national geodetic survey is adopted: The Rhode Island coordinate system of 1983 is a transverse Mercator projection of the North American datum of 1983 having a central meridian 71° 30' west of Greenwich, on which meridian the scale is set at one part in one hundred sixty thousand (160,000) too small. The origin of coordinates is at the intersection of the meridian 71° 30' west of Greenwich and the parallel 41° 05' north latitude. This origin is given the coordinates: x = 100,000 meters, and y = 100,000 meters, and y = 0 meters.

The following RIGL also applies:

TITLE 34 Property; CHAPTER 34-8 Rhode Island Coordinate System; SECTION 34-8-10 Meter-to-foot conversion; For purposes of this chapter, and for purposes of conversion between the two (2) systems set forth in § 34-8-1 of this chapter, one meter equals 3.2808- 1/3 survey feet.

RIDOT Standards are in English units and NOT Metric. All drawing files should reflect English units as described in DPM 450.02, Plan Content Requirements. Additionally, mapping or drawing files on the state grid shall not be moved or rotated (“D-viewed” only) to reduce the need for labor-intensive inserts.


Page 10

7. Drawing Features and Layers 7.1 Overview Designers shall adhere to the naming and symbology standards defined in Appendix B, which contains a list of standard symbols, corresponding layer names, custom shapes and preferred Linetypes. These features are normally represented by AutoCAD™ standard or custom line types, standard blocks representing point symbols, text objects, or hatch patterns. 7.2 Existing vs. Proposed Features Some projects may call for existing and proposed features (i.e. utility feature, right-of-way line, road edge) to be included and differentiated on the same drawing. This standard defines different layer naming, and in some cases symbology and line types for existing versus proposed features. In cases where differentiation on a particular drawing is necessary, Designers should use the symbology defined in Appendix B, and should apply consistent rules to differentiate appearance so that proposed features are more prominently depicted than existing features for the same type. Existing features are to be depicted as ‘screened’ at a minimum of 30 %. Designer should ensure that screening is not lost during typical reproduction / photocopying processes. 7.3 Text Annotation Associated with Features This standard includes guidelines for text annotation for the purpose of ensuring readability. All text annotations should utilize Roman S font. For project Cover Sheets, including Plat Plans, Roman C font shall be used (see Cover Sheet samples in Appendix D) For Titles only, AutoCAD-provided block-style fonts Arial, Roman S or Roman D may be used. For most annotation the preferred height is .1”. For bridge plans, preferred height is .125” (refer to Bridge plans sheets in Appendix B). Other annotation height must fall within the range of .08” and .2”, with the latter size reserved mainly for headings and titles on the drawings. Text annotation should be oriented horizontally (wherever possible) or at an angle that is easily readable without rotating the drawing. Dimensions should be placed along the axis of a feature or should point to a feature with a tie line. RIDOT recommends that text annotation layers be set-up in Model Space for a drawing layout that supports plotting at the standard RIDOT sheet sizes. 7.4 Leader Lines

Leader lines may be used where necessary but should adhere to the following design principles:

• Leader lines should terminate at the feature, leaving no doubt regarding which feature is being pointed to.

• Multiple leader lines may not intersect. • Vertical and horizontal arrangement of leaders lines must follow the vertical or

horizontal position of features being annotated.


Page 11

• Text annotation must be positioned to eliminate confusion regarding which leader line is being labeled.

Text annotation may be placed on a separate layer associated with that feature. If the annotation for a feature is placed on a separate layer, it should use the layer naming convention shown in this Manual.


Page 12

8. Layer Naming Conventions 8.1 Overview Standardized layer naming has been created to address the following requirements:

• Arrange features into Major Categories that reflect feature type. • Layer names should use easy-to-understand abbreviated descriptions whenever

possible. • The order in which elements of a layer name appear are intended to reflect the

frequency of needing to ‘sort by’ common file characteristics. The order of elements that comprise layer names suits this purpose.

Though this manual’s Appendix B includes a large number of layers and symbols which commonly occur on drawing file submittals, specific Projects may require additional features or a sub-categorization of features defined in this standard. Consultants may include additional features not found in this standard providing that these features are assigned layer names that use this standard’s format, and at the discretion of the PM. See Appendix B. 8.2 Layer Names

1. The layer naming conventions set forth in this standard organize drawing elements which appear on a list of “Major Category” layer names (see table, below). Flexibility for customization is addressed through inclusion of more detailed descriptive text at the end of the layer name, in the “Notes and Details” field.

2. This naming convention was created to optimize sorting efficiency in cases where many files are present.

3. All layer name characters should be capitalized and all sub-fields (see table, below) should be separated by a single dash (‘ – ’).

4. A master list of layer names appears in Appendix C. Appendix C is sorted two ways: • Alphabetically by Layer Name • Alphabetically by Major Category then by Layer Name

8.3 Layer Name Sub-Fields

1. Three-letter “Major Category” 2. One-letter representation of “Existing”, “Proposed”, “Future” or “Temporary”

(X/P/F/T) 3. Layer Description: An abbreviated description. All “text” layers should be appended

with –TXT in this field. 4. Notes/Details (Optional): As brief as possible. This sub-field should be used

sparingly. The layer name will end with the “Description” sub-field, in most cases. This is to be used for providing information such as Street Name/Number, owner etc.

This system emphasizes appending existing layers, as opposed to adding unnecessary new layers.. For instance, if lines for the Smith property easement are required, locate the most suitable existing layer for the item and append descriptive text to the end of the layer name.


Page 13

A layer name will be comprised of three or four components:

Sub-Field Name:

Major Category

Exist / Proposed /

Future / Temp

Description Notes and Details(Optional)

Max # Characters

3 (3 letters +

dash)

2 (1 letter + dash)

<10 (+ dash, if needed)

(brief description)

Example ROW- X- EASEMENT- SMITH A table of allowable “Major Category” sub-fields appears below, followed by a brief “Description” and clarifying “Remarks”:

Category Name

Description Remarks

ALN Alignment Alignment File: XREF use only. Not to be confused

with AutoCAD Land Desktop Data.

BRG Bridge DET Detail Layers DIG Digitized Information Example: scanned TIF image ENV Environmental GEN General General plan information; not

MISC GEO Geo-Technical Borings etc. HWY Highway IMG Image External image files such as

JPGs of company logos, etc LND Landscape MAP Base Mapping Base Mapping files: XREF

use only MSC Miscellaneous PRF Profile Layers

ROW Property Info SEC Cross-Section Layers SHT Border / Sheet

Elements

SVY Survey Information STR Structural Information Wingwalls, Piers TRF Traffic TXT Text Layer UTL Utilities Information


Page 14

NOTES: • “MSC” shall be used sparingly and only with the approval of the RIDOT PM. • For smaller projects, “Major Category” layer name sub-fields may be combined, with the approval of

the RIDOT PM. A typical example would include adding UTL data to MAP files – i.e., adding Drainage and Utilities information to base mapping files, as is common practice by base-mapping providers.

8.4 Color and Line Weights Use of color, line weights and linetypes when output to plotting devices should reflect those specified in the downloadable RIDOT.CTB file (Appendix A), RIDOT.LIN (Linetype) and RIDOT.SHX (Shape) files. Standard line weights for each of the layers are provided in Appendix B. The RIDOT CTB (Appendix A) file provides requirements for assignment of colors to drawing layers. Designers may use color assignments which best depict and differentiate features on their drawings, providing these assignations fall within the range of options available in the RIDOT.CTB file. This CTB file was created to provide flexibility from both aesthetic and functional perspectives. It addresses common concerns regarding light colors that do not show up well when plotted in black and white, common plotting conflicts, including those pen sizes and/or colors which are commonly obscured when a PDF file is generated.


Page 15

9. XREFs 9.1 XREF Best Practices The intent for larger projects is to have the disciplines separated into individual files and XREF’d into the plans to aid in indexing, sorting and searchability. There is an array of existing third-party software which automates the process of naming XREF files and folders/directories. Though potentially beneficial as a time-saving technique, use of this software must adhere to the following parameters.

1. All XREFs should be placed on locked layer. 2. All XREFs are to be overlaid, not attached. 3. Care should be taken to ensure that the UCS (Universal Coordinate System) is set to

“world” with the insertion point at 0,0. 4. The “MAP” Major Category should incorporate all base mapping. This category is

not to be used when naming Layers. Its use is restricted to XREF names. 5. The “ALN” Major Category should incorporate the alignment file. This category is

not to be used when naming Layers. Its use is restricted to XREF names. 6. The PTS number shall be the name of the folder containing all XREFs. 7. The PTS number shall also be the first identifying sub-field in any XREF file name.

A second sub-field, uses a modified version of the existing Major Category list. A third sub-field, when needed, must be as brief and descriptive as possible. PTS # Major Category (Optional)

XREF Description Example 0031E MAP Abutment-1

# Characters 5 3 (total of 9) (as brief as possible)

9.2 Binding XREFs Drawing (DWG) files and associated XREF files should be submitted “unbound”.


Page 16

10. Using Images 10.1 Images Best Practices Images such as JPGs, TIFs, etc are frequently included in DWG files submitted to RIDOT. Use of such images adheres closely to the usage guidelines of XREF files. A unique image description sub-field (shown below) is optional but when used should be as descriptive and concise as possible. Images are to be placed in a directory/folder named as followed:

PTS # Major Category (Optional) Image Description

Example 0031E IMG Company logo # Characters 5 3 (total of 9) (as brief as possible)

C1-2

(BRG ~ HWY)

MAJOR CATEGORY

EXIST / PROP / FUT / TEMP

LAYER DESCRIPTION MAJOR

CATEGORY


LAYER DESCRIPTION

BRG P ABUTMENT BRG P SAFETYCURB BRG P APPSLAB BRG P SHEETING BRG P BACKWALL BRG P SIDEWALK BRG P BARRIER BRG P SOLDPILELAG BRG P BEAM BRG P STEM BRG P BEAMSEAT BRG P WINGWALL BRG P BEARING ENV X 100BUFF BRG P CHEEKWALL ENV X 200BUFF BRG P CURB ENV X 50BUFF BRG P CURTAINWALL ENV X ASSF BRG P DECK ENV X FLOOD BRG P DIAPHRAGMS ENV X LOD BRG P ENDPOST ENV P SILTFENCE BRG P EXPJT ENV X WETLAND BRG P FOOTING GEO P BORING BRG P GRADING GEO X BORING BRG P HATCH HWY X BASELINE BRG P PARAPET HWY P BASELINE BRG P PIER HWY X BASELINE-TXT BRG P PILE HWY P BASELINE-TXT BRG P RAIL HWY P BERM BRG P REINF HWY P BERMBACK

LAYERS: ALPHA BY “MAJOR CATEGORY”

C1-3

(HWY ~ LND)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

HWY P BERMHATCH HWY P LEDGE HWY P BOUND HWY P LOR HWY F BOUND HWY P MAILBOX HWY X CENTERLINE HWY P MEDBAR HWY P CENTERLINE HWY T MEDBAR HWY X CENTERLINE-TXT HWY P RAILROAD HWY P CONTMJR HWY P RDDIRT HWY P CONTMNR HWY P RDMAINT HWY P CURB HWY P RIPRAP HWY P CURBBACK HWY P SIDEWALK HWY P CURVEDATA HWY P SLOPE HWY P CUTMATCH HWY P SPOT HWY P CUTMATCHDWY HWY P STNBAFL HWY P CUTMATCHRDY HWY P TOESLOPE HWY P DEMO HWY P TOPSLOPE HWY P DIRFLOW HWY P WALL HWY P DRIVEWAY HWY P WCRAMP HWY P EOP LND P BEDLINE HWY P EROSION LND P CLRINVSE HWY P FENCE LND P DRIPLINE HWY P FENCE-TYPE LND P PEREN HWY P GEN-TXT LND P PERENHATCH HWY P GUARDRAIL LND P PLNTLIST HWY P LCLEAR LND P PLNTNOTE


C1-4

(LND ~ ROW)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

LND P PLNTTAG PRF X WATEREL LND P RTPRUNE ROW X BL-DATA LND P RTPRUNMECH ROW X CL-DATA LND P SENSTREE ROW X EASEMENT LND P SHRUBCNTR ROW X FL LND P SHRUBHATCH ROW P FL LND P SHRUBMASS ROW X FL-DATA LND P STLEDGE ROW X FL-TXT LND P TLINE ROW P FL-TXT LND P TREE ROW X HISTORICAL LND P TREECNTR ROW P LOC-TXT LND P TREEHATCH ROW X MUNICIPAL PRF X BORING ROW X MUNICIPAL-TXT PRF P DIM ROW X PAB PRF P DRAIN ROW P PAB PRF P DRAIN-TXT ROW X PAB-TXT PRF P FORCEMAIN ROW P PAB-TXT PRF P GRADE ROW P PARCEL-TXT PRF X GRADE ROW X PDB PRF P PRESSMAN ROW P PDB PRF P SEWER ROW X PDB-TXT PRF X SEWER ROW P PDB-TXT PRF P SEWER-TXT ROW X PGB PRF X UTILITY ROW P PGB


C1-5

(ROW ~ TRF)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

ROW X PGB-TXT SHT P DU-TXT ROW P PGB-TXT SHT P GEN-TXT ROW X PROPERTY SHT P GRAPHICSCALE ROW X SHL SHT P LOC-TXT ROW P SHL SHT P MATCHLINE ROW X SHL-DAT SHT P MATCHLINE-TXT ROW X SHL-TXT SHT X NORTH ROW P SHL-TXT SHT X STNAME-TXT ROW X STATELINE STR P ABUT ROW X STATELINE-TXT STR P FOOTING ROW X TEB STR P PIER ROW P TEB STR P WWALL ROW X TEB-TXT SVY X BENCHMARK ROW P TEB-TXT SVY X CONTROL SEC P DIM SVY X TRAVERSE SEC X GRADE TRF P CARSTOP SEC P GRADE TRF P OHSIGN SEC F GRADE TRF X PM SEC X LEDGE TRF P PM SEC P LEDGE TRF P PMARROWS SEC P QUANTITYBOX TRF P PM-HC SEC P RAILROAD TRF P SIGN SEC X UTILITY TRF P SIGNAL SEC P UTILITY TRF P SIGNAL-TXT


C1-6

(TRF ~ UTL)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

TRF P SIGNALWIRING UTL P HYDRANT TRF P SIGN-TXT UTL P LIGHT TRF P TRCONTROL UTL P LIGHTPOLE UTL P CABLETV UTL P MANHOLE UTL X COMBDRAIN UTL X OHWIRES UTL P CONDUIT UTL T POLE UTL X DRAIN UTL P POLE UTL P DRAIN UTL P POLEGUY UTL P DRAINSTR UTL P SERVICEPED UTL P DRAIN-TXT UTL X SEWER UTL P DU-TXT UTL P SEWER UTL X ELECTRIC UTL X SUBDRAIN UTL P ELECTRIC UTL P SUBDRAIN UTL X FLOW UTL P SUBDRAINMAT UTL P FLOW UTL X TELEPHONE UTL X GAS UTL P TELEPHONE UTL P GAS UTL X WATER UTL P HANDHOLE UTL P WATER UTL P HPLP


C2-2

(100BUFF ~ CURTAINWALL)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

ENV X 100BUFF GEO P BORING ENV X 200BUFF PRF X BORING ENV X 50BUFF GEO X BORING STR P ABUT HWY F BOUND BRG P ABUTMENT HWY P BOUND BRG P APPSLAB UTL P CABLETV ENV X ASSF TRF P CARSTOP BRG P BACKWALL HWY P CENTERLINE BRG P BARRIER HWY X CENTERLINE HWY P BASELINE HWY X CENTERLINE-TXT HWY X BASELINE BRG P CHEEKWALL HWY P BASELINE-TXT ROW X CL-DATA HWY X BASELINE-TXT LND P CLRINVSE BRG P BEAM UTL X COMBDRAIN BRG P BEAMSEAT UTL P CONDUIT BRG P BEARING HWY P CONTMJR LND P BEDLINE HWY P CONTMNR SVY X BENCHMARK SVY X CONTROL HWY P BERM BRG P CURB HWY P BERMBACK HWY P CURB HWY P BERMHATCH HWY P CURBBACK ROW X BL-DATA BRG P CURTAINWALL

LAYERS: ALPHA BY “LAYER DESCRIPTION”

C2-3

(CURVEDATA ~ GRADE)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

HWY P CURVEDATA HWY P EOP HWY P CUTMATCH HWY P EROSION HWY P CUTMATCHDWY BRG P EXPJT HWY P CUTMATCHRDY HWY P FENCE BRG P DECK HWY P FENCE-TYPE HWY P DEMO ROW P FL BRG P DIAPHRAGMS ROW X FL PRF P DIM ROW X FL-DATA SEC P DIM ENV X FLOOD HWY P DIRFLOW UTL X FLOW PRF P DRAIN UTL P FLOW UTL X DRAIN ROW P FL-TXT UTL P DRAIN ROW X FL-TXT UTL P DRAINSTR BRG P FOOTING PRF P DRAIN-TXT STR P FOOTING UTL P DRAIN-TXT PRF P FORCEMAIN LND P DRIPLINE UTL X GAS HWY P DRIVEWAY UTL P GAS SHT P DU-TXT HWY P GEN-TXT UTL P DU-TXT SHT P GEN-TXT

ROW X EASEMENT SEC F GRADE UTL X ELECTRIC PRF P GRADE UTL P ELECTRIC SEC P GRADE BRG P ENDPOST PRF X GRADE


C2-4

(GRADE ~ PIER)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

SEC X GRADE HWY T MEDBAR BRG P GRADING ROW X MUNICIPAL SHT P GRAPHICSCALE ROW X MUNICIPAL-TXT HWY P GUARDRAIL SHT X NORTH UTL P HANDHOLE TRF P OHSIGN BRG P HATCH UTL X OHWIRES ROW X HISTORICAL ROW P PAB UTL P HPLP ROW X PAB UTL P HYDRANT ROW P PAB-TXT HWY P LCLEAR ROW X PAB-TXT SEC P LEDGE BRG P PARAPET HWY P LEDGE ROW P PARCEL-TXT SEC X LEDGE ROW P PDB UTL P LIGHT ROW X PDB UTL P LIGHTPOLE ROW P PDB-TXT

ROW P LOC-TXT ROW X PDB-TXT SHT P LOC-TXT LND P PEREN ENV X LOD LND P PERENHATCH HWY P LOR ROW P PGB HWY P MAILBOX ROW X PGB UTL P MANHOLE ROW P PGB-TXT SHT P MATCHLINE ROW X PGB-TXT SHT P MATCHLINE-TXT BRG P PIER HWY P MEDBAR STR P PIER


C2-5

(PILE ~ SILTFENCE)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

BRG P PILE LND P SENSTREE LND P PLNTLIST UTL P SERVICEPED LND P PLNTNOTE PRF P SEWER LND P PLNTTAG UTL P SEWER TRF P PM PRF X SEWER TRF X PM UTL X SEWER TRF P PMARROWS PRF P SEWER-TXT TRF P PM-HC BRG P SHEETING UTL P POLE ROW P SHL UTL T POLE ROW X SHL UTL P POLEGUY ROW X SHL-DAT PRF P PRESSMAN ROW P SHL-TXT ROW X PROPERTY ROW X SHL-TXT SEC P QUANTITYBOX LND P SHRUBCNTR BRG P RAIL LND P SHRUBHATCH SEC P RAILROAD LND P SHRUBMASS HWY P RAILROAD BRG P SIDEWALK HWY P RDDIRT HWY P SIDEWALK HWY P RDMAINT TRF P SIGN BRG P REINF TRF P SIGNAL HWY P RIPRAP TRF P SIGNAL-TXT LND P RTPRUNE TRF P SIGNALWIRING LND P RTPRUNMECH TRF P SIGN-TXT BRG P SAFETYCURB ENV P SILTFENCE


C2-6

(SLOPE ~ WWALL)

MAJOR CATEGORY



CATEGORY


LAYER DESCRIPTION

HWY P SLOPE HWY P TOESLOPE BRG P SOLDPILELAG HWY P TOPSLOPE HWY P SPOT SVY X TRAVERSE ROW X STATELINE TRF P TRCONTROL ROW X STATELINE-TXT LND P TREE BRG P STEM LND P TREECNTR LND P STLEDGE LND P TREEHATCH SHT X STNAME-TXT SEC P UTILITY HWY P STNBAFL PRF X UTILITY UTL P SUBDRAIN SEC X UTILITY UTL X SUBDRAIN HWY P WALL UTL P SUBDRAINMAT UTL P WATER

ROW P TEB UTL X WATER ROW X TEB PRF X WATEREL ROW P TEB-TXT HWY P WCRAMP ROW X TEB-TXT ENV X WETLAND UTL P TELEPHONE BRG P WINGWALL UTL X TELEPHONE STR P WWALL LND P TLINE
