Matthijs Melissen wrote:
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.
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:<http://www.openstreetmap.org/browse/node/502389340>
http://www.openstreetmap.org/browse/node/502389340
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?
This far removed from the original naptan import, you'd really need to
vet each uploaded bus stop, in order to try and reconcile:
o duplications (stops that were mapped before the original import), such
as http://www.openstreetmap.org/browse/node/502389340 .
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.
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.
o Updated information from Naptan to stops verified (or not verified) in
OSM.
A "guided merging" approach has been tried in the past, with DfT cycling
data:
https://wiki.openstreetmap.org/wiki/Potlatch_2_merging_tool
Maybe something like that could work?
Cheers,
Andy
_______________________________________________
Talk-GB mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/talk-gb
