Changelog

4.6.24 (04/04/2024)

• Added AZDOT Detector datasource

4.6.23 (04/01/2024)

• Added WMATA Parking datasource

4.6.22 (03/27/2024)

• Updated KITS Signal Inventory output to include sequence data for timing patterns

4.6.21 (03/26/2024)

• Added output parameters 'hasMedia' and 'hasChat' for XSL outputs to indicate if an event supports these features
• Updated AZDOT Dust and WWD events to guard against historical searching from applications
• Updated GTFS output to support additional fields missing from the spec

4.6.20 (03/21/2024)

• Updated GTFS-RT Output to include Occupancy Status
• Fixed a bug with GTFS-RT caching that was incorrectly filtering vehicle location results in the cache

4.6.19 (03/07/2024)

• Fixed a bug where alternateRoads elements were being skipped for the rf-json output format
• Fixed a bug with KITS signal data not ordering associated intersection names correctly for a given signal device

4.6.18 (02/29/2024)

• Add AZDOT Events to WORKZONE_SYSTEMS config for WZPMA

4.6.17 (02/27/2024)

• Updated VDOT event processing to use agency segment_status for Workzone status

4.6.16 (02/27/2024)

• Added a new XSL for DMS that provides tilers with more details (rfDMSToJson.xsl)
• Updated KITS to pull from a caching database located on the RITIS Filter proxy server
• Updated icon mappings for Restriction Class events to be construction work event icons
• Updated icon mappings for visibility reduced to use the fog icon
• Fixed a bug with AZDOT Dust and Wrong Way Detection that would attempt to alias a missing a table
• Disabled a failing unit test for VTRANS RWIS that relies on the loader to always be running in development (VtransRwisDataProviderTest.testWeatherDataOutput)

4.6.15 (02/09/2024)

• Added KITS Signal data provider to RM3P
• Added AZDOT Wrong Way Detection data provider
• Added AZDOT DUST Sensor data provider
• Fixed a bug with AZDOT RWIS providing an extra comma in its output

4.6.14 (02/07/2024)

• Updated Event Historical Index to use the "earliest" start time
• Updated Lane status grouping to use the originating_lane_id column value
• Added reportingSystem to RF output to identify original data source
• Added AZDOT RWIS data provider
• Added ad-hoc AZDOT DUST and WWD detection "events"

4.6.13 (01/24/2024)

• Added AZDOT DMS data provider
• Added AZDOT Event data provider
• Fixed a bug with VTRANS CCTV devices with periods in their ID not pulling most recent snapshot

4.6.12 (12/20/2023)

• Added GTFS agency, MBTA (Massachusetts Bay Transportation Authority)
• Added AZDOT CCTV data provider
• Updated VTRANS RWIS dataprovider to adhere to the new data format in the database
• Updated RWIS output to support non-wxde agencies, i.e. VTRANS
• Fixed an issue with unit tests not cleaning up after themselves for tree-indices

4.6.11 (12/11/2023)

• Fixed a bug when parsing the 'state' parameter for historical event searching
• Fixed an issue when selecting event types with multiple attributes
• Removed extra whitespace in the rf-json output for communication messages
• Updated the VDOT Toll Rate query to use a one week boundary for performance

4.6.10 (11/29/2023)

• Updated email notifications for RITIS Speed Alerts to be more accurate
• Added a new endpoint /dep_noaa_weather that provides segment based precipitation data

4.6.9 (11/17/2023)

• Removed GTFS agencies from AVL permissions that are GTFS (Static) Only

4.6.8 (11/16/2023)

• Increased performance with GTFS-RT Vehicle caches to take cache timr from 30+ minutes to under 30 seconds

4.6.7 (11/16/2023)

• Enabled NJDOT Workzones for WZPMA
• Added Barometric Pressure readings for VTRANS RWIS
• Fixed a bug where GTFS Vehicles could not be requested without a system provided

4.6.6 (10/31/2023)

• Added new output parameters for event locations to indicate the head and the center endpoints
• Added ability to filter NWS Weather Alerts by state
• Fixed a bug with GTFS Transit output that included an invalid backslash

4.6.5 (10/17/2023)

• Added VTRANS GTFS and GTFS-RT Datasources

4.6.4 (10/03/2023)

• Added VTRANS CCTV Datasource
• Enabled media queries for WAZE Incidents
• Removed historical chat log processing for incidents

4.6.3 (09/19/2023)

• Updated Planned During Filter to account for the events closed timestamp when no planned closure was given by the dataprovider
• Fixed an issue where uploaded media was not being picked up by the other data nodes in the processing cluster
• Fixed an issue where VTRANS RWIS was returning old oberservations

4.6.2 (09/07/2023)

• Added VTRANS Incident and Workzone Datasources
• Added VTRANS RWIS Datasource

4.6.1 (08/31/2023)

• Added VTRANS DMS Datasource
• Updated SQL query processing to use standard Strings instead of Query objects for simplicity

4.6.0 (08/23/2023)

• Added a new filter request type to allow querying for GTFS Service Alerts
• Updated Road Name Filter to allow for contains comparisons for checking substring in road name

4.5.4 (08/07/2023)

• Updated Attribute processing to not interpret Weather Conditions as Attributes
• Code cleanup for defaulting permission logic

4.5.4 (06/28/2023)

• Increased performance for RITIS Alerts subscription processing
• Updated the RITIS Alerts email contents to be more consistent
• Updated the historical pre-processing to use case-insensitive county filtering
• Updated MDOT_CHART CCTV processing to use the feed specific privacy field
• Organized permission code

4.5.3 (06/20/2023)

• Added HLS Stream URL support for MDOT_CHART cctv
• Added TDOT TSS Datasource
• Updated the County filter to be case-insensitive
• Updated Clearence Time requests logic to be split by request type
• Fixed a bug with event indexing for IDs that were too long

4.5.2 (06/02/2023)

• Hotfix for Clearance Time Requests to properly return the end result

4.5.1 (05/30/2023)

• Removed the geoId filter functionality for event searches
• Updated road name processing accuracy for VDOT TMS Detectors
• Updated incident XSL files to include a timeline output flag
• Increased the performance of DMS Historical searches

4.5.0 (05/15/2023)

• Improved service architecture to make internal data handling more efficient
• Updated data cache handling to remove race conditions for data invalidation
• Updated cache jobs to not fail on a single error
• Updated road name handling for certain data types to be consistent across the service

4.4.9 (04/18/2023)

• Updated ATIS output to conform to the schema
• Updated cache jobs to split up device data into separate jobs
• Updated DRPT Ridership permission handling to match the new group in RITIS
• Fixed issue where certain data types were associated to the wrong filter type

4.4.8 (04/11/2023)

• Added ILDOT DMS datasource
• Updated FDOT Event Type handling to use more accurate values
• Updated output of rfIncidentToJson.xsl to show road information for events with multiple locations

4.4.7 (04/03/2023

• Updated DRPT Ridership Permission Handling

4.4.6 (03/29/2023

• Added MDOT MTA GTFS and GTFS Realtime datasources for MARC
• Fixed an issue where Speed Alerts were not sending notifications after a successful recovery

4.4.5 (03/13/2023)

• Added LADOTD Detector data source
• Added PG County TheBus GTFS and GTFS-RT data sources
• Code clean up for unit test organization

4.4.4 (02/21/2023)

• Updated output to the user to indicate when an unsupported filter is used for a specific endpoint
• Updated user permission handling to block requests when a user includes any invalid agency
• Removed references to HAR and SHAZAM devices
• Fixed broken unit tests not running in the automated testing environment

4.4.3 (02/09/2023)

• Fixed issue with road filtering on open events

4.4.2 (01/24/2023)

• Added support for the format parameter in historical requests
• Updated RITIS Alerts to send an expiration email to users after 30 days
• Updated RM3P CCTV to use the new WOWZA streaming server
• Reorganized RF Documentation Service codebase

4.4.1 (01/19/2023)

• Added new XSL (rfDetectorToBBQ.xsl) for the BBQ Application
• Updated Transurban Event output to include proper location and type information
• Updated user error messages for integer overflow errors
• Updated scheduled jobs to show up on the jobs page when no schedule is defined
• Updated FDOT CCTV authentication to check for the agency properly
• Removed the use of ALERT and TRIP_UPDATE types from GTFS searches

4.4.0 (12/21/2022)

• Added filtering events by TS Segments
• Updated TSS Detector TMC Filtering to account for all zones at a given location

4.3.2 (12/16/2022)

• Fixed issue with Toll Rate filtering not working on Start Zone
• Fixed issue with Arlington County TMS SQL formatting

4.3.1 (12/15/2022)

• Updated Arlington County TMS Detectors SQL for historical search performance
• Updated permission checking for Transit Agency endpoint to handle non GTFS Transit agencies

4.3.0 (12/9/2022)

• Added DRPT Ridership datasource
• Added Arlington TMS Detectors datasource
• Updated TSS Detector output to assign appropriate TMC codes to zones
• Updated Footer message in RITIS Alerts emails
• Fixed an issue where the radius-filter was not consistent on different environments

4.2.15 (11/15/2022)

• Added Arlington Bike Counters data source

4.2.14 (11/15/2022)

• Updated response to user for intentional timeouts for requests
• Updated cache jobs to continue processing if one data provider fails
• Updated cache job status tracking to report how many failures occurred for the most recent job execution
• Cleaned up VDOT RM3P Detector data source to remove unnecessary WHERE clause
• Cleaned up CHART WZDx to remove events that paused
• Cleaned up CHART WZDx to show "Active Closure" instead of "Planned Closure"

4.2.13 (11/01/2022)

• Updated cache jobs to process new one time caches for appropriate data nodes
• Updated VDOT Detector data source to filter out detectors with invalid direction
• Updated WZDx feed to sort coordinates and cross streets based on event direction
• Cleaned up TMS Detector permissions from the previous hotfix
• Fixed a bug with Historical Requests that were rejecting apiy-key GET parameter

4.2.12 (10/19/2022)

• Fix a bug with TMS Detector permissions

4.2.11 (10/18/2022)

• Updated WZDx coordinates to use the correct values

4.2.10 (10/13/2022)

• Updated MDOT WZDx to use standardized time formats
• Updated MDOT WZDx to remove events missing end dates
• Enabled searching for Transurban by ID only
• Removed an extra XML element from Bike Facilities
• Removed m3u8 playlist files from CCTV requests missing permissions
• Cleaned up Weather data output
• Fixed VDOT RWIS sensor grouping in output

4.2.9 (10/04/2022)

• Added support for events with both start and end locations
• Updated Transcom (NJDOT) events to use agency prefix in the database
• Updated CHART WZDx to remove external events from the feed

4.2.8 (09/27/2022)

• Added support for one time cache jobs
• Renamed Historical Bike endpoint
• Added API documentation for Bike Facilities and Historical Weather
• Added initial support for CHART WZDx Endpoint
• General code cleanup

4.2.7 (09/21/2022)

• Fixed a null expcetion with AVL Data processing

4.2.6 (09/20/2022)

• Added VDOT Static Bike Facility endpoint
• Added TMS Detectors data provider
• Added RWIS historical searching
• Standardized weather data for both WXDE and RWIS
• Removed use of mobility-db.ritis.org database in the codebase

4.2.5 (09/12/2022)

• Added a new cache for TMC Area queries
• Updated AustinTX CCTV snapshot URL query
• Updated logging configuration to separate RF indexing logs
• Removed references to midot-archive database

4.2.4 (08/23/2022)

• Added CUE GTFS Source
• Updated pointLocation element ID to include _c or _p1
• Updated SQL for VDOT Transurban to populate missing data elements
• Fixed issue with HERE TMCs in tmc_expand

4.2.3 (08/09/2022)

• Added option to ignore opposite side of road for tmc_expand_info
• Added additional VDOT toll rates datasource
• Updated CHART AVL SQL to remove duplicate vehicles
• Updated Metaspace memory settings for Webservice and Datagrid for stability
• Updated WAZE event requests to a separate database for performance

4.2.2 (07/26/2022)

• Updated cache jobs to fail gracefully on invalid records
• Updated Bikeshare SQL for performance
• Fixed duplicate TMC issue in tmc_expand endpoint

4.2.1 (07/18/2022)

• Fixed an issue with Transcom returning extra rows with multiple event types for a single event
• Updated error message for invalid arguments for GET requests
• Updated error handling for filters provided with no value (empty string)
• Added XML output for Historical Device requests (Previously only JSON)

4.2.0 (06/30/2022)

• Updated existing endpoints to include previously unsupported filters
• Cleaned up an error message to users to not include the Java class in the error message
• Fixed a bug with tmc_expand_data endpoint to always see the most recent TMC inventory

4.1.10 (06/27/2022)

• Added Transurban Event Datasource
• Added Transurban DMS Datasource
• Added Transurban Detector Datasource
• Added Transurban Gate Controller Datasource
• Added VDOT Toll Rates Datasource
• Removed duplicate objects between VDOT OpenTMS and Transurban in results

4.1.9 (06/06/2022)

• Fixed a bug with FDOT events not returning XD's in the output results

4.1.8 (05/31/2022)

• Updated Transit Agency endpoint to provide XML and JSON output ooptions
• Improved the performance of the Transit Agency endpoint
• Fixed a Nullpointer exception in the state filter
• Added additional logging for historical device reqeusts

4.1.7 (05/24/2022)

• Fixed bug where historical index file was being closed too early
• Fixed bug with road logical operator SQL generation that clashed with SQL any() operator
• Enabled aditional filters for Bikeshare requests
• Updated historical device requests to not cache when the endTime paramater is within 2 hours of current time
• Added an excludeGeometry filter for Transit
• Updated LADTOD CCTV to use the 511 devices instead of the C2C devices

4.1.6 (05/06/2022)

• Fixed "too many open files" error with historical index searching

4.1.5 (05/04/2022)

• Added Historical TSS Search functionality
• Fixed issue with Historical Index TreeNode cache
• Fixed WAZE data issue by removing a specific set of duplicate events in 2019
• Standardized RITIS Filter configuration files for deployments
• Updated API documentation to list endpoints individually instead of by group
• Updated the error returned to the user if no user is found for a given API key

4.1.4 (04/21/2022)

• Removed incompatible TCP CCTV Feeds from LADOTD

4.1.3 (04/20/2022)

• Add LADOTD CCTV source

4.1.2 (04/13/2022)

• Updated the HistoricalRequest schema to handle the endTime correctly
• Updated TreeNode logging to prevent a false alarm about node removal
• Updated request routing to prevent some requests working in the wrong endpoint
• Fixed bug with Historical Aggregation requests throwing an error if no IDs are found in the index

4.1.1 (03/31/2022)

• Fixed a bug with Detector requests not showing up in results when using rf-json format
• Fixed the historical searching code to not skip requests with one TMC
• Fixed a bug with DDOT Permit events attempting to use County filtering when no metadata exists
• Improved Evacuation and DMS data jobs load times by caching the alternate street names during the geocode process

4.1.0 (03/30/2022)

• Updated GlobalExceptionhandler for HistoricalController to validate date ranges in requests
• Updated INRIX Archive DB connections to use prepareThreshold=0 to deactivate PreparedStatements
• Disabled MSPCAD from showing up in "system=all" internal requests
• Stability Updates
• Updated the TreeIndex thread pool to be static instead of per agency (eliminated about 250 threads)
• Fixed memory leak in DeflatorOutputStream classes by calling end() on Delfator instances
• Reduced LRU Node cache for TreeIndex nodes
• Updated use of ByteBuffer.allocateDirect() to ByteBuffer.allocate() to remove a Native Memory leak
• Updated Garbage Collector to G1GC and updated heap size and flags
• Updated service to use jemalloc as the system "malloc" allocator

4.0.8 (03/25/2022)

• Generalized Deivece historical searching between different device types
• Added a JSON Reducer for Weather data
• Added a check for daylights savings time for WZPMA calculations
• Updated all data endpoints to have a default output format when none are providedin the request
• Added VDOT Wavetronix Detectors datasource
• Fixed bug with VDOT Gate Controllers that were not setting a State value when county was missing
• Added VDOT Combined Detectors datasource (VDOT OpenTMS + Wavetronix)
• Added permission handling for Speed and Travel Time endpoints
• Added Road filter handling for DMS search

4.0.7 (03/08/2022)

• Fixed bad SQL grammar for DDOT Captop Events
• Updated Parking output to be standardized between XML and JSON
• Fixed divide by zero error in WorkzoneUDCSubprocessor

4.0.6 (03/04/2022)

• Updated Historical Event Search when filtering by TMC
• Removed FDOT CCTV Security Token from output
• Updated Support Email for RM3P API
• Improved Historical Event Search Performance
• Added a Historical Search tree traversal timeout to prevent overly large requestst to hit the database
• Enabled GET requests for Transit endpoint

4.0.5 (02/25/2022)

• Added request type for Bikeshare Requests

4.0.4 (02/22/2022)

• Updated rfIncidentToEQT.xsl to not return agencyExtensions with empty string values
• Fixed a null pointer expcetion for index swapping race conditions

4.0.3 (02/18/2022)

• Added the original eventType node back in for any request not using XSL
• Fixed null pointer exception in WMATA GTFS SQL

4.0.2 (02/17/2022)

• Added Capital Bikeshare Datasource
• Added permissions check for VDOT Gate Controllers
• Added a new mode filter for GTFS searches
• Added support for FDOT authenticated CCTV
• Updated XSL's to return all event types (RITIS / Agency / RF)
• Fix JSON bug with non-escaped quotes

4.0.1 (01/31/2022)

• Updated default incident permissions for TrafficView API keys
• Added VDOT RWIS datasource
• Optimized historical DMS requests
• Added VDOT Gate Controller datasource

4.0.0 (12/23/2021)

• Added Historical Parking search feature
• Updated Transit Agency timeout to account for additional data
• Added Fredericksburg GTFS datasource
• Updated cache jobs to be more specific to allow the disabling of specific features per node

3.18.7 (12/15/2021)

• Replaced SQL statements using PreparedStatements with normal connections
• Fixed a bug with PRTC GTFS preventing requests from authorizing outside of ADMIN accounts

3.18.6 (12/02/2021)

• Added GTFS and GTFS-RT Sources
• Alexandria DASH
• ART
• DASH
• Fairfax County
• Loudon County Transit
• PRTC
• Updated ORDOT events to return agency types and subtypes in the response
• Added the ability to search by Functional Road Class (frc) for Events

3.18.5 (11/17/2021)

• Removed uses of SQL PreparedStatements when hitting pgbouncer
• Updated WMATA Events to use new datasource
• Updated AlertTypeMappings for RITIS Alerts to include restrictions

3.18.4 (11/02/2021)

• Updated SQL generation to escape additional characters
• Updated EQT event requests to output additional fields for WAZE data
• Updated cache job SQL to only include list of open event id's for historical datasources only
• Updated XSL files to be loaded on service startup

3.18.3 (10/18/2021)

• Updated database used for AADT values for UDC calculations
• Updated NYSDOT query to only include events from New York state

3.18.2 (10/11/2021)

• Added new countyFull parameter to compatible device data
• Added LADTOD DMS Datasource
• Fixed bug with CCTV request not applying XSL based on permissions
• Updated wording on the Parking API request section

3.18.1 (09/20/2021)

• Added missing cache locations for Parking Data

3.18.0 (09/20/2021)

• Added a new endpoint to request Parking data from RITIS Filter
• Updated RITIS Filter API documentation for Parking data
• Added a new search controller for RM3P. Mimics current production functionality.

3.17.24 (08/31/2021)

• Updated CCTV URL's to show evostream links to users
• Updated MDOT CHART to hide inactive Detectors
• Updated FDOT District naming to match common use names
• Added ORDOT Detector Datasource
• Added ORDOT DMS Datasource

3.17.23 (08/24/2021)

• Added VRE GTFS Static and Realtime Datasources

3.17.22 (08/02/2021)

• Fixed bug in lane processing where lanes without the most recent timestamp were filtered out
• Added RTSP CCTV stream support to TrafficView

3.17.21 (07/27/2021)

• Added FDOT Statewide CCTV
• Fixed a bug where TrafficView snapshot image URLs were being mangled if multiple links existed

3.17.20 (07/22/2021)

• Fixed a bug in VDOT lane configurations not using unique IDs

3.17.19 (06/29/2021)

• Updated processing of event road data to enforce RITIS Filter Schema rules
• Fixed broken links in XML schema namespaces
• Added a new column to /db endpoint to show number of queued requests for databases
• Added a new infinispan cache (tmcExpandCache) to keep a cache of road ordering for Timelines
• Updated memory configurations of processing nodes for stability
• Added a nw GIS database user connection to split connection pools by functionality

3.17.18 (06/18/2021)

• Updated configs to move RITIS Filter out of PDC into CHR
• Updated sentry logging configs to reduce spam to sentry server

3.17.17 (06/08/2021)

• Updated CHART TSS queries to filter out devices with invalid location names
• Added a new output field named "countyNameFull" to provide official suffixes for counties
• Updated logging to only send specific types of errors to Sentry
• Added TDOT (Tennessee) Event Datasource

3.17.16 (06/02/2021)

• Updated Vehicle metadata retrieval and parsing from EPA and Wikipedia
• Updated event types and subtypes to match TMDD v3.1 standard
• Improved performance of dms tables

3.17.15 (05/18/2021)

• Updated the tmc_expand_data endpoint to not return duplicate TMCs

3.17.14 (05/11/2021)

• Updated CHART TSS inventory requests to only return devices with valid location descriptions and coordinates
• Updated timeout for historical search to handle a race condition with lucene index closures

3.17.13 (04/20/2021)

• Updated LADOTD Clearence Time queries to include agency types
• Updated Radio Reference to use the new data feed entries

3.17.12 (04/01/2021)

• Updated LADOTD event type mappings
• Added Alerts and Advisory events to LADOTD
• Fixed bug in INRIX event archiving
• Updated WAZE event queries to match new table design for performance

3.17.11 (03/23/2021)

• Improved Waze event query performance
• Enabled LADOTD 511 event datasource
• Additional logging for indexing

3.17.10 (02/24/2021)

• Added a new endpoint to check database query plans
• Enable RIDOT for Workzone processing
• Updated RIDOT event query to include agency types

3.17.9 (02/16/2021)

• Updated database connection strings to support pgBouncer

3.17.8 (02/15/2021)

• Updated database connection settings for stability and security
• Updated datasource queries to add support for media upload and operator logs

3.17.7 (01/25/2021)

• RITIS Filter
• Enabled RIDOT Event Data Source

3.17.6 (01/20/2021)

• RITIS Filter
• Enabled LADOTD Event Data Source

3.17.5 (01/11/2021)

• RITIS Alerts
• Enabled "Contact Verification" service
• Updated "All Lanes Closed" message to be more accurate
• Implemented Alerts service for TrafficView

3.17.4 (01/05/2021)

• Updated ORDOT Event locations to prioritize start location for center point
• Added RF attribute mapping for "closed for the season"

3.17.3 (12/17/2020)

• Updated WMATA GTFS Bus SQL to use proper Schedule
• Updated CHART Mobile CCTV SQL to provide a Description
• Fixed an issue with RITIS Alerts not sending alerts on Saturday Nights

3.17.2 (11/24/2020)

• Enabled Closed Notifications for Event Subscriptions in RITIS Alerts

3.17.1 (11/18/2020)

• RITIS Alerts
• Defined agency list for Incident Alerts
• Disabled Subscription Alert Notification while starting Service
• RITIS Filter Datagrid
• Added additional type mappings for RF Attributes
• Fixed typo for a de-activated user API Key
• Disabled RIDOT Event Job
• Updated Memory Configuration for all datacenter RF instances

3.17.0 (11/12/2020)

• RITIS Alerts Service Upgrade
• Updated RITIS Alerts to newest RITIS Filter Framework
• Enabled use of INRIX and HERE Probe data for Speed Alerts
• Added qualityIndex field to HERE Hazard Warnings data output

3.16.15 (11/11/2020)

• Enabled HERE Hazard Event Source

3.16.14 (10/27/2020)

• Enabled Lane Data for Oregon DOT

3.16.13 (10/14/2020)

• Updated CHART CCTV to stop using SWGI URLs

3.16.12 (10/05/2020)

• Add INRIX Incidents (Open Events Only)

3.16.11 (09/15/2020)

• Updated GTFS cache to remove orphaned data
• Updated Evacuation filter to handle new Baltimore data

3.16.10 (08/18/2020)

• Enabled Oregon Workzone Events

3.16.9 (08/09/2020)

• Enabled Louisiana Waze Events
• Updated Bottleneck Service URL to New Proxy

3.16.8 (07/22/2020)

• Added WMATA GTFS as a Transit Datasource

3.16.7 (07/7/2020)

• Fixed issue with Road Weather CacheJob not properly building Observations
• Updated DetectorCache to remove Detectors no longer in inventory
• Improved next stop identification for GTFS

3.16.6 (07/6/2020)

• Optimized AustinTX CCTV SQL (~30 Minutes -> 1 Minute)
• Updated Transit Processing to Include AVL
• Updated WXDE (Clarus) Processing for new Schema
• Updated "adviceInstructionsRecommendations" and "adviceInstructionsMandatory" RITIS Types Mapping to "Incident -> Alert" RF Types

3.16.5 (04/13/2020)

• Removed South Carolina / New York / New Jersey / Delaware / Rhode Island from WZPMA processing

3.16.4 (03/05/2020)

• Restored active-during behavior for PDA (enabled point in time searches)

3.16.3 (03/04/2020)

• Updates to AVL CCTV camera feeds
• Fixed issue with active-during filter that would return events in the future that were not in the date range
• Fixed bug in the open event cache that would allow events to remain if distinct meta data was updated such as the ID

3.16.2 (01/20/2020)

• Enable Static CCTV Devices in Public Feed

3.16.1 (01/09/2020)

• Updating staging URL's for Raptor Test Instances
• Switch to new database host for Transit data (transit-deb.ritis.org:6432)

3.16.0 (11/13/2019)

• Updated the URL for simple speed endpoint
• Added a new endpoint (/clearance) to handle Clearance Time Widgets for PDA
  • Average (/clearance/avg) returns the average Clearance Time for all events per year/month
  • Interval (/clearance/interval) returns the number of events that have Clearance Time that fall within 30 minute bins
  • Statistics (/clearance/stats) calculates the Min / Max / Median / [5th, 25th, 75th, 95th] percentiles per event type per year

3.15.4 (10/29/2019)

• Updated request clause limit from 10,000 to 128,000
• Fixed an issue with TMC expansion to return the proper TMCs for a road request
• Updated Vehicle requests to filter out Vehicles with invalid locations

3.15.3 (10/14/2019)

• Aggregation API now supports more options for GROUP BY

3.15.2 (9/9/2019)

• Improved performance for GTFS Route Data cacheing
• Upgraded Infinispan from 7.1.0 to 7.2.5
• Tweaked JVM memory settings for all environments
• Updated /internal/requests to auto-refresh
• Updated OS TCP buffer settings for Infinispan

3.15.1 (8/19/2019)

• Updated transit endpoint to supply realtime vehicles
• Updated datagrid JVM options for stability
• Updated handling of media file uploads to support additional types, such as Power Point

3.15.0 (7/22/2019)

• Updated transit endpoint to provide Maryland Transportation Authority (MDOT MTA)
• Add an updated box filter to use only lat/lon points

3.14.1 (6/28/2019)

• Update SQL for CHART AVL Vehicles
• Fix event cache not capitalizing counties with hyphens, e.g. "Miami-Dade"

3.14.0 (6/11/2019)

• Use Bottleneck API for all bottleneck endpoints

3.13.7 (5/20/2019)

• Add ILDOT TSS

3.13.5 (4/16/2019)

• Add ILDOT events
• Add CCTVs from Alexandria, VA

3.13.4 (4/15/2019)

• Fix error refreshing events without start times

3.13.3 (3/21/2019)

• Add FDOT DMS
• Refresh cached planned events when they should become open

3.13.2 (3/1/2019)

• Add associated DMS data to FDOT events

3.13.1 (2/13/2019)

• Allow county filter values to contain single quotes, e.g. "O'Brien|Iowa"

3.13.0 - Tenacious Tigh (2/4/2019)

• Fix error returning events with agency event subtypes

3.12.0 - Singular Sharon (1/24/2019)

• Update rf-schema-xml event output:
  • Add field for Every Day Counts (EDC) incident type
  • Add field for timestamp when all lanes are opened, if lane data is available
  • Allow multiple agency event subtypes

3.11.1 (12/13/2018)

• Fix input schema for flexible requests

3.11.0 - Ruthless Roslin (12/5/2018)

• Add XD segment ID to event output
• Add XD segment ID filter for events

3.10.0 - Paranormal Pegasus (11/15/2018)

• Allow county filter values to specify states, e.g. "Montgomery|MD" instead of "Montgomery"

3.9.6 (10/31/2018)

• Add field to CCTV device output to signify mobile cameras

3.9.5 (10/16/2018)

• Fix incorrect disabled vehicle count in CHART events
• Update vehicle types for CHART AVL

3.9.4 (9/26/2018)

• Add MoDOT TSS
• Speed up TSS queries

3.9.3 (9/5/2018)

• Add MoDOT events
• Add Austin, TX TSS

3.9.2 (8/22/2018)

• Add Austin, TX CCTV
• Add responders to VDOT events
• Fix invalid device name in atis-tmdd-xml DMS output
• Update documentation for input schemas and output lanes

3.9.1 (8/14/2018)

• Add Austin, TX DMS
• Fix invalid direction, lane count, and speed in atis-tmdd-xml detector output

3.9.0 - Nihilistic Narcho (8/2/2018)

• Fix probe data providers INRIX and HERE in /ritisfilter/bottleneck/search_by_tmc

3.8.5 (7/24/2018)

• Add Waze events from more states

3.8.4 (7/9/2018)

• Fix event and responder types in atis-tmdd-xml event output

3.8.3 (6/14/2018)

• Fix API key permissions for CAD events

3.8.2 (6/6/2018)

• Parse interstate prefix from PA Turnpike construction events

3.8.1 (5/23/2018)

• Add GDOT CCTV snapshots
• Fix FDOT responder names

3.8.0 - Mercurial Margaret (5/18/2018)

• Fix timestamps and cross street information in atis-tmdd-xml event output

3.7.5 (5/14/2018)

• Add Austin, TX events
• Add MiDOT CCTV

3.7.4 (4/24/2018)

• Add PA Turnpike events

3.7.3 (4/10/2018)

• Fix DDOT event location description

3.7.2 (3/29/2018)

• Add GDOT TSS

3.7.1 (2/27/2018)

• Add GDOT CCTV
• Speed up open DMS queries

3.7.0 - Maverick Margaret (2/13/2018)

• Add caching for /ritisfilter/probe/average
• Fix inconsistent intervals in /ritisfilter/probe/user_delay_costs output during DST changeover

3.6.2 (2/12/2018)

• Fix error loading caches for TMC expansion

3.6.1 (2/6/2018)

• Fix refreshing open events after media uploads
• Fix probe data providers in TMC location and speed data API documentation

3.6.0 - Meteoric Margaret (1/11/2018)

• Fix VDOT_NOVA media downloads
• Fix refreshing closed events after media uploads
• Fix open DMS queries to exclude closed messages
• Fix end intervals in /ritisfilter/probe/user_delay_costs exceeding the requested interval

3.5.2 (10/18/2017)

• Exclude outdated vehicles from event output
• Use Ansible for deployment

3.5.1 (9/15/2017)

• Fix VDOT event types

3.5.0 - Loquacious Laura (9/7/2017)

• Support metropolitan planning organizations in Geometry API
• Support mobile WxDE stations

3.4.1 (8/29/2017)

• Use prefix "CR" instead of "CO" for MD county routes

3.4.0 - Lackadaisical Laura (8/15/2017)

• Add PGCoTRIP events, DMS, and CCTV
• Fix CAD event description

3.3.1 (7/24/2017)

• Fix VDOT location description only containing direction
• Fix error finding average speeds in /ritisfilter/probe/tmc_expand_data

3.3.0 - Kafkaesque Kara (7/7/2017)

• Update the TMC location and speed data API to support:
  • Event data providers in the I-95 Corridor Coalition
  • Probe data providers INRIX and HERE
• Fix bugs in workzone cumulative UDC calculations
• Fix missing PGCoCAD event end times

3.2.1 (6/2/2017)

• Include events that have a proposed start time in the past but not a proposed end time when active-only filter is enabled

3.2.0 - Klutzy Kara (5/17/2017)

• Add CCTVs from Arlington County, VA
• Add Prince George's County CAD events

3.1.1 (4/19/2017)

• Add Caltrans CCTV
• Fix WxDE stations appearing at Null Island
• Fix NCDOT agency event types

3.1.0 - Kaleidoscopic Kara (3/10/2017)

• Allow planned-during filter to use only active events

3.0.5 (3/1/2017)

• Display WxDE observation times in stations' time zones

3.0.4 (2/22/2017)

• Update cached events only if their timestamps change
• Fix Waze event description

3.0.3 (2/10/2017)

• Add MiDOT DMS and TSS

3.0.2 (2/3/2017)

• Fix NY511 event types and description

3.0.1 (1/18/2017)

• Fix incorrect "fatalities involved" event types
• Fix timed out cache queries

3.0.0 - Killer Kara (12/22/2016)

New features

• Use RPM for deployment
• Overhaul the filter request parsing engine
• Validate incoming filter requests against their schemas
• Overhaul internal management tools
• Add the system-all filter option, allowing users to select all data sources they can access

Bug fixes

• Re-index all events for improved time range filtering
• Fix updated times of Howard County CAD events

2.4.8 (11/23/2016)

• Fix VDOT lane parsing

2.4.7 (11/04/2016)

• Fix MiDOT event types

2.4.6 (10/21/2016)

• Fix RTMP stream URLs for TrafficView

2.4.5 (10/20/2016)

• Filter out Waze congestion events

2.4.4 (10/19/2016)

• Allow events from different systems to update independently

2.4.3 (10/10/2016)

• Add Waze events

2.4.2 (08/12/2016)

• Filter data type documentation by permissions

2.4.1 (07/22/2016)

• Replace Clarus weather data with WxDE
• Upgrade reverse geocoding cache
• Fix parsing CHART vehicle types
• Remove invalid TrafficView cameras

2.4.0 - Jazzy Jamie (05/19/2016)

• Add SCDOT events and DMS
• Add DelDOT events, DMS, and CCTV
• Fix CHART lane parsing
• Add operations centers to communication logs in CHART events
• Add weather and road condition to events where available
• Fix WISDOT_CAD event ID filter
• Fix VDOT_NOVA media downloads

2.3.3 (03/17/2016)

• Add device coordinates to historical DMS output
• Handle CHART pending events

2.3.2 (01/26/2016)

• Add DDOT CCTV
• Add beacon status and device name to historical DMS output
• Cache historical DMS requests

2.3.1 (12/16/2015)

• Use the most recent message for WisDOT DMS devices

2.3.0 - Jubilant Jamie (12/14/2015)

• Add WisDOT data: DMS, CCTV, and CAD events
• Add API for historical DMS

2.2.5 (11/18/2015)

• Add DDOT events

2.2.4 (10/30/2015)

• Add timeout on RF requests

2.2.3 (10/9/2015)

• Fix case-insensitive road search backwards compatibility

2.2.2 (9/25/2015)

• Fix WZMPA missing opposite TMC bug

2.2.1 (9/16/2015)

• Add WisDOT events

2.2.0 - Jealous, Jaded Jingoistic John (8/20/2015)

• Change the lane parsing algorithm
• Change road filter to be case insensitive
• Add new Geometry API
• Fix several bugs

2.1.2 (7/17/2015)

• Fix reporting system for VDOT events

2.1.1 (7/16/2015)

• Fix outputting NWS Alerts that have ended

2.1.0 - Jaded Jingoistic John (5/28/2015)

• Add RIDOT events
• Relax rate limiting for most users
• Fix several WZMPA data bugs
• Fix sort-by distance calculations
• Update the available list of CCTV devices for CHART

2.0.12 (4/6/2015)

• Fix VDOT lane ordering
• Fix VDOT historical queries
• Fix outputting incorrect format in certain cases

2.0.11 (3/12/2015)

• Support new Virginia data sources

2.0.10 (3/12/2015)

• Fix media upload bug

2.0.9 (3/3/2015)

• Improve the reference docs
• Fix several bugs

2.0.8 (2/23/2015)

• Add MIDOT events
• Fix a bug with duplicate VDOT CCTVs

2.0.7 (2/12/2015)

• Fix a bug where null system returned all systems
• Improve performance slightly

2.0.6 (2/9/2015)

• Fix a bug where media for Iowa events would not appear
• Fix spelling of X-Request-Identifier
• Fix road name filter for certain data types
• Improve event attributes

2.0.5 (1/29/2015)

• Tweak IowaDOT event data
• Fix several bugs

2.0.4 (1/27/2015)

• Fix error when there is no Content-Type
• Update media upload success message to match RF 1.4

2.0.3 (1/21/2015)

• Fix some incorrect permissions
• Fix several bugs

2.0.2 (1/20/2015)

• Make output schemas publicly accessible
• Minor backend improvements to historical queries
• Tweak CCTV output

2.0.1 (1/5/2015)

• Fix several bugs

2.0.0 - Jingoistic John (1/5/2015)

New features

• Complete internal overhaul, improve overall reliability and performance
• Improve historical query performance up to 30x
• Improve documentation
• Use HTTP status codes in errors responses
• Allow logging in with RITIS credentials
• Add authentication via HTTP header
• Add IOWADOT events
• Add request identifier HTTP header
  • Every request has a new header in the response: 'X-Request-Identifier'. If you encounter a problem, try to include this value when you contact support@ritis.org.

Bug fixes

• Fix closed lane filters
• Update UDC algorithm
• Various CCTV fixes
• Various event data improvements

Other

• Deprecate authentication with API key in the body of a POST request (to be removed in 2.1.0)
• Remove since filter
• Remove authentication via basic authentication

1.4.0 - Incredibly Iconic Ionian

• Add DDOT permits
• Add HERE TSS
• Add VDOT CCTV

1.3.0 - Heroic Helo

• Add flexible filtering for events
• Deprecate event-filter
• Evacuation overhaul

1.2.0 - Gallivanting Galactica

• Add AuthMod support

1.1.5 - Furious Felix

• Add CALTRANS & DDOT DMS
• Add CALTRANS & WSDOT events
• Add evacuation data types
• Add weather alerts data type
• Add developer API key scheme
• Add transit data sources

1.1.4r1 - Everloving Elegant Ellen

• Deprecate xml-type parameter; use format instead
• Add format parameters
• Improve server module

1.1.4 - Everloving Ellen

• Add PADOT data source
• Add RITIS Filter Media
• Type & attribute filtering for RF-Schema XML Type is now fully functional
• Speed improvements for historical event requests
• ID filter will determine the correct system if not present

1.1.3 - Dead Dualla

• Significant internal changes
• Add OHDOT & MSTraffic data source
• Deprecate fuzzy geospatial filter

1.1.2-r1 - Completely Collapsed Caprica R1

• Fix since, geospatial, fuzzy-geo filters
• Standardize lane parsing

1.1.2 - Collapsed Caprica

• Add caching for common requests
• Add geospatial cache using fuzzy-geospatial
• Add number of messages filter for DMS requests in RF-Schema

1.1.1 - Bizarre Baltar

• Add VATraffic support for events
• Add Radio Reference feeds
• Add CHART CCTV feeds
• Add Clarus Road Weather feeds
• Change device filter types to: device_[type of device] (supports 'cctv' amd 'radiofeed' currently)
• DMS, Detector, Clarus, Radio Reference & CCTV now use the same location node as Events
• VATraffic won't return data for a 72km radius around (38.864643, -77.499414) because this is the area for OpenTMS

1.1.0 - Admiral Adama

• First general release
• Support snapshot filtering for incident/event requests
• Fix incorrect content-length bug in JSON conversion
• Add TMC filter
• Improve support for historical data