Newer
Older
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
### <a name="Angle"></a>Angle
This DE is used to describe an angular measurement in units of degrees. This data
element is often used as a heading direction when in motion. In this use, the current heading of the sending device is
expressed in unsigned units of 0.0125 degrees from North, such that 28799 such degrees represent 359.9875 degrees.
North shall be defined as the axis defined by the WGS-84 coordinate system and its reference ellipsoid. Any angle "to the
east" is defined as the positive direction. A value of 28800 shall be used when Angle is unavailable.
**Unit:** _0.0125 degrees_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Note that other heading and angle data elements of various sizes and precisions are found in other parts of this standard and in ITS.
>>>
```asn1
Angle ::= INTEGER (0..28800)
```
### <a name="ApproachID"></a>ApproachID
This DE is used to relate the index of an approach, either ingress or egress within the
subject lane. In general, an approach index in the context of a timing movement is not of value in the MAP and SPAT
process because the lane ID and signal group ID concepts handle this with more precision. This value can also be useful
as an aid as it can be used to indicate the gross position of a moving object (vehicle) when its lane level accuracy is
unknown. This value can also be used when a deployment represents sets of lanes as groups without further details (as is
done in Japan).
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: zero to be used when valid value is unknown
>>>
```asn1
ApproachID ::= INTEGER (0..15)
```
### <a name="BasicVehicleRole"></a>BasicVehicleRole
This DE provides a means to indicate the current role that a DSRC device is playing
This is most commonly employed when a vehicle needs to take on another role in order to send certain DSRC message
types. As an example, when a public safety vehicle such as a police car wishes to send a signal request message (SRM)
to an intersection to request a preemption service, the vehicle takes on the role "police" from the below list in both the
SRM message itself and also in the type of security CERT which is sent (the SSP in the CERT it used to identify the
requester as being of type "police" and that they are allowed to send this message in this way). The BasicVehicleRole
entry is often used and combined with other information about the requester as well, such as details of why the request is
being made.
- 0 - `basicVehicle` - Light duty passenger vehicle type
- 1 - `publicTransport` - Used in EU for Transit us
- 2 - `specialTransport` - Used in EU (e.g. heavy load)
- 3 - `dangerousGoods` - Used in EU for any HAZMAT
- 4 - `roadWork` - Used in EU for State and Local DOT uses
- 5 - `roadRescue` - Used in EU and in the US to include tow trucks.
- 6 - `emergency` - Used in EU for Police, Fire and Ambulance units
- 7 - `safetyCar` - Used in EU for Escort vehicles
- 8 - `none-unknown` - added to follow current SAE style guidelines
- 9 - `truck` - Heavy trucks with additional BSM rights and obligations
- 10 - `motorcycle` - Motorcycle
- 11 - `roadSideSource` - For infrastructure generated calls such as fire house, rail infrastructure, roadwork site, etc.
- 12 - `police` - Police vehicle
- 13 - `fire` - Firebrigade
- 14 - `ambulance` - (does not include private para-transit etc.)
- 15 - `dot` - all roadwork vehicles
- 16 - `transit` - all transit vehicles
- 17 - `slowMoving` - to also include oversize etc.
- 18 - `stopNgo` - to include trash trucks, school buses and others
- 19 - `cyclist` - bicycles
- 20 - `pedestrian` - also includes those with mobility limitations
- 21 - `nonMotorized` - other, horse drawn, etc.
- 22 - `military` - military vehicles
Values:
* **basicVehicle** (0)<br>
* **publicTransport** (1)<br>
* **specialTransport** (2)<br>
* **dangerousGoods** (3)<br>
* **roadWork** (4)<br>
* **roadRescue** (5)<br>
* **emergency** (6)<br>
* **safetyCar** (7)<br>
* **none-unknown** (8)<br>
* **truck** (9)<br>
* **motorcycle** (10)<br>
* **roadSideSource** (11)<br>
* **police** (12)<br>
* **fire** (13)<br>
* **ambulance** (14)<br>
* **dot** (15)<br>
* **transit** (16)<br>
* **slowMoving** (17)<br>
* **stopNgo** (18)<br>
* **cyclist** (19)<br>
* **pedestrian** (20)<br>
* **nonMotorized** (21)<br>
* **military** (22)<br>
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: It should be observed that devices can at times change their roles (i.e. a fire operated by a volunteer
fireman can assume a fire role for a period of time when in service, or a pedestrian may assume a cyclist role when using
a bicycle). It should be observed that not all devices (or vehicles) can assume all roles, nor that a given
device in a given role will be provided with a security certificate (CERT) that has suitable SSP credentials to provide the
ability to send a particular message or message content. The ultimate responsibility to determine what role is to be used,
and what CERTs would be provided for that role (which in turn controls the messages and message content that can be
sent within SAE-defined PSIDs) rests with the regional deployment.
>>>
```asn1
BasicVehicleRole ::= ENUMERATED {
basicVehicle (0),
publicTransport (1),
specialTransport (2),
dangerousGoods (3),
roadWork (4),
roadRescue (5),
emergency (6),
safetyCar (7),
none-unknown (8),
truck (9),
motorcycle (10),
roadSideSource (11),
police (12),
fire (13),
ambulance (14),
dot (15),
transit (16),
slowMoving (17),
stopNgo (18),
cyclist (19),
pedestrian (20),
nonMotorized (21),
military (22),
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
}
```
### <a name="DDay"></a>DDay
The DSRC style day is a simple value consisting of integer values from zero to 31. The value of zero shall represent an unknown value.
**Unit:** _days_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DDay ::= INTEGER (0..31)
```
### <a name="DeltaAngle"></a>DeltaAngle
This DE provides the final angle used in the last point of the lane path. Used to "cant" the stop line of the lane.
With an angle range from negative 150 to positive 150 in one degree steps where zero is directly
along the axis or the lane center line as defined by the two closest points.
**Unit:** _degree_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DeltaAngle ::= INTEGER (-150..150)
```
### <a name="DeltaTime"></a>DeltaTime
This DE provides a time definition for an object's schedule adherence (typically a transit
vehicle) within a limited range of time. When the reporting object is ahead of schedule, a positive value is used; when
behind, a negative value is used. A value of zero indicates schedule adherence. This value is typically sent from a vehicle
to the traffic signal controller's RSU to indicate the urgency of a signal request in the context of being within schedule or
not. In another use case, the traffic signal controller may advise the transit vehicle to speed up (DeltaTime > 0) or to slow
down (DeltaTime < 0) to optimize the transit vehicle distribution driving along a specific route (e.g. a Bus route).
Supporting a range of +/- 20 minute in steps of 10 seconds:
- the value of `-121` shall be used when more than -20 minutes
- the value of `+120` shall be used when more than +20 minutes
- the value `-122` shall be used when the value is unavailable
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DeltaTime ::= INTEGER (-122 .. 121)
```
### <a name="DescriptiveName"></a>DescriptiveName
This DE is used in maps and intersections to provide a human readable and
recognizable name for the feature that follows. It is typically used when debugging a data flow and not in production use.
One key exception to this general rule is to provide a human-readable string for disabled travelers in the case of
crosswalks and sidewalk lane objects.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DescriptiveName ::= IA5String (SIZE(1..63))
```
### <a name="DHour"></a>DHour
The DSRC hour consists of integer values from zero to 23 representing the hours within a day. The value of 31 shall
represent an unknown value. The range 24 to 30 is used in some transit applications to represent schedule adherence.
**Unit:** _hours_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DHour ::= INTEGER (0..31)
```
### <a name="DMinute"></a>DMinute
The DSRC style minute is a simple value consisting of integer values from zero to 59 representing the minutes
within an hour. The value of 60 shall represent an unknown value.
**Unit:** _minutes_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DMinute ::= INTEGER (0..60)
```
### <a name="DMonth"></a>DMonth
The DSRC month consists of integer values from one to 12, representing the month within a year. The value of 0
shall represent an unknown value.
**Unit:** _months_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DMonth ::= INTEGER (0..12)
```
### <a name="DOffset"></a>DOffset
The DSRC (time zone) offset consists of a signed integer representing an hour and minute value set from -14:00 to
+14:00, representing all the worldâs local time zones in units of minutes. The value of zero (00:00) may also represent an
unknown value. Note some time zones are do not align to hourly boundaries.
**Unit:** _minutes from UTC time_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DOffset ::= INTEGER (-840..840)
```
### <a name="DrivenLineOffsetLg"></a>DrivenLineOffsetLg
This DE is an integer value expressing the offset in a defined axis from a
reference lane number from which a computed lane is offset. The measurement is taken from the reference lane center
line to the new center line, independent of any width values. The units are a signed value with an LSB of 1 cm.
**Unit:** _cm_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DrivenLineOffsetLg ::= INTEGER (-32767..32767)
```
### <a name="DrivenLineOffsetSm"></a>DrivenLineOffsetSm
The DrivenLineOffsetSmall data element is an integer value expressing the offset in a defined axis from a reference
lane number from which a computed lane is offset. The measurement is taken from the reference lane center line to the
new center line, independent of any width values. The units are a signed value with an LSB of 1 cm.
**Unit:** _cm_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DrivenLineOffsetSm ::= INTEGER (-2047..2047)
```
### <a name="DSecond"></a>DSecond
The DSRC second expressed in this DE consists of integer values from zero to 60999, representing the
milliseconds within a minute. A leap second is represented by the value range 60000 to 60999. The value of 65535 shall
represent an unavailable value in the range of the minute. The values from 61000 to 65534 are reserved.
**Unit:** _milliseconds_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DSecond ::= INTEGER (0..65535)
```
### <a name="DYear"></a>DYear
The DSRC year consists of integer values from zero to 4095 representing the year according to the Gregorian
calendar date system. The value of zero shall represent an unknown value.
**Unit:** _years_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
DYear ::= INTEGER (0..4095)
```
### <a name="Elevation"></a>Elevation
This DE represents the geographic position above or below the reference ellipsoid (typically WGS-84).
The number has a resolution of 1 decimeter and represents an asymmetric range of positive and negative
values. Any elevation higher than +6143.9 meters is represented as +61439.
Any elevation lower than -409.5 meters is represented as -4095.
If the sending device does not know its elevation, it shall encode the Elevation data element with -4096.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: When a vehicle is being measured, the elevation is taken from the horizontal spatial center of the vehicle
projected downward, regardless of vehicle tilt, to the point where the vehicle meets the road surface.
>>>
```asn1
Elevation ::= INTEGER (-4096..61439)
```
### <a name="ElevationConfidence"></a>ElevationConfidence
This DE is used to provide the 95% confidence level for the currently reported value of [**Elevation**](#Elevation),
taking into account the current calibration and precision of the sensor(s) used to measure and/or
calculate the value. This data element is only to provide the listener with information on the limitations of the sensing
system, not to support any type of automatic error correction or to imply a guaranteed maximum error. This data element
should not be used for fault detection or diagnosis, but if a vehicle is able to detect a fault, the confidence interval should
be increased accordingly. The frame of reference and axis of rotation used shall be in accordance with that defined in Section 11.
- `unavailable` - 0: B'0000 Not Equipped or unavailable
- `elev-500-00` - 1: B'0001 (500 m)
- `elev-200-00` - 2: B'0010 (200 m)
- `elev-100-00` - 3: B'0011 (100 m)
- `elev-050-00` - 4: B'0100 (50 m)
- `elev-020-00` - 5: B'0101 (20 m)
- `elev-010-00` - 6: B'0110 (10 m)
- `elev-005-00` - 7: B'0111 (5 m)
- `elev-002-00` - 8: B'1000 (2 m)
- `elev-001-00` - 9: B'1001 (1 m)
- `elev-000-50` - 10: B'1010 (50 cm)
- `elev-000-20` - 11: B'1011 (20 cm)
- `elev-000-10` - 12: B'1100 (10 cm)
- `elev-000-05` - 13: B'1101 (5 cm)
- `elev-000-02` - 14: B'1110 (2 cm)
- `elev-000-01` - 15: B'1111 (1 cm)
Values:
* **unavailable** (0)<br>
* **elev-500-00** (1)<br>
* **elev-200-00** (2)<br>
* **elev-100-00** (3)<br>
* **elev-050-00** (4)<br>
* **elev-020-00** (5)<br>
* **elev-010-00** (6)<br>
* **elev-005-00** (7)<br>
* **elev-002-00** (8)<br>
* **elev-001-00** (9)<br>
* **elev-000-50** (10)<br>
* **elev-000-20** (11)<br>
* **elev-000-10** (12)<br>
* **elev-000-05** (13)<br>
* **elev-000-02** (14)<br>
* **elev-000-01** (15)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Encoded as a 4 bit value
>>>
```asn1
ElevationConfidence ::= ENUMERATED {
unavailable (0),
elev-500-00 (1),
elev-200-00 (2),
elev-100-00 (3),
elev-050-00 (4),
elev-020-00 (5),
elev-010-00 (6),
elev-005-00 (7),
elev-002-00 (8),
elev-001-00 (9),
elev-000-50 (10),
elev-000-20 (11),
elev-000-10 (12),
elev-000-05 (13),
elev-000-02 (14),
elev-000-01 (15)
}
```
### <a name="FuelType"></a>FuelType
This DE provides the type of fuel used by a vehicle.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
FuelType ::= INTEGER (0..15)
unknownFuel FuelType ::= 0
gasoline FuelType ::= 1
ethanol FuelType ::= 2
diesel FuelType ::= 3
electric FuelType ::= 4
hybrid FuelType ::= 5
hydrogen FuelType ::= 6
natGasLiquid FuelType ::= 7
natGasComp FuelType ::= 8
propane FuelType ::= 9
```
### <a name="GNSSstatus"></a>GNSSstatus
This DE is used to relate the current state of a GPS/GNSS rover or base system in terms
of its general health, lock on satellites in view, and use of any correction information. Various bits can be asserted (made
to a value of one) to reflect these values. A GNSS set with unknown health and no tracking or corrections would be
represented by setting the unavailable bit to one. A value of zero shall be used when a defined data element is
unavailable. The term "GPS" in any data element name in this standard does not imply that it is only to be used for GPS-
type GNSS systems.
- `unavailable` - 0: Not Equipped or unavailable
- `isHealthy` - 1:
- `isMonitored` - 2:
- `baseStationType` - 3: Set to zero if a moving base station, or if a rover device (an OBU), Set to one if it is a fixed base station
- `aPDOPofUnder5` - 4: A dilution of precision greater than 5
- `inViewOfUnder5` - 5: Less than 5 satellites in view
- `localCorrectionsPresent` - 6: DGPS type corrections used
- `networkCorrectionsPresen` - 7: RTK type corrections used
Values:
* **unavailable** (0)<br>
* **isHealthy** (1)<br>
* **isMonitored** (2)<br>
* **baseStationType** (3)<br>
* **aPDOPofUnder5** (4)<br>
* **inViewOfUnder5** (5)<br>
* **localCorrectionsPresent** (6)<br>
* **networkCorrectionsPresent** (7)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
GNSSstatus ::= BIT STRING {
unavailable (0),
isHealthy (1),
isMonitored (2),
baseStationType (3),
aPDOPofUnder5 (4),
inViewOfUnder5 (5),
localCorrectionsPresent (6),
networkCorrectionsPresent (7)
} (SIZE(8))
```
### <a name="HeadingConfidenceDSRC"></a>HeadingConfidenceDSRC
The DE_HeadingConfidence data element is used to provide the 95% confidence level for the currently reported
calculate the value. This data element is only to provide the listener with information on the limitations of the sensing
value of DE_Heading, taking into account the current calibration and precision of the sensor(s) used to measure and/or
system, not to support any type of automatic error correction or to imply a guaranteed maximum error. This data element
should not be used for fault detection or diagnosis, but if a vehicle is able to detect a fault, the confidence interval should
be increased accordingly. The frame of reference and axis of rotation used shall be in accordance with that defined Section 11.
- `unavailable` - 0: B'000 Not Equipped or unavailable
- `prec10deg` - 1: B'010 10 degrees
- `prec05deg` - 2: B'011 5 degrees
- `prec01deg` - 3: B'100 1 degrees
- `prec0-1deg` - 4: B'101 0.1 degrees
- `prec0-05deg` - 5: B'110 0.05 degrees
- `prec0-01deg` - 6: B'110 0.01 degrees
- `prec0-0125deg` - 7: B'111 0.0125 degrees, aligned with heading LSB
Values:
* **unavailable** (0)<br>
* **prec10deg** (1)<br>
* **prec05deg** (2)<br>
* **prec01deg** (3)<br>
* **prec0-1deg** (4)<br>
* **prec0-05deg** (5)<br>
* **prec0-01deg** (6)<br>
* **prec0-0125deg** (7)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
HeadingConfidenceDSRC ::= ENUMERATED {
unavailable (0),
prec10deg (1),
prec05deg (2),
prec01deg (3),
prec0-1deg (4),
prec0-05deg (5),
prec0-01deg (6),
prec0-0125deg (7)
}
```
### <a name="HeadingDSRC"></a>HeadingDSRC
This DE provides the current heading of the sending device, expressed in unsigned units of
0.0125 degrees from North such that 28799 such degrees represent 359.9875 degrees. North shall be defined as the axis
prescribed by the WGS-84 coordinate system and its reference ellipsoid. Headings "to the east" are defined as the
positive direction. A value of 28800 shall be used when unavailable. This element indicates the direction of motion of the
device. When the sending device is stopped and the trajectory (path) over which it traveled to reach that location is well
known, the past heading may be used.
Value provides a range of 0 to 359.9875 degrees
and in ITS. This element should no longer be used for new work: the [**Angle**](#Angle) entry is preferred.
**Unit:** _0.0125 degrees_
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
HeadingDSRC ::= INTEGER (0..28800)
```
### <a name="IntersectionID"></a>IntersectionID
This DE is used within a region to uniquely define an intersection within that country or region in a 16-bit
field. Assignment rules are established by the regional authority associated with the RoadRegulatorID under which this
IntersectionID is assigned. Within the region the policies used to ensure an assigned valueâs uniqueness before that value
is reused (if ever) is the responsibility of that region. Any such reuse would be expected to occur over a long epoch (many years).
The values zero through 255 are allocated for testing purposes
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: Note that the value assigned to an intersection will be unique within a given regional ID only
>>>
```asn1
IntersectionID ::= INTEGER (0..65535)
```
### <a name="IntersectionStatusObject"></a>IntersectionStatusObject
The Intersection Status Object contains Advanced Traffic Controller (ATC) status information that may be sent to
local OBUs as part of the SPAT process.
With bits as defined:
- `manualControlIsEnabled` - 0: Timing reported is per programmed values, etc. but person at cabinet can manually request that certain intervals are terminated early (e.g. green).
- `stopTimeIsActivated` - 1: And all counting/timing has stopped.
- `failureFlash` - 2: Above to be used for any detected hardware failures, e.g. conflict monitor as well as for police flash
- `fixedTimeOperation` - 5: Schedule of signals is based on time only (i.e. the state can be calculated)
- `trafficDependentOperation` - 6: Operation is based on different levels of traffic parameters (requests, duration of gaps or more complex parameters)
- `standbyOperation` - 7: Controller: partially switched off or partially amber flashing
- `failureMode` - 8: Controller has a problem or failure in operation
- `off` - 9: Controller is switched off
- `recentMAPmessageUpdate` - 10: Map revision with content changes
- `recentChangeInMAPassignedLanesIDsUsed` - 11: Change in MAP's assigned lanes used (lane changes) Changes in the active lane list description
- `noValidMAPisAvailableAtThisTime` - 12: MAP (and various lanes indexes) not available
- `noValidSPATisAvailableAtThisTime` - 13: SPAT system is not working at this time
- Bits 14,15 reserved at this time and shall be zero
Values:
* **manualControlIsEnabled** (0)<br>
* **stopTimeIsActivated** (1)<br>
* **failureFlash** (2)<br>
* **preemptIsActive** (3)<br>
* **signalPriorityIsActive** (4)<br>
* **fixedTimeOperation** (5)<br>
* **trafficDependentOperation** (6)<br>
* **standbyOperation** (7)<br>
* **failureMode** (8)<br>
* **off** (9)<br>
* **recentMAPmessageUpdate** (10)<br>
* **recentChangeInMAPassignedLanesIDsUsed** (11)<br>
* **noValidMAPisAvailableAtThisTime** (12)<br>
* **noValidSPATisAvailableAtThisTime** (13)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: All zeros indicate normal operating mode with no recent changes. The duration of the term 'recent' is defined by the system performance requirement in use.
>>>
```asn1
IntersectionStatusObject ::= BIT STRING {
manualControlIsEnabled (0),
stopTimeIsActivated (1),
failureFlash (2),
preemptIsActive (3),
signalPriorityIsActive (4),
fixedTimeOperation (5),
trafficDependentOperation (6),
standbyOperation (7),
failureMode (8),
off (9),
recentMAPmessageUpdate (10),
recentChangeInMAPassignedLanesIDsUsed (11),
noValidMAPisAvailableAtThisTime (12),
noValidSPATisAvailableAtThisTime (13)
} (SIZE(16))
```
### <a name="LaneAttributes-Barrier"></a>LaneAttributes-Barrier
This DE relates specific properties found in a Barrier or Median lane type (a type of lane object used to separate traffic lanes).
It should be noted that various common lane attribute properties (such as travel directions and allowed movements or maneuvers) can be found in other entries.
With bits as defined:
- `median-RevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
Values:
* **median-RevocableLane** (0)<br>
* **median** (1)<br>
* **whiteLineHashing** (2)<br>
* **stripedLines** (3)<br>
* **doubleStripedLines** (4)<br>
* **trafficCones** (5)<br>
* **constructionBarrier** (6)<br>
* **trafficChannels** (7)<br>
* **lowCurbs** (8)<br>
* **highCurbs** (9)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Barrier ::= BIT STRING {
median-RevocableLane (0),
median (1),
whiteLineHashing (2),
stripedLines (3),
doubleStripedLines (4),
trafficCones (5),
constructionBarrier (6),
trafficChannels (7),
lowCurbs (8),
highCurbs (9)
} (SIZE (16))
```
### <a name="LaneAttributes-Bike"></a>LaneAttributes-Bike
This DE relates specific properties found in a bicycle lane type. It should be noted that various common lane attribute properties
(such as travel directions and allowed movements or maneuvers) can be found in other entries.
With bits as defined:
- `bikeRevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present
- `pedestrianUseAllowed` - 1: The path allows pedestrian traffic, if not set, this mode is prohibited
- `isBikeFlyOverLane` - 2: path of lane is not at grade
- `fixedCycleTime` - 3: the phases use preset times, i.e. there is not a 'push to cross' button
- `biDirectionalCycleTimes` - 4: ped walk phases use different SignalGroupID for each direction. The first SignalGroupID in the first Connection
represents 'inbound' flow (the direction of travel towards the first node point) while second SignalGroupID in the
next Connection entry represents the 'outbound' flow. And use of RestrictionClassID entries in the Connect follow this same pattern in pairs.
-`isolatedByBarrier` - 5: The lane path is isolated by a fixed barrier
-`unsignalizedSegmentsPresent` - 6: The lane path consists of one of more segments which are not part of a signal group ID
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
Values:
* **bikeRevocableLane** (0)<br>
* **pedestrianUseAllowed** (1)<br>
* **isBikeFlyOverLane** (2)<br>
* **fixedCycleTime** (3)<br>
* **biDirectionalCycleTimes** (4)<br>
* **isolatedByBarrier** (5)<br>
* **unsignalizedSegmentsPresent** (6)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Bike ::= BIT STRING {
bikeRevocableLane (0),
pedestrianUseAllowed (1),
isBikeFlyOverLane (2),
fixedCycleTime (3),
biDirectionalCycleTimes (4),
isolatedByBarrier (5),
unsignalizedSegmentsPresent (6)
} (SIZE (16))
```
### <a name="LaneAttributes-Crosswalk"></a>LaneAttributes-Crosswalk
This DE relates specific properties found in a crosswalk lane type. It should be noted that various common lane attribute properties
(such as travel directions and allowed movements or maneuvers) can be found in other entries.
With bits as defined:
- `crosswalkRevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present
- `bicyleUseAllowed` - 1: The path allows bicycle traffic, if not set, this mode is prohibited
- `isXwalkFlyOverLane` - 2: path of lane is not at grade
- `fixedCycleTime` - 3: ped walk phases use preset times. i.e. there is not a 'push to cross' button
- `biDirectionalCycleTimes` - 4: ped walk phases use different SignalGroupID for each direction. The first SignalGroupID
in the first Connection represents 'inbound' flow (the direction of travel towards the first
node point) while second SignalGroupID in the next Connection entry represents the 'outbound'
flow. And use of RestrictionClassID entries in the Connect follow this same pattern in pairs.
- `hasPushToWalkButton` - 5: Has a demand input
- `audioSupport` - 6: audio crossing cues present
- `rfSignalRequestPresent` - 7: Supports RF push to walk technologies
- `unsignalizedSegmentsPresent` - 8: The lane path consists of one of more segments which are not part of a signal group ID
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
Values:
* **crosswalkRevocableLane** (0)<br>
* **bicyleUseAllowed** (1)<br>
* **isXwalkFlyOverLane** (2)<br>
* **fixedCycleTime** (3)<br>
* **biDirectionalCycleTimes** (4)<br>
* **hasPushToWalkButton** (5)<br>
* **audioSupport** (6)<br>
* **rfSignalRequestPresent** (7)<br>
* **unsignalizedSegmentsPresent** (8)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Crosswalk ::= BIT STRING {
crosswalkRevocableLane (0),
bicyleUseAllowed (1),
isXwalkFlyOverLane (2),
fixedCycleTime (3),
biDirectionalCycleTimes (4),
hasPushToWalkButton (5),
audioSupport (6),
rfSignalRequestPresent (7),
unsignalizedSegmentsPresent (8)
} (SIZE (16))
```
### <a name="LaneAttributes-Parking"></a>LaneAttributes-Parking
This DE relates specific properties found in a vehicle parking lane type. It should be noted that various common lane attribute
properties can be found in other entries.
With bits as defined:
- `parkingRevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present
- `doNotParkZone` - 3: used to denote fire hydrants as well as short disruptions in a parking zone
- `noPublicParkingUse` - 6: private parking, as in front of private property
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
Values:
* **parkingRevocableLane** (0)<br>
* **parallelParkingInUse** (1)<br>
* **headInParkingInUse** (2)<br>
* **doNotParkZone** (3)<br>
* **parkingForBusUse** (4)<br>
* **parkingForTaxiUse** (5)<br>
* **noPublicParkingUse** (6)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Parking ::= BIT STRING {
parkingRevocableLane (0),
parallelParkingInUse (1),
headInParkingInUse (2),
doNotParkZone (3),
parkingForBusUse (4),
parkingForTaxiUse (5),
noPublicParkingUse (6)
} (SIZE (16))
```
### <a name="LaneAttributes-Sidewalk"></a>LaneAttributes-Sidewalk
This DE relates specific properties found in a sidewalk lane type. It should be noted that various common lane attribute properties
(such as travel directions and allowed movements or maneuvers) can be found in other entries.
With bits as defined:
- `sidewalk-RevocableLane`- 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present.
- `bicyleUseAllowed` - 1: The path allows bicycle traffic, if not set, this mode is prohibited
- `isSidewalkFlyOverLane` - 2: path of lane is not at grade
- `walkBikes` - 3: bike traffic must dismount and walk
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
Values:
* **sidewalk-RevocableLane** (0)<br>
* **bicyleUseAllowed** (1)<br>
* **isSidewalkFlyOverLane** (2)<br>
* **walkBikes** (3)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Sidewalk ::= BIT STRING {
sidewalk-RevocableLane (0),
bicyleUseAllowed (1),
isSidewalkFlyOverLane (2),
walkBikes (3)
} (SIZE (16))
```
### <a name="LaneAttributes-Striping"></a>LaneAttributes-Striping
This DE relates specific properties found in various types of ground striping lane
types. This includes various types of painted lane ground striping and iconic information needs to convey information in a
complex intersection. Typically, this consists of visual guidance for drivers to assist them to connect across the
intersection to the correct lane. Such markings are typically used with restraint and only under conditions when the
geometry of the intersection makes them more beneficial than distracting. It should be noted that various common lane
attribute properties (such as travel directions and allowed movements or maneuvers) can be found in other entries.
With bits as defined:
- `stripeToConnectingLanesRevocableLane` - 0: this lane may be activated or not activated based on the current SPAT message contents if not asserted, the lane is ALWAYS present
- `stripeToConnectingLanesAhead` - 5: the stripe type should be presented to the user visually to reflect stripes in the intersection for the type of movement indicated.
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
Values:
* **stripeToConnectingLanesRevocableLane** (0)<br>
* **stripeDrawOnLeft** (1)<br>
* **stripeDrawOnRight** (2)<br>
* **stripeToConnectingLanesLeft** (3)<br>
* **stripeToConnectingLanesRight** (4)<br>
* **stripeToConnectingLanesAhead** (5)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Striping ::= BIT STRING {
stripeToConnectingLanesRevocableLane (0),
stripeDrawOnLeft (1),
stripeDrawOnRight (2),
stripeToConnectingLanesLeft (3),
stripeToConnectingLanesRight (4),
stripeToConnectingLanesAhead (5)
} (SIZE (16))
```
### <a name="LaneAttributes-TrackedVehicle"></a>LaneAttributes-TrackedVehicle
This DE relates specific properties found in a tracked vehicle lane types (trolley
and train lanes). The term ârail vehicleâ can be considered synonymous. In this case, the term does not relate to vehicle
types with tracks or treads. It should be noted that various common lane attribute properties (such as travel directions and
allowed movements or maneuvers) can be found in other entries. It should also be noted that often this type of lane object
does not clearly relate to an approach in the traditional traffic engineering sense, although the message set allows
assigning a value when desired.
With bits as defined:
- `spec-RevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present.
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
Values:
* **spec-RevocableLane** (0)<br>
* **spec-commuterRailRoadTrack** (1)<br>
* **spec-lightRailRoadTrack** (2)<br>
* **spec-heavyRailRoadTrack** (3)<br>
* **spec-otherRailType** (4)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-TrackedVehicle ::= BIT STRING {
spec-RevocableLane (0),
spec-commuterRailRoadTrack (1),
spec-lightRailRoadTrack (2),
spec-heavyRailRoadTrack (3),
spec-otherRailType (4)
} (SIZE (16))
```
### <a name="LaneAttributes-Vehicle"></a>LaneAttributes-Vehicle
This DE relates specific properties found in a vehicle lane type. This data element provides a means to denote that the use of a lane
is restricted to certain vehicle types. Various common lane attribute properties (such as travel directions and allowed movements or maneuvers)
can be found in other entries.
With bits as defined:
- `isVehicleRevocableLane` - 0: this lane may be activated or not based on the current SPAT message contents if not asserted, the lane is ALWAYS present
- `isVehicleFlyOverLane` - 1: path of lane is not at grade
- `permissionOnRequest` - 7: e.g. to inform about a lane for e-cars
Values:
* **isVehicleRevocableLane** (0)<br>
* **isVehicleFlyOverLane** (1)<br>
* **hovLaneUseOnly** (2)<br>
* **restrictedToBusUse** (3)<br>
* **restrictedToTaxiUse** (4)<br>
* **restrictedFromPublicUse** (5)<br>
* **hasIRbeaconCoverage** (6)<br>
* **permissionOnRequest** (7)<br>
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneAttributes-Vehicle ::= BIT STRING {
isVehicleRevocableLane (0),
isVehicleFlyOverLane (1),
hovLaneUseOnly (2),
restrictedToBusUse (3),
restrictedToTaxiUse (4),
restrictedFromPublicUse (5),
hasIRbeaconCoverage (6),
permissionOnRequest (7)
} (SIZE (8,...))
```
### <a name="LaneConnectionID"></a>LaneConnectionID
This DE is used to state a connection index for a lane to lane connection. It is used to
relate this connection between the lane (defined in the MAP) and any dynamic clearance data sent in the SPAT. It should
be noted that the index may be shared with other lanes (for example, two left turn lanes may share the same dynamic
clearance data). It should also be noted that a given lane to lane connection may be part of more than one GroupID due
to signal phase considerations, but will only have one ConnectionID. The ConnectionID concept is not used (is not
present) when dynamic clearance data is not provided in the SPAT.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: It should be noted that the LaneConnectionID is used as a means to index to a connection description
between two lanes. It is not the same as the laneID, which is the unique index to each lane itself.
>>>
```asn1
LaneConnectionID ::= INTEGER (0..255)
```
### <a name="LaneDirection"></a>LaneDirection
This DE is used to denote the allowed direction of travel over a lane object. By convention, the lane object is always described
from the stop line outwards away from the intersection. Therefore, the ingress direction is from the end of the path to the stop
line and the egress direction is from the stop line outwards.
It should be noted that some lane objects are not used for travel and that some lane objects allow bi-directional travel.
With bits as defined:
- Allowed directions of travel in the lane object
- All lanes are described from the stop line outwards
Values:
* **ingressPath** (0)<br>
travel from rear of path to front is allowed
* **egressPath** (1)<br>
travel from front of path to rear is allowed
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
>>>
NOTE: No Travel, i.e. the lane object type does not support travel (medians, curbs, etc.) is indicated by not
asserting any bit value Bi-Directional Travel (such as a ped crosswalk) is indicated by asserting both of the bits.
>>>
```asn1
LaneDirection ::= BIT STRING {
ingressPath (0),
egressPath (1)
} (SIZE (2))
```
### <a name="LaneID"></a>LaneID
This DE conveys an assigned index that is unique within an intersection. It is used to refer to
that lane by other objects in the intersection map data structure. Lanes may be ingress (inbound traffic) or egress
(outbound traffic) in nature, as well as barriers and other types of specialty lanes. Each lane (each lane object) is
assigned a unique ID. The Lane ID, in conjunction with the intersection ID, forms a regionally unique way to address a
specific lane in that region.
- the value 0 shall be used when the lane ID is not available or not known
- the value 255 is reserved for future use
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LaneID ::= INTEGER (0..255)
```
### <a name="LayerID"></a>LayerID
Large [**MapData**](#MapData) descriptions are not possible to be broadcast with a single message and have to be
fragmented using two or more messages over the air. Therefore, the LayerID allows defining an
index for fragmentation of large [**MapData**](#MapData) descriptions. The fragmentation of the messages shall be
executed on application layer. The fragmentation occurs on an approach base. This means that almost a
complete approach (e.g. lanes, connectsTo, etc.) has to be included within a fragment.
The decimal value of the `layerID` is used to define the amount of maximum [**MapData**](#MapData) fragments. The
lower value defines the actual fragment.
Example:
If a MapData consists of three fragments (e.g. three approaches), the fragments are identified as follows:
- `31` - first fragment of three (e.g. approach south);
- `33` - third fragment of three (e.g. approach north).
- `32` - second fragment of three (e.g. approach west);
If there are only two fragments, the fragment identification will be 21, 22.
**Categories:** Infrastructure information
**Revision:** _V1.3.1_
```asn1
LayerID ::= INTEGER (0..100)