Tracking Cumulative Travels
Contents
🔗 Data errors
code
of a data error is indicated in the last column of the waypoint table. Use the tool tip for additional info.
After manual changes within the editor field, the data check is done on the next editor action, e.g. when pressing the Load
button.
Check the table for errors before saving the .wpt
file. Fix unintended errors or mark intended errors false positive.
Note: Not all data errors are detected by the WPT file editor, see below: Link | Code | Description | WPT FileEditor | FP possible |
🔗 | ABBREV_AS_CHOP_BANNER | The route's chopped routes .csv file entry has the Abbrev erroneously entered into the Banner field. | ||
🔗 | ABBREV_AS_CON_BANNER | The 2 potential underlying causes are:
|
||
🔗 | ABBREV_NO_CITY | The route's chopped routes .csv file entry has an Abbrev, but no City.
If the same route is also flagged as ABBREV_AS_CON_BANNER, the Abbrev data should probably be moved to the Banner .
| ||
🔗 | BAD_ANGLE | Angles cannot be computed for two adjacent points at the same coordinates. Instead, use AltLabels or fix coordinates of one point or both. |
||
🔗 | BUS_WITH_I | Label looks like an Interstate with Bus banner instead of BL or BS . |
||
🔗 | CON_BANNER_MISMATCH | The route's Banner field in its chopped routes .csv file mismatches the Banner field in its connected routes .csv file. | ||
🔗 | CON_ROUTE_MISMATCH | The route's Route field in its chopped routes .csv file mismatches the Route field in its connected routes .csv file. | ||
🔗 | DISCONNECTED_ROUTE | The 3 potential underlying causes are:
|
||
🔗 | DUPLICATE_COORDS | Duplicated coordinates for two or more waypoints | ||
🔗 | DUPLICATE_LABEL | Duplicated labels for more than one waypoint. Labels must be unique for each route. | ||
🔗 | HIDDEN_JUNCTION | Concurrent route splits off at a hidden waypoint. The concurrency is most likely broken by accident, or the waypoint needs to be visible. | ||
🔗 | HIDDEN_TERMINUS | Hidden point at the beginning or end of a route. Routes must begin and end with visible waypoints so that users can mark all of them as traveled. | ||
🔗 | INTERSTATE_NO_HYPHEN | Label looks like an Interstate without a hyphen between the I and numerals. |
||
🔗 | INVALID_FINAL_CHAR | Disallowed character at end of label | ||
🔗 | INVALID_FIRST_CHAR | Disallowed character at beginning (after any leading * characters) of label |
||
🔗 | LABEL_INVALID_CHAR | Label contains at least 1 invalid character, or no valid characters other than * or + .
Labels may only contain letters, numerals, parentheses, slashes, underscores, hyphens, or periods, with an optional leading plus sign or asterisk. |
||
🔗 | LABEL_LOOKS_HIDDEN | X123456 style label without a leading + . |
||
🔗 | LABEL_LOWERCASE | Label starts with a lowercase letter. | ||
🔗 | LABEL_PARENS | Number of parentheses do not match. Opened ( must be closed with ) . |
||
🔗 | LABEL_SELFREF | Label appears to reference own route.
This datacheck is designed to flag cases where a line was directly copied from another .wpt file without the label being changed.
The site update program looks at intersecting routes in order to eliminate false positives. Several error subtypes are listed in the Info column, with different ways they can be fixed before marking false positive:
|
||
🔗 | LABEL_SLASHES | Too many slashes in label (> 1 ). |
||
🔗 | LABEL_TOO_LONG | Label is too long to fit in the space allocated for the DB field. | ||
🔗 | LABEL_UNDERSCORES | Too many underscored suffixes (> 1 ) |
||
🔗 | LACKS_GENERIC | Label begins with Old followed immediately by a number without a
preceding generic designation type such as US , E , A , Hwy , Rte , etc. |
||
🔗 | LONG_SEGMENT | Long segment (distance > 20 mi , 32 km ) between this and the previous hidden point. |
||
🔗 | LONG_UNDERSCORE | Label has long underscore suffix: > 4 characters after underscore,
or 4 characters not ending in a capital letter. |
||
🔗 | LOWERCASE_SUFFIX | Underscored suffix starts with a lowercase letter. | ||
🔗 | MALFORMED_LAT | Invalid argument after lat= in URL which cannot be converted to a numeric value |
||
🔗 | MALFORMED_LON | Invalid argument after lon= in URL which cannot be converted to a numeric value |
||
🔗 | MALFORMED_URL | URL (last field in WPT line) is missing lat= and/or lon= argument(s) |
||
🔗 | NONTERMINAL_UNDERSCORE | Label has underscore suffix before slash | ||
🔗 | OUT_OF_BOUNDS | Latitude > 90° or < -90° , or longitude > 180° or < -180° .
False positives are allowed for the rare potential case of routes spanning the international date line. |
||
🔗 | SHARP_ANGLE | Sharp angle (> 135° ) with previous and next waypoint. |
||
🔗 | SINGLE_FIELD_LINE | WPT file line only contains one field. Each line must have a minimum of 2 space-separated fields: A waypoint label followed by an OpenStreetMap URL. Deprecated alternate labels may optionally be included in between. | ||
🔗 | US_LETTER | Label uses USxxxA or USxxxB rather than USxxxAlt , USxxxBus , USxxxByp , etc. |
||
🔗 | VISIBLE_DISTANCE | Long distance (Visible distance > 10 mi , 16 km ) between this and the previous visible point. Not reported for active routes! |
||
🔗 | VISIBLE_HIDDEN_COLOC | Visible waypoint is hidden on intersecting/concurrent route(s).
The Info column lists only the first hidden point at the same location.
Best practice is to check this location on all intersecting/concurrent routes and ensure:
|
🔗 Highway data check list
Route
column to load the route into the HB.🔗 Marking errors false positive (FP)
FP entry to Submit
.🔗 Concurrency check
🔗 Load graph with mapview
OK
.Color by Concurrencies
under Visible Routes
.Highlight None
.🔗 Load graph with Highway Data Examiner (HDX)
Option 1
on the left and enter the name of the region you want to check.Show Markers
and select whatever region graph you are actually interested in to speed up loading.Show Data Tables
to close the table to the right.Show Markers
.Show Markers
again, it was just to show you what happened.🔗 Check for broken concurrencies
.wpt
files..wpt
files into the WPT file editor to avoid causing unintended data errors.🔗 Near-miss points
0.000001°
. This was likely done intentionally to break concurrencies and the waypoints are candidates to be marked FP..wpt
files..wpt
files into the WPT file editor to avoid causing unintended data errors.🔗 Marking NMPs false positive FP
FP Entry to Submit
can only be found in nearmisspoints.log which contains all NMP entries including those which are already marked FP. The list is sorted by region code.
lat
or lon
coordinates (or route code) which one can copy from the HDX table.[LOOKS INTENTIONAL]
, this part of the entry must be removed.[MARKED FP]
are already entered as FP.