Aaron Antrim wrote:
> After the TriMet
> presentation<http://www.slideshare.net/headway/portland-trimet-presentation-on-data-sharing-updated-version/>(link
There is a small (but growing) group of us who met at the Vancouver
TransitCamp who are pushing for a public feed here. It would be great
if we could post information about what we have done, and who we have
spoken with so others who are interested in getting data can pick up
from where we are now, instead of starting from square one.
--
Michael Weisman
mwei...@gmail.com
http://www.mweisman.com
as long as no one has an issue with people posting info how to sue an
uncooperative transit agency.
We both know that publishing data will enable many kinds of new uses.
Some agencies have taken the leap and made it available. Others aren't
convinced a public feed is worth the resources it will take to
maintain, are concerned about how the data will be used or have
legitimate legal issues to address. Once people such as yourself have
created some useful apps using the data that's already available
(http://code.google.com/p/googletransitdatafeed/wiki/PublicFeeds) I
think the value of publishing will be much clearer and more agencies
will work to overcome the barriers.
Google Transit started by working with one agency. Our coverage has
expanded as agencies learned about the value of the product and the
ease of working with us. I'm optimistic that similar growth in public
data will happen as its value is demonstrated.
I'm not quite sure how to respond to such total disinformation. But I'll
give it a shot.
Laws exist to protect people, including developers. Transit agencies
develop their data with tax payer dollars, thus every American has a
right to the data. Some agencies take a very resistant approach to
giving the people what is rightfully theirs; using the courts in that
kind of situation is completely reasonable and very effective.
I met fierce opposition of data sharing from the New York State MTA. Yes
I started by asking nicely. But honestly, they don't care. So I filed a
FOIL request and even then they stalled; in one case we ultimately had
to file papers in court against one of their sub-agencies to make them
comply with the federal freedom of information law request. But I can
tell you, that made them pay attention! They settled immediately. So I
won and I now have the complete MTA schedule data set which I am happily
DEVELOPING with. And I got it a lot faster than by trying to prove to
them I'm worthy, when in fact I already had the right to the data anyway.
If this is about creating a knowledge share of experiences about how to
get data, it seems knowing one's legal rights and how to successfully
exercise them is certainly something worthy of inclusion. If its not
about that, then what's the point?
Mmm... look a frozen margarita on my desk, very cooling.
David Crow owns the domain, and Mark Kuznicki is one of the community
stewards in these parts. Might be worth contacting them.
Here are a couple of things we ( my attorneys and I ) think are
important to consider in the matter of acquiring data from public
transit agencies, particularly schedule data.
/* Transit Agencies are already maintaining their schedule data */
Most transit agencies are maintaining online schedule lookup services.
They are either reading it from a database or text files. In some cases
both. All transit agencies maintain their schedule data for the purposes
of publishing print based schedules. They also do so for the purposes of
circulating schedule changes internally to their different internal
departments and contractors. So transit agencies are already maintaining
their data in some form. So there is no overhead for transit agencies to
keep their data up to date, they already do this. That doesn't mean they
are doing it in GTFS, but that hardly matters. Each transit agency
within the MTA has its is own data format. The NYC Transit agency is
maintaining two formats alone - one for bus and one for subway. We have
written a script to convert all that data to GTFS. We'll be publishing
the MTA Data, our scripts, and the GTFS sets once we have GraphServer
running smoothly. At this point the MTA could just use our scripts to
maintain their data in GTFS format. So they have zero overhead
maintenance cost, so it is not a reasonable excuse for not making data
public.
/* Transit Agencies do not like litigating */
Transit Agencies don't enjoy having to respond to FOIL requests or
having to respond to court filings. NYC Transit tried to put up a fight,
but that lasted only one or two phone calls. Long Island Rail Road
immediately backed down when we served them. They responded incredibly
foolishly to our FOIL request, so with them we were forced to file in
court. As soon as they were served, they were on the phone to my lawyers
asking what we wanted and jumping to make it happen. This story is
documented here:
http://www.onnyturf.com/blogs/view_post.php?content_id=11314
http://www.onnyturf.com/blogs/view_post.php?content_id=12210
http://www.onnyturf.com/blogs/view_post.php?content_id=12272
http://www.onnyturf.com/blogs/view_post.php?content_id=12379
What seemed to us that happened at LIRR was a junior attorney didn't
really know what the request was about and decided he didn't need to ask
someone technical what we were talking about. When they were served a
senior attorney got involved and told the person to get us what we
wanted, pronto!
Transit agencies periodically update their data. We expect to FOIL for
those updates until MTA decides they will eliminate the hassle for all
of us and simply publish it publicly. While Google may find it easier to
ask nice, we don't. We find the legal process very efficient.
/* Its our data anyway */
Last thing to remember, from our perspective: this data already belongs
to all of us. We could use printouts for toilet paper if we wanted to.
Legally speaking we need not explain or prove or demonstrate anything to
anyone. The data is created by a public agency using tax dollars; we are
entitled to the data unless the agency can prove some sort of incredibly
compelling reason to not give it to us. Further, legal precedent holds
they MUST deliver it digitally if they are maintaining it digitally, so
they can not just send you printed schedules - as they tried in our LIRR
case.
How you choose to pursuing things with your transit agency is up to you
and the resources you have available. Asking nice is one way, and suing
is another. I don't know that there is any evidence to support
litigating is less effective than asking nice when the agency is
non-responsive.
Benchmarking on FOIL: we faced data prep and delivery fees of about $50
per sub-agency (cost of burning a CD with the data for us by the Transit
Agency). Prepping the paperwork for the FOIL was a day (i'll gladly post
my FOIL letter which others can then copy paste to use if they want).
FOILs require timely response but most govt agencies blow you off on
that. We filed, were denied in several cases after a few months or more,
appealed, won on appeal after another month or two (it varied by
sub-agency), were denied a second time by LIRR. Filed in court which
cost a couple hundred dollars. We had a settlement and data within a
week of settling. I think it took us about 5-6 months overall from
initial FOIL to getting the last data set, which at the time seemed like
forever, but on reflection was pretty quick. In the case of Metro North
they responded very fast, in something like a month or so. There was
also the cost of having a real attorney to do all discussions with the
agencies. My total bill for getting all MTA data was $700. My lawyers
are friends and a bunch of civil rights do gooders who wanted to do the
FOIL, so it was a bargin. YMMV.