1 / 52

Course Information

Framework Data Content - Hydrography. Related Topics. NSDI Training Tracks: An initiative to define areas, topics, and materials for training within the NSDI. ISO 19100 Series:

scaudill
Télécharger la présentation

Course Information

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Framework Data Content - Hydrography Related Topics NSDI Training Tracks: An initiative to define areas, topics, and materials for training within the NSDI. ISO 19100 Series: Suite of standards developed for geographic data and datasets. The most notable is ISO 19135 which pertains to metadata. ANSI Standards: Similar work to ISO, but standards directly apply to data created within the United States. Course Information The National Spatial Data Infrastructure (NSDI) Framework is a collaborative initiative to develop geographic datasets that are compatible based upon spatial location and content. The Framework approach allows data collected for variety of reasons and agencies to work together seamlessly; which can ultimately reduce project costs and increase interagency cooperation. The Framework Data Content Base Standards Suite dictates the requirements for Framework data. This course covers the fundamentals of the Framework Data Theme: Hydrography as developed by the Framework Data Content Standard. It is designed for users who are both interested in an overview of the Framework Data Content Standard Hydrography theme as well as designers and developers implementing Framework data, and associated tools. Prerequisites • General Understanding of GIS, Geospatial Data and Metadata • Familiarity with the FGDC and NSDI • Basic knowledge of Geographic Data Standards (specifically ISO 19100 series) • Completion of Framework Data Content Base Standard Course

  2. Navigating Through the Course Explanation of Navigation Buttons

  3. Learning Objectives Understand what hydrography really is Comprehend basics of hydrography framework standard Understand how to implement the standard Course modules • Understanding Hydrography • Hydrography (Part 6) of the Framework Data Content Standard • Implementing the Hydrography Component • Course Review and Comprehensive Self-Test Estimated Time Estimated time for the entire course is 150 minutes.

  4. Module 1: Understanding Hydrography Time Requirement Topics • What is Hydrography • Types of Hydrography • Hydrography in Action • Module Exercise and Summary Estimated time for this module is 30 minutes Key Terms Hydrography Framework NSDI/FGDC First Topic What is Hydrography

  5. What is HydroGraphy Related scientific field Hydrology: The scientific study of the waters of the earth, especially with relation to the effects of precipitation and evaporation upon the occurrence and character of water in streams, lakes, and on or below the land surface. In terms of the hydrologic cycle, the scope of hydrology may be defined as that portion of the cycle from precipitation to re-evaporation or return to the water of the seas. Applied hydrology utilizes scientific findings to predict rates and amounts of runoff (river-forecasting), estimate required spillway and reservoir capacities, study soil-water-plant relationships in agriculture, estimate available water supply, and for other applications necessary to the management of water resources. The study of waters (including oceans, lakes, and rivers) embracing either: (a) their physical characteristics, from the standpoint of the oceanographer or limnologist; or (b) the elements affecting safe navigation, from the point of view of the mariner. Hydrographic data is a comprised of data that contains information about surface water features such as lakes, ponds, streams, rivers, springs and wells. This data is often collected in various forms, including: remote sensing, field work, and interpolation. This data, can be developed or converted to digital spatial datasets which can be used with Geographic Information Systems (GIS) for a variety of purposes. The National Hydrography Dataset (NHD) is one such dataset; examples from the NHD will be used throughout this course to help illustrate Hydrography and the Hydrography Framework Standard. next Topic Types of Hydrography

  6. Types of Hydrography What is the NHD? The National Hydrography Dataset (NHD) is a comprehensive set of digital spatial data that encodes information about naturally occurring and constructed bodies of water, paths through which water flows, and related entities. In general terms hydrography is defined as the study of water; thus it stands to reason that hydrography data is usually a water source. Clearly rivers and lakes fall within this category; but so do pipelines, canals, swamps, and reservoirs. In fact there are 53 different types of hydrographic data referenced by the NHD. Thus it is key to express hydrographic data in various formats: points, lines, and polygon vector data. Additionally the data needs to include the appropriate attribute information to give a user a true indication of what is data is being represented. Are the NHD and Framework the Same? Although this question seems simple enough, the answer is somewhat more difficult to answer. In reality the NHD is a nationwide dataset that represents hydrographic data based on a specific set of rules or data model. However this data model is not the same data model that is outlined in the Framework hydrology standard. Thus tools and crosswalks will need to be developed to convert data between the two different models. next Topic Hydrography in Action

  7. Hydrography in action Example In General terms the following diagram represents one way we can represent real hydrologic features and use them for analysis in GIS and other tools. The purpose of this Hydrology Framework Standard is to provide a process by which data is standardized and categorized to ensure a level of consistency and interoperability. next Topic Hydrography Exercise

  8. Hydrography Module 1 exercise EPA Surf your Watershed The EPA Surf Your Watershed website allows a user to locate, use, and share environmental information about your state and watershed. This website is an application that takes existing hydrography data (watershed boundaries created by the NHD) and uses them as a spatial reference for environmental issues which occur in the delimited area. Hydrography in action Hydrography data that meets Framework specifications is being applied and used in real world projects by many different agencies. As we have discussed the National Hydrography Dataset is one such example. Now that you have some basic hydrography knowledge let’s see some a hydrography data set in action. Step 1) Open an Internet Browser and proceed to: http://cfpub1.epa.gov/surf/locate/index.cfm Step 2) Find the Locate by geographic unitlink and type in your local zip code and click submit Step 3) Choose and click on HUC (watershed boundary code) of interest Step 4) Explore the resources available about the watershed as well as the other features that comprise the Surf Your Watershed website Step 5) Close all Internet windows and proceed with the course next Topic Module Summary

  9. Module Summary Understanding hydrography • Hydrography is the study of waters • Hydrography data, i.e. NHD, is a representation of “real-world” water features • Many different water features can be collected and mapped next Topic Module 2: Hydrography (Part 6) of the Framework Data Content Standard

  10. Module 2: Hydrography (Part 6) of the Framework Data Content Standard Time Requirement Topics Estimated time for this module is 20 minutes • What is the Hydrography Standard • Purpose for Standard • Goals of the Standard • Capacities of the Standard • Standard Related Contact Information • Module Exercise and Summary Key Terms Hydrography Framework Standard Framework Hydrographic Hydrologic

  11. Next Topic Purpose for the Standard What is the Hydrography standard • The Hydrography Framework Data Content Standard: • One of the seven themes defined as Framework data • Establishes a baseline for hydrographic data collection and creation • Builds on the Framework Data Content Base Standard. • Only when a dataset meets both the requirements set forth in a thematic standard part(s) and the Framework Base Standard can it be considered Framework data.

  12. Next Topic Goals of the Standard Purpose for the Standard Quick Facts Each standard part was developed and edited by thematic experts Certain themes have additional pieces to address sub components. For example Transportation has separate parts to address different elements (i.e. roads, airports, etc.) However the Hydrography standard incorporates all hydrographic features within one standard. The purpose of Geographic Information Framework Data Content Standard, Part 6: Hydrography is to establish the content requirements for the collection and interchange of hydrography features and to facilitate the maintenance and use of that information by all users of geographic information. The Hydrography part identifies and defines terminology, encoding schema, and the data components required for describing hydrographic features, along with the metadata needed for the hydrography data exchange. This part specifies the content and its organization necessary for the successful interchange of hydrography data. The scope of the Hydrography part is limited to the information regarding surface water features and hydrographic networks for the purpose of cartography and network analysis and is intended to be applicable at a variety of scales.

  13. Next Topic Capacities of the Standard Goals for the Hydrography Standard • The goal of the Hydrography part of the Framework Data Content Standard is to provide common definitions and syntax to enable collaborative development, use, and exchange of hydrography data. • It is the intent of the part to set a common baseline of information content for exchange within the hydrographic community that will enhance data sharing and applications development when used with standards-based Web services or file transfer. • It is anticipated that multiple representations of hydrographic features will exist within the broader community. Policies have been or will be established for describing, maintaining, and exchanging the various representations of features within specific application communities, such as the NHD. This part will accommodate the exchange of these multiple representations. • This part supports the mapping and conversion of native data in any format into a common representation for exchange over the Web or as files. Encoding of hydrography data for transfer, based on the models in this part, is described in the Framework Data Content Base Standard. • The audience of this part of the standard includes hydrography data users, maintainers, and distributors. Specific guidance on the implementation of this part for specific user communities will be made through external guidance or policy documents.

  14. Capacities for the Hydrography Standard More Information The goals, tasks, and accomplishments of this standard were determined by the Hydrography Modeling Advisory Team (MAT) – a group of domain experts convened to define a common set of hydrography information content. • The development of this part of the Framework Data Content Standard will greatly assist in mitigating the following issues: • Duplication of data and application development • Complications exchanging hydrography data and information • Difficulties integrating data • Poor framework/support for analytic activities • Difficulties managing multiple representations of features next Topic Contact Info

  15. Who to Contact for Questions about the Hydrography Standard Part Standard Coordination The FGDC is the responsible organization for coordinating work on all parts of the Geographic Information Framework Data Content Standard. The development and maintenance authority for Part 6: Hydrography is held jointly by the U.S. Geological Survey and U.S. Environmental Protection Agency. The FGDC shall be the sole organization responsible for direct coordination with the InterNational Committee for Information Technology Standards (INCITS) concerning any maintenance or any other requirements mandated by INCITS or ANSI. Federal Geographic Data Committee Secretariat c/o U.S. Geological Survey 590 National Center Reston, Virginia 20192 USA Telephone: (703) 648-5514 Facsimile: (703) 648-5755 Internet (electronic mail): gdc@fgdc.gov WWW Home Page: http://www.fgdc.gov next Topic Module 2 Exercise

  16. Hydrography Module exercise Instructions: The following Quiz will test the knowledge you should have gained in Module 2. There are 3 True or False Questions. Good Luck! Proceed To Quiz

  17. True or False: The Hydrography part identifies and defines terminology, encoding schema, and the data components required for describing hydrographic features, along with the metadata needed for the hydrography data exchange A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  18. True or False: One goal of the standard is to set a common baseline of information content for exchange within the hydrographic community that will reduce the need for data sharing and allow users to create their own data without the need to share with others. A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  19. True or False: The Federal Geographic Committee is NOT involved with these standards in anyway. A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  20. Module 2 Quiz next Topic Module Summary

  21. Module summary • The goal of the Hydrography part of the Framework Data Content Standard is to provide common definitions and syntax to enable collaborative development, use, and exchange of hydrography data. • Establish the content requirements for the collection and interchange of hydrography features • Supports the mapping and conversion of native data in any format into a common representation for exchange over the Web or as files next Topic Module 3: Hydrography Requirements

  22. Module 3: Hydrography Requirements Time Requirement Topics Estimated time for this module is 60 minutes • Framework Data Content Hydrography Standard Requirements • Encoding and Implementing the Standard • Module Summary Key Terms UML Coding Elements Feature Relationships First Topic Hydrography Standard Requirements

  23. Framework Data Standard Hydrography Requirements In this module you will learn about the three different requirements for Framework Hydrography data, as specified in the standard. Each requirement is addressed as a separate topic, however more attention may be given to certain requirements as they are the most crucial requirements for creating Framework quality hydrography data. Many of the requirements are specific UML features. For these requirements the a brief description of the component will be included. Please see the UML chart and associated tables, included as an appendix for more specifics. Additionally encoding and implementation will be covered briefly. next Topic Hydrography Requirements Continued

  24. Framework Data Standard Hydrography Requirements The diagram to the right is the UML flow chart for the Framework Hydrography Standard. This diagram shows the components and relationships that comprise the Framework Hydrography Standard. UML is designed to show these relationships in a generic manner without specifying a coding language or specific software needed to complete the task. For more information about UML visit http://www.uml.org next Topic Hydrography Requirements Continued

  25. Framework Data Standard Hydrography Requirements • The following list is a comprehensive list of each UML object specified in the hydrography standard. Each one coresponds to a box on the UML diagram on the previous slide. For more detailed information please see the Appendices which have a copy of the compete standard including tables outlining the specifics of each UML object. • HydroCollection: is the container for the features packaged in an exchange of hydrographic information. • HydroFeature: is an abstract class that captures the characteristics of the hydrographic feature. As the core component of the model, HydroFeature has several significant associations to other classes. HydroFeature has HydroElement and HydroComplex subclasses. • HydroElement: Basic hydrographic features with explicit geometry. HydroElement inherits all properties (generalizes) from the abstract parent class, HydroFeature. next Topic Hydrography Requirements Continued

  26. Framework Data Standard Hydrography Requirements • HydroComplex: is an aggregate of HydroElement. The HydroComplex may impose property requirements onto the associated HydroElements. For example, a HydroComplex of Reach requires measure values based on the extent of the Reach, not of the HydroElements that make up the Reach. As an aggregate representation, a HydroComplex is retired if the HydroElements that make up the HydroComplex are retired. The reverse situation does not apply. HydroComplex inherits all properties from the parent abstract class, HydroFeature. These properties are not shown in the table below. • FeatureRelationship: describes binary relationships between feature instances. The order of the elements in the relationship is explicit and is represented using a self-association in the UML model. The RelationshipAttribute qualifier will have relevance to a specific RelationshipType. • Event: is an object supports the linking of external attribute information to a portion of a HydroFeature, either HydroElement or HydroComplex. Events can be of two types: MeasuredEvent or UnmeasuredEvent. MeasuredEvents are those that reference portions of features that participate in the linear reference model. UnmeasuredEvents are those that reference portions of features that do not participate in the linear reference model. next Topic Hydrography Requirements Continued

  27. Framework Data Standard Hydrography Requirements • MeasuredEvent: represents a point or span along a linear feature. In order to have MeasuredEvents, a linear feature must participate in the linear reference model. A MeasuredEvent always has a StartMeasure and, if it represents a span along a feature, it also has an EndMeasure. The measures specifies the exact location of the event relative to the addresses/measures along the referenced feature. A MeasuredEvent may also have a geometric representation (inherits “location”) which provides an independent location for the event. MeasureEvent inherits all properties from the parent class, Event. • UnmeasuredEvent :may be linked to any feature that does not participate in the linear reference model. The referenced feature may be a zero-dimensional, one-dimensional, or two-dimensional feature and may be either an HydroElement or HydroComplex feature. UnmeasuredEvents must have a location (geometry) that specifies the location of the event independent of the geometry of the referenced feature. The geometry may be of point, line, or polygon as declared in the ElementGeometry Union class. UnmeasuredEvent inherits all properties from the parent class, Event. These properties are not shown in the table below. next Topic Hydrography Requirements Continued

  28. Framework Data Standard Hydrography Requirements • Name:object holds feature names that are managed by a naming authority. The authority may be a recognized authority such as the Board of Geographic Names or an un-recognized authority such as a local hydrography maintainer. An ExchangeCollection may contain names from different authorities. Feature names are linked to HydroFeatures, both HydroElement and HydroComplex, in a many-to-many relationship. This permits a given feature to have names from different authorities. It also permits a single name to be linked to HydroFeature instances that represent parts of a named feature. • HydroFeatures, both HydroElement and HydroComplex, will have more than one representation in the hydrography community. A representation is one instance combination of feature attributes and geometry – variation in one characteristic constitutes a new representation. Each HydroFeature instance within a given ExchangeCollection will have a single representation and the Representation object describes which representation is being exchanged. If the ExchangeCollection contains more than one representation for a given HydroFeature, there will be a feature instance (with unique identifier) for each representation in the ExchangeCollection. next Topic Hydrography Requirements Continued

  29. Framework Data Standard Hydrography Requirements 11) Measurement: is used to store empirical measurements of features such as real- world reported elevation, length, area, and depth – typically of values portrayed on topographical maps. HydroElement, HydroComplex, and Event features may have one or more ReportedMeasurements. 12) ComputedNetworkValues: The National Hydro Dataset (NHD) includes a number of computed values for hydrographic features (HydroElements) with basic geometries. These properties are only calculated for features that participate in the network for which flow direction is known or inferred. next Topic Hydrography Requirements Continued

  30. Framework Data Standard Hydrography Requirements 13) Common framework classes: Three classes are shown in Figure 1 that are included from the Base Document (Part 0) for completeness. These classes are ExtendedAttribute, Identifier, and ExternalResource. The ExtendedAttribute object, described in Part 0, provides the ability to link additional attributes to HydroFeature instances, both HydroElement and HydroComplex. The ExtendedAttribute must have an authority which is documented with an authority (ISO19115::ResponsibleParty). The ExtendedAttribute may be documented through a URL to an ExternalResource object instance. The fuller description of this behavior is provided in the Part 0 but the classes are only shown here for convenience. The ExternalResource object provides the ability to link Internet URLs to HydroFeatures, both HydroElement and HydroComplex, to Events, to ISO19115::ResponsibleParty, and to ExtendedAttributes. There are a number of different types of ExternalResources as enumerated in the ResourceType code list. Identifier stores a set of related properties required for the management of information within a namespace. The identifier, a description, and a reference to an assigning authority are provided. The ResponsibleParty class comes from the ISO 19115 metadata concept of the same name but is implemented here to simplify the possible associations and recursion in the data model. ISO19115::ResponsibleParty provides descriptive details of an organization to which one can go and get additional contextual information. next Topic Hydrography Requirements Continued

  31. Framework Data Standard Hydrography Requirements 14) External packages: several UML packages of structured information are used or referenced from ISO sources in this part of the standard. These include geometry and linear referencing constructs from other ISO standards (GM_Object from ISO19107, CharacterString and Date from ISO/TS 19103). The inclusion of these packages of information complements the model. 15) Code lists and enumerations: the code lists presented in Figure 2 represent known values that are encouraged to promote interoperability. Code lists, by their nature are not closed enumerations and are not intended to be exhaustive. In fact, they might be placed online and would support controlled update by the community. In implementation, strict validation may include tests for the presence of these codes, whereas lax validation may permit these and additional code values. next Topic Encoding and Implementation

  32. Encoding and implementation The Bigger Picture The Framework Standards do not have a specific application schema that can be implemented. Implementation of the Framework Standards in relation to data and tool creation occurs at the thematic level. Each thematic part complies with the Framework Base Standard. As such a road layer (for example) created in accordance with the Framework Transportation Roads part meets all Framework requirements. • The process of encoding is simply formatting or structuring data in a regulated manner. The Framework standards are encoded by applying the application schemas through the use of several different modeling and markup languages: • Unified Modeling Language (UML) • Extensible Markup Language (XML) • Geographic Markup Language (GML) • Specific knowledge of each language is important for data and tool designers; for more information see the Framework Base Standard Training Materials. next Topic Module Review

  33. Module 3: HydroGraphy Requirements Summary • Three different requirements, with multiple subparts are specified by the Framework Hydrography Standard • This module covers the specifications on Hydrography data should be built • Provides rigid requirements to ensure proper structure and documentation for hydrography data • UML diagrams and data dictionaries provide specifics for programmers and data creators to develop hydrography data that meets Framework specifications next Topic Module 4: Standard Implementation

  34. Module 4: How To put The Standard into operation Time Requirement Topics Estimated time for this module is 60 minutes • Implementation Overview • Design Requirements • Hydrography UML Specifics • Code Lists • Implementation Example Key Terms UML Code Lists Hydrographic Applications First Topic Implementation Overview

  35. Implementation Overview Now that you know more about the Hydrography and how it applies to the overall objective of Framework; The goal of this module is to help you implement the Hydrography Part of the Framework Standard. It is important that you realize that currently there are no tools to help you implement, or check your data to ensure it meets Framework Standard requirements. Remember these standards are new and tools to implement these standards will take time to develop. However, the slides in this module will give you an overview of the general process and requirements needed. Please refer to the Framework Standard Hydrography Part for additional information and context. next Topic Design Requirements

  36. Design Requirements Hydrographic Applications It is important to remember that different hydrographic based applications have specific data and information requirements. Thus the Hydrography Framework part needs a complex data model to support these needs. • Design Concepts: • The Hydrography Component has 8 key design concepts defined by the standard: • Core component of the standard and model are the hydrologic features • All features have geometry • Features are classified by type, and qualified by attributes • Features may have relationships with other features • Common definition of “features” is needed for data sharing • Permanent identifiers for features are managed by an authority • Linear referencing is supported through permanent features, identifiers, and measurement references • Multiple representations of a feature can exist and are managed in a community Application Examples: including Data Needs next Topic Hydrography UML Specifics

  37. Hydrography UML Specifics Hydrography UML Classes The diagram shown to the right was introduced in Module 3, along with the data dictionary elements that are needed / available elements within the hydrography part of the Framework Standard. It is important to remember that UML is not a coding language but a rather is a model of how the features and values within a system (i.e. Framework Hydrography data layer) should be structured. For more information about UML and how to use it please visit http://www.uml.org next Topic Code Lists

  38. Code Lists Hydrography Code lists A code list is designed to limit the available choices of values that a feature can have. Although code lists are not necessarily comprehensive indices, they are designed to define the most commonly used values in a standardized format which promotes data interoperability. In fact often strict implementation rules and validation assessments will test for the presence of a code list value, while more lax rules will allow for the presence of additional code values. The diagram to the right represents values that promote interoperability of hydrographic data. next Topic Implementation Example

  39. Implementation Example Hydrography Data Example 1 The hydrography model developed for the Framework Standard is a large and complex model that provides documentation and direction for creating hydrologic data that is interoperable. To provide a step-by-step guide for producing every type of hydrologic data possible in the standard would be nearly impossible. Thus the example provided here is merely a simplified version of an implementation of the standard. As you will notice certain values that are required as part of the UML diagram are not visible in the feature or the attributes, however those that are visible are indicated on the diagram to the right. 2 3 4 5 6 7 8 next Topic • Feature Relationship – type • Hydrofeature – featureID • Hydrofeature – featuredate • Hydroelement –featuretype • Hydroelement – geometry • Hydrofeature – name • Datatype – nameID • Datatype -IDauthority Note: All indications come from UML diagram, Code list diagram provides further context Module 4 Summary

  40. Module 4 Summary • The hydrography model developed for the Framework Standard is a large and complex model that provides documentation and direction for creating hydrologic data that is interoperable. • Individual hydrographic applications and data have specific needs, however the model developed for the Hydrography Framework model encompasses all of these needs • Specific UML diagrams, code lists, and data dictionaries have been developed to document components necessary for Framework Hydrography data. next Topic Module 5

  41. Module 5:Course Review and Comprehensive Self-Test Topics • Review Exercise • Comprehensive Self-Test • Course Evaluation • Certificate of Completion next Topic Geo-pardy

  42. Course Home Next Topic FAQ Geo-pardy Game Glossary References Geo-pardy Instructions This review exercise is structured very similar to the TV show Jeopardy and pulls questions from both this training material and the Framework Base Standard training material. To play simply click on the category and dollar amount for each question. If you wish to keep score, tally your results on a scratch piece of paper. Good Luck and have fun!

  43. Let’s Play Framework Data Content Base StandardGeo-pardy!!

  44. Requirements Hydrography Hydrography Standard Framework Uses / Users $100 $100 $100 $100 $100 $200 $200 $200 $200 $200 $300 $300 $300 $300 $300 $400 $400 $400 $400 $400 $500 $500 $500 $500 $500 Final Geo-pardy

  45. Next Topic Self-Test Self-Test Instructions This test is designed to test your understanding of Framework and the Framework Base Standard after completing this course. The test is comprised of both multiple choice and true/false questions. Good Luck!

  46. True or False: NHD and Framework Hydrology are the same? A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  47. The _____ was created to help the FGDC develop the hydrography standard A) MAT B) SAC C) TEAC D) Carpet Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  48. True or False: Ground water is part of the Framework Hydrography. A) True B) False Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  49. Which is NOT a Hydro Standard Requirement? A) HydroCollection B) HydroTrend C) HydroFeature D) HydroElement Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

  50. Hydrography data is: A) the study of the hydrologic cycle B) seimic readings that occur underwater C) a representation of "real-world" water features D) the amount of instream flow a river has at a given moment Correct - Click anywhere to continue Incorrect - Click anywhere to continue Your answer: You answered this correctly! You did not answer this question completely You must answer the question before continuing The correct answer is: Submit Clear

More Related