<?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 - en_alt</title>
        <description></description>
        <link>http://wiki.opentrafficmap.org/</link>
        <image rdf:resource="http://wiki.opentrafficmap.org/_media/wiki:dokuwiki.svg" />
       <dc:date>2026-08-24T00:34:25+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:c-its?rev=1786366257&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:community?rev=1786745203&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:coverage?rev=1786805103&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:faq?rev=1786745204&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:placement?rev=1786366259&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:receivers?rev=1786745205&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:senders?rev=1786805104&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:server?rev=1786745206&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:start?rev=1786745207&amp;do=diff"/>
                <rdf:li rdf:resource="http://wiki.opentrafficmap.org/en_alt:your_node?rev=1786745208&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_alt:c-its?rev=1786366257&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-10T12:50:57+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>c-its</title>
        <link>http://wiki.opentrafficmap.org/en_alt:c-its?rev=1786366257&amp;do=diff</link>
        <description>What is C-ITS?

C-ITS stands for Cooperative Intelligent Transport Systems: vehicles and road infrastructure exchange information directly with each other over radio, without going through any network operator or manufacturer cloud.

This page explains the technology itself. Which vehicles and which infrastructure actually transmit is covered on</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:community?rev=1786745203&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:43+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>community</title>
        <link>http://wiki.opentrafficmap.org/en_alt:community?rev=1786745203&amp;do=diff</link>
        <description>Community

OpenTrafficMap is an open project run by volunteers. This page covers how to take part, who is behind it, and where to find the code.

Contributing

Run a receiver

The most valuable contribution by a distance. The map can only show live data where a receiver is nearby, so every new location extends what the project can see — and a location nobody covers yet is worth more than a better antenna somewhere already covered.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:coverage?rev=1786805103&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-15T14:45:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>coverage</title>
        <link>http://wiki.opentrafficmap.org/en_alt:coverage?rev=1786805103&amp;do=diff</link>
        <description>Coverage

Where C-ITS is actually live. This page is purely geographic — which regions have deployed C-ITS, and what people have really received there. Which vehicles and infrastructure transmit in the first place is covered on Senders.

How this list works</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:faq?rev=1786745204&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>faq</title>
        <link>http://wiki.opentrafficmap.org/en_alt:faq?rev=1786745204&amp;do=diff</link>
        <description>Common questions

This page is an index, not an article. Each question links to the place where it is answered in context, together with everything else you need to know about that topic.

The receiver

	*  What do the LEDs mean? → LEDs &amp; troubleshooting
	*  Does it matter which USB-C port powers it?</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:placement?rev=1786366259&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-10T12:50:59+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>placement</title>
        <link>http://wiki.opentrafficmap.org/en_alt:placement?rev=1786366259&amp;do=diff</link>
        <description>Placement &amp; Outdoor

C-ITS reaches a few hundred metres in a town and a few kilometres with a clear view. Within those limits, where you put the receiver decides almost everything — far more than which board you built. A well-placed cheap receiver beats a badly-placed good one every time.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:receivers?rev=1786745205&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>receivers</title>
        <link>http://wiki.opentrafficmap.org/en_alt:receivers?rev=1786745205&amp;do=diff</link>
        <description>Receivers

What you need to actually hear C-ITS. There is one purpose-built receiver that most people use, and a growing number of independent projects that solve the same problem with different hardware. All of them end up in the same place: raw 802.11p frames on the</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:senders?rev=1786805104&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-15T14:45:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>senders</title>
        <link>http://wiki.opentrafficmap.org/en_alt:senders?rev=1786805104&amp;do=diff</link>
        <description>Senders

Who actually transmits C-ITS. This page is about models and manufacturers; for the geography — which cities and motorways are live — see Coverage.

The single most important distinction: only vehicles with ITS-G5 (WLANp / IEEE 802.11p, 5.9 GHz) broadcast CAM and DENM messages over direct radio, and only those can be picked up by a receiver. Several manufacturers market a hazard-warning feature under a similar name, but route it through their own cloud over the cellular network. Those ve…</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:server?rev=1786745206&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>server</title>
        <link>http://wiki.opentrafficmap.org/en_alt:server?rev=1786745206&amp;do=diff</link>
        <description>The OpenTrafficMap server

Every receiver, whatever it is built from, ends up doing the same thing: publishing raw 802.11p frames to one central MQTT broker, which feeds the live map. That broker is the OpenTrafficMap server, and this page covers both directions — how data gets there, and how to read it back.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:start?rev=1786745207&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>http://wiki.opentrafficmap.org/en_alt:start?rev=1786745207&amp;do=diff</link>
        <description>OpenTrafficMap

OpenTrafficMap is an open project that visualises C-ITS data — the messages that traffic lights, trams, buses and modern cars already broadcast unencrypted today. Volunteers run small receivers, the receivers report what they hear, and the result is a live map.</description>
    </item>
    <item rdf:about="http://wiki.opentrafficmap.org/en_alt:your_node?rev=1786745208&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2026-08-14T22:06:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>your_node</title>
        <link>http://wiki.opentrafficmap.org/en_alt:your_node?rev=1786745208&amp;do=diff</link>
        <description>Your Node

The self-service portal is a small web interface for a single receiver. It is where you name your node, decide whether it appears on the map, adjust the LEDs and look at what it has been hearing.

This page is about the things you click. The machine side — the broker, the topics, the wire format — is on</description>
    </item>
</rdf:RDF>
