13

Implementing the ArcGIS Hydro Data Model

The ArcGIS Hydro Data Model provides a set of Objects and Features that you can be used as a starting point for your project. The ArcGIS Hydro model can be implemented with no modifications or it can be highly customized to fit your specific needs. In this chapter: Typical Hydro Projects Case Study for a Typical Project ArcGIS Project Design Guidelines Project Implementation Process CASE Tools and UML

Implementing the ArcGIS Hydro Data Model 1

Implementing the ArcGIS Hydro Data Model There are several different scales at which the ArcGIS Hydro data model can be implemented. These include: 1. National Hydro Dataset Development: An organization wants to publish a dataset in Arc Hydro format for a large geographic area or national coverage (e.g., National Hydrography Dataset (NHD) or National Elevation Dataset-Hydrography (NED-H) in USGS-EPA). Aerial Mapping companies may also be interested in publishing data in Arc Hydro format. Internal and external users would obtain data in this common format. Many of the issues of data consistency, quality and preprocessing can be handled at the source, simplifying project implementation. This type of application usually involves only a few feature classes of the data model but the geographic extent is large. 2. Regional Hydro Dataset for a Water Management Agency: A State or regional water management organization (e.g. a river authority or a city) wants to assemble a comprehensive water resources management database for its region of jurisdiction. The database will be used by various groups within this organization that perform hydrologic studies They may have a standard set of of Basins and Catchments, but the Watersheds used may vary from one group to another within the organization depending on their interests. This application involves most or all of the feature classes in the ArcGIS Hydrodata model but the geographic extent is smaller than in Case (1). 3. Local Engineering Applications/Projects: An organization or individual wants to take an existing Arc Hydro database and add more information to it. These may include time series, drainage areas, or stream channel definitions for particular water resources studies. In this way, engineering consultants can add value to a core dataset by providing additional detail. A city or regional water management agency can build and maintain a core geodatabase and consultants add detail when doing studies in particular areas. This application involves just a few feature classes and objects in the data model, and the geographic extent is smaller than in Case (2). At each level, groups provide additional detail using the common data structure, from National to Regional to Local content. The Arc Hydro data model provides the opportunity to build a valueadded chain of datasets from all three sources.
Creating Arc Hydro Datasets

In most cases the content of the ArcGIS Hydro data model will be sufficient for your implementation. You can create your geodatabase from a Microsoft Repository database if this is the case. This process will allow you to use the data model without the need for CASE Tools or modeling in UML, as described later in this chapter.

2 ArcGIS Hydro Data Model

Most people create their Arc Hydro database using the Schema Wizard

To implement your data model from the Microsoft Repository containing the ArcGIS Hydro data model, the following steps are required: 1. Install ArcInfo/ArcEditor Desktop, and any analysis extensions you plan to use. 2. Define your conceptual data model and modify the ArcGIS Hydro Analysis diagram to reflect your design (optional). 3. Create a personal geodatabase or enterprise geodatabase in ArcSDE. 4. Create feature datasets with the correct spatial references for your geographic area. The names of the four datasets are: Hydrography, Drainage, Network, and Channel. By default you will get an unkown spatial reference for your datasets and this cannot be changed once the schema is defined. 5. Use the ArcCatalog Schema Wizard to create a physical schema from the Arc Hydro repository database. 6. Use ArcCatalog to edit the database design to match your conceptual design/project needs. a) Delete the classes and attributes that are not needed for this particular application b) Add additional classes and attributes to the basic model. c) Add additional information (object and feature classes) that are not directly part of the model but is required for your project. Examples are background layers like county or land parcel boundaries. 7. Load your data into the geodatabase. 8. Deploy your geodatabase. In the case of an enterprise geodatabase this involves versioning the database and setting up security (if required). More detail on steps 3-8 can be found in the ESRI book Building a Geodatabase.
Implementing the ArcGIS Hydro Data Model 3

Deploy your Geodatabase

Once you've built your geodatabase, you will usually need to make it available to people in your organization who use the data. This is true in enterprise projects where multi-user editing is required, also in water resource management agencies where many project teams will use a common regional database. These people may work with a geodatabase in different ways. People on your project team may create and edit alternative versions of the database during the design process, analysts may model flows or trace connected parts of the network, and managers may want to view progress on specific project tasks. You can give people access to the information they need, with the tools they need, through ArcCatalog and ArcMap. Case Study: Implementing ArcGIS Hydro on a Typical Project The previous section introduced some general methods for implementing the ArcGIS Hydro Data Model. In this section we will examine in greater detail the process of implementing ArcGIS Hydro for a specific engineering/hydrological study. The steps involved for a typical project are: 1. Define the spatial extent of the study region. 2. Define and tailor your ArcGIS Hydro Database 3. Assemble the map Hydrography for the study region. 4. Build a Hydro Network. 5. Define Drainage Areas for the study region and attach them to Hydro Junctions. 6. Attach Time Series for key monitoring points. 7. Define Channel shape in regions of interest for detailed study. 8. Deploy the geodatabase and map documents. 9. Expand the geodatabase with additional data as it becomes available. These Steps will now be described in more detail.
Step 1: Define the Spatial Extent of the Study Region

For a detailed study the focus is on a specific geographic area. Understanding the extent and available data for your study is the first step in your project.
Step 2: Define and Tailor your ArcGIS Hydro Database

There are several steps in creating your data model.

Analysis

Complete an assessment of your needs. Look at the data you will need to complete your project, understand the map products you will produce and any required data elements for analysis.
Design

Define the components required to adequately model your system. Most people create an analysis diagram for their project as a way to explain the data they used in their project. On some projects

4 ArcGIS Hydro Data Model

this is not necessary, especially if you are using the ArcGIS Hydro model with very few modifications.
Construction

The physical database model defines the database schema, class structure of objects, and how rules and relationships are implemented. In most cases you will build the physical model using the Schema Creation Wizard and other tools in ArcCatalog. The schema wizard reads the structure of the database design from a Microsoft Repository file. Based on whether you are building a personal geodatabase or an enterprise database on ArcSDE, the schema wizard then creates and applies database creation statements appropriate to the specific database platform you are working with. While the process sounds complicated, it is actually quite simple to create a database using the schema wizard. You can then use ArcCatalog to add, remove, and modify the database to your project needs. In this type of project we assume that you would be using a personal geodatabase. For an enterprise database in ArcSDE the process is quite similar but there are additional things you need to understand while creating the database and loading data. Refer to http://ArcOnline.esri.com in the White Papers section for additional information on Building Multi-User Geographical Information Systems with ArcInfo 8.
Step 3: Assemble Hydrography for the Study Region

Obtain the basic feature data for your study area by digitizing features from existing maps or converting tabular data inventories into point feature classes. Load the data into your target geodatabase. These are the Hydrography feature classes for your project in the Arc Hydro model.
Step 4: Build a Hydro Network

Delete the geometric network in your target geodatabase. Load data from your Map Hydrography and other data sources into the target schema using the simple data loader in ArcCatalog. Recreate the geometric network in ArcCatalog. If you have only a small amount of data then you dont need to go through the process of deleting the network, just use the Object Loader in ArcMap instead.
Step 5: Define Drainage Areas for the Study Region and attach them to Hydro Junctions

The link between the landscape or watershed polygons and the Hydro Network is through HydroJunctions. HydroJunctions connect edges in the geometric network. Your drainage areas, typically watersheds, need to have the correct outlet junction associated with them. This is the way that we transfer flow from the landscape onto the network. You can do this manually or use a tool to populate the JunctionID for each Drainage Area.
Step 6: Attach Time Series for Key Monitoring Points

If you are using time series data, now is the time to associate the data with the correct monitoring points. MonitoringPoints are in the Hydrography package, TimeSeries records have an attribute FeatureID that can be associated with the MonitoringPoint HydroID value or a project-specific identifier. It is acceptable to add additional ID fields to hydro features and your time series objects as required.

Implementing the ArcGIS Hydro Data Model 5

Step 7: Define Channel shape in Regions of Interest for Detailed Study

If you need to create Channel shapes for your area of interest, create/load this data. This data typically consists of Profile and Cross Section representations. Often this data is passed on to hydraulic analysis programs for more specific analysis. Managing this data in ArcGIS is a good way to load and validate the data you are using in the context of the rest of your project database. It is also a good way to make sure the data from your project is available for other people to use in the future.
Step 8: Deploy the Database and Map Documents

In this stage you make the data in your geodatabase available for use. ArcCatalog and ArcMap are the two main applications you and others in your organization will use to work with your geodatabase. ArcCatalog lets you manage your database, publish layers with symbology throughout your organization, load data, and create versions of your geodatabase. You make the data in your geodatabase available by placing maps and layer files which reference the data in the database in shared folders for your system's various types of users. You can control access to data by creating password-protected connections to your database. ArcMap allows you to edit your data while maintaining network connectivity, trace through the network with a variety of tools, and create maps tailored to specific purposes.
Step 9: Expand the Geodatabase with Additional Data

Often projects will begin with Map Hydrography and gradually more data will become available through the lifetime of the project. Once you get used to working with ArcGIS, whether with the CASE Tools or without, you will realize that it is easy to add additional classes, attributes, and load data into your database. Often people are very concerned at the beginning of their project to get the database design just right, only to have their project scope and data requirements change over time due to changes in priorities or budgets. The key point in designing and building your project database is that it is easy to modify and enhance your schema over time. The software has been designed to support multiple iterations of design and deployment so that you can easily implement your project and adapt to future needs.
Creating Arc Hydro Datasets

In most cases the content of the ArcGIS Hydro data model will be sufficient for your implementation. You can create your geodatabase from a Microsoft Repository database if this is the case. This process will allow you to use the data model without the need for CASE Tools or modeling in UML. ArcGIS Project Design Guidelines ArcGIS Hydro is a geodatabase design that may be implemented as is or used as a framework for designing a custom geodatabase implementation. To determine how to best implement ArcGIS Hydro, you should be familiar with the requirements for your project or organization. This section provides basic guidelines and techniques for creating a geographic database design and implementing that design with ArcGIS Hydro.

6 ArcGIS Hydro Data Model

Implementation options Designing a geodatabase is an important process that requires planning and revision until you reach a design that meets your requirements. The actual process of creating and populating a geodatabase, however, is quite simple. The process usually involves several attempts at matching the available data and planned map products to your current design. The primary technique for doing this is to load existing shapefile and coverage data into a geodatabase and create or modify database items with ArcCatalog so that they are consistent with the Arc Hydro naming conventions. Design guidelines The following are general guidelines for the design process: 1) Understand the data requirements of your project a) Examine existing and planned map products. b) Look at existing data sets, identify additional data needs. c) Understand your functional requirements and the implications for your database and map design. 2) Define the conceptual content of your model a) Take a first pass at identifying the features in your data model. You could do this based on existing data sets or begin with the Hydro model. In either case you should compare the two to better understand your needs. The data model diagrams included in the ArcGIS Hydro Data Model CD can be marked up and used in your design process. b) Organize your classes into conceptual groups. The Hydro Model has 4 conceptual groups -Drainage, Map Hydrography, Hydro Network, and Channels. This step will define the overall scope of the model and help you to focus on the relevant data elements for your model. 3) Select geographic representation types. a) Represent discrete features with points, lines, and areas. Characterize continuous phenomena with rasters. Model surfaces with triangulated irregular networks (TINs) or rasters. b) Plan the map layers including symbology, scale dependency, source(s) of data. c) Plan map templates and map products. 4) Build the geodatabase structure. a) Organize the geodatabase into feature datasets. Consider thematic groupings, topological associations, and responsibility for data maintenance. 5) Define objects and relationships. a) Identify and describe the objects and their attributes in detail, and specify object relationships. Build the logical data model with the set of objects. Many relationships are implicit or geographic in nature and do not require explicit relationships in the geodatabase. Model only the necessary relationships. b) Define subtypes as required. c) Set up any coded value domains that are required in your model.

Implementing the ArcGIS Hydro Data Model 7

6) Configure layers, map templates and map documents using ArcMap. All of these steps are important to a successful project. The implementation process will now be described in more detail. Project Implementation Process The process of deploying ArcGIS Hydro unfolds in three stages, each of which has several steps.

Analysis
Existing Data Sets

Design

Implementation

Map Templates

New Data Requirements

Graphical Design

New Functional Requirements

Database Design

Layers, Connections, Databases, Tools

Existing and Planned Map Products

Stage I: Analysis

1. Evaluate your geographic area of interest and available data. 2. Compare the data you plan to use with the design of the ArcGIS Hydro data model. 3. Understand additional data requirements, functional requirements, and plan your map products.
Stage II: Design

1. Extend and customize the ArcGIS Hydro objects to fit your needs. 2. Document your design. Most people will create an analysis model based on the Hydro Data Model.
8 ArcGIS Hydro Data Model

3. Design your layers, symbology, scale dependencies, map output products, and map templates.
Stage III: Implementation

1. Use the ArcCatalog Schema Creation Wizard to create an empty geodatabase. 2. Use ArcCatalog to modify the schema for your needs. 2. Load data into the geodatabase. 3. Create connections to the database. 4. Use layers to symbolize features. 5. Use maps for specific tasks. 6. Use connections to control access. Each stage of deploying ArcGIS Hydro is discussed in greater detail in the next three sections. Stage I: Analysis In this stage you need to examine your data and organizational needs. Typically this will involve looking at available data sets and required map products. It may also involve understanding your application/project analysis requirements from the standpoint that this will impact the design of the database or your map products. It will be helpful to list the objects in your system and group them according to their properties and functions. Compare the objects in your system to the ArcGIS Hydro objects using this book and the object models that are distributed with Arc Hydro. Identify the areas where your system matches the ArcGIS Hydro model and where they do not match. This is the process of developing a conceptual model of your database. In UML terms we often refer to this as the Analysis Diagram, it is essentially a new kind of Entity Relationship diagram. Differences might include attributes of ArcGIS Hydro features that you do not store but that are present in the object model, attributes that you wish to store that are not included in the object model, subtypes of objects that do not occur in your system or that you do not want, objects that are not modeled in the ArcGIS Hydro system that you need to represent, and relationships or rules that you wish to model that are not included in the ArcGIS Hydro model. Stage II: Design Once you've identified how well the existing model fits your needs, you can customize it. The most simple way to document the database design is to modify the ArcGIS Hydro Analysis model. The best way to document the graphical design for your map products is to use ArcMap to define map layers using the empty database structure defined in Stage III. Stage III: Implementation In this stage you take your design and transform it into a real working system. The geodatabase model is a generic model for geographic information that supports a wide variety of object relationships and behavior. ArcGIS Hydro is a set of geodatabase objects for modeling surface water bodies, networks, catchment basins, channel profiles and cross-sections, monitoring equipment and other user-defined measurements, and time series data. You can use these objects out of the box or customize them.
Implementing the ArcGIS Hydro Data Model 9

Geodatabase Object class Feature class Network Feature class Edge Junction

Polygon Line Point

Feature Hydro Point Monitoring

Simple Edge Hydro Edge Flow Edge

Geodatabase data model

ArcGIS Hydro data model (subset)

The model you use could be a highly extended custom model that includes many new objects of your own design, or it could be a slightly pared down version of one of the models included with ArcGIS Hydro. In either case, the ArcCatalog Schema Creation Wizard can import the Hydro Design and create a geodatabase for you. Once you've created an empty geodatabase with a schema that matches your logical model, you will load data into it. Another approach is to use the schema wizard to apply a schema and create relationships in a geodatabase into which you've already imported data.

Creating a geodatabase and loading data

10 ArcGIS Hydro Data Model

Work flow and security

Geodatabases support versioning so you can create multiple versions in your database to manage work flow processes. You can create connections to different versions for different classes of users, and you can use user names and passwords with these connections to control access to the geodatabase.

Creating a password-protected connection to the HydroNet version of the HydroGeoDatabase for a database manager

For more information about versioning your database, see Building a Geodatabase. For more information on creating connections to folders and geodatabases, see Using ArcCatalog. You can also control access to the geodatabase through your file system-level security. Layers are lightweight files that provide a shortcut to data and also define how that data will be symbolized. By placing sets of layers tailored for specific groups of users in shared folders on your network, you can organize the data that is available for each group. Layers also allow you to display data with a consistent set of symbols across an organization. Everyone who adds a layer to their map will see the data symbolized in the same way. You can create your own layers and symbols in ArcMap. For more information on layers, see Using ArcMap. If you create a multiuser geodatabase in an ArcSDE-managed commercial relational database management system (RDBMS) like Oracle, Informix, IBM DB2, or SQL Server, there are more ways to share your geodatabase. You can make data available to users through custom applications developed using ArcObjects, or the ArcSDE C or Java Client APIs, or through your RDBMS's SQL interface. You can even serve your geodatabase to the Web using ArcIMS software.

Implementing the ArcGIS Hydro Data Model 11

Map Products and Tools for specific tasks

The main tool for viewing, editing, and analyzing data in an ArcGIS Hydro geodatabase is ArcMap. ArcMap is highly customizable, and it allows you to save your customization, as well as layers of data, to maps. You can easily add the specific tools and data needed for a particular task to a map; for example, a digitizer might use a map with a simple set of editing tools tailored for digitizing, an analyst might use a map with trace and flow-modeling tools, and an engineer might use a comprehensive set of CAD-like tools for design.

Maps and layers can be stored in different locations on your network, so you can use file system-level security to control access to your data.

You can create maps with specific layouts for different purposes. You can make very simple maps with just the necessary tools and data for specialized tasks, or you can make very elaborate maps with complex layouts. Sample maps of hydrographic data with sample symbology and layouts are included in the ArcGIS Hydro Data Model CD. For more information about creating map templates, map documents, and layers see Using ArcMap.

Map insets and data fusion: a map combining vector data with raster imagery, using transparency, measured grids, and inset data frames

12 ArcGIS Hydro Data Model

CASE Tools and the Unified Modeling Language (UML) Much of the hard work of analyzing and building a good Hydro geodatabase design has been done for you. But for some organizations there will be a need to go through the full analysis and design cycle to build enterprise level data management systems. Some of these project teams will want to use UML to define and manage their database design. Designing with CASE tools CASE (Computer Aided Software Engineering) tools and techniques automate the process of developing software and database designs. You can use CASE tools to create new custom objects and to generate a geodatabase schema from a UML diagram. The two main advantages of the CASE Tool environment are 1) the ability to create a schema quickly using automated tools, and 2) the tools provide a way to systematically capture the refinement of your design over time so you dont need to have dozens of design notes scattered all over your desk.
Strategies for using CASE tools for schema design and generation

Two general strategies exist for using UML and CASE tools to design and create your geodatabase. The first strategy involves using UML to define the schema for the geodatabase, generating that schema, then populating the schema with data. The second strategy takes a different approach. It involves creating the schema by importing existing data into your geodatabase, building geometric networks, then using CASE tools to apply your UML model to the existing data. You can use a combination of the two strategies. Once your schema has been created, you can modify it by modifying your UML model, then reapplying the model to your geodatabase schema using the Schema Creation Wizard. In general, the CASE tool environment will always add to the existing schema. For instance, if you delete a class in the UML, that class will not be deleted by the schema wizard. If you rename a column, the schema wizard will ask whether this is a new field or whether it maps to an existing field name in the geodatabase. You can work in ArcCatalog before and after running the Schema Wizard to ensure the changes you want to make are correctly applied in the database. Alternatively, you can just use the schema management tools in ArcCatalog to modify your geodatabase schema and ignore UML after the initial schema creation.
Example: modeling a ProfileLine

There are many different methods of modeling real-world objects. The following example shows the steps needed to model a common Channel Feature, a ProfileLine, and shows how it can be modeled in the ArcGIS Hydro data model. ProfileLine is a general class designed to model 3 common types of cartographic features along a river: 1) The center or Thalweg of the channel 2) Left and right Banklines where the water meets the shoreline

Implementing the ArcGIS Hydro Data Model 13

3) A Streamline that represents any other cartographic line

Modeling Thalweg and other Types of ProfileLine

In the Hydro model we have the option to implement these types of Profile Lines as a coded value domain or as a subtype. A coded value domain is a simple list of codes, like 1, 2, 3 and a descriptive label. In UML a domain for Ftype looks like:

A coded value domain for Profile Line

Another option for ProfileLine type would be to make geodatabase subtypes for each of the types. Subtypes provide additional abilities to specify different default values and domains for each subtype of the class. In the case of ProfileLine we might create subtypes if we have different sources for the attribute ProfOrigin, the origin of the profile data. We could associate a different list of values for Thalwegs, Banklines, and Streamlines. ArcGIS Hydro implementation Scenario Using CASE Tools In the previous sections we discussed the process of defining the ArcGIS Hydro data model and typical implementation approaches. The section describes how to implement the ArcGIS Hydro geodatabase using UML and the CASE Tool environment. You may use some or all of the described methods, depending on your requirements. The ESRI books Modeling our World and Building a Geodatabase provide directions for designing and implementing custom geodatabases. Implementing a system using the ArcGIS Hydro geodatabase UML is a quick and easy method of implementation. This approach provides the most control over the database content. CASE Tools are valuable when multiple projects require a similar database design, they are also useful for large projects that involve data management in an enterprise environment. This approach requires additional software, Visio Enterprise, to manage the .vsd files included with this data model.

14 ArcGIS Hydro Data Model

Data Model Design and Refinement Using CASE Tools Establish a data model

To begin, install the ArcInfo or ArcEditor Desktop and the sample geodatabase design for the ArcGIS Hydro Data Model from the CD. You also need to install Visio Enterprise. After you have completed your conceptual design, you can modify the UML to reflect your logical design. From Visio, you can export a Microsoft Repository database. Using ArcCatalog, you can import the schema from MS Repository into your geodatabase. The ArcGIS Hydro data model UML is a diagram that captures a design for a geodatabase. The design itself can be stored in a DBMS (either Access or SQL Server) as a Microsoft Repository, which can then be read by ArcCatalog to create a schema for your geodatabase. The repository contains a generalized representation of all the objects (tables or feature classes) showing their inheritance relationships as well as subtypes, domains, default values, relationships, and connectivity rules. ArcCatalog contains tools to read the Microsoft Repository. The Schema Creation Wizard guides you through the process of creating new feature classes, tables, and other components of your geodatabase. The geodatabase schema can be read directly from the repository. Once the wizard is finished, you will have schema that you can modify in ArcCatalog to suit your needs.
Refine the geodatabase using ArcCatalog

You can use ArcCatalog to continue defining your geodatabase by establishing how objects in the database relate to one another. This is the simplest and most direct method of implementing ArcGIS Hydro. Using ArcCatalog you can establish relationships between objects in different object classes, add attributes, and associate them with domains. You can continue to use the geodatabase management

Implementing the ArcGIS Hydro Data Model 15

tools in ArcCatalog to refine or extend a mature database throughout its life. You may want to use a combination of ArcCatalog and UML to maintain your database design.
Implementation Steps

To implement your data model from Arc Hydro using UML, the following steps are required: 1. Install ArcInfo Desktop, and any analysis extensions you plan to use. 2. Create your logical data model in UML. 3. Create a geodatabase and feature dataset(s) with the correct spatial reference(s). 3. Generate the physical database model from the logical UML model. 4. Use ArcCatalog and/or UML to edit the schema. If you modify the UML you will need to reapply the schema to the existing database. 5. Load your data into the geodatabase. For larger data sets, drop the relationships and networks, use the simple data loader in ArcCatalog, rebuild the network, and then reapply the schema. 6. Deploy the geodatabase. For more specific information on performing these steps, please refer to the ESRI books Using ArcCatalog and Building a Geodatabase.

16 ArcGIS Hydro Data Model