On 9 Mar 2009, at 21:07, Roger Slevin wrote:
Brian and all
I am happy to arrange for an updated NaPTAN file to be used for the
proposed test import. I think Peter Miller may have made the
current test data available (with my agreement) – and I am happy if
Peter supplies the updated files as and when you are ready to use
them.
NaPTAN data is continually changing (albeit slowly) so it is worth
taking the most up to date data once you are ready.
Excellent news!
With regard to actually getting the data, are you able to download it
from the Thales site? If you are then please do that. For the
avoidance of doubt can you provide me with the URL you will be using
to access the data to ensure that it is current.
Regards,
Peter
Best wishes
RogerS
From: [email protected] [mailto:[email protected]
]On Behalf Of Brian Prangle
Sent: 09 March 2009 10:00
To: [email protected]
Subject: [Talk-transit] NaPTAN import
Hi everyone
Summarising where I believe we've got to:
1. Thomas: schedule for completion - we're entirely in your hands -
agree it's best to avoid the API update.
2. Birmingham only for test import
3. No highway=bus_stop tags, enabling us to merge/verify existing
OSM data ( Christophe's visual tool to eventually solve this manual
task) BUT tag taxi ranks as amenity=taxi
4. Import on the basis of the current selection/naming in naptan
tagging wiki. Imports to be carried out by new user naptan
5. Plusbus zones and stop areas - import the naptan data only and
leave doing anything with it until the debate on stopareas reaches a
conclusion
6. Roger/Peter: is our current method of accessing the data OK? Or
do you have to explicitly issue us with a dataset (perhaps the data
publicly available for test is not the most current/accurate?)
7. Andy: agree on re-tagging w mids bus stops with route_ref and
using semicolons instead of pipes to separate route nos in order to
standardise - presume you have an automated routine for this?
8. Update needed on wiki regarding bus_stops (Andy? I'm happy to do
a first draft for you to edit before publication - or better still
submit it to this discussion list)
Parked for later discussion/solution
a)Stopareas (see above)
b)Big-bang vs regional adoption (probably a talk gb discussion once
Birmingham data and process completed)
c)handling NaPTAN bus_stop updates
d) importing further NaPTAN public transport data
e) user feedback - there's a wide range of skill and experience in
the OSM community and there are certain to be problems. An explicit
route needed?
f) how to maintain data integrity once it's imported and
inexperienced users potentially delete data that other users have
written applications that rely on it being there. I guess this is
general problem not specific to this project- but this is a donated
dataset and potentially could drive a considerable number of
applications
Unless there are any strong objections,(or I've ommitted anything
from the discussions) I'd like to think we can close the discussion
on the import and let Thomas get on with finishing the coding. Thank
you everyone for your time and contributions
We can continue discussion on the parked items and anything else
that doesn't impact the coding for the first live Birmingham import
Regards
Brian
_______________________________________________
Talk-transit mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk-transit
_______________________________________________
Talk-transit mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/talk-transit
