GIS Using AutoCAD Map - cdn.ymaws.com · AutoCAD® Map® provides a tremendous amount of GIS...

GIS / Mapping Applications with AutoCAD Map John Cooke CivilTraining, LLC a division of Wetland Studies and Solutions, Inc.

Training presentations and materials by CivilTraining, LLC are

copyrighted and licensed for each exclusive engagement.

Any recording, reuse or redistribution without prior written consent is prohibited.

10/03/2012 1.03 © Copyright (2012) Wetland Studies and Solutions, Inc. Do not reproduce without permission. 1

GIS/Mapping Applications with AutoCAD Map AutoCAD® Map® provides a tremendous amount of GIS functionality, and many surveyors have the benefit of already owning the product. The GIS functionality provided by Map can be found in all releases of AutoCAD Land Desktop®, Civil 3D Land Desktop Companion®, Civil 3D® or Map 3D®. This document demonstrates workflow using Civil 3D in a stormwater inventory project. The client required GIS deliverables as well as CAD deliverables for analysis in EPA MS4 (Municipal Separate Storm Sewer Systems) permitting. Starting a Drawing in Civil 3D Using a Template for C3D Styles A critical practice when working in Civil 3D is never to start a drawing from scratch; every drawing initiated in Civil 3D must be started from a template drawing containing Civil 3D object and label styles. Civil 3D is dependent on its template drawing(s) to insure that the program will function in the proper units, and be able to display and label data properly. Working without a template in Civil 3D will place everything on layer Ø, and the operator will have little or no ability to control color, pen weights or annotation for plotting deliverable drawings. Figure 1.01 shows sample point object and label styles present in the template drawing used in this example.

To obtain a copy of the template drawing used in this demonstration email us at [email protected]. Figure 1.01 – Point Object and Label Styles in Template


Checking or Setting Units and Coordinate system in Drawing Setup

Civil 3D units are an especially critical setting, as Civil 3D wakes up in International Feet. The units must be changed to US Survey Feet, especially when tied to a coordinate zone as seen here. The coordinate system set in Civil 3D will be included as an ESRI coordinate projection when the final deliverables are prepared using Map. These settings are found on the Settings tab of the Civil 3D Toolspace, by Right-Clicking on the drawing name and accessing Edit Drawing Settings.

Be sure to always check the unit settings in Civil 3D, as the program defaults to International Feet.

Figure 1.02 – Units and Zone Tab in Drawing Settings Raster Design Image Insert

There is an aerial image available as a

SID file which can be inserted into the drawing as a background image using Raster Design. The Raster Design Insert Options setting shown in Figure 1.03 set to Insertion Dialog insures that the correlation data in the image file can be checked. Figure 1.03 – Raster Design Image Insert


Image Correlation from SID File

Image correlation data can be found in a number of formats, including World Files or embedded in the image file itself. In this case the insertion coordinates were found within the image file, and the units required changing to feet to insert the image on NJ State Plane coordinates. Figure 1.04 – Raster Design Image Insertion

Mapimport ESRI® Shape Files

A substantial amount of existing conditions data for the project were provided by the client in the form of ESRI GIS data, as both Shape Files and e00 Interchange Files. Both can be imported into the drawing using the MapImport command. Figure 1.05 shows the processing of the attribute data for the

Planimetric Base Shape File, insuring that Map Object Data will be created from the data underlying the GIS and making it available within the Map drawing.

Figure 1.05 – MapImport Shape File Data


Shape File Data in AutoCAD Properties Dialog

With the Shape File attribute data imported as Object Data in Map, the data can be explored by selecting an object and examining the data in the Properties Palette, where they are displayed at the bottom.

Figure 1.06 – Shape File Attribute Data as Object Data in Properties


e00 GIS Import in Separate Topo Drawing

The e00 topo data from GIS could be processed into the working survey drawing using the MapImport command in the same fashion as the Shape Files, but doing so would add a significant amount of overhead to the survey drawing. Since the topo will only be used occasionally, a better strategy is to create a separate topo drawing from these data, and to then display them as required using a Map Source Drawing and Quick View.

In Figure 1.07, a second drawing has been started, again setting the appropriate coordinate system, and the e00 interchange file for the topo is being imported with MapImport, again processing the attribute data.

Figure 1.07 – MapImport e00 Interchange File


The resulting topo drawing is seen in Figure 1.08.

Figure 1.08 – Resulting Separate Topo Drawing

Attach Source Drawing for Topo

The topo drawing produced can be displayed as a Map Source Drawing by attaching it in the Map Task Pane, and then Quick Viewing it to display (or plot) the info. Figure 1.09 shows the process of attaching a source drawing, including the creation of a Map Drive Alias to access a network drive. Figure 1.09 – Attaching Map Source Drawing


Quick View Source Drawing

Map Source Drawings can be Quick Viewed at any time by Right-Clicking on the source drawing in the Task Pane and selecting Quick View from the menu. A Map Quick View will persist on the screen until a redraw, regen or save (including autosave), and will plot. Map Source drawings attached to the parent drawing are remembered with a file save, and will be present the next time the parent file is opened.

Figure 1.10 – Attached Topo Drawing Quick Viewed in Survey working Drawing

A Map Quick View of a Source Drawing is a great tool for managing the display of very large topo drawings in this fashion. Remember that the topo will not automatically display, however; the Quick View command must be executed to make the drawing info display for plotting.


Working Sections for Field Work Determined

With the base mapping and existing conditions available, targeted area for the first round of field work in the stormwater inventory project were established, coinciding with the four areas shown in Figure 1.11. This initial fieldwork took place before our involvement in the project as evidenced later; though this work followed conventional practices as would be exploited by most firms, see some comments regarding projects of this type at the end of this document under lessons learned….

Figure 1.11 – Four Working Sections of Project for Field Work


Sample Field Notes

Based on our twenty five plus years of experience in the industry, we cannot overemphasize the need for detailed, complete, accurate field notes. There is a tendency, in our opinion, to focus too much on technology for data capture. When the individuals who must process the data are not the same individuals who collected them, there can be a significant disconnect between the field and office. Only accurate field notes and sketches will overcome this. A page of the field notes from the first pass fieldwork for this project are shown in Figure 1.12. we are quick to comment that these field notes would be more than adequate for some purposes, but their shortcomings for an MS4 inventory of this type will become evident later. Again, refer to lessons learned at the end of this document. Notably the field sketches lacked point numbers or indications of inverts in structures.

Figure 1.12 – Sample Page of Field NotesIt should be noted that the field crews involved here are personal friends of ours, so we’re taking pains to keep the tire tracks of anyone’s back. Still there are important lessons to be learned here.


Structure Point Data as ASCII File

The actual import of field data into Civil 3D utilizes ASCII

files, comma separated files using the PNEZD (Point Number, Northing, Easting, Elevation, Description) format. This format and methodology is common to virtually any data collection system. A section of the structure inventory import is seen in Figure 1.13. The descriptions used followed a convention where the first character identifies the fieldwork area (all Section 1 in this example), the second two characters identify the structure type (Manhole Storm, Inlet, B‐Inlet, A‐Inlet and Headwall shown), and the last three characters are an incremental number for the structure type within each area. The final descriptions were finessed in Microsoft® Excel® prior to importing into Civil 3D. Figure 1.13 – Section of Structure Import ASCII File Layer Creation for Point Import

Since the unique descriptions used in this project will not match standard Description Keys in the Civil 3D template drawing, a layer is prepared for the points to reside on. The template drawing is configured to place points on the current layer if no description key match is found. The layer used in this example

is V-PNTS-SSWR-STRUCTURE, but there’s no magic in that name

Figure 1.14 – Layer Creation for Point Import


Point Import into C3D Drawing

In this project the points were to be used solely within one drawing and by a single operator; accordingly a decision was made to import them into the drawing only as Cogo Points rather than through the Survey Database as Survey Points. The process therefore takes place from the Home tab of the ribbon, and the menu selection and ASCII import settings can be seen in Figure 1.15. Note that the points were imported into their own new Point Group as seen in the bottom of the dialog, an important step in formatting their display later.

Figure 1.15 – Import of ASCII File into Drawing as Civil 3D Cogo Points


Changing Properties of Point Group to Display Points

Point display and labeling in Civil 3D are dependent on a hierarchy of settings at four levels involving

default settings, description keys, the _All Points point group and point groups with overrides. While a thorough discussion of these settings is beyond the scope of this document, the fact that the imported points were placed in their own point group allows their display to be easily manipulated.

Configuring the desired display consists of selecting the proper Point Label Style on the Information tab of the Point Group Properties dialog box for the selected group. A Point Label style Override is then turned on using the Overrides tab of the same dialog box. These steps are shown in Figures 1.16 and 1.17, and the resulting point display is seen in Figure 1.18.

Figure 1.16 – Selecting Desired Point Label Style


Figure 1.17 – Point Group Overrides

Figure 1.18 – Structure Data Displayed as Civil 3D Points


Verifying Survey Data Against As-Built and Other Sources

Examination of the first‐pass field work and its comparison with imported GIS data and observed conditions did yield areas where additional field work would be required. As a guide in targeting more field work other data from the client were examined, including design, construction and as‐built

drawings in a variety of formats. While some of these drawings were in CAD (DWG or DGN), many were

raster data as PDF or TIF. These drawings were indispensable in figuring out the actual topology of the system, as a number of manholes were not evident do to being covered or paved over. Where possible these drawings were inserted into the working drawing as raster data, scaled and rotated to match actual coordinates.

Examples of raster data used are seen in Figures 1.19 and 1.20.

Figure 1.19 –Example Raster Drawing Used for Field Verification


Figure 1.20 –Example Raster Drawing Used for Field Verification

Figure 1.21 shows the working drawing with reference data inserted; the bold squares are areas targeted for follow‐up field work.

Figure 1.21 –Working drawing with Follow-Up Areas


The working drawing was then used to create a series of work‐order drawings as seen in Figure 1.22. These drawings were used to direct targeted field work in questionable areas, and to complete the data collection phase of the project.

Figure 1.22 – Work Order Drawing for Follow-Up Field Work

Ultimately all structures were found except three: two were paved over in parking lots and the client deemed them too expensive to access. The third was actually covered over by the expansion of a building, and was totally inaccessible. There were several manholes that were welded shut, and were not opened.


Data Development in Excel

With the data acquisition phase of the project complete the emphasis shifted to data development and processing. The eventual vehicle for data connection in Map would be Microsoft Access®, but data were processed through Excel as an intermediate step.

A portion of the Excel structure table is seen in Figure 1.23, containing data added in the second pass

field work and/or processed through Civil 3D. The PNO column in the spreadsheet is the Civil 3D point

number, while the EQ_ID column (Equipment ID) was the original point description from Civil 3D but will become the unique identifier for each structure for data connectivity in Map.

Figure 1.23 – Structure Data Table in Excel The column names used in Excel should be unique for each column and should not contain spaces to facilitate their use as field names in Access.


Excel Import Into Access

While Excel tables can be attached to drawing objects using Map, the data are much more robust from an analysis standpoint if a true database such as Microsoft Access or Microsoft SQL Server® is used. In this project Access was the database of choice. Processing data through Excel first before import into Access is usually recommended, as the formatting of the data through Access’s Excel Import Wizard is very helpful.

The import process begins on the External Data tab in Access, Excel button, selecting the spreadsheet file to import.

Figure 1.24 – Excel Import into Access

Access and Excel 2010 are shown here, but this process can be performed in any version of the products.

The next steps are critical to insure that data are formatted correctly in Access.


On the first page of the Import Wizard select the desired Worksheet and press Next.

Figure 1.25 – Select Excel Worksheet On the next page, toggle on the use of Excel Column Headings as Field Names and press next.

Figure 1.26 – Select column Headings as Field Names


The column names used in Excel should be unique for each column and should not contain spaces to facilitate their use as field names in Access.

On the next page click on each field and set the data type. Any fields containing hyphens, such as the Longitude seen in Figure 1.27 must be set to Text. Fields which will be subject to any type of arithmetic analysis must be set to Integer or Double. Indexing should be turned Off for each field to prevent conflicts with Map, unless specifically required for Access queries. Press Next to continue.

Figure 1.27 – Set Data Type and Indexing


On the next page set the option to No Primary Key, allowing Map to use a selected field as the primary key for data attachment. Finally press Next to continue and enter the desired name for the table on the last page of the Wizard.

Figure 1.28 – Disable Primary Key The completed Structure table in Access is seen in Figure 1.29.

Figure 1.29 – Structure Table in Access


Create Data Source in Map

The ability to connect a database to drawing objects in Map revolves around the creation and use of a Microsoft UDL, or Universal Data Link. Without delving too deeply into an alphabet soup of acronyms such as OLE, ODBC or MDAC (Google them if you’re technically intrigued), UDL’s provide a connection to databases and are stored on the local computer as pointers for the database connections.

There are significant implications here for 64-Bit Windows systems. Only 64-Bit installations of Microsoft Office allow database connections to Access on 64-Bit machines. Access connectivity will not be available if the common installation of 32-Bit Office is used. 64-Bit Office can be readily installed from the same media as the 32-Bit if desired, but the installation can have detrimental effects on Outlook. Contact us for more information if desired. Configuration of the Data Source is accomplished by Right-Clicking on the Data Sources level in the Map Task Pane, and selecting Configure. Enter the desired Data Source Name and press OK.

Remember the Data Source name used, as this step will have to be repeated for each computer that will access the data. Figure 1.30 – Configure Data Source


As the Data Link Properties dialog displays, select the OLE DB Provider as Microsoft OLE DB Provider for ODBC Drivers. Press Next to continue.

There are other DB providers that could be used, particularly on 32-Bit systems. The 32-Bit Microsoft Jet driver is one we have used with great success. The ODBC provider allows greater portability when the project needs to be moved from one location to another, as the database will be selected each time the drawing is opened. The ODBC provider also provides for more robust querying using SQL if desired. Figure 1.31 – Select DB Provider On the second page of the Data Link Properties dialog select the option to Use Data Source Name, and pick the MS Access Database driver from the list. Press OK to complete the UDL configuration. Figure 1.32 – Select Data Source Name


Attach Database

Using the Data Source configured, the database itself can be attached to the drawing in Map. To attach the database, Right-Click on the Data Sources level in the Map Task Pane and select Attach from the menu. Select the UDL created for the project from the dialog displayed. Since the ODBC driver was used, a dialog displays prompting to browse to and select the database. Press OK once the database is selected (repeat the selection if the dialog reappears, as it commonly does with the ODBC driver).

Figure 1.33 – Attach Database The attached database with its tables and queries will be displayed in the Task Pane. An individual table or query can be opened by Right-Clicking on the level in the Task Pane and selecting Edit Table or View Table as desired. The table selected opens in the map Data View.

Figure 1.34 – Structure Table in Data View Attached data sources are saved with the drawing, and will be re‐opened with the drawing.


Creation of Attributed Blocks for Map Data Attachment

While Civil 3D can manage the surveyed structure data very nicely as Civil 3D point objects, and could even manage user‐defined data fields on them, Map cannot attach data to Civil 3D point objects. (And Civil 3D user‐defined data cannot be exported to ESRI Shape Files). Fortunately, Civil 3D provides an easy method to insert attributed blocks to which Map database attachments can be made.

Although a layer can be created on‐the‐fly in the insertion of the blocks themselves, the layer is created

in advance here to set a color. The layer name sued this time is V-PNTS-SSWR-STRUCT-DATALINK.

Figure 1.35 – Layer Creation for Attributed Blocks

Converting Civil 3D point objects to attributed blocks requires a point block in the drawing with three

AutoCAD attributes named POINT, ELEV and DESC. An old Land Desktop point block, POINT.DWG fills this bill nicely, but this block is no longer supplied with Civil 3D. Although the blocks formerly in the Land Desktop Symbol Manager can now be found in various drawings under

C:\ProgramData\Autodesk\C3D 201X\enu\Data\Symbols, the point block is conspicuously absent. The template drawing available from CivilTraining, LLC or supplied with this class contains the point block. If you do not have the file, again, email us at [email protected] and we’ll gladly provide it. Or you can create it from scratch……


To insert attributed blocks from Civil 3D Cogo Points go to the Home tab of the ribbon, Create data panel, Points dropdown, and select Create Blocks from COGO Points. In the resulting dialog filter the point selection if desired, select the point block inserted into the drawing, and select the layer. Press OK to create the blocks.

Figure 1.36 – Create Attributed Blocks from Cogo Points

Completed blocks are seen in Figure 1.37 along with dragged Civil 3D point labels.

Figure 1.37 – Attributed Blocks with Point Objects


Define Link Template for Data Attachment

The process of attaching database connections to drawing objects in Map begins with the definition of a Map Link Template. The Link Template establishes the actual connection between a value in the drawing (attribute in this case) and a particular value in a particular row in a particular column in the database, The Link Template is created by Right-Clicking on Link Templates in the Map Task Pane and selecting Define Link Template. In the Define Link Template dialog select the Data Source (database) and Table Name. Provide a unique name for the Link Template (SID for Structure ID in this case), and select the individual Field containing the unique identifier to which the connection should be made. For the unique identifier, click on the Key option to select this as the table’s primary key. The Key field should have unique values in both the table and the drawing data, unless multiple drawing objects are to be connected to the same field in the database intentionally. Figure 1.38 – Define Link Template Create No_Hit Layer

A step in the attachment of Map Data Sources to objects in the drawing permits the identification of objects which should have data attachments but don’t. These “No Hit” objects are selected by Map during the process, and can then be changed to a different layer for later examination and correction. For this to be accomplished, the desired layer must exist when the data attachment is made.

In this example a G-NO-HIT-STRUCT layer is created, and assigned a desired color, as seen in Figure 1.39 on the next page. This new layer should NOT be made current, but must exist in the drawing.


Figure 1.39 – No Hit Layer Created

Generate Links

The process of linking Data Source information to drawing objects in Map is actually very easy, consisting of simply matching values found in attributes or text to records found in the database table via the Link Template configured.

To attach the data, Right-Click on the Link Template created earlier and select Generate Links from the menu. In the Generate Data Links dialog select the Linkage Type (Blocks in this case). Select Create Database Links, select the Link Template, block and Block Attribute Tag containing the data for the connection.

Turn on Link Must Exist Validation in the dialog to provide a QAQC check for matching data in the drawing and database, and press OK to proceed. Select the desired drawing objects when prompted at the command line. Figure 1.40 – Generate Links


The process of generating links makes two passes through the data, one at the database level and one at the drawing level to determine matches and connections. If there are data in the drawing without corresponding data in the table, Link Must Exist validation leaves them selected in the drawing when the process completes. These objects can then be changed to the No Hit layer created previously by selecting the layer from the Layer Drop-Down list as seen in Figure 1.38. This MUST be done while the objects are selected at the end of the Generate Links process, as there is no way to repeat this selection later. Once segregated on the No Hit later these objects can be examined and corrections made in the drawing or database as required and links generated on them in the same manner using a selection set. Figure 1.41 – Changing Layer of No Hit Objects

If you want to use the No Hit layer you get one chance to get it right. Check Linked Data

To check the data linkage, open the table from the Link Template as described earlier. In the Data View, use the Highlight pulldown and turn on AutoHighlight, AutoZoom and AutoSelect. Click on Zoom Scale and set the value to 15. Then use Highlight Records Select Objects as seen in Figure 1.42 and select a block in the drawing.

Figure 1.42 – Data view Highlight Pulldown


The Data View scrolls to and highlights the corresponding field in the database.

Figure 1.43 – Database Field Highlighted in the Map Data View

The connectivity in the Data View is bi‐directional; clicking on a field in the Data View using the button to its left zooms to the corresponding object in the drawing and selects it.

Figure 1.44 – Block Selected in Drawing by Selecting Row in Data View


Viewing Database Information

The database information for the structures in this project supplied an essential element for the connection of the structures with pipes – the invert information was available through the database. An easy way to view the database information attached to any object in the drawing is through the Properties Palette, where the data again display near the bottom for each selected object as shown in Figure 1.45.

Figure 1.45 – Database Information in Properties Palette Creating Map Annotation – Property Alteration Query

Another way to make the structure information available for use in creating the network of pipes in this project is to use the database information for annotation, inserting the invert information into the drawing as text labels.

There are a number of ways to create annotation using Map, including the display of connected Map data through an Annotation Template. The simplest method, however, and one that works for all versions of Map since 1.0, is to Query the objects in a separate drawing using a Map Property Alteration Query to produce annotation.

Property Alteration Queries are also the key to doing things like changing 2D contours imported from a Shape File into polylines with elevation to support terrain modeling.

To begin the creation of the annotation the working Survey Base drawing is Closed, as it must be attached to another drawing session as a source drawing to create the annotation.


In a new blank drawing created from the template and using appropriate unit and coordinate settings, the Survey base drawing is attached as a Source Drawing as described earlier. The source drawing is Quick Viewed as described earlier to get zoomed up in the project area as seen in Figure 1.46.

Figure 1.46 – Working survey Base drawing Attached As Source Drawing and Quick Viewed

The database must also be attached to the new drawing, following the process described earlier using the Data Source previously configured. Figure 1.47 – Database Attached Through Data Source


Map can transfer information from one drawing to another using the concept of a Query. In the process of executing the transfer, or query, the properties of the queried objects can be altered based on data found in the drawing or attached database(s), hence the term Property Alteration Query. While a thorough discussion of querying in Map is beyond the scope of this document, the major steps are summarized here (and in figure 1.48 on the next page). Right-Click on Current Query in the Task Pane and select Define to begin a new

query.;

In the Current Query dialog click the Property button, set the queried Property as Block Name, and use the Values button to select the Point block. Press OK to add the Property to the Query.

Toggle the Query Mode to Draw.

Click the Alter Properties button on the right side of the dialog to set up the property alterations.

In the Set Property Alterations dialog press the Text button to create a line of text.

In the Define Text dialog press the Expression button to access the available information. In the Expressions dialog access the Link Template level. Select the Link Template corresponding to the database to be used for labeling, and the individual field to provide the first label to be placed (multiple fields will be used to label as much data as required). Press OK back to the Define Text dialog. Continuing in the Define Text dialog, set a Text Height in model space units. Set the Justification to position the label where desired adjacent to the data. Specify the Text Style and Layer as desired. Press OK to add the first line of text to the annotation query.

Repeat the preceding step for each line of data to be added to the drawing; the fields of data will be stacked one above the other in the final annotation.

Press OK to return from the Set Property Alterations dialog to the Current Query dialog, and press Execute Query to perform the property alteration query.

The resulting annotation consists of AutoCAD text objects. These objects can then be copied and pasted into the working survey drawing, or transferred to it via an AutoCAD Wblock. The interim drawing used to execute the actual query can be discarded.


Figure 1.48 – Property Alteration Query

Figure 1.49 – Text Produced by Property Alteration Query


Export Data to ESRI Shape Files

Recalling that the requirements for this project specified ESRI data, the information prepared in Map is to be exported to Shape Files for preparation of deliverables.

The final deliverable was an SDSFIE Geodatabase, but that’s a topic for another day.

Preparing Data Using Map Queries

The deliverable requirements specified that multiple Shape Files be produced based on structure type,

as organized using the CODE column added in the database. Map queries again facilitate the separation

of data into the various type based on the CODE information for final export to Shape Files.

Figure 1.507 – CODE Column and Data in Database

Once again, work takes place in a new empty drawing configured with the correct units and coordinate system, and to which the working survey drawing is attached as a source drawing and the database is attached using the Data Source.

Setting the coordinate system is especially important at this step in the process, as it will be included in the export to ESRI data.


Again a query is initiated by Right-Clicking on Current Query in the Task Pane and selecting Define.

In the Current Query dialog click the SQL button this time to query against the attached database using Structured Query Language.

Make sure the Link Template is selected correctly in the top of the SQL Link Condition dialog.

Using the Column drop‐down list, select the field containing the data on which to query. Type the desired Value (this entry is case sensitive).

Press Add Condition to add the SQL condition to the query.

Press OK to leave the SQL Link Condition dialog, returning to the Current Query dialog.

Toggle the Query Mode to Draw, and press Execute Query to perform the query

Figure 1.51 – Formatting SQL Query for CODE value MS


The query transfers only those objects with data attachments meeting the SQL data filter. The data connections to these objects can be checked using the Data View as described earlier.

Figure 1.52 – Data Attachment on Queried MS Blocks

Performing the Export to Shape File

Once the appropriate data are available in the drawing, the actual export to Shape File is accomplished with the MapExport command. In the Export Location dialog, make sure the File Type is set to ESRI Shape File. Specify the desired location and file name.

Figure 1.53 – MapExport File Location Dialog


The remaining steps in the process consist of three tabs in the Export dialog. On the Selection tab select the Object Type, corresponding to the type of info to be exported and the ESRI Shape file data requirements. Select the objects to be exported as appropriate.

Figure 1.54 – MapExport Selection Tab On the Data tab use the Select Attributes button to access the database data. Access the Link Templates level. Select the Link Template corresponding to the database to be used for labeling, clicking at that level to include all information in the data export. Press OK to return to the Export dialog. Figure 1.55 – MapExport Data Tab


On the Options tab use the Driver Options button, and toggle the output to 3 Dimension Shape Files. Press OK to return to the Export dialog, and press OK to complete the export.

The completed Shape File export can be seen in

Figure 1.57. Note the presence of the PRJ projection file, where the exported unit and coordinate system information has been transferred to ESRI. Figure 1.56 – MapExport Options Tab

Figure 1.57 – Manholes Shape File


Civil 3D Pipe Network

As mentioned earlier, a component of the project was a hydraulic analysis of the stormwater system to be completed in Civil 3D’s Storm and Sanitary Analysis module. The actual preparation of the data for his part of the project and its execution are beyond the scope of this document, and this is the only aspect of this presentation that could not be completed in a product as early as Land Desktop 3; Civil 3D SSA is only available in Civil 3D 2011, 2012 and 2013. Despite this, the actual data and their presentation are interesting, in terms of annotation presentation and analysis capabilities. A portion of the Section 2 stormwater data are shown in Civil 3D in plan and 3D in Figures 1.58 and 1.59, and the same data are shown in the SSA product in Figure 1.60.

Figure 1.58 – Section 2 Stormwater Data in Civil 3D Plan View


Figure 1.59 – Section 2 Stormwater Data in Civil 3D 3D View

Figure 1.60 – Section 2 Stormwater Data in Civil 3D SSA


Lessons Learned

Considerable value can be attached to performing a post‐mortem on almost any project, and this one was no exception. There were many lessons learned from this project by all parties, including a thorough understanding of the deliverable requirements at the outset. (Can you say “SDSFIE”?) Major lessons learned are appropriate here as they relate to the field data collection aspects of a stormwater inventory project of this nature.

Many of the lessons learned can be summarized in the email dialog below, where we reviewed a survey scope for another project of this type. It should be emphasized that these comments were directed to an engineer preparing a survey scope for another project, and are not indicative of problems with this project or any other; the intent here was to head off problems before they arose:

“I have reviewed the survey scope, and do have some concerns based on my experience with similar projects.

The primary problem I see with the survey scope is that the surveyor is not responsible for actually connecting the pipes between inverts collected in stormwater structures. While reference is made in the scope to "pipe slopes, pipe diameters, pipe material", no specification is made that the surveyor should designate the pipe connectivity. Connecting the structures is a critical component of defining the pipe network for hydraulic analysis. Performing this connectivity can be extremely difficult if not done on‐site and by personnel personally observing the conditions. Errors made in connectivity of the network will invalidate its later analysis. The illustration and connectivity of the inverts in the system is critical and should definitely be added to the survey scope.

There are other components of the stormwater conveyance system which impact its analysis and are either absent in the scope or should be further elaborated:

Inlets ‐ While included in the scope, all inlets should be checked for the presence of flow diverters, which are common in systems such as this. Each inlet should clearly connect to one or more pipes in the stormwater system, unless identified as an inlet point for infiltration (unlikely in this application), In addition to the other invert information specified in the scope, invert positions in the inlet structure should be recorded (northeast, southwest, etc.).

Junction Points ‐ Usually drainage manholes, all junction points should be collected with the same data requirements as inlets.

MS4 Discharge Points ‐ There will be a fixed number of DP's within the system, which must be accounted for in the analysis. All discharge points should be photographed.

Culverts ‐ Impacting runoff hydrograph preparation, any culverts present must be identified. Data should include inverts in and out, diameter, material and condition. Visual analysis should be made to check for possible presence of buried junction or deflection points. Inverts of all culverts should be photographed.

Basins ‐ A complete topographic survey of any detention, retention or stilling basins should be performed, including breaklines at all top and/or toe of slope features. All inlet structures within basins should be treated as separate features. If basins are fully or partially water‐filled, water surface elevation should be indicated but topographic survey should be conducted to the physical bottom of the basin.


Channels or Swales ‐ A complete topographic survey of any channels or swales should be performed, including breaklines at all top and/or toe of slope features. The channel or swale should be identified as paved, unpaved or grassed. If unpaved, characteristics of its material should be recorded, including size of aggregate materials found. One or more photographs of each channel or swale should be included. All inlet structures within channels or swales should be treated as separate features. If channels or swales are fully or partially water‐filled, water surface elevation should be indicated but topographic survey should be conducted to the physical bottom of the channel or swale.

Weirs ‐ A detailed survey of any weirs should be performed, including all dimensions and elevations of each stage. Photographs of all weirs shall be provided.

Headwalls ‐ A detailed survey of any headwalls should be performed, including all dimensions and the invert, diameter and material of all pipes. All headwalls should be connected to identified pipes within the stormwater system. Photographs of all headwalls shall be provided.

Oil‐Water Separators ‐ All oil‐water separators should be identified. All inlets and outlets from oil‐water separators should be treated as structures and connected to the stormwater system as illustrated. Manufacturer, capacity or other data on oil‐water separators present on data plates should be provided.

Downspouts ‐ Downspouts or similar connections from rood drains should be identified. Data should include the size or diameter of the connecting pipe. Downspouts should be photographed.

Flow Control Devices ‐ Any flow control devices used to regulate stormwater flow should be identified, described and photographed.

Valves or Gate Valves ‐ Any valves used to regulate stormwater flow should be identified, described and photographed.

Tanks, Underground or Buried Detention ‐ The presence of any tanks, buried or underground detention should be included, with inlet and outlet structures identified as separate structures. Photographs of tanks or of evidence of underground or buried detention shall be provided.

Infiltration Systems ‐ The presence of any infiltration systems should be included, with inlet structures identified as separate structures.

Pumps or Pump Stations ‐ Any pumps or pump stations should be identified. All inlets and outlets from pumps or pump stations should be treated as structures and connected to the stormwater system as illustrated. Manufacturer, capacity or other data on pumps or pump stations present on data plates should be provided.

Pervious versus Impervious Areas ‐ While pervious versus impervious areas may be distinguishable from the aerial survey, their physical boundaries should be confirmed in the ground survey.

CivilTraining, LLC a division of Wetland Studies and Solutions, Inc.

5300 Wellington Branch Drive | Suite 100 | Gainesville, Virginia 20155

Telephone: 732.869.0592 | Fax: 732.377.5454 CivilTraining.com

Date post:	21-Jan-2019
Category:	Documents
Upload:	ngonhu
View:	225 times
Download:	1 times

GIS Using AutoCAD Map - cdn.ymaws.com · AutoCAD® Map® provides a tremendous amount of GIS...

Documents