The sources are varied and can include traffic operations, roadway, weather, maintenance, and safety data. As shown below, the information will be both agency and acquired data (like INRIX or HERE probe data). The data will be turned into data feeds and information streams for use by both public and private entities.
The Open Data Service is functioning and currently has 12 feeds available which are being consumed by both DOT (OTO, OLE, TAS) and non-DOT users (HNTB and ISE). A sample of how the feeds are being used within the DOT include the in the project prioritization tool for OLE, the lane closure planning tool (LCPT) for TAS and the operations dashboard in the TMC for OTO. The feeds include a unified sensors feed (location+data), performance measures for INRIX and sensors, work zone congestion detection, DMS/ATMS historical archiving, and a waze clean data feed.
In addition to the data feeds, the open data service is archiving data from 16 different sources which include the DOT sensors (ITS and RWIS), INRIX, Waze, DOT ATMS events, DOT Snowplow AVL, etc. This allows for easy development of additional feeds and data integration. Integration with the Iowa DOT LRS has been a priority when developing the Open Data Service and most features include fields which allow for integration within RAMS. A separate module is also being developed through the Open Data Service which will allow for offline conflation to RAMS. The current RAMS system has several limitations including the numbers of records which can be sent as well as the response time. This module will significantly increase the speed of this process.
https://iastate.box.com/s/2penu56i15hajm97i5e2eharmynjgqq2
The user guide contains a follow list of data feeds and dependencies of the data provided through the open data service. Below are some sample feeds which are available:
Feed: http://reactorfeeds.org:80/feeds/sensorfeed
Documentation: http://reactorfeeds.org/docs/feeds/sensorfeed
Search Filters:
Each feed result can be limited by using the search filters. Currently, we are supporting three different cafeterias.
a. start: Gives results from this start date.
b. end: Gives results till this end date.
c. code: Gives results for the given particular code.
1. Daily Performance Measures:
URL: http://reactorfeeds.org/feeds/inrix/daily (XML) / http://reactorfeeds.org/feeds/inrix/daily.json (JSON)
We can add the search filters to limit the results. The date's filter should be in the format of "MM-dd-YYYY".
Sample: http://reactorfeeds.org/feeds/inrix/daily.json?code=1450418477&start=08-15-2017
2. Monthly Performance Measures:
URL: http://reactorfeeds.org/feeds/inrix/monthly (XML) / http://reactorfeeds.org/feeds/inrix/monthly.json (JSON)
We can add the search filters to limit the results. The date's filter should be in the format of "MM-YYYY".
Sample: http://reactorfeeds.org/feeds/inrix/monthly.json?code=1450418477&start=08-2017 [Rightnow, I don't have any monthly data]
3. Historical Performance Measures:
URL: http://reactorfeeds.org/feeds/inrix/historical (XML) / http://reactorfeeds.org/feeds/inrix/historical.json (JSON)
We can add the search filters to limit the results. The date's filter should be in the format of "MM-YYYY".
Sample http://reactorfeeds.org/feeds/inrix/historical.json?code=118-04493&start=04-2017
The work zone alert feed was developed during the 2017 construction season. Using machine learning a algorithm was developed which identifies both slow and stop conditions across the state. A feed was developed to to summarize this information for each work zone and is used in the TMC Operations Dashboard as well as for Text Alerting to DOT staff. The work zone alert feed API is available at the following link: http://reactorfeeds.org/feeds/alertfeed (additional documentation at http://reactorfeed.org)
TMC ATMS Events stored on cloud
INRIX data stored on cloud (ability to perform value added feeds)