Attribute Rules

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

Unique ID Sequence

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

    • Markings Specialty Point - MARKINGS_SPECIALTY_POINT_ID

    • Markings Specialty Line - MARKINGS_SPECIALTY_LINE_ID

    • Markings Short Line - MARKINGS_SHORT_LINE_ID

    • Markings Long Line - MARKINGS_LONG_LINE_ID

  • Attribute Rule is not Editable

  • Triggers - Insert

  • Execution - Exclude from application evaluation

Text(NextSequenceValue("ATD_ADMIN.atd_markings_data_sequence"))

Intersection ID

  • Every Markings 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.

  • Triggers - Insert

  • Execution - Exclude from application evaluation

Segment ID

  • Every Markings 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.

  • Triggers - Insert

  • Execution - Exclude from application evaluation

CBD - Central Business District

  • All Markings GIS layers except Markings Long Line have a CBD field, which is automatically calculated based on the DAPCZ Polygon Layer. If the feature intersects with the Central Sector of the DAPCZ layer, the CBD field is coded to Yes, otherwise No.

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

  • The CBD field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Signal Intersection

  • All Markings GIS layers except Markings Long Line have a SIGNAL_INTERSECTION field, which is automatically calculated based on a 100' Buffer Polygon layer of the Street Signals and Pedestrian Signals Point layer (Signals turned on only). If the feature intersects with the 100' Buffer Polygon layer, the SIGNAL_INTERSECTION field is coded to Yes, otherwise No.

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

  • The SIGNAL_INTERSECTION field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule.

  • Triggers - Insert, Update

  • Execution - Exclude application evaluation

School

  • All Markings GIS layers except Markings Long Line have a SCHOOL field, which is automatically calculated based on a 1/4 mile Buffer of the Schools layer located on MAINT. If the feature intersects the layer on creation, the SCHOOL field is calculated to Yes, otherwise No.

  • If there are other stipulations for changing the value, the field is editable and can be changed.

  • Triggers - Insert

  • Execution - Exclude application evaluation

Bike - Specialty Line

  • The BIKE field in the Markings Specialty Line Layer is automatically calculated based on the SPECIALTY_LINE_TYPE field in the same layer.

  • If the SPECIALTY_LINE_TYPE field is edited after it is created, the BIKE field will be updated depending on the change made.

  • The BIKE field is not manually editable. If the SPECIALTY_LINE_TYPE field is changed by accident, the BIKE field will automatically update based on the Attribute Rule.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Bike - Specialty Point

  • The BIKE field in the Markings Specialty Point Layer is automatically calculated based on the SPECIALTY_POINT_TYPE and SPECIALTY_POINT_SUB_TYPE fields.

  • Since there are 6 different Subtypes, 6 separate rules had to be created to correctly calculate the BIKE field depending on which Specialty Point Type is chosen.

  • If the SPECIALTY_POINT_TYPE or SPECIALTY_POINT_SUB_TYPE fields are edited after the record is created, the BIKE field will be updated depending on the change made.

  • The BIKE field is not manually editable. If either the SPECIALTY_POINT_TYPE or SPECIALTY_POINT_SUB_TYPE fields are changed by accident, the BIKE field will automatically update based on the Attribute Rules.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Specialty Point Type

Description

1

Word

2

Arrow

3

Symbol

4

Parking

5

Other

6

Raised Pavement Markings

Word

  • Attribute Rule Subtype: Word

Specialty Point Subtype for BIKE - Word

Description

14

Bike (word)

Arrow

  • Attribute Rule Subtype: Arrow

Specialty Point Subtype for BIKE - Arrow

Description

11

Bike Arrow

Symbol

  • Attribute Rule Subtype: Symbol

Specialty Point Subtype for BIKE - Symbol

Description

1

Bicycle (Bike)

3

Bicyclist

5

Chevron

Other

  • Attribute Rule Subtype: Other

Specialty Point Subtype for BIKE - Other

Description

1

Green pad

2

Green launch pad

Parking

  • Attribute Rule Subtype: Parking

Specialty Point Subtype for BIKE - Parking

Description

7

Bicycle

Raised Pavement Markings

  • Attribute Rule Subtype: Raised Pavement Markings

Specialty Point Subtype for BIKE - Raised Pavement Markings

Description

None

None

Other Area

  • All Markings GIS layers except the Markings Long Line layer have an OTHER_AREA field, which is automatically calculated based on specific fields depending on the layer.

  • If any changes are made to any of the fields that affect the OTHER_AREA field, it will automatically update as well.

  • The OTHER_AREA field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule.

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Short Line

  • The OTHER_AREA field is calculated based on the CBD, SIGNAL_INTERSECTION, and SCHOOL fields.

  • If CBD, SIGNAL_INTERSECTION, or SCHOOL fields are coded to Yes, then OTHER_AREA will automatically be coded to No. If all are No, then OTHER_AREA will be coded to Yes.

Specialty Line / Point

  • The OTHER_AREA field is calculated based on the CBD, SIGNAL_INTERSECTION, and BIKE fields.

  • If CBD, SIGNAL_INTERSECTION, or BIKE fields are coded to Yes, then OTHER_AREA will automatically be coded to No. If all are No, then OTHER_AREA will be coded to Yes.

Crew Assigned

  • All Markings GIS layers except the Markings Long Line layer have a CREW_ASSIGNED field, which is automatically calculated based on specific fields depending on the layer.

  • If any changes are made to any of the fields that affect the CREW_ASSIGNED field, it will automatically update as well.

  • The CREW_ASSIGNED field is not manually editable. If the field is changed by accident, it will default back based on the Attribute Rule.

  • The CREW_ASSIGNED field is calculated by the following hierarchy:

    • CBD

    • SIGNAL_INTERSECTION

    • SCHOOL or BIKE

    • OTHER_AREA

  • Triggers - Insert, Update

  • Execution - Exclude from application evaluation

Short Line

  • The CREW_ASSIGNED field is calculated based on the CBD, SIGNAL_INTERSECTION, SCHOOL, and OTHER_AREA fields. The hierarchy for which the CREW_ASSIGNED field is coded is listed above.

Specialty Line / Point

  • The CREW_ASSIGNED field is calculated based on the CBD, SIGNAL_INTERSECTION, BIKE, and OTHER_AREA fields. The hierarchy for which the CREW_ASSIGNED field is coded is listed above.

School Name

  • Only the Markings Short Line layer has a SCHOOLNAME field, which is automatically calculated based on a 1/4 mile Buffer of the Schools layer located on MAINT. If the feature intersects the layer on creation, the SCHOOLNAME field is calculated based on the SCHOOL_NAME field in the 1/4 mile Buffer of the Schools layer.

  • If there are other stipulations for changing the value, the field is editable and can be changed.

  • Triggers - Insert

  • Execution - Exclude application evaluation

High Injury Network

  • All layers except the Markings Long Line layer have a HIN field, which is automatically calculated based on the High Injury Network Combined layer located in MAINT. If the feature is within a specified buffer distance, the HIN field is calculated to Yes, otherwise No.

  • Since each buffer is not perfect for calculating 100% of the features, the field is editable and can be changed.

  • Triggers - Insert

  • Execution - Exclude application evaluation

Short Line

  • The Short Line buffer is large as all features located at an intersection where one or both streets are on the High Injury Network are calculated to Yes on the HIN field

Specialty Line / Point

  • The attribute rule for calculating the HIN field for Specialty Line and Point is identical

Last updated

Was this helpful?