Using the viewer¶
Open the viewer and drop a DATEX II file into the window, or click Open DATEX II file…. Don't have a file yet? See Getting a DATEX II file.
Layout¶
The window has three panes:
- Feed (left): the report, the RTTI 5-Star panel and the record list with its filters.
- Map (centre): record geometries, OpenStreetMap roads, lane arrows and OpenLR points.
- Inspector (right): details of the selected record or OSM road, in tabs.
Below 900 px width, the layout shows one pane at a time; the Feed, Map and Inspector buttons in the top bar switch between them.
Report¶
The report keeps the layers of the analysis apart, so a problem in one does not hide in another:
- XML: well-formed or the first error with line and column.
- DATEX II: version,
modelBaseVersion, publication type, publication time and creator, SOAP envelope, namespaces, and the axis order ofgmlLineStringpositions (you can override it). - XSD validation: "not performed" until you select schema files (see below).
- Profile (heuristic): the detected profile, with a selector to re-run the checks with another.
- Extensions, then the findings, grouped by layer (semantics, location, lanes, passability, …).
Each finding names its rule (for example LOC-002 or DQ-RW-001) and links to the affected records.
Click it to select the record and open the right inspector tab. Checks explains the rules.
Record list and filters¶
Every situationRecord appears in the list. Only visible rows are rendered, so feeds with 60,000+
records stay fast. Filters:
- Record type chips with counts, coloured as on the map.
- Passability: passable, restricted, closed, conditional, conflicting, unknown (see Passability and contradictions).
- Location: on the map, not drawable, OpenLR present.
- active now: records whose validity includes the current time.
- Lane configuration (only for feeds with lane status codes): reversible lane, hard shoulder open or closed, narrowed or closed lane, parking lane and restrictions, cycleway and pedestrian path open or closed. The same icons mark records in the Situation section of the Record tab.
- Search over id, situation id, road number and name, description, record type and management types.
Keyboard: ↑ / ↓ move through the list, Esc clears the selection.
Map¶
The map shows the records that pass the list filters. Each record is drawn from the best location it has, in this order:
- a
gmlLineString, drawn as a line; - a
LinearElementByPointsin a linear location (linearWithinLinearElement): a line through its points, cut to the section between itsfromPointandtoPoint(distances measured along the points); - a structured OpenLR line whose location reference points are all valid WGS 84 positions (the
firstDirectionsection first; one of zero length is skipped): straight segments between its points, trimmed by its offsets (scaled to that line; offsets that would leave nothing are ignored); - a
gmlLineStringwhose positions are all the same point, drawn as a point; - point coordinates or a display point (
locationForDisplay,coordinatesForDisplay), drawn as points. This includes the points of aLinearElementByPointsin apointAlongLinearElement: the viewer does not compute the point along the element.
The Geometry row of the Record tab says which of these the drawn geometry comes from. It marks steps
3–5 approximate: OpenLR carries no road shape between its points, so its line cuts corners. On the
map, these look like any other line or point. OpenLR point locations are not drawn as lines. Records
with nothing to draw are listed with the reason (LOC-001). The location examples
show the first three in XML.
- Select record mode (default): click a record on the map to select it. A record drawn as a line is matched to OSM roads by itself, and the best way is highlighted.
- Select OSM road mode: click a road (zoom ≥ 14) to look it up in OpenStreetMap; its tags appear in the inspector.
- Arrows along the selected record show the order of its points. Arrows along the highlighted OSM way show the direction it is shown in: the travel direction on a one-way road, otherwise the record's direction when that is known. The compass rose in the Lanes and OSM tabs points the same way.
- OpenLR location reference points are marked for the selected record: the first green, the last red, joined by a dashed line in their order.
The map position is kept in the URL (#map=…), so you can share a view. Nothing about your file is put
in the URL.
Inspector tabs¶
| Tab | Shows |
|---|---|
| Record | Type, validity, management types, cause links, situation with its other records, location methods, the drawn geometry with its source and confidence (direct or approximate), and OpenLR references: their points and road classes (FRC, LFRCNP) as published, with the OSM road class hierarchy for comparison. |
| QA | Which RTTI criteria this record holds down and why, then every finding about the record. |
| XML | The original XML of the record or of its whole situation, cut from the file. |
| Lanes | DATEX II lane status next to the OSM lane layout of the matched way (details). |
| Matching | OSM road candidates with their score components (details). |
| OSM | Tags of the selected or matched OSM way, each linked to the OSM wiki. |
XSD validation¶
Real schema validation runs in your browser with libxml2 compiled to WebAssembly. The viewer downloads no schema by itself.
- Get the XSD files of the DATEX II version or profile your feed uses (see Schemas and profiles) and unpack them.
- In the report, section 3 · XSD validation, click Validate against XSD files….
- Select the main schema together with all files it imports or includes (multi-select). The viewer takes the file that no other file references as the main schema.
- The result shows valid or the number of errors with line numbers (the first 100 are listed), and which schema was used.
XSD validation loads the whole document into memory; files up to 400 MB are accepted.
Dark mode, motion and privacy¶
Dark mode follows your system setting, and motion is reduced when your system asks for it. The map credits link to the Impressum and to a Privacy dialog that lists every service your browser contacts; see Privacy.