Electronic File Plan Submittal Standards Project CAD Data Submittal Standards. Table of Contents

Transcription

1

2 T Table of Contents List of Acronyms... III Introduction Project Overview Software Requirements AutoCAD Civil 3D Submission AutoCAD Submission without Civil 3D Submissions... 4 General Requirements File Format and Naming AutoCAD Resource Files General Drawing Templates Coordinate System Requirements Model Space Requirements... 7 Specific Data Requirements Layer Naming Format Discipline Designator Major Group Minor Group Status Master Layer List Civil 3D Object Requirements and Definitions Civil 3D Points Civil 3D Alignments Civil 3D Parcels Civil 3D Gravity Pipe Networks Civil 3D Pressure Pipe Networks Blocks And Symbols Civil 3D and AutoCAD Block Attributes Policy on External References Relationship to Standards City Standards Table of Contents I

3 3.6.2 National CAD Standard AutoCAD Submittal Workflows Extracting AutoCAD Polylines from A Civil 3D Surface Appendices Appendix A: Batch Standards Checker Appendix B: Layer Translator Instructions Appendix C: All Civil Site Discipline Designators for Civil/Site Plans Appendix D: All Major Group Names for Civil/Site Plans Appendix E: All Minor Group Names for Civil/Site Plans Appendix F: All Coded Domains Attribute Values List of Tables Table Page Table 1: List of Required Features... 8 Table 2: List of Discipline Designators Table 3: List of Major Group Layer Names Table 4: List of Minor Group Layer Names Table 5: List of Potential Status Codes Table 6: List of Composite Layer Names Table 7: List of Required Attributes Table of Contents II

4 List of Acronyms A-E A/E/C BIM CAD CHX CIM.CTB.DGN.DWF.DWG.DWS ENG FAQ GIS HTM/.HTML ISO.LIN NCS NIBS PDF SHX TTF XLS/XLSX XREF ZIP Architect Engineer Architecture, Engineering, and Construction Building Information Modeling Computer-Aided Design AutoCAD Standards Check File Civil Information Modeling AutoCAD Color-Based Plot Style File MicroStation Design File Design Web Format File AutoCAD Drawing Database File AutoCAD Drawing Standards File Engineering Frequently Asked Questions Geographic Information System Hypertext Markup Language (Webpage) International Organization for Standardization AutoCAD Linetype File National CAD Standards National Institute of Building Sciences Portable Document Format File AutoCAD Font and Shape File True Type Font Microsoft Excel File Format External Reference File Zipped File (Compressed File) List of Acronyms III

5 1 Introduction 1.1 Project Overview The City of Aurora has developed AutoCAD (CAD) Data Submission Standards for internal and external use to streamline the process of importing CAD information into the City s Enterprise GIS. Internally, the CAD Data Submission Standards define the data feature and attribute standard for plan development to maintain consistency. Externally, the CAD Data Submission Standards are required by consultants on development projects when submitting drawings to the City for approval and on capital projects funded by the City. The requirements ensure data received by the City can be rapidly incorporated into the City s GIS and made available for future maintenance and design projects. These requirements are limited to the data the City has defined as important information required for department function and operation. The Standards have been developed based on Version 6.0 of the United States National CAD Standard (NCS) and adapted for City use. The Standards are required to ensure data structure uniformity and clarity on CAD submission needs. It is not the intent to provide the drawing information necessary to reproduce plan sets, but rather to migrate data from CAD to the City s GIS platform. Upon completion of the project, the designer should create a separate drawing that holds the design entities with the required attributes of the Standards described herein. Only information detailed in Table 7 List of Required Attributes should be included in this new drawing and submitted for the purposes of CAD to GIS migration. If the CAD feature and attribute data in Table 7 is not included as part of the design process the consultant is not required to generate the information to meet this submittal standard. Also, please note that prior to submitting the standardized CAD drawing to the city, please remove all unnecessary layers that are not included in Table 6 and Table 7 in the required features and attributes section. Only the proposed design features and information are required. Please exclude all existing features and layers not included in Table 6 and Table 7. The City recognizes this is an additional effort of between 8-16 hours based on project complexity. The designer should continue to prepare their plans to be used in construction in the manner in which they choose. These standards do not dictate any aspect of plan production for construction. All information regarding engineering and plan development in the City of Aurora Roadway Design & Construction Specifications is available and maintained by Aurora Public Works at following link: Introduction 1

6 The Roadway Design & Construction Specifications documents will be the required reference for producing plans and supersedes any conflicting plan presentation or engineering information contained in this CAD Data Submission Standards document. The Aurora CAD Data Submission Standards are broken into four sections: Introduction, General Requirements, Specific Data Requirements, and Submittal Workflows with related Appendices to follow. Section 1: Introduction: This section includes the introduction and overview, including the software preference and requirements of the City of Aurora s CAD Data Submission Standards. Section 2: General Requirements: This section discusses the file formats, coordinate systems, and universal standards required by all City departments. Descriptions of the resource files and the associated links to those files used by the City for generating design information and document resources related to the Standards are also included. Section 3: Specific Data Requirements: This section includes details on the potential data submitted, the layer structure it should adhere to, and how this data maps to the City s Enterprise GIS environment. The data requirements are based on the operational needs of each City department. Section 4: AutoCAD Submittal Workflows: This section includes procedural guidelines for submitting CAD data to the City for integration into the GIS. This includes the AutoCAD extraction workflow, Batch Standards Checker, and the Layer Translator workflow to migrate a consultant s data to the City layer standard. Appendices: This section includes supporting reference documents. 1.2 Software Requirements The City conducted an online stakeholder survey as well as an in-person stakeholder session in fall 2015 to gather feedback on software and CAD standards used by the consultant community. The results found over 50% of consultants are using a version of AutoDesk s Civil 3D for design work; 40% use AutoCAD without Civil 3D; and 10% use other products such as Microstation or IntelliCAD. Based on these findings, the City concluded to focus the majority of the Data Submission Standards on AutoDesk s Civil 3D. The City will also provide guidance and tools for consultants using AutoCAD or other platforms AutoCAD Civil 3D Submission The City is providing a comprehensive set of templates and tools for use with AutoCAD Civil 3D submissions. Not all drawing submissions will require all features within each template. These tools and templates include: A list of the features and attributes associated that may be required for submission (see Table 1 and Table 7) Introduction 2

7 An AutoCAD Civil 3D template-drawing file with the layers that may be required for submission. A Version 2013 or newer AutoCAD Civil 3D template, which includes all Civil 3D objects that may be required for submission. An AutoCAD Batch Standards File to check and report on conformance with the City s Standards. The associated files can be downloaded at this URL: (also available via the full link): Instructions on how to use the Batch Standards Checker are included in Appendix A. The recommended process for working with this standard when using AutoCAD Civil 3D is as follows: 1. Prior to beginning a submission, download the latest version of the document download package, including the AutoCAD Civil 3D template. 2. Prepare the drawings required for the submission by using the appropriate AutoCAD Civil 3D object(s) and drawing the non-object features on the specified layer. 3. Before making the submission, run the AutoCAD Batch Standards Checker to test data conformance and fix any non-conformance issues found. 4. Provide the Batch Standards Report with the drawings submitted AutoCAD Submission without Civil 3D For consultants making submissions using AutoCAD without Civil 3D, the City is providing a comprehensive set of templates and tools to ease the submission process, including: A list of the features and attributes associated that may be required for submission (see Table 1 and Table 7) An AutoCAD template-drawing file set up with the layers that may be required for submission that are not created using an AutoCAD block. All AutoCAD blocks that may be required for a submission (included in the AutoCAD template file, including all attributes). An AutoCAD Batch Standards File to check and report on conformance with the City s Standards. The associated files can be downloaded at this URL: (also available via the full link): A comprehensive master list of features and layers is located in Table 1 and Table 7. If a feature on this list is required for a design submission, it must conform to the requirements of this document. If a feature is not required for a design submission it can be disregarded. Introduction 3

8 The recommended process for working with this standard when using AutoCAD without Civil 3D is as follows: 1. Prior to beginning a submission, download the latest version of the AutoCAD template file. 2. Prepare the drawings required for the submission using the AutoCAD blocks provided or by drawing the feature on the layer specified in the feature and layer list if it cannot be drawn using an AutoCAD block. 3. Before making the submission, run the Batch Standards Checker to test data conformance and fix any non-conformance issues found. 4. Provide the Batch Standards Report with the drawings submitted. Optional Approach: The City recognizes that consultants may have custom routines, tools, and plotting parameters to improve the efficiency of drawing production. Some may want to preserve a particular artistic aspect of a drawing they produce and not use the City s Data Submission Standard as part of production, but translate the data into it prior to a submission. To facilitate this approach, the City recommends using the AutoCAD Layer Translator to match this standard. See Appendix B for instructions on using this tool Submissions For consultants making submissions using other environments such as Microstation or IntelliCAD, the City will provide a set of templates and tools that to ease the submission process, including: A list of the features and attributes associated that may be required for submission (see Table 1 and Table 7) An AutoCAD template-drawing file set up with the layers that may be required for submission that are not created using an AutoCAD block. An AutoCAD template can be downloaded at this URL: This file can be imported into your preferred environment to create a template file consistent with the City Standard. For example, the AutoCAD file can be imported into IntelliCAD to create a template file with the same layer names. The AutoCAD template can also be used to create level names in Microstation that match the standard. Please refer to the user manual of your preferred environment for instructions. All AutoCAD blocks that may be required for a submission are included in the AutoCAD template file, including all attributes, and can be used in other environments. The AutoCAD blocks can be imported into IntelliCAD to create blocks. AutoCAD blocks can also be used natively in Microstation to create cells matching the standards. Please refer to the user manual of your preferred environment for instructions. An AutoCAD Batch Standards File to check and report on conformance with the City s Data Submission Standard once a file is exported from the platform. The Batch Standards File can be downloaded at this URL: Introduction 4

9 A comprehensive master list of features and layers is located in Table 1 and Table 7. If a feature on this list is required for a design submission, it must conform to the requirements of this document. If a feature is not required for a design submission, any features or layers described in this master list can be disregarded. The recommended process for working with this standard when not using AutoCAD or AutoCAD Civil 3D is as follows: 1. Prior to beginning a submission, download the latest version of the AutoCAD template file. 2. Using tools in your software product, import the file to create a new template including layer names and blocks. 3. Verify layers have converted properly by comparing the names in your template to those in this document to ensure proper translation. The most common issue is truncated names. 4. Verify blocks have converted properly by comparing with this document. 5. Prepare the drawings required for submission using the blocks provided or by drawing the feature on the layer or level specified in the feature and layer list if it could not be drawn using a block. 6. Export the drawing into an AutoCAD file format before submission. 7. Before making the submission, run the Batch Standards Checker to test data conformance. 8. Provide the Batch Standards Report with the AutoCAD drawings submitted. Introduction 5

10 2 General Requirements This section discusses the file formats, coordinate systems, and universal standards required by all City departments. Descriptions of the resource files (i.e., Civil 3D drawing template, Color Plot Style, Layer Translator, etc.,) used by the City for generating design information and document resources related to the CAD Data Submission Standard is also included. 2.1 File Format and Naming All site and civil plan packages submitted to or prepared for the City will require a digital drawing submittal in the following file format: The primary drawing format shall be AutoCAD 2013 DWG file format (any file generated in versions of AutoCAD Civil 3D, AutoCAD, or AutoCAD LT use this format). The DWG files generated by Civil 3D shall contain the Civil 3D design objects provided by the City in the respective City template. All design files with Civil 3D objects should utilize the COA C3D Template.dwt file available on the City s website. Related file types used to produce the DWG files (.dwg,.lin,.shx,.ttf) and raster image files (tif, jpeg, etc.) shall be provided. An AutoCAD Batch Standards Checker report (see Appendix A), produced by running against the actual file submitted, shall accompany the submittal. If the submittal was created using a program other than AutoCAD Civil 3D, AutoCAD, or AutoCAD LT, the submitting organization must convert the file to an AutoCAD 2013 DWG file and ensure all data has been converted. The Batch Standards Checker must be run and a copy of the Batch Standards Checker report provided to the City with the final drawing submittal AutoCAD Resource Files The standard drawings and templates listed below can be downloaded from the City s website at the following URL: General Requirements 6

11 Note to reviewers: Final links with updated directory location upon approval we recommend a compressed folder with all pertinent files included along with a readme.txt file that includes descriptions and uses the following: Civil 3D All Required Features Template Files to be attached as references for data location validation (for consultants unable to use the batch standards checker) As stated in the Introduction, please refer to the Roadway Design & Construction Specification for civil plans development and review at the following link: General Drawing Templates The COA C3D Template.dwt template file, compliant with the City s Data Submission Standard, is available for use as a general drawing template. The files can be downloaded from the City s website at the following URL: Coordinate System Requirements All data provided as part of the submission shall be created in real world coordinate systems based on the following projection: NAD83, State Plane, Colorado Central Zone, US Foot (CO83-CF). Please refer to the projection file included in the download package for more specifics related to projection parameters. 2.3 Model Space Requirements All design work and annotation shall be completed in model space in accordance to the City Engineering Design Standards. All borders, legends, margins, scale bars, etc. are not required as part of the DWG submission. General Requirements 7

12 3 Specific Data Requirements This section includes details on the potential data submitted, the layer structure it should adhere to, and how this data maps to the City s Enterprise GIS environment. The data requirements are based on the operational needs of each City department. The City of Aurora has identified a set of key required features that are needed to be extracted from plan submissions and loaded into the City s Enterprise GIS. The following table lists the key required features: Table 1: List of Required Features Feature Feature Type Description Building Footprint Polygon Building footprint Subdivision Line Extent of subdivision Park/Open Space Polygon Extent of park or open space Construction Limits Line Construction limit Temporary Easement Line Temporary easement edges Permanent Easement Line Permanent easement edges Ponds Point Detention Pond Parking Lot Polygon Parking lot edge Parcel Line Property lines Sidewalk Line Sidewalk edges Pedestrian Bridge Line Sidewalk bridge edge Signs Point Roadway signage Traffic Signals Point Roadway Traffic Signal Tunnel/Underpass Line Roadway tunnel/underpass edge Street Centerlines Line Centerline of street Curb Line Face of curb Roadway median boundary (face of Right-of-Way Line curb) Hydrant Point Center of fire protection hydrants Wastewater Pipe Line Sanitary sewer pipe Specific Data and Layer Naming Requirements 8

13 Manhole (Sewer) Point Center of sewer manhole Stormwater Pipe/Culverts Line Storm sewer pipe Manhole (Storm) Point Center of storm sewer manhole Inlet Point Center of storm sewer inlet Center edge of storm sewer outlet Outlet Point invert Potable Water Pipe Line Potable water supply pipe Valve Point Center of water valve Fittings Point Center of water fitting Meter Point Center of water meter Playground Surface Polygon Playground surface boundary Park Surface Polygon Park surface boundary Fence Access Location Point Center of fence gate Fences Line Fencing boundary line Irrigation Controller Point Center of irrigation equipment Irrigation Pipe Line Irrigation pipe Playground Locations Point Center of playground boundary Trees Point Center of tree trunk Trails Line Trail/path edges Line parallel to and in center of Retaining Walls Line retaining wall Legal City Limit Boundary Polygon City boundary limits Survey Benchmark Point Center of control benchmark(s) Restrooms Point Center of restroom building (each) Shelters Point Center of shelter (each) Note regarding requirements: The City is aware that due to the nature of each individual project, not all design submissions will include all features. If an above listed feature is not required, then this standard does not make it a required part of a design submission. Similarly, if a required feature is not listed above, that feature is still required as part of the submitted plan set. All requirements for the drawings contents must adhere to the City s standards and specifications for design and construction of public improvements. 3.1 Layer Naming Format The City of Aurora based its standard layer naming on the National CAD Standards (NCS) Version 6.0. For more comprehensive details on the NCS see the following URL: The NCS layer name format is organized as a series of up to five data fields (four fields with option Minor Group Field), allowing users to select from a number of options for naming layers according Specific Data and Layer Naming Requirements 9

14 to the level of information desired. Layer names consist of a series of data fields separated by dashes. Most of these data fields are easily remembered mnemonic English abbreviations so a user can recognize what is on the layer. There are four defined layer name elements: Discipline Designator, Major Group, up to two Minor Groups, and Status. The Discipline Designator and Major Group elements are mandatory. The Minor Group and Status elements are optional Discipline Designator The Discipline Designator denotes the major category of the data contained on the specified layer and is a two-character element. The first character is the discipline character and the second character is an optional modifier. Appendix C contains a comprehensive list of all of the potential Discipline Designators that could be used for a site or civil drawing. Only Discipline Designators pertaining to the City s standard have been included. The following table is a list of the Discipline Designators used: Table 2: List of Discipline Designators Discipline Designator Definition Notes C Civil Used for proposed non-utility features CU Civil Utilities Used for proposed utilities CT Civil Transportation Used for proposed transportation features L Landscape Used for proposed landscape features V Survey Mapping Used for existing features Major Group The Major Group is a four-character element that identifies the major category for the feature. The Major Group field element (four character abbreviations) shown on the Layer List is logically grouped with specific discipline designators. However, any Major Group may be combined with any Discipline Designator, provided that the definition of the Major Group remains unchanged. Therefore, any combination of Discipline Designators and Major Groups is permitted. Specific Data and Layer Naming Requirements 10

15 Appendix D contains a comprehensive list of all potential Major Groups that could be used for a site or civil drawing. Only Major Groups pertaining to the City s standard have been included. The following table is a list of the designators used: Table 3: List of Major Group Layer Names Major Group AREA BLDG BNDY CSTL CTRL ESMT FENC FIRE IRRG PLNT POND PRKG PROP ROAD SIGN SSWR STRM SWLK TRAF TRAL WALL WATR Definition Area Buildings and primary structures Political boundaries Construction limits Control points Easements Fences Fire protection Irrigation Plant and landscape material Ponds Parking lots Property Roadways Signs Sanitary sewer Storm sewer Sidewalks Traffic Trails or paths Walls Water supply Minor Group A Minor Group is an optional, four character field to further define the Major Groups. For example, CU-WATR-TEXT-N denotes Civil Utilities, Water, Pipe, Annotation Text, New work. This layer would include all of the text for the water system. A second minor group may be used to further define the data contained on a layer. The Minor Group elements (four character abbreviations) shown on the Layer List are logically grouped with specific Major Groups. However, any Minor Group may be used to modify any Major Group, provided that the definition of the Minor Group remains unchanged. Therefore, any reasonable combination of the prescribed Major and Minor Groups is permitted. Specific Data and Layer Naming Requirements 11

16 Appendix E contains a comprehensive list of all of the potential Minor Groups that could be used for a Civil/Site drawing. Only Minor Groups pertaining to the City s standard have been included. The following table is a list of the Minor Group elements used: Table 4: List of Minor Group Layer Names Minor Group AREA BLIN BMRK BRDG CITY CURB EDGE EQPM FITI GATE HYDT INLT LIMI LINE METR OTLT PARK PIPE PLAY RTWL RWAY STRC SUBD SURF TEXT TREE TUNL VALV Definition Area Baseline Benchmarks Bridge (pedestrian), bridge survey points City Curb Edge Equipment Fitting Gate Hydrants Inlet Limit of earthwork Lines Meters Outlet Park Piping Playground equipment/structures Retaining wall Right-of-way (public access) Structures Subdivision (interior) lines Surface Text Trees Tunnel Valves Status The Status field is an optional single-character element that distinguishes the data contained on the layer according to the status of the work or the construction phase when needed for clarity. For example, temporary easements and new easements are differentiated by the use of the T Specific Data and Layer Naming Requirements 12

17 status indicator for temporary easements and an N status indicator for new easements. The following table lists all of the potential indicators that can be used to define the status of a feature. Table 5: List of Potential Status Codes A D E F M N T Status Definition Abandoned Existing to demolish Existing to remain Future work Items to be moved New work Temporary work Master Layer List Combining all of these elements; Discipline Designator, Major Group, Minor Groups, and Status creates the Layer Name that should be used to provide the data to the City for a submission. The following table the Master Layer List that the City requires to have submitted as part of a submission. Descriptive Name Building Footprint - Closed Areas Political Boundaries Lines Park - Closed areas Political Boundaries Lines Subdivision Discipline Name Table 6: List of Composite Layer Names Feature Type Layer Name Discipline Major Minor Status Civil Polygon C-BLDG-AREA C BLDG AREA Civil Line C-BNDY-PARK- AREA C BNDY PARK Civil Polygon C-BNDY-SUBD C BNDY SUBD Construction Limits Civil Line C-CSTL C CSTL Easement Civil Line C-ESMT C ESMT Easement Temporary Civil Line C-ESMT-T C ESMT T Parking Edge Civil Polygon C-PRKG-EDGE C PRKG EDGE Property Lines Civil Line C-PROP-LINE C PROP LINE Sidewalk Bridge Civil Line C-SWLK-BRDG C SWLK BRDG Sidewalk Bridge C-SWLK-BRDG- BRDG- Civil Line C SWLK Combination COMB COMB Sidewalk Bridge C-SWLK-BRDG- BRDG- Civil Line C SWLK Concrete CONC CONC Specific Data and Layer Naming Requirements 13

18 Sidewalk Bridge Civil Line C-SWLK-BRDG- OTHER C SWLK Sidewalk Bridge Steel Civil Line C-SWLK-BRDG-STL C SWLK Sidewalk Bridge Wood Civil Line BRDG- OTHE BRDG- STL BRDG- WOOD C-SWLK-BRDG- WOOD C SWLK Sidewalk Edge Civil Line C-SWLK-EDGE C SWLK EDGE Topography Major Contours Topography Minor Contours Roadway Baseline Roadway Bridge Roadway Curb Roadway Right of Way Roadway Signage Area Surface Roadway Tunnel/Underpass Fire Protection Hydrants and connections Sanitary Sewer Structures Civil Line C-TOPO-MAJR C TOPO MAJR Civil Line C-TOPO-MINR C TOPO MINR Civil Transportation Civil Transportation Civil Transportation Civil Transportation Civil Transportation Civil Transportation Civil Transportation Line CT-ROAD-BLIN CT ROAD BLIN Line CT-ROAD-BRDG CT ROAD BRDG Line CT-ROAD-CURB CT ROAD CURB Line CT-ROAD-RWAY CT ROAD RWAY Line CT-ROAD-SIGN CT ROAD SIGN Line CT-ROAD-SURF CT ROAD SURF Line CT-ROAD-TUNL CT ROAD TUNL Civil Utilities Line CU-FIRE-HYDT CU FIRE HYDT Civil Utilities Line CU-SSWR-MHOL CU SSWR MHOL Sanitary Sewer Pipe Civil Utilities Line CU-SSWR-PIPE CU SSWR PIPE Storm Sewer Inlet Civil Utilities Line CU-STRM-INLT CU STRM INLT Storm Sewer Structures Civil Utilities Line CU-STRM-MHOL CU STRM MHOL Storm Sewer Outlet Civil Utilities Line CU-STRM-OTLT CU STRM OTLT Storm Sewer Piping Civil Utilities Line CU-STRM-PIPE CU STRM PIPE Storm Detention Pond Civil Utilities Polygon CU-STRM-POND CU STRM POND Water Supply Fitting Civil Utilities Point CU-WATR-FITI CU WATR FITI Water Supply Meter Civil Utilities Point CU-WATR-METR CU WATR METR Water Supply Piping Civil Utilities Line CU-WATR-PIPE CU WATR PIPE Water Supply Piping ABCE Water Supply Piping ACP Civil Utilities Civil Utilities Line Line CU CU WATR WATR CU-WATR- ABCE CU-WATR- ACP ABCE ACP Specific Data and Layer Naming Requirements 14

19 Water Supply Piping ASP Water Supply Piping CAP Water Supply Piping CCP Water Supply Piping CIP Water Supply Piping CONC Water Supply Piping COPPER Water Supply Piping DIP Water Supply Piping HDPE Water Supply Piping LEAD Water Supply Piping NPCONC Water Supply Piping OTHER Water Supply Piping PB Water Supply Piping PCCP Water Supply Piping PERMA Water Supply Piping POLY Water Supply Piping PVC Water Supply Piping STL Civil Utilities Line CU-WATR-ASP CU WATR Civil Utilities Civil Utilities Line Line ASP CAP CCP CIP CONC COPPE R DIP HDPE LEAD NPCO NC OTHER PB PCCP PERM A POLY PVC STL CU-WATR- CAP CU-WATR- CCP CU CU WATR WATR Civil Utilities Line CU-WATR-CIP CU WATR Civil Utilities Civil Utilities Line Line CU-WATR- CONC CU-WATR- COPPER CU CU WATR WATR Civil Utilities Line CU-WATR-DIP CU WATR Civil Utilities Civil Utilities Civil Utilities Civil Utilities Line Line Line Line CU-WATR- HDPE CU-WATR- LEAD CU-WATR- NPCONC CU-WATR- OTHER CU CU CU CU WATR WATR WATR WATR Civil Utilities Line CU-WATR-PB CU WATR Civil Utilities Civil Utilities Civil Utilities Civil Utilities Line Line Line Line CU-WATR- PCCP CU-WATR- PERMA CU-WATR- POLY CU-WATR- PVC CU CU CU CU WATR WATR WATR WATR Civil Utilities Line CU-WATR-STL CU WATR Water Supply Valves Civil Utilities Line CU-WATR-VALV CU WATR VALV Area Median Concrete Landscaping Polygon L-AREA-MEDN-C L AREA Area Median Dirt Landscaping Polygon L-AREA-MEDN-D L AREA Area Median Mulch Landscaping Polygon L-AREA-MEDN-M L AREA Area Median Native Grass Landscaping Polygon L-AREA-MEDN-NG L AREA Area Median Rock Landscaping Polygon L-AREA-MEDN-R L AREA Area Median Synthetic Turf Landscaping Polygon L-AREA-MEDN-ST L AREA MEDN- C MEDN- D MEDN- M MEDN- NG MEDN- R MEDN- ST Specific Data and Layer Naming Requirements 15

20 Area Median Turf Landscaping Polygon L-AREA-MEDN-T L AREA MEDN- T Area Park Site Landscaping Polygon L-AREA-PARK L AREA PARK Area Park Site Class BOS Area Park Site Class CHS Area Park Site Class CNTYP Area Park Site Class CP Area Park Site Class DP Area Park Site Class GC Area Park Site Class GWGB Area Park Site Class LB Area Park Site Class LM Area Park Site Class LUP Area Park Site Class NCA Area Park Site Class NP Area Park Site Class PP Area Park Site Class RP Area Park Site Class SUP1 Area Park Site Class SUP2 Landscaping Polygon L-AREA-PARK-BOS L AREA Landscaping Polygon L-AREA-PARK-CHS L AREA Landscaping Polygon PARK- BOS PARK- CHS PARK- CNTY PARK- CP PARK- DP PARK- GC PARK- GWGB PARK- LB PARK- LM PARK- LUP PARK- NCA PARK- NP PARK- PP PARK- RP PARK- SUP1 PARK- SUP2 L-AREA-PARK- CNTYP L AREA Landscaping Polygon L-AREA-PARK-CP L AREA Landscaping Polygon L-AREA-PARK-DP L AREA Landscaping Polygon L-AREA-PARK-GC L AREA Landscaping Polygon L-AREA-PARK- GWGB L AREA Landscaping Polygon L-AREA-PARK-LB L AREA Landscaping Polygon L-AREA-PARK-LM L AREA Landscaping Polygon L-AREA-PARK-LUP L AREA Landscaping Polygon L-AREA-PARK-NCA L AREA Landscaping Polygon L-AREA-PARK-NP L AREA Landscaping Polygon L-AREA-PARK-PP L AREA Landscaping Polygon L-AREA-PARK-RP L AREA Landscaping Polygon L-AREA-PARK-SUP1 L AREA Landscaping Polygon L-AREA-PARK-SUP2 L AREA Area Playground Landscaping Polygon L-AREA-PLAY L AREA PLAY Area Surface Landscaping Polygon L-AREA-SURF L AREA SURF Fencing Barb Wire Landscaping Line L-FENC-BW L FENC BW Fencing Chain Link Landscaping Line L-FENC-CL L FENC CL Fencing Cable Wire Landscaping Line L-FENC-CW L FENC CW Fencing Gate Landscaping Line L-FENC-GATE L FENC GATE Fencing Line Landscaping Line L-FENC-LINE L FENC LINE Fencing Landscaping Line L-FENC-OT L FENC OT Fencing Prairie Dog Fabric Landscaping Line L-FENC-PDF L FENC PDF Fencing Plastic Rail Landscaping Line L-FENC-PR L FENC PR Fencing Smooth Wire Landscaping Line L-FENC-SW L FENC SW Specific Data and Layer Naming Requirements 16

21 Fencing Wire Fabric Landscaping Line L-FENC-WF L FENC WF Fencing Wood Rail Landscaping Line L-FENC-WR L FENC WR Irrigation Equipment Landscaping Point L-IRRG-EQPM L IRRG EQPM Irrigation Pipe Landscaping Line L-IRRG-PIPE L IRRG PIPE Irrigation Pipe ABCE Landscaping Line L-IRRG-ABCE L IRRG Irrigation Pipe ASP Landscaping Line L-IRRG-ASP L IRRG Irrigation Pipe CAP Landscaping Line L-IRRG-CAP L IRRG Irrigation Pipe CCP Landscaping Line L-IRRG-CCP L IRRG Irrigation Pipe CIP Landscaping Line L-IRRG-CIP L IRRG Irrigation Pipe CONC Landscaping Line L-IRRG-CONC L IRRG Irrigation Pipe COPPER Landscaping Line ABCE ASP CAP CCP CIP CONC COPPE R DIP HDPE LEAD NPCO NC OTHER PB PCCP PERM A POLY PVC STL L-IRRG- COPPER L IRRG Irrigation Pipe DIP Landscaping Line L-IRRG-DIP L IRRG Irrigation Pipe HDPE Landscaping Line L-IRRG-HDPE L IRRG Irrigation Pipe LEAD Landscaping Line L-IRRG-LEAD L IRRG Irrigation Pipe NPCONC Landscaping Line L-IRRG- NPCONC L IRRG Irrigation Pipe OTHER Landscaping Line L-IRRG-OTHER L IRRG Irrigation Pipe PB Landscaping Line L-IRRG-PB L IRRG Irrigation Pipe PCCP Landscaping Line L-IRRG-PCCP L IRRG Irrigation Pipe PERMA Landscaping Line L-IRRG- PERMA L IRRG Irrigation Pipe POLY Landscaping Line L-IRRG-POLY L IRRG Irrigation Pipe PVC Landscaping Line L-IRRG-PVC L IRRG Irrigation Pipe STL Landscaping Line L-IRRG-STL L IRRG Area Playground Location Area Park Surface Bluegrass - Mowed Landscaping Point L-NODE-PLAY L NODE PLAY Landscaping Polygon L-PARK-BGM L PARK BGM Specific Data and Layer Naming Requirements 17

22 Area Park Surface Bluegrass - Un- Mowed Landscaping Polygon L-PARK-BGNM L PARK BGNM Area Park Building Landscaping Polygon L-PARK-BLDG L PARK BLDG Area Park Surface Hard Plowed Area Park Surface Hard Shoveled Area Park Surface Hard/Soft - Unplowed Area Park Surface Native Grass Area Park Surface Shrub/Flower Bed Landscaping Polygon L-PARK-HSP L PARK HSP Landscaping Polygon L-PARK-HSS L PARK HSS Landscaping Polygon L-PARK-HSUP L PARK HSUP Landscaping Polygon L-PARK-NG L PARK NG Landscaping Polygon L-PARK-SFB L PARK SFB Park Sign Landscaping Polygon L-PARK-SIGN L PARK SIGN Area Park Surface Synthetic Turf Area Park Surface Texas Hybrid - Mowed Area Park Surface Water Landscaping Polygon L-PARK-ST L PARK ST Landscaping Polygon L-PARK-THM L PARK THM Landscaping Polygon L-PARK-W L PARK W Plant Tree Landscaping Point L-PLNT-TREE L PLNT TREE Trail/Path Bike Lane Landscaping Line L-TRAL-BKLN L TRAL BKLN Trail/Path Bike Route Landscaping Line L-TRAL-BKRT L TRAL BKRT Trail/Path Baseline Landscaping Line L-TRAL-BLIN L TRAL BLIN Trail/Path Path Landscaping Line L-TRAL-PATH L TRAL PATH Trail/Path Sidewalk Landscaping Line L-TRAL-SDWLK L TRAL SDWLK Trail/Path Sharrow Landscaping Line L-TRAL-SHRRW L TRAL Trail/Path Street Landscaping Line L-TRAL-ST L TRAL ST Trail/Path Trail Landscaping Line L-TRAL-TL L TRAL TL SHRR W Retaining Wall Landscaping Line L-WALL-RTWL L WALL RTWL Political Boundary City Annexation Control Benchmarks Building Points, Restroom Building Points, Shelter Survey/ Mapping Survey/ Mapping Node Node Polygon V-BNDY-CITY- ANNX V BNDY CITY- ANNX Point V-CTRL-BMRK V CTRL BMRK Point Point V V NODE NODE V-NODE-BLDG- BATH V-NODE-BLDG- SHLT BLDG- BATH BLDG- SHLT Specific Data and Layer Naming Requirements 18

23 3.2 Civil 3D Object Requirements and Definitions The use of Civil 3D objects allows the City to simplify the data migration process from CAD to GIS. To assist in this process, the following Civil 3D objects have been created and are provided in the download package for use in complying with the City Standards: Points: Survey benchmark data Alignments: New roadway alignments Parcels: Existing and new parcel geometry Pipe networks: Gravity pipe networks (sanitary and storm) This information should be included in the object data for each of the feature types. Any and all surfaces from your DWG not targeted by proposed pipe networks must be removed prior to submission Civil 3D Points Civil 3D points will be used to provide survey benchmark data to the City. The points will contain horizontal location information and benchmark elevation information. They will use point names matching the benchmark names. The description field within the Point object will describe the type of monument. The following is the list of required attributes of a point object: Point name Elevation Description Civil 3D Alignments Civil 3D Alignment objects will be used to define all proposed (new) roadway centerlines. The Alignments will be named to match road names. The following is the list of required attributes of an alignment object: Alignment Name Civil 3D Parcels Civil 3D Parcels will define parcels, right-of-way, and subdivision lot lines, while Parcels styles will define the three types of parcel lines. Easements will not be required to be Civil 3D objects; they will instead use the proper layers to identify permanent and temporary easements. This will prevent duplicate line work necessary to create the easement lines in Civil 3D. The following is the list of required attributes of a parcel object: Specific Data and Layer Naming Requirements 19

24 Parcel Style Subdivision boundary polygon, Right-of-Way line, Parcel line Civil 3D Gravity Pipe Networks Pipe Networks will be used for Storm Sewer and Drainage networks designed for projects with the City. The Part lists provided in the drawing templates include structures (manholes, inlets, and outlets), pipe materials, and pipe sizes. Additional pipe sizes, materials, and structures can be added to the part lists in Civil 3D as needed. Pipes and structure objects include start and end invert elevations, sump elevations, and outlet elevations. In addition, structures will include the structure diameter as defined in the part list. Existing drainage structure information is not part of the CAD Data Submittal Standard. As such, please remove all existing layers and existing pipe networks that are not required prior to submission. The following is the list of required attributes of a pipe network: Pipe Diameter (Horizontal/Vertical) Pipe Material Upstream Invert Elevation Downstream Invert Elevation Structure Type Civil 3D Pressure Pipe Networks The City is evaluating the use of Pressure Pipe Networks in the data migration. Until such evaluation is complete, this standard will only require AutoCAD entities to represent all potable water systems, irrigation systems, and public fire protection systems. Civil 3D Pressure Pipe Network objects, if in the design, will be converted to standard AutoCAD entities for the purpose of this submission. 3.3 Blocks And Symbols All blocks and symbols for data migration are stored within the drawing template. They may be used either as standard AutoCAD blocks or linked to Civil 3D object styles which can be used as design features. The legend below highlights the commonly used features in plan production and the preferred method to be used for display. The City also recognizes that consultants have viable reasons and desires for displaying data in a certain way on a particular plan set so the City is not requiring data to be displayed in a certain way as part of this standard. 3.4 Civil 3D and AutoCAD Block Attributes The City has defined a minimum set of Civil 3D or AutoCAD block attributes that are required to be provided with a submission. The Civil 3D objects and AutoCAD blocks that have been created and provided for use include all of these attributes. The following table lists the details of each of the attributes that must be provided. If no attributes are listed in the table than no attributes are required as part of the submission. Specific Data and Layer Naming Requirements 20

25 Table 7: List of Required Attributes Feature Feature CAD Feature Type / Type Name Potable Water Pipe Line Line/Polyline Stormwater Pipe / Culverts Line Civil 3D Pipe Network Wastewater Pipe Line Civil 3D Pipe Network Feature Feature CAD Feature Type / Type Name Manhole (Storm) Point Civil 3D Pipe Network Manhole (Sewer) Point Civil 3D Pipe Network CAD Attribute Definition Attribute Data Type Linetype Diameter Double Line Property Length Double Layer Material Text Civil 3D Object Data Material Text Civil 3D Object Data Type Text Civil 3D Object Data Horizontal Double Diameter Civil 3D Object Data Vertical Double Diameter (optional) Civil 3D Object Data Upstream Double Invert Elevation Civil 3D Object Data Downstream Double Invert Elevation Civil 3D Object Data Slope Double Civil 3D Object Data Pipe Shape Text Civil 3D Object Data Material Text Civil 3D Object Data Diameter Double Civil 3D Object Data Upstream Double Invert Elevation Civil 3D Object Data Downstream Double Invert Elevation Civil 3D Object Data Slope Double CAD Attribute Definition Attribute Data Type Civil 3D Object Data Diameter Double Civil 3D Object Data Unit Text Civil 3D Object Data Depth Double Civil 3D Object Data Elevation (Rim) Double Civil 3D Object Data Diameter Double Civil 3D Object Data Unit Text Specific Data and Layer Naming Requirements 21

26 Inlet Point Civil 3D Pipe Network Outlet Point Civil 3D Pipe Network Valve Point Block with Attributes COA Valve Fittings Point Block with Attributes COA Fitting Hydrant Point Block with Attributes COA Hydrant Meter Point Block with Attributes COA Meter Parcel Line Civil 3D Object Subdivision Line Civil 3D Object Feature Feature CAD Feature Type / Type Name Building Footprint Polygon Line/Polyline Street Centerlines Line Civil 3D Object Bridge/Overpass Line Line/Polyline with Object Table Road Bridge Civil 3D Object Data Sump Depth Double Civil 3D Object Data Elevation (Rim) Double Civil 3D Object Data Width Double (Perpendicular to Street) Civil 3D Object Data Length (Parallel Double to Street) Civil 3D Object Data Type Text Civil 3D Object Data Type Text Civil 3D Object Data Elevation Double (Invert) Civil 3D Object Data Owner Text Structure Diameter Material Valve Type Double Text Text Structure Material Material Text Structure Type Type Text Diameter Diameter Double Diameter Meter Function Civil 3D Object Style Parcel Line Type Civil 3D Object Style CAD Attribute Definition Layer Attribute Double Text Text Text Data Type Civil 3D Object Name Street Name Text Width Double Specific Data and Layer Naming Requirements 22

27 Length Clearance Height Grade Double Double Text Curb (Face) Line Line/Polyline Layer Sidewalk Line Line/Polyline Parking Lot Polygon Polyline Permanent Easement Line Civil 3D Object Construction Limits Line Line/Polyline Survey Benchmark Point Block with Attributes COA Benchmark Layer Layer Civil 3D Object Style Layer Easement Line Type Elevation Name Text Double Text Ponds Polygon Line/Polyline Annexation City Limit Boundary Polygon Polyline Object Property Ownership Capacity (Cubic Feet) Text Integer Pedestrian Bridge Line Line/Polyline With Object Table - Bridge Playground Surface Polygon Polyline Layer Bridge Length Double Bridge Width Double Layer Deck Material Text Railing Material Text Playground Location Point Block With Attributes COA Playground Layer Surface Material Text Playground Name Text Specific Data and Layer Naming Requirements 23

28 Feature Feature Type CAD Feature Type / Name Restrooms Point Block With Attributes COA Restroom CAD Definition Attribute Attribute Type Seats Data Type Text Double Retaining Walls Line Line/Polyline With Object Table - Walls Shelters Point Block With Attributes - COA Rain Shelter Depth of Wall Double Height of Wall Double Layer Material Text Object Property Length Double Sign(Public Works) Point Block With Attributes COA Sign Electricity Service Electricity Service Yes/No Sign (Parks) Point Block With Attributes COA Sign Post Type Text Trails Line Line/Polyline With Object Table - Trail Type 1 Type 2 Sign Material Post Type Text Text Text Text Surface Surface Text Layer Trail Type Text Width of Trail Width Double Trees Point Block With Attributes CTR/DTR Tunnel / Underpass (edge) Line Line/Polyline With Object Table - Tunnel Common Name Diameter Text Double Specific Data and Layer Naming Requirements 24

29 Fence Access Location Point Block With Attributes COA Gate Vertical Clearance Underpass Shape Height Tunnel Lighted Tunnel Width Access Type Access Width Double Text Double Text Double Text Double Fences Line Line/Polyline With Object Table - Fence Post Material Text Layer Fence Material Text Fence Height Double Irrigation Controller Point Block With Attributes COA Irrigation Control Controller Type Size Zones Text Text Irrigation Pipe Line Line/Polyline Median Surfaces Polygon Polyline With Object Table - Park Layer Material Text Linetype Size Double Type Irrigated Text Yes/No Park / Open Space Polygon Polyline Object Property Area Double Site Class Text Park Surface Polygon Polyline With Object Table - Park Specific Data and Layer Naming Requirements 25

30 Irrigated Yes/No Layer Surface Text 3.5 Policy on External References The use of XREF files in the creation of plan sets is an acceptable practice, but for the purposes of the submission, all required data should be merged into a single CAD file and provided to the City. 3.6 Relationship to Standards The City of Aurora layer standard is based on the National CAD Standard, though it is not intended to be a design standard, but a data migration translation standard for Civil 3D layer data into a GIS data structure City Standards These CAD Standards are a supplemental guide to other documentation, requirements, and standards that exist at the City including the following: Engineering Design Standards o Roadway Design & Construction Specifications o Water, Sanitary Sewer, and Storm Drainage Infrastructure Standards and Specifications o Drainage Criteria Manual o Material Prequalification Planning Design Standards o Parks & Open Spaces Dedication & Development Criteria Manual o Planning Department Design and Architectural Standards Site Plan Manual Subdivision Plat Manual Plan Review Checklist Pavement Design Submittal Checklist All submittals still must adhere to all application City standards and checklists. It is recognized that there remains existing documentation found within the City of Aurora which may conflict with this CAD Standard. All efforts have been made to resolve these instances of conflict, but the City does not guarantee that all discrepancies have been found or resolved. The City of Aurora Roadway Design & Construction Specifications should take precedence National CAD Standard This standard is fundamentally based on the NCS and an attempt has been made to comply with that standard wherever possible. However, there are many items within the NCS that are open to Specific Data and Layer Naming Requirements 26

31 interpretation or items that may hinder the goals of City s standardization project. Where contradictions or interpretations exist, the City of Aurora CAD Data Submission Standard will take precedence. Specific Data and Layer Naming Requirements 27

32 4 AutoCAD Submittal Workflows This section includes procedural guidelines for submitting CAD data to the City for integration into the City s GIS. This includes Batch Standards Checker and the Layer Translator workflow to migrate a consultant s data to the City layer standard. 4.1 Extracting AutoCAD Polylines from A Civil 3D Surface If your plan submission includes a proposed surface as a Civil 3D object, you must extract polylines representing the proposed contours with elevations for the purpose of this CAD to GIS workflow. To do this, select your surface in Civil 3D. Once selected, a context sensitive Ribbon will appear in Civil 3D, From this Ribbon select the Extract Objects command. In the Extract Objects from Surface dialog select Major and Minor Contours and press OK After this you can detach the surface from the file, your contours will be placed in the file. AutoCAD Extraction Workflows 28

33 5 Appendices This section includes supporting reference documents. 5.1 Appendix A: Batch Standards Checker Each set of provided templates/drawings have a corresponding.dws file to help ensure the standards have been properly utilized. These files audit and analyze drawings for proper layer use and compare what they have found to the predefined standards. Prior to performing the standards check, an additional plug-in will need to be installed. This will require the user to have local administrator rights on the PC. Included with the standards is an executable file, Aurora_CADCheckerInstall.exe, which when run will install the plug-in, and add the following files: the.dws files used in the standards checker, a readme.txt document, an uninstall executable, and the files AuroraBounds.pdb and AuroraBounds.dll. If the plug-in, Sample Standards checker, is not installed and ready for use when you run the batch standards checker, refer to the AuroraBounds_readme.txt file for information on how to manually add the registry key and register the dll file. Open the Batch Standards Checker by searching for it in your start menu or you can find it under the Autodesk Civil 3D folder in your start menu. On the Drawings tab, click the + (plus) symbol to add the drawing you want to check for compliance with the Aurora CAD Data Submission Standards. Appendices 29

34 Appendices 30

35 In the Standards tab, check the option to Check all drawings using the following standards files. Then click the + (plus) symbol to add the.dws standards files to use in performing the check. These files were included in the plug-in installation. Appendices 31

36 In the Plug-Ins tab, check only the Layers and Coordinate Check plug-ins. Once all of these settings are complete, start the check by selecting the Start Check button at the top. Click ok to save your settings. Upon completion, a report will open in your default browser. Use this to determine any problems inconsistencies between the.dws and your.dwg that need to be addressed. To review the Standards Violations previously reviewed in CAD, pick the Problems option in the list. Address the problems in the drawing and run the check again until the document meets the compliance requirements of the City. If your CAD design includes features outside of the city limits, violations will occur when running the batch standards checker. This is acceptable. Please utilize the Notes tab in the report dialog to state the explanation of the design boundary exception. Print this report as a PDF to be included in submittal process. Appendices 32

37 5.2 Appendix B: Layer Translator Instructions In order to take the layers from an existing file and bring them up to standard layer naming, you can use the Layer Translator tool in AutoCAD. Prior to running the tool, it would be best to purge the unused layers in your existing drawing to reduce the number of layers you are trying to translate. To access the tool, click the Layer Translator button, located on the Manage tab of the ribbon on the CAD Standards panel (alternately type LAYTRANS at the command line): The Layer Translator pop-up window will appear with a list of the layers in the current drawing on the left panel labeled Transfer From. On the right panel Transfer To you want to load the layers from the standards drawing. Click Load to browse for the drawing with the desired layers names: Appendices 33

38 Appendices 34

39 Choose the layer on the left, in the existing file, that matches the layer you want it to translate to on the right, the standard file. You can select 1 or multiple layers from the Translate From column to map to the desired layer in the Translate To column. Once you have chosen the layers from each column, click Map and a list of mappings will populate in the box on the lower half of the Layer Translator window. Appendices 35

40 The default settings can be changed by selecting Settings in the lower left. You can refer to the Autodesk help topic Settings Dialog Box (Layer Translator) for information on how each option functions. Once you have completed selecting the layers to translate from and to as described above, you may click Translate in the lower right corner. A popup box will ask if you want to save the mapping settings. Clicking Translate Only will translate the layers without prompting you to save the settings as a dws file. Appendices 36