Attribute Rules

All feature classes accessed by Attribute Rules must be located in the same database.

Unique ID Sequence

  • Every Signs GIS layer has a unique ID field that will be automatically populated by a Database Sequence.

    • Asset Locations - ASSET_LOCATIONS_ID

    • Asset Signs Poles - ASSET_SIGNS_POLES_ID

  • Attribute Rule is not Editable

  • Triggers - Insert

  • Execution - Exclude from application evaluation

Text(NextSequenceValue("ATD_ADMIN.atd_signs_data_sequence"))

Intersection ID

  • Only the Asset Locations GIS layer has the INTERSECTION_ID field, which is automatically calculated based on a Thiessen Polygon layer of the COA Intersection Points layer. This layer is used to find the closest Intersection point to the new record that has been added.

  • If the Intersection ID that is automatically calculated is not the Intersection ID you would like entered, the field is editable where a new Intersection ID can be entered (Editable is checked).

  • Triggers - Insert

  • Execution - Exclude from application evaluation

var intersectLayer = Intersects(FeatureSetByName($datastore, "ATD_ADMIN.COA_Intersection_Points_TP"), $feature);
for (var fc in intersectLayer) {
   return fc.INTERSECTION_ID
}

Segment ID

  • Only the Asset Locations GIS layer has the SEGMENT_ID field, which is automatically calculated based on the ATD Maintained Streets Line layer.

  • If the Segment ID is left null or is automatically calculated to a Segment ID that is not ideal, the field is editable where a new Segment ID can be entered (Editable is checked).

  • Triggers - Insert

  • Execution - Exclude from application evaluation

Engineering Area

  • Only the Asset Locations GIS layer has the ENGINEER_AREA field, which is automatically calculated based on the Engineering Service Areas polygon layer.

  • If a feature is moved after it is created, the ENGINEER_AREA field will automatically update.

  • The ENGINEER_AREA field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule (Editable is not checked).

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Jurisdiction

  • Only the Asset Locations GIS layer has the JURISDICTION field, which is automatically calculated based on the Jurisdictions polygon layer.

  • If a feature is moved after it is created, the JURISDICTION field will automatically update.

  • The JURISDICTION field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule (Editable is not checked).

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Council District

  • Only the Asset Locations GIS layer has the COUNCIL_DISTRICT field, which is automatically calculated based on the Single Member Districts polygon layer.

  • If a feature is moved after it is created, the COUNCIL_DISTRICT field will automatically update.

  • The COUNCIL_DISTRICT field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule (Editable in not checked).

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

X Coordinate

  • Only the Asset Locations GIS layer has the X_COORDINATE field, which is automatically calculated based on the features location.

  • If a feature is moved after it is created, the X_COORDINATE field will automatically update.

  • The X_COORDINATE field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule (Editable is not checked).

  • Coordinates calculated are based on the NAD 1983 State Plane Texas Central FIPS 4203 (US Feet) coordinate system.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Y Coordinate

  • Only the Asset Locations GIS layer has the Y_COORDINATE field, which is automatically calculated based on the features location.

  • If a feature is moved after it is created, the Y_COORDINATE field will automatically update.

  • The Y_COORDINATE field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule (Editable is not checked).

  • Coordinates calculated are based on the NAD 1983 State Plane Texas Central FIPS 4203 (US Feet) coordinate system.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Last updated

Was this helpful?