[Open-transport] Open Transport Data tools / webservices

Tue Jul 16 09:07:39 UTC 2013

I agree that fares have historically been a weak spot for GTFS, but I've
been working hard to improve the situation:

https://groups.google.com/forum/#!forum/gtfs-fare-wg
https://docs.google.com/document/d/1mK3--o5g4-3cCXaqmch92U63JTwChh0L2VCmcDViIlM/edit?usp=sharing

I know that you have already given some feedback on that process, but we
are always looking for more feedback if others want to get involved.

And by current standards, I assume you mean NeTEx?  Or something else?

On Tue, Jul 16, 2013 at 10:35 AM, Stefan Kaufmann
<transit at shutterworks.org>wrote:

> On 16.07.2013 07:42, Brian Ferris wrote:
>
>  "some agencies are complaining that Google is not listening enough what
>> agencies want/need"
>>
>> […] Replacing GTFS with something else
>>
>> might make some sense for agencies, but I'm not sure riders will
>> necessarily be better off.
>>
>
> One problem my agency has right now is the question how to fit their fare
> system into GTFS. The service area is divided into cells, and due to
> special fares in between several cells the fare can currently only be
> calculated through an n×n matrix. So, yep, while the local system might be
> complex and sometimes a bit tedious, I have yet to find convincing
> arguments why the agency should adapt their fare rules to GTFS instead of
> the other way round, when their current standards fully support what
> they're doing.
>
> regards,
> -stk
>
>
> ______________________________**_________________
> open-transport mailing list
> open-transport at lists.okfn.org
> http://lists.okfn.org/mailman/**listinfo/open-transport<http://lists.okfn.org/mailman/listinfo/open-transport>
> Unsubscribe: http://lists.okfn.org/mailman/**options/open-transport<http://lists.okfn.org/mailman/options/open-transport>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-transport/attachments/20130716/e09d39e2/attachment.html>