Presentation is loading. Please wait.

Presentation is loading. Please wait.

Physical Structure of GDB

Similar presentations


Presentation on theme: "Physical Structure of GDB"— Presentation transcript:

1 Physical Structure of GDB
Geodatabase Feature datasets Spatial Reference Object classes, subtypes Features classes, subtypes Raster datasets Rasters Relationship classes Geometric networks TIN datasets nodes, edges, faces Planar topologies Locators Attribute Domains Addresses, X.Y location ZIP Codes, Place names Validation rules Introduction to Geodatabases

2 Subtypes and Attribute domain
Problem Scenario (2) Subtypes (6) Integrity with Attribute Domain (3) Domain Types (3) Split and Merge Policy (5) Attribute Validation Creating Domains (6) Summary, Review Questions and Next… Geography, KHU, Jinmu Choi Introduction to Geodatabases

3 Introduction to Geodatabases
Scenario Scenario Assuming a feature class called WaterMains may store pressurized water mains It may be true in a water network that only transmission water mains can have a pressure between 60 and 100 psi, while distribution water mains can have a pressure between 40 and 65 psi Now you have to implement this validation rule: How? Introduction to Geodatabases

4 Introduction to Geodatabases
Solving scenario Use lightweight classification: subtypes You don’t have to create separate feature classes for transmission and distribution water mains You want to distinguish these types of water mains from each other to establish separate set of domains and default values with subtypes Introduction to Geodatabases

5 Introduction to Geodatabases
When to use Subtypes Use subtypes When trying to distinguish objects by their default value, attribute domains, various rules Use additional classes When trying to distinguish objects based on different behaviors, attributes, access privileges, or multi-versioned Introduction to Geodatabases

6 Introduction to Geodatabases
Subtypes Feature classes or objects contain subtypes A feature’s subtype is determined by its subtype code value The subtype code is stored in an integer field in the feature class or table Each subtype can have own set of default values and attribute domains for a given field Introduction to Geodatabases

7 Introduction to Geodatabases
Creating Subtypes Add a Field for subtype using Integer Use subtype tab on the feature property Introduction to Geodatabases

8 Creating Subtypes (cont.)
Introduction to Geodatabases

9 Creating Subtypes (cont.)
Introduction to Geodatabases

10 Introduction to Geodatabases
Deleting Subtypes Use Subtype tab in the feature property Select subtype in the list and click Delete key You cannot delete a subtype if it is currently referenced by a topology rule: close ArcMap Introduction to Geodatabases

11 Introduction to Geodatabases
Enforcing Integrity Maintaining accurate data is a concern of all GIS users Attribute domains in a geodatabase specify valid values for an attribute When attributes are being edited, attribute domains help prevent data errors in one of two ways: Create a list of valid attribute values from which users must choose With valid range of data, give users the ability to check that all features are valid after editing Introduction to Geodatabases

12 Introduction to Geodatabases
Attribute domain Attribute domains are rules that describe the permissible values of a field type Attribute domains are used to constrain the values allowed in any particular attribute for a table, feature class, or subtype Multiple feature classes and tables can share attribute domains in the database Attribute domains are stored in a geodatabase, Not feature dataset and classes Introduction to Geodatabases

13 Check Integrity with Domain
Use Domain Class Property Create Domain Validate Features Geodatabase Property Introduction to Geodatabases ArcMap: Editor/validation

14 Domain Types - Range domain
Two different types of attribute domains Range domain specifies a valid range of values for a numeric attribute Validation in ArcMap: After editing, run Editor/Validation to validate features that have a range domain After running Validate Features, the features with errors remain selected Introduction to Geodatabases

15 Domain Types – Coded value domain
Coded value domain are explicit lists of acceptable values and can apply to any type of attribute Attribute domains don’t have a property that allows or disallows null values in an associated field: treat null as valid value Introduction to Geodatabases

16 Domain Types – Coded value domain
Validation is automatic for coded value domains When you're editing an attribute of a feature class that references a coded value domain, you cannot manually enter an attribute value of the feature class Instead, choose the desired value from a dropdown list that contains the valid values Introduction to Geodatabases

17 Validation with Policies
Introduction to Geodatabases

18 Splitting Behavior in AD
Type of Split policy Duplicate — both features inherit the same attribute value as the original feature Default value — both features are assigned the default attribute value if one has been specified in the field properties (or subtype) [If no default value has been specified, both features inherit the same value as the original feature] Geometry ratio — each feature is assigned a new attribute value based on a ratio of the original feature's attribute value Introduction to Geodatabases

19 Introduction to Geodatabases
Examples of Splitting Introduction to Geodatabases

20 Introduction to Geodatabases
Merging Behavior in AD Type of Merge policy Default value — the new feature is assigned the default attribute value if one has been specified [If no default value has been specified, the feature will inherit the value of one of the originals] Sum — the new feature is assigned an attribute value that is the sum of the values of the original features Weighted average — the new feature is assigned an attribute value that is the weighted average, based on geometry, of the values of the original features Introduction to Geodatabases

21 Introduction to Geodatabases
Examples of Merging Introduction to Geodatabases

22 Setting Attribute Domain
Introduction to Geodatabases

23 Browsing Attribute Domain
Use Domain tab on the GDB property Use Domain button on the Subtype tab of the feature class property Introduction to Geodatabases

24 Introduction to Geodatabases
Creating Range Domain Use Domain tab on the GDB property Introduction to Geodatabases

25 Introduction to Geodatabases
Creating Coded Domain Use Domain tab on the GDB property Introduction to Geodatabases

26 Deleting Attribute Domain
User Domain tab in the GDB property Select domain and click Delete key While a domain is being used by a table or feature class, it cannot be deleted or modified: close ArcMap Introduction to Geodatabases

27 Introduction to Geodatabases
Use Domain in a Table If a domain is associated with a feature class or table, an attribute validation rule is created in the GDB Introduction to Geodatabases

28 Introduction to Geodatabases
Summary Subtypes Integrity with Attribute Domain Domain Types Attribute Validation: Split and Merge Policy Creating Domains Introduction to Geodatabases

29 Introduction to Geodatabases
Next… Lab: Working with Domains and Subtypes Next: Field Study Exam Guide Next: Relationships Reading Read Building GDB (handout) Ch 6 Introduction to Geodatabases


Download ppt "Physical Structure of GDB"

Similar presentations


Ads by Google