<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
As others have said, this data doesn't really belong in OSM.<br>
It's too transient, too complicated to maintain.<br>
<br>
GB timetables are officially updated every 6 months, but services
vary on an ad-hoc basis. This previous year being a good example.
How detailed would your system be? Would you adjust it to the level
of maintenance closures & rail replacement services?<br>
<br>
We don't even a valid database for buses. The Naptan import was
poorly executed & even more poorly maintained. There are
currently over 15000 without highway=bus_stop tags.<br>
<br>
The bus route relations are so poor Traveline/Travel West don't use
them<br>
<br>
Maybe it's best using your OSM time to improve & complete what
is already in the OSM database.<br>
<br>
DaveF<br>
<br>
<div class="moz-cite-prefix">On 31/05/2021 22:18, Michael Tsang
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1757892.8Zqesq1BtZ@fujitsu-lifebook-e547">
<pre class="moz-quote-pre" wrap="">On Monday, 31 May 2021 16:14:47 BST Roger Slevin wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">and one in which I agree with Tony, Mark and Peter in saying that public
transport services and timetables don’t appear to me to have a valid place
in OSM
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
We have already mapped the complete bus networks in certain cities. In OSM
terms, a public transport route is defined as "the order where the service
stops to carry passengers, and the path where it transverse on". It does not
include the timetable data.
I have also mapped a lot of bus and train routes in different cities as well,
and it is very useful for OSM to have bus and train routes. When I travel to a
new city I use OsmAnd a lot to find which bus I need to take to go to a certain
direction, and where it will stop.
The problem with GB railways is that each departure serves completely different
stops, which means, if we strictly follow the "one variant = one relation"
model as in current PTv2 schema, we have to map each departure as distinct
relations on the map, because each departure serves different stops, which mean
they are different variants.
Michael
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-GB mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-GB@openstreetmap.org">Talk-GB@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-gb">https://lists.openstreetmap.org/listinfo/talk-gb</a>
</pre>
</blockquote>
<br>
</body>
</html>