I would certainly hope that any updates are not used to overwrite
existing local edits. I have spent far too many hours checking and
updating the data to have a newer version overwrite it. A smart merge
would be more useful, I would write it if required.
As too 'dumping in' the remaining county
You mean extract the area from OSM & convert it to a shp file, then
open the current available NaPTAN data, then using a program like
OpenJUMP or FME to run a DIFF, then only select those that are not
matched with attributes/location, and make an .osm file out of the
rest of the data?
Is this data
Thomas
If you want a refresh of the NaPTAN dataset, then just ask me and I
will arrange for this be made available. I appreciate that this could be a
two-edged sword it would update the data, but in the areas where work
has already been done on the data from a year ago, it may over-writ
I'm living in South Kensington at the moment, so I should really get
around to reviewing the changes there :)
Everything else will happen as soon as I get around to it, or provides
the code to me to run with the dataset - the former will be done when
I get the time - which I seem to be always lack
That certainly sounds good to me.
Along those lines, what are the chances of importing updated data from
a newer edition of NaPTAN for the existing regions? In London I know
of several areas where bus stops have been relocated/reconfigured
recently (Camden Town, South Kensington) so OSM is already
Hello all,
It's now been more than a year since we got permission to import the
NaPTAN dataset, so far only 53 of the 143 counties that we have the
data for have been imported.
So, in short, is it time for the rest to be dumped in?
Discussion please.
Regards,
Thomas
