Post about UK National Highways OPML
This commit is contained in:
parent
74e9b82797
commit
091a085dec
38
feed.xml
38
feed.xml
|
|
@ -2053,6 +2053,44 @@ because astronomers need coffee to go through the night -->
|
|||
<p>Anyway, since I like to get all the interesting feeds neatly organized into even more XML, <a href="https://tildegit.org/lucidiot/rsrsss/commit/8921e100fac29789c9321af5b57fa2b4cd0444ed/" target="_blank">I wrote a script</a> to generate an OPML file for all the Chicago Transit Authority feeds. Since they provide feeds for both a single line or category of alerts and for all at once, you'll get duplicates if you import that, but at least you will know about all the available feeds.</p>
|
||||
]]></description>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
<title>UK National Highways alerts</title>
|
||||
<pubDate>Sun, 10 Dec 2023 17:33:50 +0100</pubDate>
|
||||
<guid isPermaLink="false">uk-highways-opml</guid>
|
||||
<category domain="https://envs.net/~lucidiot/rsrsss/">OPML</category>
|
||||
<category domain="https://envs.net/~lucidiot/rsrsss/">Transport</category>
|
||||
<link>https://envs.net/~lucidiot/rsrsss/opml/uk-highways.opml</link>
|
||||
<description><![CDATA[
|
||||
<p>In the same vein as the <a href="https://envs.net/~lucidiot/rsrsss/feed.xml#cta-opml" target="_blank">Chicago Transit Authority alerts</a> <abbr title="Outline Processor Markup Language">OPML</abbr> file I generated, here's another OPML file of transportation alerts, but for England's highways.</p>
|
||||
<p>These feeds are quite strange. They use non-namespaced extensions to RSS, which are illegal but will not break most feedreaders, to give some metadata on each item:</p>
|
||||
<dl>
|
||||
<dt><code><<dfn>reference</dfn>></code></dt>
|
||||
<dd>A unique identifier for the event. I suppose this could just have been a <code><guid isPermaLink="false"></code>.</dd>
|
||||
<dt><code><<dfn>road</dfn>></code></dt>
|
||||
<dd>The number of the road where the event occurs, like <code>M20</code>.</dd>
|
||||
<dt><code><<dfn>region</dfn>></code></dt>
|
||||
<dd>The region where the event occurs, which is equivalent to the region names in the regional feeds list.</dd>
|
||||
<dt><code><<dfn>county</dfn>></code></dt>
|
||||
<dd>The county where the event occurs.</dd>
|
||||
<dt><code><<dfn>latitude</dfn>></code></dt>
|
||||
<dd>The WGS84 latitude of the event's location. This could have been a <code><georss:point></code> or a <code><gml:pos></code> or a <code><icbm:latitude></code> or a <code><geo:lat></code>…</dd>
|
||||
<dt><code><<dfn>longitude</dfn>></code></dt>
|
||||
<dd>The WGS84 longitude of the event's location. This could have been a <code><georss:point></code> or a <code><gml:pos></code> or a <code><icbm:longitude></code> or a <code><geo:long></code>…</dd>
|
||||
<dt><code><<dfn>eventStart</dfn>></code></dt>
|
||||
<dd>ISO 8601 date of when the event starts. This could have been a <code><ev:startdate></code> from the <a href="https://web.resource.org/rss/1.0/modules/event/" target="_blank">RSS 1.0 Event Module</a>.</dd>
|
||||
<dt><code><<dfn>eventEnd</dfn>></code></dt>
|
||||
<dd>ISO 8601 date of when the event ends. This could have been a <code><ev:enddate></code> from the <a href="https://web.resource.org/rss/1.0/modules/event/" target="_blank">RSS 1.0 Event Module</a>.</dd>
|
||||
<dt><code><<dfn>overallStart</dfn>></code></dt>
|
||||
<dd>ISO 8601 date of when the cause of the event starts. For incidents, this is the same as <code><eventStart></code>. For road works that start before the event occurs (for example, road works that only close a road during a given time of day), this will be a different date.</dd>
|
||||
<dt><code><<dfn>overallEnd</dfn>></code></dt>
|
||||
<dd>ISO 8601 date of when the cause of the event ends. For incidents, this is the same as <code><eventEnd></code>. For road works that end after the event occurs (for example, road works that only close a road during a given time of day), this will be a different date.</dd>
|
||||
</dl>
|
||||
<p>Obviously, not a single feed reader will support these tags.</p>
|
||||
<p>A larger issue however is just the sheer amount of items. Adding this OPML into a feedreader made it pull over fourteen thousand items. Now of course there are a lot of duplicates, since there are feeds by road, area, and for the whole network, as well as for incidents, roadworks, or both at once. The <a href="https://m.highwaysengland.co.uk/feeds/rss/AllEvents.xml" target="_blank">everything-everywhere firehose</a> still has three thousand items, with tons and tons of roadworks everywhere.</p>
|
||||
<p>Just the <a href="https://m.highwaysengland.co.uk/feeds/rss/UnplannedEvents.xml" target="_blank">incidents-everywhere</a> feed gets a new item from every few minutes to <strong>every few seconds</strong>, which is the fastest update rate I have ever seen on a feed. I guess those feeds really can only be used by software for further processing.</p>
|
||||
]]></description>
|
||||
</item>
|
||||
</channel>
|
||||
<access:restriction relationship="allow" />
|
||||
</rss>
|
||||
|
|
|
|||
Loading…
Reference in New Issue