<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div>> And it's re-inventing the wheel. GTFS already exists.</div><div>> Could we do better? Maybe, maybe not.</div><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">Indeed. If someone determines GTFS needed improvement, it’s best to work in that community to improve it instead of inventing another standard. This xkcd comic is particularly well suited for this situation: <a href="https://xkcd.com/927/">https://xkcd.com/927/</a>.</span></div></div><div><br></div><div>> We could perhaps encourage mappers to generate</div><div>> feeds where the operator doesn't provide them and maybe even</div><div><div dir="ltr"><div class="gmail_quote"><div>> go so far as to run a web server hosting those feeds until</div><div>> such time as a more official feed is available.</div><div><br></div><div>It’s very much what I have in mind as well.</div><div><br></div><div>We should think one step further than the tagging and figure a solution for maintaining and hosting GTFS files in case the PT organization doesn’t publish one. If we can resolve the issue of hosting the files, it will encourage OSM contributors to think more towards contributing to a web of data and less into “forcing” whatever geo-related data in OSM database.</div><div><br></div><div><div><span style="background-color: rgba(255, 255, 255, 0);">And hosting these files doesn’t need to be complex. For example, certain JOSM plug-in’s have their configuration hosted in the wiki: <a href="https://josm.openstreetmap.de/wiki/Presets#JOSMwikiAvailablepresetpreferredmethod">https://josm.openstreetmap.de/wiki/Presets#JOSMwikiAvailablepresetpreferredmethod</a>. So, we maybe already have the solution (with the OSM wiki, not the JOSM wiki).</span></div></div></div></div></div></body></html>