The TNDS data isn't going to be based on what is already in OSM, if I've understood you correctly Oliver. Rather, in our bit, we import the GIS, route on it using proprietary (to our contractor) routing engines and manually adjust where appropriate, and then we can export the track coordinates as OSGR into the TNDS data.
I haven't looked at the service tags in any detail, so what I'm about to say may well be there already. But if we want to represent the complexity then we either have to capture the individual departures at a stop or, more likely, try and represent the frequency/regularity of a service on a link. Then renderers could show dotted/thin lines, or put the service number in different colours for infrequent services. Of course, there are plenty of issues around that as well! Stuart From: Shaun McDonald [mailto:sh...@shaunmcdonald.me.uk] Sent: 01 August 2014 3:57 PM To: Oliver Jowett Cc: Stuart Reynolds; Talk GB Subject: Re: [Talk-GB] NaPTAN (stop) import I see it as being better to put the right hints into the OSM data and the routing algorithm so that they can be automatically chosen from the TNDS data, rather than having the data in OSM, which is hard to represent some complexities such as a few journeys go via a school, some are part route, etc Shaun On 1 Aug 2014, at 15:32, Oliver Jowett <oliver.jow...@gmail.com<mailto:oliver.jow...@gmail.com>> wrote: Right - I was just trying to understand which was the canonical source. One of the things I've been wanting to try (but never have the time) is repair the OSM bus route relations based on the TNDS schedule info - which sounds very much like your track-finding system. But that gets dangerous if TNDS is indirectly pulling data from OSM itself.. Oliver On 1 August 2014 14:20, Stuart Reynolds <stu...@travelinesoutheast.org.uk<mailto:stu...@travelinesoutheast.org.uk>> wrote: Oliver, TNDS data (Traveline National Data Set, for other's benefit - national set of bus & coach timetables) does not currently have the route detail - known in TransXChange as tracks. This is because up to now there have been issues of IPR with OSGR coordinates derived from OS and/or Navteq data. Certainly from our point of view - and by "us" I mean the traveline regions of South East, London, East Anglia, South West, East Midlands and (shortly) West Midlands - we are all now on a merged system using OSM data so those problems have gone away. But I still won't be exporting Tracks until TNDS asks me to. Even then, it still has the issues of "is this right". Most of the time it is, but we do get some routes which find a shorter path along a back street rather than down the main road. Cheers Stuart From: Oliver Jowett [mailto:oliver.jow...@gmail.com<mailto:oliver.jow...@gmail.com>] Sent: 01 August 2014 1:51 PM To: Stuart Reynolds Cc: Talk GB Subject: Re: [Talk-GB] NaPTAN (stop) import On 1 August 2014 11:17, Stuart Reynolds <stu...@travelinesoutheast.org.uk<mailto:stu...@travelinesoutheast.org.uk>> wrote: In terms of bus routes, we also compute the most likely route between stops, and could use that to update the services on each link. But that is a whole different ball game - we have to make sure our data is good quality, and I will need to think what to do when a bus turns off halfway along a road that is mapped as one line, for example, - and I'm not about to get into that for now! Although I would like to, eventually! Where does TNDS fit into this? Oliver _______________________________________________ Talk-GB mailing list Talk-GB@openstreetmap.org<mailto:Talk-GB@openstreetmap.org> https://lists.openstreetmap.org/listinfo/talk-gb
_______________________________________________ Talk-GB mailing list Talk-GB@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-gb
