<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 05/07/2019 13:19, Silent Spike
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAGtsW_YFxoWm4p0OGcREpBdjdpKZ=0SDzhKk0Yg1obhwuj0B6A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Fri, Jul 5, 2019 at 1:02 PM Gareth L <<a
href="mailto:o.i@live.co.uk" moz-do-not-send="true">o.i@live.co.uk</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div dir="ltr">Forgive me if this is silly
question/statement, but the adj/alt names etc are in the
naptan dataset. Wouldn’t it be better to have the link
made between the stop in OSM and the record in naptan
(using the codes prior mentioned).</div>
<div dir="ltr">My thinking is data consumers could link
and retrieve values using that. Merging the extra data
values again might potentially develop discrepancies
over time.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I’d think the atco code is unique and
(hopefully) not reused, but the alt names etc could be
modified over time.</div>
</div>
</blockquote>
<div><br>
</div>
A perfectly valid question and something I wonder also.
<div><br>
</div>
<div>For example, the indicator field is somewhat meaningless
to a data consumer unless they know what it represents as
per the NaPTAN schema - so perhaps it's best left out of the
OSM data?</div>
</div>
</div>
</blockquote>
<p>FWIW I did actually append that to name when displaying those
because it "looked useful" (to append to the name and distinguish
between other identically named stops):<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua#L5010">https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua#L5010</a></p>
<p>As to the original question "Would there be any objections to an
import of the following scope" - certainly not from me. I
wouldn't personally use the PTv2 "platform" tag but its presence
doesn't break anything.</p>
<p>The most interesting bit would be the "Manually conflate and
review the data before upload using JOSM" - any JOSM CSS style
that you end up using to highlight duplicates would be really
useful, as would a basic OSM diary entry describing the process
and the end result.</p>
<p>Best Regards,</p>
<p>Andy</p>
<p><br>
</p>
<p><br>
</p>
<br>
<blockquote type="cite"
cite="mid:CAGtsW_YFxoWm4p0OGcREpBdjdpKZ=0SDzhKk0Yg1obhwuj0B6A@mail.gmail.com"></blockquote>
</body>
</html>