Origin Destination Data Services

The Vendor is required to provide origin-destination (OD) data via a web-based interface.
- Data discussion shall include:
• Availability and accuracy of spatial level, temporal level and user class data;
• Ability to provide daily average, hourly or other sub-daily breakdowns;
• Ability to accurately provide vehicle mix representation
• Discussion of the presence and effects of biases such trip length distribution, income, vehicle type etc.;
• Discussion of how many years of historical data are available for query as well as the frequency that new data are added to the data set;
• Effective sample size of the data and weighting and calibration techniques applied to the data.
• A table shall be included denoting the data sources that are used as input to the vendor’s data product with the monthly (or other specified time frame) sample size of each source.
• Table of what data sources have been used over the last three years in the production of the offered department data product.
• Names of the data sources should be used when available what type of data the source represents should be denoted, and the percentage of each source by year represented in the offered department data product.
• Discussion of what methods are applied to purchased data in the development of the offered OD data product should be included as well as discussion of the data used to calibrate and validate the offered OD data product
• Discussion of other processing applied to the raw data such as outlier removal, trip end identification, road centerline snapping etc.;
• Existence of tools provided in the web interface for user control of weighting and calibration using local data, including discussion of any advanced techniques such as but not limited to iterative proportional fitting as well as any other user control provided such as dwell time thresholds to trip end identification etc.;
• Ability to provide unbiased temporal trend analysis and methods used to account for temporal changes in sample rates and sources;
• Methods provided for indicating the geography for OD catchment including methods that can be implemented in tool vs. support for uploading geography from GIS as well as ability to indicate geographies by points, lines or polygons and the ability to segment or specify trips that begin and end at a geography vs. those passing through;
• Ability to obtain roadway segment volumes, by both department linear reference system (LRS) and other non- department segments (by class including auto, truck, bike, pedestrian etc.), speeds, harsh braking events, phone use while driving, or other metrics with the query tool;
• Discussion of size of data queries that are possible; i.e. how many geographic areas or roadway segments can be queried at once and whether all roadway segments within a subarea can be queried at once (and the maximum size of that subarea);
• Ability to provide OD data for specific days or hours for the analysis of incidents, local and special events, or seasonal and weekend travel patterns.
• Ability to link trips into tours and derive tour metrics, including tour length, trip lengths, and number of stops on tours.
• Ability to provide raw trip and waypoint data from the vendors noted in (g.).