Hi, I don't know how it work in these program, but there are too ways. The easiest one is to get the stops and find ways from one to the next. This is easy because you have to solve only one problem and the the next. But its not very good. Because the next way would be much longer or imposible if you reach the stop from the wrong site. Maybe it's better to make indirection and have less poblems later.
These is posible if you have all stops and make a matching to all posible points around your stops. regards Jan Am 04.04.2014 14:36, schrieb Patrick Brosi | geOps: > Sean, it would be interesting to know whether GO-Sync's processing > includes the GTFS route shapes (the exact vehicle paths stored in > shapes.txt) in any way. For example: if the GTFS feed only covers the > location / attributes of stations and is missing shapes.txt information, > does GO-Sync try to extract these shapes from OSM data? If so, what > approach do you use? How are existing shapes compared to data already > existent in OSM? > > Many public transport companies have very good data regarding the > position of their stops, but lack the exact paths vehicles take between > succeeding stations. In my opinion, providing not only the possibility > to extract these shapes from existing OSM data but also the tools to > edit them via OSM would dramatically increase the geospatial quality of > many GTFS feeds. > > I just browsed GO-Sync's paper and couldn't find anything relating to > this problem. Are there any future plans to include the functionality > described above? > > Thank you! > > Best regards > > Patrick Brosi > _______________________________________________ Talk-transit mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-transit
