¨Convert dwg/dxf files to shapefiles

· Subset pipe features from all lines in dwg

· Subset catch basin (etc.) features from points in dwg

· Convert each theme to shapefile

· Add fields to shapefile tables (see data dictionary)

¨Populate fields based on info in dwg file and on

hard copy maps on file in engineering

· Print hard copies of tables from dwg files and manually input data into shapefile tables

· Circle records on hard tables that were not in digital database

¨Merge all shapefiles into one large shapefile

· Use geoprocessing wizard to merge shapefiles

· May have to convert 3d polylinez features to 2d features

before this will work

¨Find different words and abbreviations used to describe the same

feature and change them to one word chosen to delineate that particular feature

· Abbreviations like jb were changed to junc, tg was changed to grate, etc.

¨Delete points not referencing catch basins

· Scan through files and delete survey elevation points

· Run program created by Tim Minter to find points that contain

duplicate records.

· Scan through and delete records that are obviously duplicates and

are not needed.

¨Make notes on status of empty records

· Scan through entire database and note records where the information is not provided

in the tables

· Scan through entire database and add information that exists for

empty records.

¨Continue populating database with information that was newly

discovered when AutoCad files were pulled up in AutoCad 2000 as

opposed to ArcView.

· Information that was missing in dwg files in ArcView would show up in the same file pulled up in AutoCad 2000. ESRI was contacted by Tim and their reply is stated in the following link dwgfilecorruption

· It is important to note this complication in the process so ArcView users can watch out for this. The following map links show an example of the difference in ArcView and AutoCad.

· ArcView ArcViewZoom AutoCad AutoCadZoom These maps display the same table as shown in ArcView and AutoCad. Note that the STR#s in ArcView stopped at 7313 where as AutoCad printed the entire list. Exploding the features in the AutoCad file before bringing it into ArcView was found to be successful in showing all of the features and text in the file.

¨Incorporate data from hardcopy, hand drawn maps

· Locate project area using city streets data and imagery

· Screen digitize features

· Populate attribute table based on information on maps

¨ Do first field check to find problem areas, develop and

understanding of the stormwater system, and find what

complications/errors/needs exist StormwaterFieldCheck#1

· Take pictures of descriptions and check accuracy of data.

· Look for catch basins that aren’t there, etc.

¨Use Storm Drainage Inventory Data Report books to compare

database to, make notes explaining the status of each cell and

what (if any) problems exist with each cell

· This was done by using the single shapefile theme containing all of the city’s catch basin facilities that was created earlier in the project. The select tool was used to select all of the catch basin features in a particular cell and the selected records that corresponded with the features were promoted to the top of the table.

· Look for missing records and note them

· Dictate whether the cell is completed or will require more work.

· Note any other problems or curiosities found in the cell’s data

¨Continue populating database with information that was thought to

be missing, but was found in the previous step.

¨¨Decide if data is accurate enough for Phase 2 stormwater and how to prioritize next steps¨¨

¨¨¨Data Dictionary¨¨¨

Line Features (pipes)

Point Features (catch basins, etc.)

FIELD TYPE

Shape Shapefile required field

¨Values

· pointZ

Layer Artifact from DWG file

¨Values

· struct

· pnum

· L

· titles

Ptname Part name (?) seems to duplicate, but not well, the values in

the 'str#' field.

¨Values

· 0-n

Str# Structure number (unique values)

¨Values

· 0-n

Cell# Artifact from previous mapping methods.

locator grid value for hardcopy maps.

values

-<alpha><numeric>

-example B1

Desc Textual description of system component Abbreviation descriptions and pictures

values

-pipen (Pipe entrance)

-pipex (pipe exit)

-junc (junction box usually accessable through manhole)

-grate (metal grate - filtered input to system)

-multi (Catch basin inlet structure consisting of a slab on

pedestals which allows flow entry from multiple sides)

-comb (combination grate & curb input to system)

-curb (curb input to system)

-hedwl (head wall - water output, supports bank)

-endwl (end wall - supports bank)

-bridge (Bridge)

-chute (Outlet of catch basin connects directly to conduit

below)

Top-el elevation at top of pipe for input

-ngvd 1927 elevation in feet at the top of the (check!)

Inv-el elevation at bottom of pipe for output

-ngvd 1927 elevation in feet at the top of the (check!)

SZ(size) pipe diameter in inches

def: number, 6, 2

values

-8

-10

-12

-15

-18

-24

-30

-36

-42

-48

-54

Mate pipe material

(material) def:

values

-cmp (corrugated metal pipe)

-rcp (Reinforced Concrete Pipe)

-tcp (Terracotta Clay pipe

-pvc (polyvinyl chloride)

-stl (Steel)

-plas (Plastic)

-brick (Brick Box Culvert)

-conc (Concrete Box Culvert)

-Rock Rock-lined box culvert

-unkwn

DDM data development method

values

-0 (none noted)

-1 (converted from CAD dwg or dxf file to shapefile)

-2 (screen digitized using collateral data)

-3 (gps data capture)

-4

Notes indicates any weirdness or things we need to know about.

def: String, 128

values

-textual description of characteristics