{'fraction_non_alphanumeric': 0.026714158504007122, 'fraction_numerical': 0.006233303650934996, 'mean_word_length': 5.2444444444444445, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Deliver a Set of Tools for Resolving Bad Inductive Loops and Correcting Bad Data

This project prototyped and demonstrated procedures to find and mitigate loop detector errors, and to derive more valuable data from loops. Specifically, methods were developed to find and isolate out "bad" or invalid loop data, so that fixes can be implemented. Methods of extracting very accurate speed (+/- 3mph) and vehicle length data (+/-1meter) from single loop stations were demonstrated to be much more accurate than current Caltrans (California Department of Transportation) practice. The validity of these methods was statistically proven using hundreds of thousands of vehicles. Additionally, more accurate and reliable methods of detecting the onset of both recurring and incident-based congestion were demonstrated. These methods require access to the unprocessed loop detector card data. This unprocessed data can be acquired from the Log170 program, third party loop readers like the Infotek Wizard, or Caltrans' C1 reader. Caltrans intends to implement many of these methodologies in the C1 reader client software, Videosync