open data – Just Trying To Have A Friday, You Guys

Introducing: MTA Fare Buster

Dev, My Latest And Greatest Invention No Responses »

Oct 282014

So first off, let me start by saying that I noticed that my last post is entitled NYC Subway Data, Part 4 – moar data!. I later noticed that there is no “Part 3” in this series. There never was. Too bad, it will remain a mystery.

Going forward, I’m happy to introduce MTA Fare Buster!!!

Based on Ben Wellington (iQuantNY)‘s post on the leftover money that you commonly end up with when buying a metrocard, I did some research and despite there being a few similar apps out there on the Android market, one was good but not updated with the latest bonus policy, one doesn’t give you options, and one wasn’t free, so I decided to write my own.

Full source code here: https://github.com/loisaidasam/mta-fare-buster-android

Happy commuting!

NYC Subway Data, Part 4 – moar data!

Dev, Mondays and Tips 1 Response »

Oct 202014

After spending some fun time with the subway schedule data the other night, I’m a bit more curious now about usage.

On the data list I found the following resources:

Fare Data

(could be helpful for finding fare type popularity? dunno how interesting that is…)

Subway Entrance & Exit GIS Data

Location data, cool! Through the NYC open data site, I even found this cool little map showing the NYC subway entrances (I’m assuming based on this data):

https://nycopendata.socrata.com/Transportation/Subway-Entrances/drex-xx56?

Turnstile Data

THIS is interesting because hourly turnstile data COULD be helpful for trying to estimate station popularity at a given time of day/day of week/etc. The only problem is that the Remote Unit/Control Area/Station Name Key data doesn’t really matchup with the GTFS dataset Stops identifiers:

Remote Booth Station Data