In a previous blog post, I discussed the value and creation of Esri domains. These domains are assigned to database fields to assist with data entry.
No matter your GIS application, there is always a need to update/tweak the database for new requirements.
Even if the reader isn’t a database administer and doesn’t have database permissions to conduct the act, this post will hopefully enhance the dialogue to communicate those requirements. So…..how does one create fields?
The creation of fields is probably most easily conducted in ArcCatalog. These procedures assume an ArcCatalog method:
Note: Not all field names are acceptable, and there are some restricted values. For example, an administrator is not allowed to name their field “field”. A more common field name problem is “name” (suggest “st_name” for street name, etc.). One also cannot have a space in the field name (If desired, add the space in the field’s alias).
Whenever possible, the user is encouraged to avoid text fields. The end user will benefit much more by using Integer, Decimal, and Date options. More statistical analysis options are available with OOTB Esri tools with non-text fields.
When text fields are used, try to minimize the length of the field. The longer the text field….the more memory (thus more processing required) is used whether the actual value actually uses the space or not.
For example, let’s say we have a state field that is populated with the random value of “KY”. If we use the default length of 50 characters, there will always be wasted storage of 48 characters. In this example, we should have a length of 2 because we will always have a two-character state value.
When using Integer or Decimal fields, try to also use the smallest memory usage option. The Long Integer option takes up twice as much memory (4 bytes) as the comparable Short Integer (2 bytes). Very similarly, the Double Precision Decimal also takes twice as much memory (8 bytes) as the comparable Float Decimal (4 bytes).
For years, the only OOTB option for tracking record-specific metadata (i.e., who created it, who modified it, or when did they do it) was ArcFM™ Autoupdaters.
There is now an Esri method that must be conducted to translate to ArcGIS Online and subsequent Collector editing (ArcFM™ properties are not applicable to ArcGIS online/Collector).
To configure the Esri functionality conduct the following procedure:
Field Order and Field Visibility
ArcFM™ has also had the ability to change the field order and/or visibility for years. These properties (once set) are stored within the database, and apply to ALL Stored Displays. They cannot be tailored for specific requirements (i.e., end user vs administrator).
Esri’s method of establishing field order and visibility is through the ArcMap project (*.mxd). As with the metadata, this configuration is directly usable for ArcGIS Online and Collector. To establish, follow the following procedure:
Hopefully this post has or will prove useful in your GIS work. We love comments, so make me look good, and leave several.