Sewer S ystem G eodatabase

1. Sewer System Geodatabase Adding line and point features

2. Oleander Public Works Dept. • In this exercise we will design feature classes to store data for a sewer system • We are going to use domain, subtype, and topology in this database too • Sewer systems are made of pipes (linear features) to carry wastewater to treatment plants • The pipes are connected to make a network • Pipes have many attributes, e.g.: size, material, year installed • Print the design form from the DVD

3. Design • In this project, because the pipes will be put together in a network, we need to set up a feature dataset • Go to: C:\ESRIPress\GIST3\Data in your computer and download a clean copy of the GDB Design Forms to be used for this project • Open the Excel version of the design forms • Save (and/or print) them in a directory of your choice so that you can fill them in • Name it: GDB Design Forms_tutorial_1_2

4. Utility Data Database • Open the GDB (Geodatabase) worksheet • Name the database as: Utility Data • Create a new dataset: Wasterwater • Create a new feature class: Sewer Lines • Type: L; name: SewerLines, Alias: Sewer Lines • Now let’s define the fields for the SewerLines table (feature class)

5. Tables Worksheet • Name the feature class/table as Sewerlines • Define the following fields (attributes): • PipeSize: short integer (SI), Pipe Size, NN • Material: Text, Pipe Material, NN • YearBuilt Long Integer (LI), Year Built, Null • Description Text, Owner, NN

7. Data Integrity with Domain • Pipes come in different sizes (6”-12”) • We do not want sized to be entered wrongly • Pipes > 12” are interceptors • Owned by a regional utility (not by the Public Works) • Since the size increases by 2”, we need to create coded values • Go to the Domains worksheet

8. Domain … • In the Domain worksheet add the following • SewerPipeSize, Sewer Pipe Size, SI, coded values, and add the following in the gray area: 6 6” 8 8” 10 10” 12 12”

9. Add the domain to the Tables worksheetcall it: SewerPipSize with a (D) before it to represent domain

10. Data Integrity with Subtype • Make a new feature class/table in the geodatabase worksheet: • L, Interceptors, Interceptors • Add the table to the Tables worksheet: • The interceptor do not have regular size and material, we do not need a domain • Copy properties of the SewerLines for the Interceptors • However, we want to define the pipe material as a subtype • Since subtypes must always be integer, we change the field type for the Material as SI • See next slide

12. Subtype for pipe material • Now, define the subtype for the pipelines in the Subtypes worksheet • Do this for: P.V.C (Polyvinyl chloride) HDPE (High-density polyethylene) DI (ductile iron) • See next side for the entries!

13. P.V.C: Polyvinyl chlorideHDPE: High-density polyethyleneDI: Ductile Iron

14. Add Point features • Manholes are points along the sewer lines • Cleanouts are also access points at the end of the pipe line to cleanout clogs • These points coincide with the pipes, i.e., they lie on the pipe lines and are connected to the pipes • Because of this, they must reside with the pipelines in the same feature dataset

15. Attributes of the points • The manholes and cleanouts have several attributes • In the GDB worksheet, write a new point feature called SewerFixtures of type PNT and Sewer Fixture description • Now, go to the Tables worksheet and add the SewerFixtures as a new layer (class/table), and add its attributes • Add the SewerFixType for the subtype of the Fixture type • See next slide

17. Create the SewerFixType Subtype • Go to the Subtypes worksheet • Add the SewerFixType subtype; with code 1 for manhole and 2 for cleanout • Interceptors also have fixture • Add InterceptorFix to the GDB worksheet with type PNT and Interceptor Fixture description • Add InterceptorFix table to the Tables worksheet • See next slide

21. End of Design • Now the design is ready and we can build the database with ArcCatalog • Try to do Exercise 1-2 on page 28.