Tracking Cumulative Travels
Travel Mapping Highway Data Datacheck Errors
Quick links: [Errors in
See also the [Log of Unmatched FPs from datacheckfps.csv]. Cleaning these up are low priority tasks for the project. Some of these are likely fixable from the information in the [Log of Near-Match FPs from datacheckfps.csv].
Errors in Active Systems (not FPs)
These errors should be corrected, or reported as false positives by adding the entry from the last column to the datacheck FP list as soon as possible. Ideally, this list should always be empty.
| Route | Waypoints | Error | Info | FP Entry to Submit |
|---|
Errors in Preview Systems (not FPs)
These errors should be corrected, or reported as false positives by adding the entry from the last column to the datacheck FP list during the final review process to promote a highway system from 'preview' to 'active'. A highway system should have no entries here before activation. Errors shown in red potentially effect travelers and should be fixed as soon as possible, while others can wait until final preparation for system activation.
| Route | Waypoints | Error | Info | FP Entry to Submit |
|---|
Errors in In-Development Systems (not FPs)
These errors should be corrected, or reported as false positives by adding the entry from the last column to the datacheck FP list before the highway system is promoted from 'devel' to 'preview'. Note: less severe errors, such as distance and angle errors can be left until final preparation for promotion to 'active'.
| Route | Waypoints | Error | Info | FP Entry to Submit |
|---|
Errors Marked as FPs ("Crossed Off")
These have been marked as FPs in the datacheck FP list and can normally be safely ignored. However, if any of these are discovered to be true errors, they should be removed from the list and fixed in the highway data.
| Route | Waypoints | Error | Info | FP Entry Matched |
|---|---|---|---|---|
| me.me104 | ME27,WatSt,TowRd | SHARP_ANGLE | 136.04 | me.me104;ME27;WatSt;TowRd;SHARP_ANGLE;136.04 |
| me.me156 | McCCorRd,ZioHillRd,KnoCorRd | SHARP_ANGLE | 141.85 | me.me156;McCCorRd;ZioHillRd;KnoCorRd;SHARP_ANGLE;141.85 |
| me.cadsumrd | +X133948,+X138493,End | SHARP_ANGLE | 136.02 | me.cadsumrd;+X133948;+X138493;End;SHARP_ANGLE;136.02 |
| me.cadsumrd | +X185788,+X133948,+X138493 | SHARP_ANGLE | 148.79 | me.cadsumrd;+X185788;+X133948;+X138493;SHARP_ANGLE;148.79 |
| me.cadsumrd | +X858922,+X185788,+X133948 | SHARP_ANGLE | 156.59 | me.cadsumrd;+X858922;+X185788;+X133948;SHARP_ANGLE;156.59 |
| me.parklprd | OttCliRd,OttPt,+X563093 | SHARP_ANGLE | 150.85 | me.parklprd;OttCliRd;OttPt;+X563093;SHARP_ANGLE;150.85 |
| me.parklprd | SieMonRd_S,SieMonRd_N | DUPLICATE_COORDS | (44.362437,-68.203779) | me.parklprd;SieMonRd_S;SieMonRd_N;;DUPLICATE_COORDS;(44.362437,-68.203779) |