Calibrating with Single Factor User-provided Counts

This tutorial will walk you through how to calibrate a Project using "Single Factor User-provided Counts." This requires using the StreetLight InSight Calibration Feature to scale to estimated counts using your own local traffic count data. This is a great tool for any user who wants to get estimated counts rather than our StreetLight Index, learn more about our Index. Single Factor Calibration is available for the following project types: Zone Activity Analysis, O-D Analysis, O-D with Middle Filter Analysis, O-D to Preset Geography and Segment Analysis. To learn more about how to create a Single Factor Calibrated Project. Also, learn more about calibration with StreetLight AADT.

For this guide, we will go step-by-step to help you set up your Calibrated Project using a Calibration Zone Set that contains your local traffic count data. You must start by adding calibration to your Zone Set--before even running a Project in StreetLight InSight. Learn more on how to create a Calibrated Zone Set. 

Note:

  • The “Single Factor User-provided Counts” option requires that you have reliable data about average daily travel for road segments near your Project study area. We recommend checking with the transportation agency in your state or province. The data can be in the form of Average Daily Trips (ADT), Average Annualized Daily Trips (AADT), Average Weekday Trips (AWDT), or Average Annualized Weekday Trips (AAWDT).
  • When calibrating with the Navigation-GPS data source, it is preferable to use data that estimates the share of personal and commercial vehicles. Also, note that this feature works best when you upload local traffic data for roads that are similar to the roads used in your analysis.  For example, don’t calibrate tiny local roads with highway data, or use data from California for a study in Toronto. While it may be fine to calibrate larger arterials with highway data, you should get better results from using calibration data that is as similar as possible to your Project. Feel free to contact us if you have questions about finding the right calibration data. Additionally, this feature is also recommended for small- to medium-sized Projects. Results may not be as accurate for very large Projects.

Setting up a Calibration Project with “Single Factor User-provided Counts"

Step 1: Create your Zone Set. Learn more on creating Zone Sets. 

Note: For “Single Factor User-provided Counts”, only Zones added to the Calibration Zone Set that are marked as pass-through and have calibration data will be used. Zones that don’t have calibration data or are not marked as pass-through will be ignored during calibration.

Step 2: Go to the “Create Projects” tab and set up your Project:

  • Project Type: "Zone Activity Analysis," "O-D Analysis," "O-D with Middle Filter Analysis." "O-D to Pre-set Geography," or "Segment Analysis" 
  • Type of Travel: "Personal" or "Commercial"
  • Modes of Travel: "All Modes," "Bicycles," "Pedestrians"
  • Data Source: "Location-Based Services with Pass-through" or "Navigation-GPS"
  • Calibration Type: "Single Factor with User-provided Counts"

Step 3: When you choose one of the “Calibrate Type” options, a new Zone Set category window will appear allowing you to select a Calibration Zone Set. Add your Calibration Zone Set by selecting it from the “Available Zone Sets” tab and clicking the arrow under “Calibration.”

Calibration_Moving.png

Step 4: Click "Confirm"

Once the Project is marked as “Complete” on the All Projects tab you’ll be able to download and visualize the results. When visualizing and working with the downloaded .csv files, look for the “Calibrated StL Index” value. You’ll see this value right next to the “StL Index” values that are generated for every project. This “Calibrated StL Index” value will reflect an estimated trip count for your selected Zone or O-D pair based on the Calibration Zones included in your Project.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.