<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://wiki.opentrafficmap.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://wiki.opentrafficmap.org/feed.php">
        <title>OpenTrafficMap Wiki</title>
        <description></description>
        <link>http://wiki.opentrafficmap.org/</link>
        <image rdf:resource="http://wiki.opentrafficmap.org/_media/wiki:dokuwiki.svg" />
       <dc:date>2026-08-08T07:19:07+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:faq?rev=1786035079&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:software:mqtt?rev=1786034290&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:pageideas?rev=1786034192&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:start?rev=1786033435&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:contributing?rev=1786033432&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:sightings?rev=1786033429&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:reception?rev=1786033426&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:software:home_assistant?rev=1786033380&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:software:transmission_methods?rev=1786033377&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:start?rev=1786033339&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:messages:ivim?rev=1786033336&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:messages:spatem?rev=1786033333&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:messages:mapem?rev=1786033330&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:messages:denm?rev=1786033327&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/verbreitung?rev=1786032731&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en:c-its:senders?rev=1786032661&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/messages:cam?rev=1786032121&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/c-its:rsu?rev=1786032117&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/c-its?rev=1786032114&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/gehaeuse?rev=1786032111&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://wiki.opentrafficmap.org/_media/wiki:dokuwiki.svg">
        <title>OpenTrafficMap Wiki</title>
        <link>http://wiki.opentrafficmap.org/</link>
        <url>http://wiki.opentrafficmap.org/_media/wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="http://wiki.opentrafficmap.org/en:faq?rev=1786035079&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:51:19+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>faq - add cross references to detail pages, fix small typos</title>
        <link>http://wiki.opentrafficmap.org/en:faq?rev=1786035079&amp;do=diff</link>
        <description>FAQ

What does the QR Code mean on the back side of the case?

If you scan the QR code with a mobile phone, you will be directed to the “Node Admin page” of this device.
URL &lt;https://opentrafficmap.org/service/?nodeId=nodeXXX&gt;

ATTENTION: Please change the “User Password” to protect your node settings!</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:software:mqtt?rev=1786034290&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:38:10+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>mqtt - clarify: topic uses the node ID from the self-service portal</title>
        <link>http://wiki.opentrafficmap.org/en:software:mqtt?rev=1786034290&amp;do=diff</link>
        <description>MQTT Server

All receivers report their data to a central MQTT broker, which feeds the live map at opentrafficmap.org.

Connecting

	*  The current connection string (host and port) is defined in the firmware: its-g5-receiver-firmware/main/config.c
	*  Publishing requires no username or password.
	*  Every node identifies itself by its</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:pageideas?rev=1786034192&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:36:32+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>pageideas - software:mqtt now fully implemented</title>
        <link>http://wiki.opentrafficmap.org/en:pageideas?rev=1786034192&amp;do=diff</link>
        <description>Page Ideas

Status Aug 2026: ✔ = implemented (link points to the actual page — some names differ from the original plan below), ◐ = partially covered, ○ = still open.
 Planned page  Status  Actual page / notes  start  ✔  start (incl. documentation overview and group order)</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:start?rev=1786033435&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:23:55+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>start - add documentation overview section</title>
        <link>http://wiki.opentrafficmap.org/en:start?rev=1786033435&amp;do=diff</link>
        <description>OpenTrafficMap Wiki

OpenTrafficMap is an open project for visualizing and analyzing C-ITS data (Cooperative Intelligent Transport Systems). Its goal is to make visible which data traffic lights, trams, buses, and modern cars are already transmitting unencrypted today.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:contributing?rev=1786033432&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:23:52+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>contributing - Create contributing page</title>
        <link>http://wiki.opentrafficmap.org/en:contributing?rev=1786033432&amp;do=diff</link>
        <description>Contributing

OpenTrafficMap is an open project — here is how you can help:

Run a receiver

The most valuable contribution: live data can only be shown where at least one receiver is nearby.

	*  Get a receiver via the group order or build one yourself — see</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:sightings?rev=1786033429&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:23:49+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>sightings - Create sightings page</title>
        <link>http://wiki.opentrafficmap.org/en:sightings?rev=1786033429&amp;do=diff</link>
        <description>Sightings

Field observations: what has actually been received where. Feel free to add your own sightings — ideally with date, location, message type, and a screenshot from the live map.

Background on what you can expect to see: Who is sending C-ITS?

Austria

Graz

	*  Traffic lights, trams, and buses are visible on the live map.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:reception?rev=1786033426&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:23:46+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>reception - Create reception and placement guide</title>
        <link>http://wiki.opentrafficmap.org/en:reception?rev=1786033426&amp;do=diff</link>
        <description>Reception &amp; Placement

C-ITS can only be received over a few hundred meters up to a few kilometers, so receiver placement makes a big difference.

Mounting position

	*  The higher, the better. With the 3D-printed enclosure, the receiver board can be mounted outdoors.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:software:home_assistant?rev=1786033380&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:23:00+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>home_assistant - Create Home Assistant integration page</title>
        <link>http://wiki.opentrafficmap.org/en:software:home_assistant?rev=1786033380&amp;do=diff</link>
        <description>Home Assistant

There are two ways to combine OpenTrafficMap with Home Assistant:

Monitoring an OpenTrafficMap node

The node publishes its telemetry to the MQTT broker. Home Assistant can read it via the MQTT integration; from there you can build sensors, automations, and dashboards. The credentials for subscribing to your own node are shown in the self-service portal — see</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:software:transmission_methods?rev=1786033377&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:57+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>transmission_methods - Create transmission methods overview</title>
        <link>http://wiki.opentrafficmap.org/en:software:transmission_methods?rev=1786033377&amp;do=diff</link>
        <description>Transmission Methods

There are several ways to get the C-ITS frames received by an ESP32-C5 into OpenTrafficMap (i.e. onto our MQTT server):

Ethernet (official firmware)

Connect the ESP32-C5 directly to the internet with an SPI-to-Ethernet chip (W5500, ENC28J60):</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:start?rev=1786033339&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:19+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>start - link all message type pages</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:start?rev=1786033339&amp;do=diff</link>
        <description>What is C-ITS?

C-ITS stands for Cooperative Intelligent Transport Systems: vehicles and infrastructure communicate with one another.

Typical C-ITS participants are:

Stationary RSUs - Road Side Units

	*  Traffic lights (traffic signal installations)
	*  Roadworks signs</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:messages:ivim?rev=1786033336&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:16+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>ivim - Create IVIM page</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:messages:ivim?rev=1786033336&amp;do=diff</link>
        <description>IVIM (Infrastructure to Vehicle Information Message)

IVIMs carry road sign and infrastructure information (ETSI TS 103 301 / ISO 19321) — essentially electronic road signage.

Typical contents:

	*  variable speed limits from overhead gantries
	*</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:messages:spatem?rev=1786033333&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:13+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>spatem - Create SPATEM page</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:messages:spatem?rev=1786033333&amp;do=diff</link>
        <description>SPATEM (Signal Phase and Timing Extended Message)

SPATEMs transmit the current state of a traffic light (ETSI TS 103 301): which signal groups are red, amber, or green right now — and how the state is expected to change.

A SPATEM contains, among other things:</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:messages:mapem?rev=1786033330&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:10+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>mapem - Create MAPEM page</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:messages:mapem?rev=1786033330&amp;do=diff</link>
        <description>MAPEM (MAP Extended Message)

MAPEMs describe the topology of an intersection (ETSI TS 103 301): the geometry of its lanes, which ingress and egress lanes exist, and which maneuvers connect them.

A MAPEM contains, among other things:

	*  the reference position of the intersection</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:messages:denm?rev=1786033327&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:22:07+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>denm - Create DENM page</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:messages:denm?rev=1786033327&amp;do=diff</link>
        <description>DENM (Decentralized Environmental Notification Message)

DENMs are event-driven warning messages (ETSI EN 302 637-3). While CAMs are broadcast continuously, a DENM is only transmitted when something exceptional happens, and it is repeated for as long as the event is valid.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/verbreitung?rev=1786032731&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:12:11+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>verbreitung - Link zur englischen Kurzfassung ergänzt</title>
        <link>http://wiki.opentrafficmap.org/verbreitung?rev=1786032731&amp;do=diff</link>
        <description>Eine englische Kurzfassung dieser Seite ist unter Who is sending C-ITS? verfügbar.

Verbreitung

Wo alles C-ITS angewendet wird.

Fahrzeuge

Nur Fahrzeuge mit ITS-G5 (WLANp / 802.11p, 5,9 GHz) senden CAM/DENM per Direktfunk und sind damit für RSUs und Empfangsstationen hörbar. Die mobilfunkbasierten Gefahrenwarnsysteme anderer Hersteller (Mercedes, BMW, Ford, Volvo, Audi) laufen über Hersteller-Clouds und tauchen im Direktfunk</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en:c-its:senders?rev=1786032661&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:11:01+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>senders - Create senders overview, extracted from verbreitung</title>
        <link>http://wiki.opentrafficmap.org/en:c-its:senders?rev=1786032661&amp;do=diff</link>
        <description>Who is sending C-ITS?

Extracted from the more detailed German page verbreitung, which also lists the individual sources.

Only vehicles with ITS-G5 (WLANp / 802.11p, 5.9 GHz) broadcast CAM/DENM messages via direct radio and can therefore be picked up by RSUs and receiver stations. The cellular-based hazard warning systems of other manufacturers (Mercedes, BMW, Ford, Volvo, Audi) run through manufacturer clouds and do</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/messages:cam?rev=1786032121&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:02:01+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>cam - Link zur englischen Version ergänzt</title>
        <link>http://wiki.opentrafficmap.org/messages:cam?rev=1786032121&amp;do=diff</link>
        <description>Diese Seite ist auch auf Englisch verfügbar.

CAM (Cooperative Awareness Message)

Kompatible Fahrzeuge senden mit 1 - 10 Hz CAM Nachrichten aus (typischerweise 4x pro Sekunde)

Die CAM Nachricht enthält:

	*  GPS-Position
	*  Geschwindigkeit
	*  Fahrtrichtung</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/c-its:rsu?rev=1786032117&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:01:57+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>rsu - Link zur englischen Version ergänzt</title>
        <link>http://wiki.opentrafficmap.org/c-its:rsu?rev=1786032117&amp;do=diff</link>
        <description>Diese Seite ist auch auf Englisch verfügbar.

 

RSU von Yunex Traffic</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/c-its?rev=1786032114&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:01:54+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>c-its - Link zur englischen Version ergänzt</title>
        <link>http://wiki.opentrafficmap.org/c-its?rev=1786032114&amp;do=diff</link>
        <description>Diese Seite ist auch auf Englisch verfügbar.

Was ist C-ITS

C-ITS steht für Cooperative Intelligent Transport Systems. Dabei kommunizieren Fahrzeuge und Infrastruktur untereinander und miteinander

Typische C-ITS Teilnehmer sind:

stationäre RSU - Road Side Units 

	*  Ampeln  (Verkehrslichtsignalanlagen)</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/gehaeuse?rev=1786032111&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-06T16:01:51+00:00</dc:date>
        <dc:creator>fasteiner (fasteiner@undisclosed.example.com)</dc:creator>
        <title>gehaeuse - Link zur englischen Version ergänzt</title>
        <link>http://wiki.opentrafficmap.org/gehaeuse?rev=1786032111&amp;do=diff</link>
        <description>Diese Seite ist auch auf Englisch verfügbar.

Gehäuse 3D drucken

&lt;https://codeberg.org/opentrafficmap/its-g5-receiver/src/branch/main/case&gt;

Wir empfehlen das Gehäuse aus ASA zu drucken, dann sollte es UV-beständig und wasserfest sein. ASA ist ohne spezielle Zusätze aus UV beständig, der Hersteller des Filament sollte relativ egal sein. Wir kaufen immer das günstigste in weiß.</description>
    </item>
</rdf:RDF>
