Implement Project Logo

Project Logo sets the minimum metadata (logos, station name, station information etc.) which can be used to enhance the way your station is shown to listeners.

This page explains how to implement Project Logo for your station, and the minimum meta-data that you must provide. If you want help doing this, ask one of our Partners.

If you provide information on your internet streaming, then car radios can switch automatically between broadcast and streaming to get the best reception (“Service Following”).

4 Steps to Project Logo for your station

  1. Create an SI.xml file for your stations. You can do it yourself or use our tool and this HOWTO Guide
    • Each station must have Short Name, Medium Name, Short Description, Long Description, 5 different sized logos
    • If you want to enable Service Following between broadcast and IP Streaming, you must also provide at least one streaming URL
    • It’s really important to add a Terms of Use to your Metadata. We recommend adding our Radio Metadata Terms of Use.
  2. Put your SI.xml file on your webserver. This HOWTO Guide can help.
  3. Make sure you have a _radioepg._tcp SRV record pointing to your webserver, using this HOWTO Guide.
  4. Register your stations with RadioDNS, using this HOWTO Guide.

That’s all there is. But keep reading if you want to know more detail.

Note: If your radio station is on FM, it must be transmitting RDS information to use RadioDNS.

The Project Logo Meta-Data Elements & Attributes

The following elements and attributes will always be present in Project Logo meta-data. The exact definition of these elements and attributes is given in the Service and Programme Information specification v3.2.1. Broadcasters can optionally include additional elements and attributes.

<serviceInformation xmlns creationTime xsi:lang>
		   <multimedia url type height width>
                       (5 instances of images in PNG format - 32px x 32px, 32px x 112px, 128px x 128px, 320px x 240px, 600px x 600px)
	        <bearer id cost mimeType bitrate offset>
(use id types of fm, hd and http[s]) <radiodns fqdn, serviceIdentifier>

Example XML

Here is an example of a <service> definition for an FM radio station on 96.9MHz using PI code c691 in the UK (ce1):

<?xml version="1.0" encoding="UTF-8"?>
<serviceInformation xmlns=""
        xsi:schemaLocation=" spi_31.xsd"
        creationTime="2016-03-29T10:15:15Z" originator="The Service Provider" xml:lang="en">
            <shortName>all fm</shortName>
            <mediumName>all fm</mediumName>
            <longName>all fm</longName>
                <shortDescription>The real voice of Manchester</shortDescription>
                <longDescription>All fm is a community radio station broadcasting to South, Central and East Manchester.
All fm’s purpose is to provide the communities of south, East and Central Manchester with the chance to work and train in a media environment, in order to improve their skills for life, education, training and work. As well as providing a medium of expression, especially for those whose voice may not ordinarily be heard.
All fm is a volunteer led organisation. Over one hundred volunteers present, produce and help run the station. We broadcast for over 16 hours per day, 7 days per week, focussing on music, talk and community issues.
We provide shows for specific communities such as South Asian, African, Afro Caribbean, Polish and Irish communities, disabled people and young people.</longDescription>
                <multimedia url="" type="logo_colour_square" />
                <multimedia url="" type="logo_colour_rectangle" />
                <multimedia url="" type="logo_unrestricted" width="128" height="128" mimeValue="image/png" />
                <multimedia url="" type="logo_unrestricted" width="320" height="240" mimeValue="image/png" />
                <multimedia url="" type="logo_unrestricted" width="600" height="600" mimeValue="image/png" />
            <genre href="urn:radioplayer:metadata:cs:Category:2012:5"></genre>
            <keywords>levenshulme,longsight, all fm, south manchester</keywords>
            <bearer id="fm:ce1.c691.09690" cost="0" />
<bearer id="" mimeValue="audio/mpeg" bitrate="96" offset="5000" cost="70" /> </service> </services> </serviceInformation>

Hosting and Signalling

The SI file should be stored on an HTTP webserver, in the following locations


Please note that the URLs are case sensitive.

Differences between SPI (v3.2.1) and RadioEPG (v1.1)

The current version of the Service and Programme Information specification is v3.2.1, and all new implementations must use this version, which produces an SI.xml file. We do not recommend continuing support for the legacy XSI format specified in RadioEPG.

If you do need to transform documents between SI and XSI, there is an unsupported XSL-T transformation, which will produce a v1.1 compliant XSI file from a v3.2.1 compliant SI file.

Share to: