|
SegmentId
|
Unique ID for the Segment |
| SegmentName |
Name that describe the segment's location. The first part of the segment name is the Highway Number (3 digits) Direction (1 digit) and Mile-marker (3 digits and start) of the Segment. The next is the common descriptive name.
Segment's are unique, have only 1 direction and do not overlap. |
| SegmentType |
Four types exist in cotrip: Highway, Arterial, Frontage and HOV. Currently only Highway and Arterial types are implemented. |
| RoadName |
Highway road name |
| Direction |
Only 1 per segment. Values include: North, South, East and West |
| SpeedLimit |
Segment's have 1 speed limit. If there are physically 2 speed limits on the actual roadway, the segment will use the lower one. For example, if the speed limit changes in the middle of the segment, the system will use the lower one |
| Length |
In miles, the length of the segment. This is the actual distance when driven by a calibrated car and not necessarily the difference between the start and end-milemarker of the segment |
| StartMileMarker |
Mile-marker at the start of the segment |
| EndMileMarker |
Mile-marker at the end of the segment |
| Status |
Only enabled segments will be available through this api. The other value is 'disabled' and these segments will not be available. |
| ExpectedTravelTime |
The current expected or estimated travel time for the segment. This is determined by the speed algorithm. Please refer to How is Speed Calculated for more details |
| CalculatedDate |
The timestamp and date of when this segment data was calculated. This is done every two minutes |
| AverageSpeed |
In miles, the expected Average Speed of the segment. This is determined by the speed algorithm. See the link above for more. If there is a '-1' here, then it means we have no data for the segment and hence cannot calculate a speed. We need to get data at least once in 6 minutes to make this calculation. In other words, if we do not get data on a given segment for 6 minutes, its Travel Time, Average Speed etc. will be set to -1 (or no data). |
| AverageOccupancy |
In %, the Occupancy for the past 2 minutes on the segment. The occupancy is the amount of time the loop was occupied during the last 2 minutes. Note, on the highway, an occupancy of 30% or greater is considered very congested or stop-n-go traffic. This is calculated by the Speed application. |
| AverageVolume |
The number of cars that the loop counted over the past two minutes across all the lanes in that segment. This is done by the speed application as well. |
| TravelTime |
Current travel time on the segment |
| SpeedUnitOfMeasure |
Measuring unit of speed |
| AverageTrafficFlow |
This is a term that we are using to denote the congestion on arterial segments (i.e. city streets). This is represented as a %. A higher number here is better while a smaller one denote more congestion. Refer to the City Congestion section of How is Speed Calculated for more information |
| TypeTrafficFlowCd |
The AverageTrafficFlow is translated into a meaning text value that is presented on the map with a color. The values are: 1-4. |
| TypeTrafficFlowTxt |
The text value of the above mentioned code. The values are: Wide Open, Slowing, Heavy and Stop-n-go traffic flow. |
| IsSlowDown |
Used on our website to display segments that are in a slow down state (see Speed page) |
|
RouteId
|
Unique ID for the Route. A Route is a destination. It is basically a summation of all the segments in it. |
| RouteName |
Name that describe the routes's location. The first part of the name is the Highway Number (3 digits) Direction (1 digit) and Mile-marker (3 digits and start) of the route. The next is the common descriptive name.
Routes can cover more than 1 road. But will have a given direction on each road. |
| Description |
The description of the route's location. |
| Status |
Only enabled destinations (routes) will be available through this api. The other value is 'disabled' and these routes will not be available. |
| ExpectedTravelTime |
This is the summation of all the segment travel times in the route (based on the length of the segment that is in the route). Please refer to How is Speed Calculated for more details |
| CalculatedDate |
The timestamp and date of when this data was calculated. This is done every two minutes |
| AverageSpeed |
In miles, the average (expected) speed of the route. This is based on the travel times in each of the segments and the total distance traveled. If it is not know this values will be set to -1 (or no data). (For example, if even 1 segment in the entire route doesn't have data, we will set the route's data to -1). |
| RoadInfo |
Routes can have more than 1 road associated with them. |
| RoadName |
For each road, there will be a road name |
| DirectionTxt |
For each road, there will be a direction. Values include: North, South, East and West |
| DirectionCd |
The type code in our tables for the direction text |
| Length |
In miles, the length of the route. This is the actual distance when driven by a calibrated car |
Weather
Route Road Condition XML Help |
| WeatherRouteId |
Unique ID for the Weather Route. A Weather
Route is a section of roadway that CDOT provides a road condition
for. It is updated 4 times a day in the winter and once daily in the
summer |
| RouteName |
The name of the weather route (descriptive, location) |
| Status |
Will always be enabled |
| StartMileMarker |
The start mile-marker of the weather route
(highway) |
| EndMileMarker |
Mile-marker at the end of the Weather Route |
| Length |
In miles, the length of the Weather Route |
| CalculatedDate |
The timestamp and date of when the road condition
was last set (most recent) |
| RoadName |
A Weather Route can have ONLY 1 Road. This
is its Road Name. And Weather Routes do not have a direction |
| Comment |
Additional comments added by the operator |
| RoadConditionCategoryTxt |
The road condition has a category associated
with it. A Weather Route can have more than 1 road condition category
associated with it |
| RoadConditionCategoryCd |
The type code in our tables for the road condition.
See the values listed below. |
| RouteGroupTxt |
The name of the group to which weather route belongs |
| IsHazardousCondition |
We use this on CoTrip to display the weather
route in the Hazardous driving section. The business logic on our
end determines this (such as Blowing Snow, or a combination of conditions) |
| RoadCondition |
The road condition that is currently set to
the Weather Route. There can be more than 1 road condition associated
with a weather route. The values possible are:
No Data 11
Error 10
Dry 9
Scattered Showers 8
Rain 8
Wet 8
Slushy 8
High Wind 7
Poor Visibility 6
Snow 5
Snow Packed 5
Snow Packed Icy Spots 5
Icy 4
Icy Spots 4
Blowing Snow 3 |
|
Type
|
The type of Alert. The values could be: Closed, Seasonal Closure, Restriction, Partial Closure, Road Work (construction), Incident, Response and Amber Alert. An Alert can only be of one type. |
| Title |
The title of the alert. For example, Bridge Construction |
| Headline |
The short description of the alert. Includes highway, location, road name |
| Description |
The detailed description of the alert. It includes the work being done or reason for closure, any alternate route information and estimated time to clear |
| Impact |
The traffic impact of the event. The values include: Severe, Medium, Low |
| Location |
The latitude and longitude of the alert |
| ReportedTime |
The timestamp and date of when this alert was created |
| LastUpdateDate |
The timestamp and date of when this alert was last updated |
| AlertIcon |
The icon cotrip.org uses to display the alert on the map (url) |
| ExpectedEndTime |
Time/Date when alert expires |
| Direction |
The direction associated with the alert. This is the text representation of TypeDirectionCode |
| DirectionType |
The direction code associated with the alert |
| RoadName |
The road name that the alert is on. There can be only 1 road name for a given alert |
| StartMileMarker |
Mile-marker at the start of the alert |
| EndMileMarker |
Mile-marker at the end of the alert |
| IsBothDirectionFlg |
Alert is valid for both direction. Value is true for bidirectional alert |
| Images |
Images that are associated with each alert. There can be several images for each alert |
|
| Location |
The latitude and longitude of the Camera |
| CameraId |
Unique ID for the Camera |
| CameraType |
The type of Camera. The values could be: Still,
Streaming, Camera Tour. Note: Streaming camera content is not currently
available through this API. The system block's this content from being
rendered from outside cotrip |
| Name |
The name of the Camera (descriptive, location) |
| Description |
A more descriptive name for the camera |
| Status |
Will always be enabled |
| IsWeatherStation |
If this camera is part of a weather station,
this will be checked (weather station cameras are of type still) |
| Source |
Which Agency this camera belongs to (i.e. CDOT ITS) |
| Icon |
An icon representing the camera type that
we use on Cotrip |
| CameraView |
1 to many relationship with camera. A camera
can have many views (typically, still and camera tour have more than
1 view, while the streaming has only 1) |
| CameraViewId |
Unique Id for the CameraView. The CameraId,
CameraName, CameraType, ImageSource are repeated in this list table
and the CameraId is what relates it to the view |
| ViewDescription |
For each view, the description of the direction
the camera view is pointing. This is more descriptive than just the
direction |
| Direction |
The directions associated with this view. The
values could be: North, South, East or West. Each Camera View will
have 1 value here |
| ImageLocation |
The url for the location of the image for the
camera view |
| DisplayOrder |
We use this in our balloon window to order
the view presented |
| RoadName |
The road name that the camera is on. There
can be only 1 road name for a given alert |
| LastUpdateDate |
The timestamp and date of when this device
was last updated (when the picture was taken). Typically, we collect
images from our still cameras every 20 minutes |
| CameraDisplayType |
The type of interface the camera will be displayed at. This field has two values Kiosk and Web |
| DMS
XML Help (Dynamic Message Sign) |
| Location |
The latitude and longitude of the device |
| DeviceId |
Unique ID for the Device |
CommonName
|
The name of the device. The format is always
3 digit hwy 1 digit direction 3 digit mile-marker space common descritive
location name. For example: 025E146 GARDEN OF THE GODS |
| Status |
Will always be enabled |
| EntityId |
An internal ID for the group / division that
owns the sign. For external purposes, please assume that the sign
is owned by CDOT |
| RoadName |
The road name that the device is on. There
can be only 1 road name for a given alert |
| Direction |
The direction the device faces. The values
could be: North, South, East or West. Can have only 1 value here |
| MileMarker |
The milemarker the device is on |
| LastUpdateDate |
The timestamp and date of when the device was
last updated |
| Icon |
An icon representing the device type that
we use on Cotrip |
| DMSId |
The specific device entity id (in our system
we have a relationship between device (generic, all devices) and specific
device type entity tables (dms in this case). This is the DMS Id that
is unique across DMSes (Dynamic Message Sign) |
| BlankMessage |
If the Sign is blank, this will be true |
| MessageImg |
An image that is based on the sign's configuration
with the current message (this is typically an animated gif image
that shows up to 3 pages depending on the actual message) |
| Weather
Station XML Help |
| Location |
The latitude and longitude of the weather station |
| DeviceId |
Unique ID for the Device |
CommonName
|
The name of the device. The format is always
3 digit hwy 1 digit direction 3 digit mile-marker space common descriptive
location name. For example: 025E146 GARDEN OF THE GODS |
| Status |
Will always be enabled |
| EntityId |
An internal ID for the group / division that
owns the sign. For external purposes, please assume that the sign
is owned by CDOT |
| RoadName |
The road name that the device is on. There
can be only 1 road name for a given alert |
| Direction |
The direction the device faces. The values
could be: North, South, East or West. Can have only 1 value here |
| MileMarker |
The milemarker the device is on |
| LastUpdateDate |
The timestamp and date of when the device was
last updated |
| Icon |
An icon representing the device type that
we use on Cotrip |
| WeatherStationId |
The specific device entity id (in our system
we have a relationship between device (generic, all devices) and specific
device type entity tables (weather station in this case). This is
the Weather Station Id that is unique across Weather Stations |
| ConfigurationId |
The Id for this weather station from it's
external system. In CDOT ITS case, the weather stations are part of
an SSI system and this is the primary key in it |
| Manufacturer |
The maker of this weather station. The values
include: SSI and Vaisalla |
| DeviceCollectionDt |
The timestamp and date of when the device collected
the data |
| SystemCollectionDt |
The timestamp and date of when the our system
collected the information from the device |
| WeatherInfo |
For each Weather Station, one weather info
section will provide information about the reading from the environment |
| EssAirTemp |
Air temperature at the site (F) |
| EssRelHumidity |
Percent of moisture in the air. A relative humidity of 0% shows
that the air contains no moisture and 100% shows that the air is completely
saturated and cannot absorb more moisture |
| EssDewPointTemp |
Temperature at which the air becomes saturated as it cools. If the
road or runway temperature drops to or below the dew point, moisture
may develop on the surface. The form the moisture takes depends on
the surface temperature and the amount of chemical present |
| EssWetBulbTemp |
The wet bulb temperature is the temperature of a thermometer whose bulb is wrapped in wet muslin. The wetbulb is always in between the temperature and dew point, except at saturation, when all three are equivalent |
| EssMinTemp |
The minimum temperature recorded during the 24 hours preceding the observation |
| EssMaxTemp |
The maximum temperature recorded during the 24 hours preceding the observation |
| EssAtmosPressure |
The force per unit area exerted by the atmosphere, measured in inches of mercury (inHg). This reading is not adjusted for site elevation |
| EssAvgWindSpeed |
Average wind speed measured during an evaluation cycle. The time period over which wind gust speed is monitored can vary based on the type and manufacturer of the RWIS site |
| EssAvgWindDir |
Average wind direction during an evaluation
cycle. Wind direction can be displayed in two formats: cardinal
points or degrees. Cardinal format has 8 possible headings. Degree
format displays wind direction in values ranging from 1 to 360.
This field will have the actual degree range
| Direction |
Cardinal Format |
Degree Range |
| North |
N |
338 - 22 |
| Northeast |
NE |
23 - 68 |
| East |
E |
69 - 112 |
| Southeast |
SE |
113 - 158 |
| South |
S |
159 - 202 |
| Southwest |
SW |
203 - 248 |
| West |
W |
249 - 292 |
| Northwest |
NW |
293 - 337 |
|
| EssMaxWindGustSpeed |
Maximum wind speed measured during an evaluation cycle. The time period over which wind gust speed is monitored can vary based on the type and manufacturer of the RWIS site |
| EssMaxWindGustDir |
See EssAvgWindDir for details |
| EssVisibility |
Average distance that you can see, both day and night, computed every three minutes |
| EssPrecipRate |
Average precipitation rate computed every minute. Snowfall is converted to water equivalent and the rate represents the rate of liquid equivalent |
| EssPrecipStartDt |
The time at which the most recent precipitation event began |
| EssPrecipEndDt |
The time at which the most recent precipitation event ended |
| TenMinPrecipAccum |
Rainfall amount or snowfall liquid equivalent for the previous 10 minute period |
| EssPrecip1Hr |
Rainfall amount or snowfall liquid equivalent for the previous 1 hour period |
| EssPrecip3Hr |
Rainfall amount or snowfall liquid equivalent for the previous 3 hour period |
| EssPrecip6Hr |
Rainfall amount or snowfall liquid equivalent for the previous 6 hour period |
| EssPrecip12Hr |
Rainfall amount or snowfall liquid equivalent for the previous 12 hour period |
| EssPrecip24Hr |
Rainfall amount or snowfall liquid equivalent for the previous 24 hour period |
| WindDir |
See EssAverageWindDir. This field will have the Cardinal format |
| WindDirIcon |
url for the location of the arrow that Cotrip uses to display the wind direction |
| WindGustDir |
See EssAverageWindDir. This field will have the Cardinal format |
| WindGustDirIcon |
Url for the location of the arrow that Cotrip
uses to display the wind direction |
| EssVisibilityTxt |
The text value of the EssAverageVisibility
(for example: Clear) |
| RwisPrecipStatus |
Type of precipitation detected by a precipitation
sensor, if one is available. Certain types of precipitation sensors
can only detect the presence or absence of precipitation and will
display Yes or No. Other types of precipitation sensors, such as
the Weather Identifier and Visibility Sensor (WIVIS) or Optical
Weather Identifier (OWI), can classify the type of precipitation
and will report a specific type of precipitation. The WIVIS and
OWI precipitation sensors may report Yes at the onset of precipitation
until sufficient time has elapsed to classify the precipitation
type. The values include: None, Yes, Rain, Snow, Mixed, Upper, Lower,
Both, Light, Light Freezing, Freezing Rain, Sleet, Hail, Lens Dirty,
No Com, Fault, Initialized, Other, Unidentified, Unknown, Frozen,
No Data
|
| RwisPrecipIntensity |
Intensity of the precipitation as derived from
the precipitation rate. The National Weather Service defines the following
intensity classes: light, moderate, or heavy. The values include:
None, Reserved, Light, Moderate, Heavy, Reserved, Reserved, Initialized,
Slight, Other, Unknown, No Data |
| SurfaceSensorData |
It is the most recent RWIS surface data collected by a weather station sensor.
There can be zero or many sensors for each weather station and hence the corresponding SurfaceSensorData. |
| WeatherStationSensorId |
It is the system generated unique identifier for each of the 'weather station sensor' collecting RWIS surface data. |
| TypeWeatherSensorTxt |
Identifies the type of sensor at the weather station. |
| SensorId |
The external system identifier for the weather station sensor. |
| SensorName |
Weather station Sensor name. |
| DeviceCollectionDt |
Date and time that surface data were last collected by the RWIS weather station sensor. |
| RwisSurfaceStatus |
The status of the surface data collected by the RWIS weather station sensor. |
| EssSurfaceTemperature |
Temperature of the pavement sensor roughly 3 mm (1/8 inch) below the surface of the sensor, in degrees Fahrenheit. |
| EssSubSurfaceTemperature |
Temperature approximately 43cm (17 inches) below the top of the pavement, in degrees Fahrenheit. |
| EssSurfaceFreezePoint |
Freezing point of the moisture on the pavement sensor based upon the specific chemical in use, in degrees Fahrenheit. |
| ChemicalFactor |
Relative indication of chemical present in the moisture on the surface. Chemical factor uses a relative scale ranging from 5 to 95 in increments of 5. |
| ChemicalPercentage |
Percent of chemical saturation in the moisture. |
| EssWaterDepth |
Depth of water layer on the sensor, in inches. |
| IcePercentage |
Percent of ice in the moisture. |
| EssSurfaceConductivity |
Conductance of the ice/liquid mixture on the pavement. |
| EssSurfaceSalinity |
Number of grams of dissolved matter per kilogram of seawater, in parts per 100,000. |
| EssSurfaceBlackIce |
NTCIP 1204 value indicating if black ice is detected by the RWIS weather station sensor. |
| EssPvmtSensorError |
NTCIP 1204 classification of the type of error at the RWIS weather station pavement sensor. |
| WeatherStation Camera |
Please refer to the Camera Device Help. The
XML is exactly the same, except the value of the IsWeatherStation
is true. The device type will be still camera (click
here ) |
| Speed Segment Polylines Help |
| Id |
Unique ID for the Segment |
| Name |
Name that describe the segment's location. The first part of the segment name is the Highway Number (3 digits) Direction (1 digit) and Mile-marker (3 digits and start) of the Segment. The next is the common descriptive name.
Segment's are unique, have only 1 direction and do not overlap |
| Points |
A series of longitude, latitude, and altitude (always 0) points that identify the polyline feature of a speed segment |
| Speed Route Polylines Help |
| Id |
Unique ID for the Route |
| Name |
Name that describe the routes's location. The first part of the name is the Highway Number (3 digits) Direction (1 digit) and Mile-marker (3 digits and start) of the route. The next is the common descriptive name.
Routes can cover more than 1 road. But will have a given direction on each road |
| Points |
A series of longitude, latitude, and altitude (always 0) points that identify the polyline feature of a speed route. |
| Weather Route Polylines Help |
| Id |
Unique ID for the Weather Route |
| Name |
The name of the weather route (descriptive, location) |
| Points |
A series of longitude, latitude, and altitude (always 0) points that identify the polyline feature of a weather route |
|