XML Traffic Signs Explorer

A local, human-readable inspector for DATEX II / VMS-style XML traffic-sign files. Built for ASFINAG-like static and dynamic publications without turning your browser into a surveillance device.

No cookies No banners No tracking No server communication No external libraries Offline-capable single file
This tool runs fully in your browser. XML files are parsed locally. No cookies. No tracking. No server communication. External URLs found inside XML are shown as text only and are not fetched by this tool.

Internal data model and parsing strategy

The parser first normalises each XML file into five working entities: FileSummary, StaticVmsController, StaticVms, DynamicVmsStatus, and JoinedVmsRecord. It uses the browser DOMParser, ignores namespace prefixes, reads elements by local name, and treats optional DATEX/VMS fields as absent rather than fatal.

Parser assumptions and known limits
  • Static publications are primarily identified by VmsTablePublication, vmsControllerTable, vmsController, and vmsLocation.
  • Dynamic publications are primarily identified by VmsPublication, vmsControllerStatus, vmsStatus, workingStatus, vmsMessage, and timeLastSet.
  • Namespace prefixes such as q1, q8, or generated aliases are intentionally ignored.
  • For values like pictogramDescription and laneUsage, the parser prefers _extendedValue when the visible text is generic, such as other or _extended.
  • Joining prefers exact controller ID + VMS index. If that fails, it falls back to VMS index alone and marks the match method.
  • Staleness is user-selectable. The default reference is the newest loaded XML timestamp, not necessarily the current clock, because archived sample files would otherwise look misleadingly stale.
  • Compressed .xml.gz files are decompressed locally in the browser when the browser supports the native Compression Streams API. No decompressed content is uploaded.
  • German or mixed-language source text is not silently translated. The tool shows the raw value and adds a small local English interpretation only for known traffic words.
Drop XML or XML.gz files here

Load one or more static and dynamic traffic-sign XML files, including .xml.gz files from access points. Nothing is uploaded. The analysis is rebuilt in memory each time.

No XML loaded yet

Load a static file, a dynamic file, or both. The useful bit is the comparison: static files say what infrastructure exists; dynamic files say what those signs are currently doing.

Executive summary

Key facts

Static vs dynamic record types

Working status distribution

Message information types

Pictogram descriptions

Speed values

Messages by timeLastSet date

Controller category distribution

Coordinate scatterplot

Word cloud: VMS text lines

Word cloud: pictograms and supplementary descriptions

Load both static and dynamic XML to see infrastructure joined to current status.

Data-quality findings

Raw XML

Preview only. The file is already parsed locally. Large files are truncated in this view to keep the browser responsive.

No raw XML available yet.