This action might not be possible to undo. Are you sure you want to continue?
Deploying ArcGIS Hydro Data Model
The ArcGIS Hydro Data Model provides a set of core components that you can use to implement your data model. The ArcGIS Hydro model can be deployed with no modifications or can be highly customized to fit your system's specific requirements. Topics discussed in this chapter: • • • • • • The process of deploying ArcGIS Hydro Data Model Implementation resources Geodatabase basics Defining your geodatabase requirements Selecting an implementation process ArcGIS Hydro deployment scenarios
The process of deploying ArcGIS Hydro Data Model This chapter provides a conceptual overview of the process of deploying the ArcGIS Hydro Data Model, beginning with an outline of the process, then discussing each of the stages in more detail. The chapter ends with three scenarios for implementing custom geodatabases with ArcGIS Hydro. At several points in this chapter you will be referred to the books Modeling Our World, Using ArcCatalog, and Building a Geodatabase for more information. You may find it useful to have these books at hand for reference. The core of ArcGIS Hydro is a set of objects that you use to create sophisticated models of your surface water system. With these objects you create a geodatabase that stores geographic features and tables as objects with behaviors and relationships. You use the ArcInfo desktop applications, ArcMap™ and ArcCatalog, to view, edit, and manage your geodatabase. You use the map templates, layers, and styles included with ArcGIS Hydro Data Model to symbolize features and create maps of your surface water features for a variety of purposes. You can use all of the powerful functions in ArcInfo to build your own maps, layers, and styles, as well. Deploying ArcGIS Hydro Data Model The process of deploying ArcGIS Hydro unfolds in three stages, each of which has several steps. In the first two stages, you design and implement an ArcGIS Hydro geodatabase. In the third stage you make the geodatabase available for use.
Deploying ArcGIS Hydro Data Model • 1
you can customize it. attributes that you wish to store that are not included in the object model. Differences might include attributes of ArcGIS Hydro features that you do not store but that are present in the object model. In this case. 2 • ArcGIS Hydro Data Model . 2. 3. you can use one of the sample repositories that come with ArcGIS Hydro to create an empty geodatabase. Evaluate your surface water system. Once you've identified how well and where the existing model fits your needs. Planning and design In this stage you need to rigorously examine your existing system and the processes that it must support for your organization. Create connections to the database. Stage II: Creating a geodatabase 1. 4. Export the UML model of the system to a repository. objects that are not modeled in the ArcGIS Hydro system that you need to represent. Use maps for specific tasks. Each of the stages of deploying ArcGIS Hydro are discussed in greater detail in the next three sections. Use layers to symbolize features. Create a logical model using ArcGIS Hydro objects to represent your system. subtypes of objects that do not occur in your system or that you do not want to differentiate. 4. You can use a UML modeling tool like Visio Enterprise to extend the model where necessary.Stage I: Planning and design 1. 2. Load data into the geodatabase. 3. You can also skip the UML modeling step (and the first step of Stage II) if the ArcGIS Hydro model conforms well to the model of your system. and relationships or rules that you wish to model that are not included in the ArcGIS Hydro model. Use connections to control access. Extend and customize the ArcGIS Hydro objects to fit your needs. 3. It will be helpful to list the components of your system and group them according to their properties and functions. If you choose to customize in UML. Use CASE tools in ArcCatalog to create an empty geodatabase. Stage III: Sharing your geodatabase 1. 2. Identify the areas where your system matches the ArcGIS Hydro model and where they do not match. you will create a logical model of your surface water system using the existing objects and your customized objects. Compare your system to the ArcGIS Hydro data model. Compare the objects in your system to the ArcGIS Hydro objects using this book and the object models that are distributed with ArcGIS Hydro.
The geodatabase model is a generic model for geographic information that supports a wide variety of object relationships and behavior. monitoring equipment and other user-defined measurements. extending the ArcGIS Hydro data model The model you use could be a highly extended custom model that includes many new objects of your own design. and time series data. or it could be a slightly pared down version of one of the models included with ArcGIS Hydro.You will find more specific information about the planning and design stage in the `Geodatabase design. to loading data. Geodatabase Object class Feature class Polygon Line Point Network Feature class Edge Junction Simple Edge Hydro Edge Flow Edge Feature Hydro Point Monitoring Geodatabase data model ArcGIS Hydro data model (subset) MyFlowEdge Attributes of MyFlowEdge Custom Behavior of MyFlowEdge Domain of Values for MyFlowEdge Connectivity Rules for MyFlowEdge Custom feature designed in UML. Creating a geodatabase In this stage you take a logical model of a geodatabase and transform it into a real working geodatabase. you will export the UML to a Microsoft Repository so the ArcCatalog Schema Creation Wizard can interpret your design into a geodatabase. catchment basins. and guidelines' and `ArcGIS Hydro implementation scenarios' sections of this chapter. to creating a catalog and symbolizing data with layers. Deploying ArcGIS Hydro Data Model • 3 . tools. In Chapter 11 you will find a tutorial that covers the entire process of customizing ArcGIS Hydro from modifying a UML diagram. networks. In either case. You can use these objects out of the box or customize them to more closely model your facility. channel profiles and cross-sections. ArcGIS Hydro is a set of geodatabase objects with behaviors and relationships appropriate for modeling surface water bodies.
or you can create a custom geodatabase by selectively choosing which objects in the repository are created in your geodatabase. You make the data in your geodatabase available by placing 4 • ArcGIS Hydro Data Model .You can use one of the sample repositories to make a geodatabase that matches the ArcGIS Hydro model exactly. Once you've created an empty geodatabase with a schema that matches your logical model. you will load data into it. ArcCatalog lets you manage your database. The steps for creating a schema from a repository are covered in Chapter 11. ArcCatalog and ArcMap are the two main applications you and others in your organization will use to work with your geodatabase. load data. and create versions of your geodatabase. Scenarios 2 and 3 in the `ArcGIS Hydro implementation scenarios' section of this chapter discuss scenarios where you create a geodatabase schema from a repository. You can also use the CASE tool to apply a schema and create relationships in a geodatabase into which you've imported data. publish layers with standardized symbology throughout your organization. Create UML Generate schema with wizard MS Repository Import data Apply UML to existing data Shapefiles Geodatabase Coverages Creating a geodatabase from a UML model Sharing a geodatabase In this stage you make the data in your geodatabase available for use.
and toolbars that you can use to interact with and share the data in your geodatabase. maps. analysis. Another technique is to use Unified Modeling Language (UML) and Computer-Aided Software Engineering (CASE) tools to design and create a custom geodatabase schema. Once you have a design. create the geodatabase from the schema. One technique is to load existing shapefile and coverage data into one of the sample geodatabases and create or modify database items with ArcCatalog. styles. the geodatabase that you create can be refined later. there are more ways to share your geodatabase. you should be familiar with the database design requirements for your organization. or the ArcSDE C or Java™ Client APIs. or SQL Server™. To determine how to best implement ArcGIS Hydro. IBM® DB2®. trace through the network with a variety of tools. layers. You can control access to data by creating password-protected connections to your database. You can make data available to users through custom applications developed using ArcObjects™. and then load your data. If you create a multiuser geodatabase in an ArcSDE™-managed commercial relational database management system (RDBMS) like Oracle®. Informix®.maps and layer files—which reference the data in the database—in shared folders for your system's various types of users. Build catalogs to organize your data. and layers. ArcMap allows you to edit your data while maintaining network connectivity. Regardless of the method you choose. Place maps or layers for specific tasks in shared folders on your network. and create maps tailored to specific jobs. and guidelines ArcGIS Hydro includes surface-water-specific geodatabases that may be implemented as is or used as a framework for designing a custom geodatabase implementation. See chapters 8-11 for various examples of hydrological network definition. You can even serve your geodatabase to the Web using ArcIMS™ software. and other tasks. using ArcCatalog or UML and CASE tools. This section provides basic guidelines and techniques for creating a geographic database design and implementing that design with ArcGIS Hydro. Deploying ArcGIS Hydro Data Model • 5 . there are two main ways you can create the geodatabase. tools. Implementation options Designing a geodatabase is a critical process that requires planning and revision until you reach a design that meets your requirements. or through your RDBMS's SQL interface. Geodatabase design. The ArcGIS Hydro CD includes samples of the maps.
These chapters and the data model diagrams included in the ArcGIS Hydro Data Model CD can be marked up and used in your design process. The ArcGIS Hydro object model presented in Chapters 1-7 provides a working model for this exercise. The last two steps develop the logical model. Model surfaces with triangulated irregular networks (TINs) or rasters. specifying object relationships. The steps for creating custom objects are: 6 • ArcGIS Hydro Data Model . 5. Specify relationships between features. Identify the organizational functions of the data and determine the data needed to support these functions. 2. 4. lines. The first three steps develop the conceptual model. and other elements—allows you to design geographic databases that are close to their logical data models. Identify and describe the objects. Select geographic representation types. Represent discrete features with points. You can use these models to create a COM object that implements the behavior of the custom object as well as the database schema where these custom objects are created and managed. The following are general guidelines for the design process: 1. You can use CASE tools to create new custom objects and to generate a geodatabase schema from a UML diagram. classifying features based on an understanding of data required to support the organization's functions and deciding their spatial representation. Plan the geodatabase structure. Define objects and relationships. knowing how they are related to one another. Characterize continuous phenomena with rasters. and departmental responsibility for data. Consider thematic groupings. topological groupings. Implement attribute types for objects. Build the logical data model with the set of objects. Designing with CASE tools CASE tools and techniques automate the process of developing software and database designs. Organize the geodatabase into feature classes and feature datasets. and areas. matching the conceptual models to ArcInfo geographic datasets. Object-oriented design tools can be used to create object models that represent your custom objects. topological associations. Match the logical model to geodatabase elements. Organize the data into logical groupings. Match the objects in the logical data model to objects in a geodatabase. Model the user's view of the data. Determine the geometry types of discrete features. relationships. 3. feature classes.Design guidelines The structure of the geodatabase—feature datasets.
This could include a physical description and an explanation of its mechanics. and drainage area. Deploying ArcGIS Hydro Data Model • 7 . then using CASE tools to apply your UML model to the existing data. Once your schema has been created. First. 3. Next describe the processes that a dam participates in. You can use a combination of the two strategies if your UML model describes a larger schema than defined when you imported your existing data. you can modify it by modifying your UML model. stored volume. For example: A dam is designed to alter the flow of water within a river network. Export the model to the Microsoft Repository. 4. then populating the schema with data. 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. dams may be used to create lakes or reservoirs for electric power generation. and shows how it can be modeled in the ArcGIS Hydro data model. It involves creating the schema by importing existing data into your geodatabase. provide any significant details related to the component. public water supplies. describe how a dam is used in your system. It is treated as a point-feature in a water network.1. For example: For purposes of hydrological calculations. Example: modeling a dam There are many different methods of modeling real-world objects. 2. generating that schema. and irrigation. recreation. Alternatively. The height of the dam and of the impounded water are needed for calculations of water volume. see Modeling Our World and the ArcInfo Developer's Guide. you need to define the dam entity in your system. then reapplying the model to your geodatabase schema using the Schema Creation Wizard. Design the object model using UML. Once a dam is defined. building geometric networks. you can use the schema management tools in ArcCatalog to modify your geodatabase schema. list the information required to support the defined processes (not all of these will necessarily be needed for every operation). Create a geodatabase schema for the custom object. a dam. from “full open” to fully closed. From the previous descriptions. Typically. The second strategy takes the opposite approach. For details on Steps 1 to 3. The following example shows the steps needed to model a common system component. surface area. Generate stubcode and implement behavior using C++ or Delphi (Visual Basic cannot be used to implement custom feature behavior). They may throttle the water at varying levels. Other aspects of a dam include its width. The first strategy involves using UML to define all of the schema for the geodatabase. a dam may be open or closed. For example: Dams are intended to control the flow of water from the upstream lake that is formed.
and dam purposes Dam length. Design and implement a highly customized geodatabase using UML based on the ArcInfo and ArcGIS Hydro logical data models. height of water. Two considerations that will influence your decision are whether you will store custom objects in the geodatabase and whether you intend to create a geodatabase from scratch. Use the ArcGIS Hydro geodatabase with minor customization in ArcCatalog. There are many implementation options. dam type. You may use some or all of the described methods. normal stored volume By comparing the above descriptions and usage to the ArcGIS Hydro component reference. 3. max stored water volume. depending on your requirements. river) National Inventory of Dams (NID) id code Owner type. There are three general scenarios for implementing ArcGIS Hydro: 1. HydroPoint Structure Monitoring Dam Bridge FlowGage WaterQuality Modeling Dam as a subtype of Structure class ArcGIS Hydro implementation scenarios In the previous sections we discussed the process of deploying the ArcGIS Hydro data model and some implementation options. height. we can see that a dam can be modeled as a Structure in the ArcGIS Hydro data model. you will probably choose scenario 2 or 3. 2. but can differ in symbology. and in value domains for their attributes. As there are other structures in the overall system that can also be represented as a Structure class—such as bridges— we will model the dam as a subtype of Structure. county.• • • • Location of the dam (longitude. In terms of ArcInfo usage. The process you choose is dependent on your database design and level of customization. spillway width. latitude. If either of these is the case. 8 • ArcGIS Hydro Data Model . Implement a new geodatabase containing a subset of the components generated by the ArcGIS Hydro UML. The books Modeling our World and Building a Geodatabase provide directions for designing and implementing custom geodatabases. this means Dams and Bridges will have the same attributes.
6. In this case. geometric networks.The first step is always to design the geodatabase. determine the data model requirements for your system. the following steps are required: 1. 3. If analysis of your logical data model shows that the ArcGIS Hydro data model fits your needs as-is or may only require minimal customization. ArcCatalog provides a complete set of tools for designing and managing items you will store in the geodatabase. The book Modeling Our World is the guide to help you design your geodatabase. as with all implementation processes. add attributes. You can then load the existing data and create new data with editing tools in ArcMap. Once this design is complete. Scenario 1: Implementing ArcGIS Hydro from a geodatabase Implementing a system using the ArcGIS Hydro geodatabase is a quick and easy method of implementation when little or no modification of the ArcGIS Hydro data model is required. 5. but often you will want to further refine what is generated by CASE to meet your geodatabase design. Deploying ArcGIS Hydro Data Model • 9 . Then. and other items inside the database. and associate them with domains. and any analysis extensions you plan to use. 2. What to do To implement your data model from the ArcGIS Hydro geodatabase. This is the simplest and most direct method of implementing ArcGIS Hydro. you can proceed down the path that best suits your situation. 4. Load your data into the geodatabase. 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. Use ArcCatalog to edit the schema. Create the logical data model. you can load your existing data directly into the ArcGIS Hydro geodatabase. Establish a data model To begin. You can continue to use the geodatabase management tools in ArcCatalog to refine or extend a mature database throughout its life. Install ArcInfo Desktop. If the geodatabase schema and the components of the ArcGIS Hydro model fit your design. tables. Using ArcCatalog you can establish relationships between objects in different object classes. Deploy the geodatabase. install ArcInfo Desktop and the sample geodatabase for the ArcGIS Hydro Data Model from the CD. you can use the tools provided in ArcCatalog to create the schema for feature datasets. In some cases the data you have to load only accounts for part of your design. then this process is suggested. Build the physical database model based on the sample geodatabase for the ArcGIS Hydro Data Model. These relationships and domains may be part of the schema that CASE tools generate.
when required. 6. the following steps are required: 1. and any analysis extensions you plan to use. attribute domains. Create the logical data model. Build the physical database model. While in the CASE tool. ArcCatalog contains tools to read the Microsoft Repository. Once exported to the Microsoft Repository.Scenario 2: Implementing ArcGIS Hydro data model from a repository In many cases. and other pieces of your geodatabase. 10 • ArcGIS Hydro Data Model . you will have schema for your design ready to be loaded with data. The repository contains a hierarchical list of all the objects (tables or feature classes) showing their inheritance relationships as well as subtypes. Use ArcCatalog CASE tools to create schema and code referencing an existing repository. Load your data into the geodatabase. 5. select only the model components you wish to generate. their subtypes. and connectivity rules for objects participating in geometric networks. and connectivity rules. The Schema Creation Wizard guides you through the process of creating new feature classes. which can then be read by ArcCatalog to create a schema for your geodatabase. relationships. Just as when implementing from the ArcGIS Hydro geodatabase. 3. CASE tools allow you to create custom objects and features that extend the geodatabase model of ArcInfo 8. a subset of components of the ArcGIS Hydro data model will be sufficient for your implementation. domains. you can use ArcCatalog to establish new relationships between object classes. You can use UML to design your feature classes and tables including what attribute fields they have. You can create your geodatabase from the repository if this is the case. To implement your data model from the Microsoft Repository containing the ArcGIS Hydro data model. Once the wizard is finished. connectivity rules. 4. Use ArcCatalog to edit the schema. relationship classes. You can also use UML to design the schema for ESRI simple and ESRI network objects. 7. new attributes and domains. the CASE tools subsystem will help you create a COM object that implements the behavior of your custom object and the database schema where these objects are stored. and so on. tables. Deploy your geodatabase. The whole geodatabase schema can be read directly from the repository. However. Scenario 3: Adding custom objects to ArcGIS Hydro with UML As described in the second scenario. default values. The ArcGIS Hydro data model UML is a diagram that shows a design plan for a geodatabase. the objects that you describe using UML don't necessarily have to exhibit custom behavior. Install ArcInfo Desktop. 2. Object-oriented design tools that support the UML and the Microsoft Repository can be used to create designs for your objects. The design itself can be stored in a DBMS (either Access or SQL Server) as a Microsoft Repository. or you can select just the components that fit your database design.
When you are ready to begin creating your UML model. Generating code The CASE tools subsystem of ArcInfo 8 has two parts: the Code Generation Wizard and the Schema Creation Wizard. Build the physical database model. You can also start from the Visio Enterprise Drawing templates from the model directory of the ArcGIS Hydro Data Model CD. the following steps are required: 1. Create the logical data model. Install ArcInfo Desktop. Load your data into the schema. 4. 3. in the \\ArcInfo\casetools\Uml Models folder where ArcInfo is installed. 6. see Modeling Our World and the ArcInfo Developer's Guide. Deploying ArcGIS Hydro Data Model • 11 . You can also use the CASE tools to apply your UML design to existing feature classes and tables. The ArcGIS Hydro UML diagrams contain the UML model implemented in ArcGIS Hydro.vst or ArcInfo UML Model Pro.The CASE tool subsystem of ArcInfo 8 lets you extend the ArcInfo geodatabase model to create custom objects. 8. You can use C++ to override and add behaviors to the behaviors inherited from the ESRI objects. ArcInfo UML Model Ent. You can use the same UML diagram to generate the schema for the object using the CASE tools subsystem. 7. The tools to export your UML model to the repository are contained in Visio. The ArcInfo UML Model diagrams contain the object model required for using UML to model a generic geodatabase. you can start with one of the ArcInfo UML model diagrams. The Code Generation Wizard allows you to create custom COM objects for each component of your geodatabase. For more information on the ESRI object model and generating code for your custom objects using the Code Generation Wizard. it must be stored inside the geodatabase. Generate the schema and code. Export the UML diagram to a repository.vst. These custom objects inherit behavior from existing ESRI data objects. Once you have implemented your custom object. and any analysis extensions you plan to use. To implement an advanced implementation of your data model using UML. 5. Deploy database. Create a UML drawing of the ArcGIS Hydro model. 2.
with the CASE tools in ArcCatalog Sharing your geodatabase Once you've built your geodatabase. 12 • ArcGIS Hydro Data Model . You can create connections to different versions for different classes of users. analysts may model flows or trace connected parts of the network. with the tools they need. Engineers may create and edit alternative versions of the database during the design process. and managers may quality check changes. as well as your geodatabase schema. You can give people access to the information they need.3rd Pary CASE Tool Microsoft Repository UML Object Model ArcInfo CASE Tools Subsystem COM Code Generator Geodatabase Schema Generator Custom Object Geodatabase Schema You can generate custom object code. and you can use user names and passwords with these connections to control access to the geodatabase. through ArcCatalog and ArcMap. Work flow and security Multiuser geodatabases support versioning so you can create multiple versions in your database to allow multistage work flow processes or provide read-only access to some users. you will need to make it available to people in your organization who use the data. These people may work with a geodatabase in different ways.
an analyst might use a map with trace and flow-modeling tools. For more information on layers. Layers also allow you to display data with a consistent set of symbols across an organization. Layers are lightweight files that provide a shortcut to data and also define how that data will be symbolized. see Building a Geodatabase. Tools for specific tasks The main tool for viewing. editing. Deploying ArcGIS Hydro Data Model • 13 . you can organize the data that is available for each group. You can also control access to the geodatabase through your file system-level security.Creating a password-protected connection to the HydroNet version of the HydroGeoDatabase for a database manager For more information about versioning your database. 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. as well as layers of data. You can easily add the specific tools and data needed for a particular task to a map. ArcMap is highly customizable. a digitizer might use a map with a simple set of editing tools tailored for digitizing. to maps. see Using ArcCatalog. By placing sets of layers tailored for specific groups of users in shared folders on your network. and an engineer might use a comprehensive set of CAD-like tools for design. for example. and analyzing data in an ArcGIS Hydro geodatabase is ArcMap. and it allows you to save your customization. see Using ArcMap. For more information on creating connections to folders and geodatabases.
so you can use file system-level security to control access to your data. pumping stations. You can make very simple maps with just the necessary tools and data for specialized tasks.Maps and layers can be stored in different locations on your network. Sample maps of hydrographic data with sample symbology and layouts are included in the ArcGIS Hydro Data Model CD. You can create maps with specific layouts for different purposes. Map insets and data fusion: Here is a presentation map combining vector data with raster imagery. she can add the Catchment layer to the map she is making. For more information about creating maps see Using ArcMap. and inset data frames 14 • ArcGIS Hydro Data Model . If Sue in Engineering has access to the folder F:\Layers. using transparency. or other equipment included at a particular site. measured grids. Maintenance maps could show a section of the network. with detailed insets showing the gages. or you can make very elaborate maps with complex layouts for presentations.
Use the ArcGIS Hydro model as a guide for determining the objects. Data assessment Complete an assessment of your utility system modeling needs. In this section we will examine in greater detail the process of implementing ArcGIS Hydro from a Microsoft Repository. Construct data model Build a logical data model based on your findings.Case Study: Implementing ArcGIS Hydro In the previous sections we discussed database design and some general methods for implementing ArcGIS Hydro Data Model. Step 2: Create a logical data model. etc. This case study reviews the implementation from installation to deployment and directs you to references and task descriptions for each step in the process. then define the data components required to adequately model your system to support the process of your organization. and classes for your design. attributes. Step 1: Install ArcInfo and any desired extensions such as Spatial Analyst. Use this book and the Visio diagrams in the Model folder of the ArcGIS Hydro CD. to see the relationships between objects in the system and to get detailed information about specific objects. 3D Analyst. The program provides you with installation instructions and prompts you for required information. Geostatistical Analyst. You may wish to copy the Visio Enterprise UML models from the ArcGIS Hydro Data Model CD to convenient locations on your hard disk. document how your data is currently represented. The first seven chapters of this book provide a good example of how to organize a logical data model for surface water analysis and how to document the functions and the attributes associated with hydrological features. Constructing a logical data model is an iteractive process and an art that is acquired through experience. There are several steps in creating a logical data model. Define model components Define the components required to adequately model the real-world objects of your system. but an indication that you are coming close is when you can answer "yes" to the following questions: • Does the logical data model represent all data without duplication? Deploying ArcGIS Hydro Data Model • 15 . While there is no single correct model. This scenario was selected because it contains tasks common to most methods of implementation. It is difficult to determine when your data requirements are correctly modeled and complete. To do this. there are good models and bad models.
feature. You do not have the option of selecting a relationship class as you do with tables and feature classes. you will be presented with a hierarchical list of all of the row. you can selectively implement parts of the model by turning objects on or off. see Modeling Our World. Once the wizard is finished. Step 5: Generate a custom geodatabase. In most cases. The physical database model is built from the logical data model and is generally constructed by a relational database specialist. and domains are applicable for your data model. tables. relationships. and how rules and relationships are implemented. The results of your comparison will show which of the ArcGIS Hydro model classes. Step 3: Build a physical database model. the logical data model is directly implemented into the geodatabase—greatly simplifying the traditional task of physical database modeling . Define which rules and behaviors must be created through customization of the geodatabase or through custom applications built using the geodatabase framework. Use the ArcCatalog Schema Creation Wizard to create the geodatabase schema and code from an existing repository. This is the case because the presence of a relationship class is dependent upon the existence 16 • ArcGIS Hydro Data Model .• • Does the logical data model support your organization's business rules? Does the logical data model accommodate different views of data for distinct groups of users? For more information about creating a logical data model. The physical database model defines the database schema. Many of the objects and features contain subtypes with attribute domains and default values. The wizard guides you through the process of creating new feature classes. you will have the schema for your design ready to be populated with data. As such. and other pieces of your geodatabase. The geodatabase is a physical implementation of data that allows a structure similar to the logical data model. subtypes. attributes. and network feature types in the repository. see Building a Geodatabase and Modeling Our World. Although all of the required information for the geodatabase schema can be read directly from the repository. class structure of objects. most physical database models are directly supported by the existing framework of the geodatabase. During the schema generation process. ArcCatalog uses CASE tools to read the Microsoft Repository database you created using the UML modeling software. Compare your logical data model and physical database model to the ArcGIS Hydro data model to determine your implementation requirements. Step 4: Determine customization requirements. For more information about customizing a geodatabase.
owner type. and a geometric network. dam type. `Quick-start tutorial'. so there’s no need to store them with the feature attributes used for most analyses. an edit session is required to insert new records into the table or feature class to ensure that the network connectivity and version information is managed correctly.cfm) for Dam features. A step-by-step tutorial for this process is available in the book Building a Geodatabase. Hyd_height. matching the NIDID. Assume you’ve taken a subset of attributes from the Corps of Engineers’ National Inventory of Dams (NID) database (available at http://crunch. Repeat the process. max stored volume. relationships. Dam and Dam_extra participate in a one-toone relationship. Use the Object Loader to load the shapefile into the Dam feature class. and Norm_stor fields from the shapefile with those in the feature class. and normal stored volume. validation rules. suppose you have maintained your Dam and Dam_extra data in a single shapefile that has all the above attributes. Max_stor. see Building a Geodatabase. and NIDID again as the primary key. In case of a versioned database. subtypes. dam length. loading the shapefile into the Deploying ArcGIS Hydro Data Model • 17 . Perhaps you don’t need these attributes very often. Step 6: Edit the hydro schema using ArcCatalog. Latitude.of the feature classes or tables that are related by it. You can use the Object Loader to take the data in that shapefile and split it between the Dam feature class and the Dam_extra table while maintaining the relationships between them. You can either create relationships in UML or through the ArcCatalog user interface after the geodatabase is created (Step 6 in this process). If the schema you are generating contains attribute domains. but you cannot modify them. `Editing your geodatabase'.tec. Chapter 2. Use ArcCatalog to modify the schema of your geodatabase and add behavior. and suppose you have created a feature class called Dam and a table called Dam_extra. and Modeling Our World.army. You have generated your schema using the CASE tool Schema Generation Wizard (see Step 5). see Building a Geodatabase. Using ArcCatalog you can add behavior to the geodatabase by creating object classes. purposes. Chapter 10. including NIDID as primary key. you can view the properties for these domains. Dam_height. The following is an example of how the Object Loader works. Step 7: Load your data into the schema. longitude. such as river name. Using ArcCatalog. water height. The CASE tool schema generator manages whether a relationship class is created based on feature classes and tables that you select.mil/nid/webpages/nid. dam height. owner name. Dam_length. This data loading operation is performed with the Object Loader Wizard in ArcMap. And suppose you wish to hold additional attributes in the Dam_extra table. latitude. For more information about generating a geodatabase from a repository. However. For more information on the Object Loader. Longitude. No programming is required when you use the data management tools in ArcCatalog.
the relationships will be maintained during the data loading process. that you will want to store in a geodatabase. Importing data It is likely that you already have data in various formats. and you can control access to the data through your file system-level security. so you can import any data into any geodatabase. Chapter 4. The key to effectively distributing your data across an organization is to build specialized catalogs of data for yourself or other users of your GIS. ArcGIS Hydro implementation resources 18 • ArcGIS Hydro Data Model . Purposes. while others may simply open predefined maps to complete their tasks. and so on. and dBASE® or other database tables. For more information on creating maps see Using ArcMap. River. maps. by making connections in ArcCatalog to databases or to network drives or folders where data. You can use tools in ArcCatalog to import data from these formats into your geodatabase. Map LIBRARIAN™. Dam_type. ArcCatalog contains tools for building geometric networks and for establishing subtypes. Own_type. and ArcSDE. When you import data into the geodatabase. though you can choose to drop or rename attributes. Since the objects in Dam are related to objects in Dam_extra by the embedded key NIDID. INFO™ tables.Dam_extra table (only the non-spatial attributes will be loaded). both the geometry and attributes are imported. To learn how to move your existing data into the geodatabase. or layers are stored. you can password-protect layers based on geodatabase connections. and several shapefiles with the same spatial extent can also be imported into the same feature dataset. Once you have imported your data into the geodatabase. All or some of the feature classes from a coverage can be imported into an integrated feature dataset. This contrasts with loading data. you can use ArcCatalog to further define your geodatabase. Importing data into a geodatabase does not depend on having a schema in the geodatabase. You may also have your data stored in other multiuser geographic information system data formats such as ArcStorm™. Some users of your geodatabase will work with the whole geodatabase directly in ArcCatalog and ArcMap. you make a connection to the geodatabase to provide access to a version. Own_name. attribute domains. You can share a personal geodatabase by placing it in a shared folder on your network. In case of an ArcSDE geodatabase. see the book Building a Geodatabase. which involves matching the attributes of the data to be loaded with the feature class or table schema you defined. You can also create layers referencing selected feature classes in a version when you don't want to provide access to all of the data in a version. If necessary. `Migrating existing data into a geodatabase'. Others may add selected layers from a public folder to maps. such as shapefiles. coverages. Step 8: Share your geodatabase. matching NIDID. For more information on creating layers and connections see Using ArcCatalog.
In this chapter you learned how to design an ArcGIS Hydro geodatabase that meets your database design criteria.S. Some of the differences between the objects used in these different implementations occur at the subtype level. others require different subclasses. Examples from various stages of the geodatabase implementation process are included to allow you to begin implementation and customization at a level appropriate to your needs. The previous chapters reviewed the ArcGIS Hydro geodatabase design and data model schema. Chapter 11 provided a tutorial for generating a geodatabase schema and network from a UML description of a data model. ArcGIS Hydro provides a domain-specific geodatabase as well as the components of its database design and implementation. Geological Survey (USGS) and the Environmental Protection Agency (EPA). and provided sample applications. Deploying ArcGIS Hydro Data Model • 19 . They also described how real-world objects are represented within the model.To assist with your implementation. The components include: • • • • • The ArcGIS Hydro database schema and logical data model presented in static analysis diagrams A component reference of objects represented in the logical data model describing the relation of entities to real-world objects An ArcGIS Hydro sample geodatabase modeled in UML A Microsoft Repository created from the ArcGIS Hydro UML The geodatabase of the ArcGIS Hydro model and components The ArcGIS Hydro model represents many core concepts that are refined in various ways by established data products such as the National Hydrographic Dataset (NHD) from the U.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.