Once you've properly set up domain values, assigned the domains to their respective fields, and determined the group of fields to create contingencies on, you must create the contingencies between the domain values. For example, the Material field has a domain for materials of types Fiberglass, Wood, and Steel.
Each field has an appropriate domain assigned. In the power pole example above, the contingent values are in a group of three fields: Class, Material, and Height. Before creating contingent values, these fields should be set up with appropriate domains containing a list, or range, of valid values. Prepare data for contingent valuesĬontingent values are created for groups of fields in a table or feature class. Likewise, the valid values for the height of a Class 1 Fiberglass pole are constrained to 30, 35, 40, or 45.īuilding contingent values like this in your data allows you to further constrain the valid values for sets of fields and more efficiently manage the validity and integrity of your data. For this group of fields (class, material, and height), the set of contingencies can be as follows:Īfter these contingent values are created, if you place a new pole feature or modify an existing one, and designate it a Class 1 power pole, the set of values that you can place on the Material field will be constrained to Fiberglass. For example, using contingent values, you can define a class 1 pole as being made only of the material fiberglass and restricted to only 30, 35, 40, or 45 feet in height.Ĭonsider the contingencies that you want between field values on the Pole subtype. To further constrain the valid values for this set of fields, you can use contingent values. For example, a pole can be of pole class 1, 2, or 3 a pole's material can be fiberglass, wood, or steel and a pole's height can be 30 feet, 35 feet, 40 feet, 45 feet, and so on. The domains constrain the values that can be placed on each field to a list of valid values. There is a point feature class for structure junctions that has subtypes for assets such as power poles, manholes, platforms, and so on.įor the Pole subtype, domains have already been applied to three of the fields. Pilot > EX-L > White, or it can be a Toyota >ĤRunner > TRD Sport > Inferno, depending on what you chooseĬontingent values allow you to set up these types ofįield dependencies in your data in which your choice for a value in one field defines and restricts the list of valid values for another field.įor a real-world GIS example, consider the StructureJunction feature class within the utility network asset package. The car model you choose dictates what trim levels are availableĪnd each trim level may have a different set of color options. Choosing a differentĬar brand will result in a different set of available car models. The decision tree may look like this: Pick a Car Brand > Carįirst you choose the car brand, for example, Honda.įor Toyota, a different list of car models is available.Ĭhoose, there are a number of trim levels available.Ĭan be a number of colors available, such as Red, Blue, Black,Įach choice in the decision tree presents a list of optionsĬontingent on what you've chosen previously. See Client and geodatabase compatibility for more information on functionality available when using mixed client and geodatabase releases.Ī relatable example for an application of contingent values is buying a vehicle.
#Subtype time calc view pro#
This can also be useful for creating decision trees or survey questions where making a choice will determine the next set of valid choices.Ĭreating contingent values on a table or feature class makes it incompatible with ArcMap and releases prior to ArcGIS Pro 2.3 and ArcGIS Enterprise 10.7.x. This can be useful when modeling real world parts and assets in your GIS, particularly for utility companies. In this way, contingent values enforce data integrity by applying additional constraints to reduce the number of valid field inputs.
Contingent values extend this model by making your choice for a value on one field further constrain the domain values that can be placed on another field. Attribute domains allow you to restrict the valid entries in a field to a set list or range of values. Contingent values, sometimes referred to as contingent attribute values, are a data design feature that allows you to make values in one field dependent on values in another field.
0 kommentar(er)
