I've been following along the few threads to better understand this topic, however I'm still feeling that mapping complex timetables is a bit like mapping the full menu of a cafe or restaurant, or the room options at a hotel. These things vary whenever the service business chooses and it is close to impossible to keep it up to date.
In Brisbane Australia, some PT timetables vary often especially with public holidays (local, state or federal), school holidays (which differ between schools) and especially with special events (sporting, concerts, etc). Sometimes timetables get more trips sometimes less, it can be quite variable throughout the year and not something that can be 100% codified into timetable rules, and obviously not known too far in advance. I appreciate that timetables are very useful for consumers of maps, and understand that in some cities timetables can be reverse engineered by being somewhat observable (I would think copying a full timetable off a sign would classify as an import), however are we concerned that this adds a massive burden to maintain this data in OSM and it is very likely to always be out of date? If it is always going to be out of date will any app developer even integrate this data into their app when they can use GTFS feeds? The proposal refers to MAPS.ME and OsmAnd, have the developers of either application been consulted? Having this data embedded in the OSM tags also forces apps to reduce their map cache duration to try to get more updated timetables. I'm not very experienced with PT in OSM, but I'd have thought improving the tags for mapping objects to GTFS feeds, including the GTFS endpoints and license info as tags, and maybe then adding the ability to discover the GTFS Realtime extension would be the way to go. I think this would give much more power to app developers. It does overlap a little with Transitland, but obviously OSM wouldn't be polling or hosting the feeds, that would be up to an application developer. Happy to hear any feedback if I've missed the point of this. On Tue, Nov 6, 2018 at 2:07 AM Jo <winfi...@gmail.com> wrote: > Hi Leif, > > You made me do it! :-) I sort of stole your proposal and started creating > a new one. It differs in rather important ways from your proposal, so I > preferred not modifying your wiki page. I also think it's important to > decouple the (voting for a) full timetable solution from the solution where > tags are added to indicate interval during 'opening_hours' or a route, > which is a lot more likely to be accepted. > > So here goes: > > https://wiki.openstreetmap.org/wiki/Proposed_features/Public_transport_timetables > > Please let me know what you think. What I still haven't figured out yet is > how to differ weekdays that fall in school holiday periods from "normal" > weekdays. So work in progress. > > Polyglot > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > -- Jono
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
