<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Matthijs Melissen wrote:<br>
</div>
<blockquote
cite="mid:CAD940Mp+e5Z8DwUgUk+8c=0FYBG=_MD8Kr+ZBwxfrF5vtYoBRw@mail.gmail.com"
type="cite">
<pre wrap="">In Birmingham, all bus stops have been imported from Naptan, but
during the import, the name tag has not been set. I am considering
adding the name tag, by setting it to something like:
camelcase(naptan:Street) + ' / ' + naptan:CommonName
That way, the name tag in OSM will match the name on the bus stop.
</pre>
</blockquote>
<br>
I can't comment on bus stops in Birmingham, but elsewhere in some
cases (Notts) "name" seems to have been set to naptan:CommonName -
see for here:<a
href="http://www.openstreetmap.org/browse/node/502389340"></a><br>
<br>
<a href="http://www.openstreetmap.org/browse/node/502389340">http://www.openstreetmap.org/browse/node/502389340</a><br>
<br>
<br>
<blockquote
cite="mid:CAD940Mp+e5Z8DwUgUk+8c=0FYBG=_MD8Kr+ZBwxfrF5vtYoBRw@mail.gmail.com"
type="cite">
<pre wrap="">
I am currently discussing whether this change is desirable on the
local mailing list [1]. Apart from whether this change is desirable,
what would be the easiest way to achieve it?
I suppose it's best to download the data with xapi, use a scripting
language to create a change set based on this data, and then upload
the change set? </pre>
</blockquote>
<br>
This far removed from the original naptan import, you'd really need
to vet each uploaded bus stop, in order to try and reconcile:<br>
<br>
o duplications (stops that were mapped before the original import),
such as <a
href="http://www.openstreetmap.org/browse/node/502389340">http://www.openstreetmap.org/browse/node/502389340</a>
.<br>
<br>
o "invalid" changes where someone's used or misused a bus stop node
for something else (for example, new mappers sometimes see a bus
stop with a pub name and add "amenity=pub" to it), or where
someone's deleted a bus stop by mistake.<br>
<br>
o "valid" changes where someone's moved a naptan-imported stop to a
more accurate location, or deleted a bus stop because buses no
longer stop there.<br>
<br>
o Updated information from Naptan to stops verified (or not
verified) in OSM.<br>
<br>
A "guided merging" approach has been tried in the past, with DfT
cycling data:<br>
<br>
<a
href="https://wiki.openstreetmap.org/wiki/Potlatch_2_merging_tool">https://wiki.openstreetmap.org/wiki/Potlatch_2_merging_tool</a><br>
<br>
Maybe something like that could work?<br>
<br>
Cheers,<br>
<br>
Andy<br>
<br>
</body>
</html>