Limitations

What the viewer does not do should be as clear as what it does.

In short

  • One file, no history. No statement on update cycle, timeliness or availability.
  • Ceilings, not ratings. RTTI star levels are upper bounds from selected criteria, not an official TISA rating.
  • Scores rank. Matching scores rank candidates; they are not probabilities.
  • Review, not verdict. A flagged contradiction calls for review; it proves no error.

Location referencing

A gmlLineString (v2 linearExtension, v3 LinearLocation) in WGS 84 degrees is drawn as a line. A record without one is drawn from the LinearElementByPoints of a linear location: a line through its points, cut to fromPoint/toPoint, with distances measured along the points. A LinearElementByPoints in a pointAlongLinearElement is not drawn as a line, because the point along it is not computed; its points are drawn as points when the record has no line. ALERT-C, TPEG and coded linear-element references are listed, not decoded. See Map for the full order.

Structured OpenLR lines and points are decoded, and their points are marked for the selected record. OpenLR areas are only recognised. OpenLR carries no road shape between its points: a decoder finds the shortest path in its own map. The viewer has no such decoder, so a record with no other line is drawn as straight segments between the points of one OpenLR line whose points are valid WGS 84 positions, trimmed by its offsets. That line cuts corners, and road matching runs against it as it is. The geometry is chosen before the checks run, so a record whose OpenLR fails OLR-003 or OLR-004 but has correct point coordinates is still drawn as the OpenLR line. Binary OpenLR is not decoded.

OpenLR road classes (FRC, LFRCNP) are shown as published and not mapped to OSM road classes, because publishers define them against different map data.

For the RTTI indicators, only a gmlLineString or a structured OpenLR line counts as a polyline (conditions). A line drawn from a LinearElementByPoints does not count.

The posList axis order is "lat lon" per EPSG:4326. "lon lat" files are detected from explicit latitude/longitude points of the same records, or can be set by hand in the report.

Profile checks are heuristic

They come from the profile documentation and observed feeds. They are no conformance test. Use XSD validation for schema conformance.

OSM ids from tiles

OpenFreeMap tiles are built with planetiler, which encodes osmId × 10 + type. Features merged from several ways are common even at zoom 14, and their id names only the first way. For those, the viewer looks up the clicked way by location, and matching splits them into their ways (details).

Matching

Matching uses the z14 tile geometries along the record, up to 150 tiles. The score ranks candidates; it is not a calibrated probability. If all lookups for the individual ways of a merged feature fail, the merged feature is kept and marked as such.

Lanes

OSM lane tags describe the usual layout and DATEX II a temporary one. A difference is a hint, not an error. The direction mapping between DATEX II and OSM is not verified.

Size

Files are streamed in a Web Worker. A 209 MB (16 MB gzipped) feed with 61,000 records works but needs several hundred MB of memory. XSD validation loads the whole document (max 400 MB).