bus f.e.e.d. (an adventure in determining what you can and cannot do with transit apis) dmitri...

7
bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Upload: sandra-walters

Post on 17-Jan-2016

215 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

bus F.E.E.D.(an adventure in determining what you

can and cannot do with transit APIs)

Dmitri ChernetskyCarl Hage

Geoffrey HatchardZachary Pallin

Page 2: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Initial Ideas• more robust bus information for users

• bus fleet fuel economy

Page 3: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Product• collating what’s available from the data published

by VTA directly, as well as AmigoCloud, 511.org (MTC), and TransLoc

• creating a library of reformatted data and repackaging it in ways that will be usable for others

Page 4: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Product

Page 5: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Product

Page 6: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Thoughts for the future

• ridership statistics (real-time arrivals, departures, boarding and alighting numbers)

• bike rack occupancy information

• fuel consumption data (saved by maintenance teams currently, needs to be made public)

Page 7: Bus F.E.E.D. (an adventure in determining what you can and cannot do with transit APIs) Dmitri Chernetsky Carl Hage Geoffrey Hatchard Zachary Pallin

Questions?

Thank you to VTA, the Tech Museum, the Knight Foundation, Joint Venture Silicon Valley, Microsoft, Code for San Jose, the city of San José, MapBox, AmigoCloud, SPUR, APPCityLife, the Silicon Valley Talent Partnership, and most importantly, the individuals

who prepared and provided all the great food!