[Open-transport] Open Data Public Transport List?
pieter.colpaert at okfn.org
Thu Jul 18 12:47:02 UTC 2013
Hi Rufus and Patrick,
I'm afraid that the created google docs will more work counterproductive:
* Agencies should not focus on an API. They should focus on having their
raw data published under an open license.
* It's the use case developers that should design the API as an engine for
their application state, and thus not the agencies themselves.
I do however see the need for a list of meta-data about these data
endpoints, whether they're raw data or APIs. Can't we all start
contributing on http://transport.datahub.io?
On Thu, Jul 18, 2013 at 2:01 PM, Stefan de Konink <stefan at konink.de> wrote:
> On Thu, 18 Jul 2013, Patrick Wolowicz wrote:
> Why would such a list be important?
>> 1) It would allow the open data community to see which APIs are most
>> used. If someone is considering writing a converter between one API to
>> another, the developer could see which regions would be covered and which
>> APIs the developer can test against.
> Could you please elaborate why interopability between API's from different
> regions is important. You seem te advocate that open data public transport
> is something like building a view on an existing system. While what most
> transit developers require is the freedom to have access to the raw data
> behind it.
> So are you advocating for open data api's were you can fetch raw data
> from, such as Networkrail, or more like a documented API to a route planner
> like Dutch Rail provides?
> open-transport mailing list
> open-transport at lists.okfn.org
> Unsubscribe: http://lists.okfn.org/mailman/**options/open-transport<http://lists.okfn.org/mailman/options/open-transport>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the open-transport