mapublisher assign same value in attribute table

Once the field type is set, the name of the domain will appear in the domain drop-down list for any field of that type in the Properties dialog box. Range domains-A range domain specifies a valid range of values for a numeric attribute.There are two types of attribute domains: When you create a domain, you must specify which type of domain you want to use. When creating a range domain, you enter a minimum and maximum valid value. A range domain can be applied to short-integer, long-integer, float, double, and date attribute types.įor example, in a feature class for water mains, you could have subtypes for transmission, distribution, and bypass water mains. Distribution water mains can have a pressure between 50 and 75 psi. For a distribution water main object to be valid, its pressure value must be entered as some value between 50 and 75 psi. Range domains are validated through the use of the Validate Features command. Coded domains-A coded value domain can apply to any type of attribute-text, numeric, date, and so on.Learn more about Editing with default values and attribute domains. Coded value domains specify a valid set of values for an attribute.įor example, water mains may be buried under different types of surfaces as signified by a GroundSurfaceType attribute field: pavement, gravel, sand, or none (for exposed water mains).

The coded value domain includes both the actual value that is stored in the database (for example, 1 for pavement) and a more user-friendly description of what that value actually means. Validation for coded value domains is accomplished by restricting the user to choose field values from a drop-down list. Often, when editing data, a single feature is split into two features or two separate features are combined, or merged, into a single feature. For example, in a landbase database, a land parcel may be split into two separate land parcels due to rezoning. Similar zoning changes may require two adjacent parcels to be merged into a single parcel. While the results of these types of edit operations on the feature's geometry are easily predictable, their effects on the attribute values are not. The behavior of an attribute's values when a feature is split is controlled by its split policy. The attribute scheme, structure, and attribute values are inherited from the source layer to the split layers.When two features are merged, an attribute's value is controlled by its merge policy.Įach attribute domain has both a split policy and a merge policy. Now you have eight new MAP layers created based on the unique values of the “Continent” attribute. Here, we entered the word “continent” as the prefix.ģ.

If you have a specific word you would like to include with the eight layers, enter the value for the “New layer prefix” option. Choose the world_area source layer, then select the option “Split art to new layer(s) by unique attribute value:”. To split this world_area layer into eight different layers based on unique values in the “Continent” attribute, we simply specify the Continent layer in the Split Layer dialog box.Ģ.With the “Continent” attribute, there are eight unique values: 1) Africa, 2) Antarctica, 3) Asia, 4) Australia, 5) Europe, 6) North America, 7) Oceania, and 8) South America. The world_area layer has many attributes and one of the attributes is about “Continent” information. If you have some data you would like to divide into multiple layers using unique values in an attribute, you might want to try using the Split Layer feature in MAPublisher.įor example, we have a MAP Layer of the world (world_area layer).

Mapublisher assign same value in attribute table