Road conditions
Road Conditions must be sent as POINT data.
| Element | Required | Data Type | Description |
||
|---|---|---|---|---|---|
error |
Yes | String | 980 for Road Conditions |
||
details |
Yes | String | Free text description of the obstacle on the road |
||
domain |
Yes | Object | Road Conditions Request structure with the following attributes encoded |
||
↳ type |
Yes | Integer | Main differentiator of road conditions. 1 for condition type Physical Road Conditions |
||
↳ subType |
Yes | Integer | Condition subtype For possible values, see the table below. |
||
↳ surface |
Yes | Integer |
Surface type, possible values are:
|
||
↳ lanenumber |
No | Integer, Array | Affected lanes, for example |
||
↳ severity |
No | Integer | Severity of the reported road conditions, possible values: 1-100, *not* applicable to requests specifying the following subtypes: 1, 10, 11, 20, 30, 31, 41, 43, 100 |
||
↳ rev |
Yes | Boolean | Specific direction of the link |
||
↳ timeconstraint |
No | Object | Specification of the time constraint |
||
↳ type |
Yes | String |
Property of object
|
||
↳ from |
Yes | String | Start date or date of first recognition in the format "YYYY-MM-DD", property of object |
||
↳ to |
No | String | End date in the format "YYYY-MM-DD", property of object |
||
Condition subtype
The following tables describe the values for subType
| Code | Description |
|---|---|
| 1 | Pothole |
| 10 | Missing speedbump |
| 20 | New pavement applied |
| 30 | Paved |
| 31 | Not paved |
| 40 | Drainage gully missing |
| 41 | Drainage gully removed |
| 42 | Drainage channel missing |
| 43 | Drainage channel removed |
| 60 | Lane grooves |
| 70 | Cattle stop |
| 80 | Railway crossing |
| 81 | Ford |
| 100 | Lane damaged |
Updated last month