Should appear in iTunes App Store within a couple of days.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: StationStops for iPhone v 2.9 Submitted to Apple with Winter Service Changes

We are actively working on the new schedule database for StationStops, but
it is likely to be approved prior to the change. In the meantime, use the
‘Links’ section to check your trains by clicking the link to the official
Metro-North schedule form.

Also, don’t forget to check the Metro-North Train Time link in the same
section so you are aware of any related delays.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: NEW HAVEN LINE REDUCED WINTER SERVICE CHANGES

Train Time uses sensors at stations to attempt to locate trains and determine their on-time status.

Accuracy has reportedly also been improved, and changes have been made to avoid confusion as to when a station’s arrivals appear and fall off of the schedule.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: MTA Metro-North Train Time App Adds 28 Stations, Improves Accuracy

If you select the ‘Metro-North TrainTime‘ link from the MTA mobile site’s homepage, you will be able to see, for now, the ontime status of current trains. Unless one of the trains is delayed, they will pretty much just all read ‘On Time’ or ‘Arrived’ for now.

At the Bedford Ave L-line Subway Station, things get a little more interesting. A graphical LCD screen shows where nearby trains are, updated every 15 seconds.

It’s great that MTA is making progress on this, but I hope these are not long-term how this information is going to be disseminated.

Let’s take the mobile site as a first example.

The realtime train data should not be a separate menu on the Metro-North mobile website, it should be integrated into the schedule results (like track info .

There is no usability reason to fill out one form for schedule information and then backup and go to another for realtime information.

As for the L line, the LCD board is not going to cut it. Its too small and can only be read by people standing directly in front of it – but its information is of interest to everyone on the platform at all times. Also, the map display is unnecessary – all that is relevant is ETA of next trains.

So, lets take these two important pieces of information and rethink how to display this data.

The results look exactly like DC’s realtime train ETA signs.

These signs show exactly how long before the next 3 trains arrive in minutes, and can be seen by passengers standing 100 ft away.

There is no advantage to making people crowd around an LCD screen to see a relatively small diagram when all they want to know is ‘how long do I have to wait here?’.

This is a complaint I have had before with the Grand Central Terminal monitors as well – they use small color television screens that users need to stop and crowd around to read.

It would be much better to use a large overhead LED display that users could see from a distance and read without stopping.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: MTA Takes a Shot at Realtime Info on Subway, Metro-North

40 trains have been added to the New Haven Line schedule to accommodate holiday shoppers.
The Harlem Line is also adding a special shoppers train on Sunday.

Also on the New Haven Line:

In the AM Peak, the 8:14 AM train from New Haven will now depart at 8:16 AM; the 9:18 AM train from Harrison will now depart at 9:19 AM.

On the Hudson Line, reverse-peak substitute busing will continue at Scarborough and Philipse Manor.

More information at MTA.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: Metro-North Schedule Change Adds Holiday Shopping Weekend Trains

MBTA has become the 3rd largest transit organization to make its scheduling data free to developers in the industry-standard Google Transit Feed Specification (GTFS).

What does this mean?

Well, instead of paying lawyers to surf the internet all day to find transit developers to call and threaten with false copyright claims into signing an abusive licensing contract (MTA), MBTA is simply doing that which is simplest, most obvious, and in the best interest of its ridership – making timely and accurate scheduling information available to ALL developers for free!

More and more major US public transportation hubs are making this move to free release of data and standardization through Google’s outstanding GTFS program – cities such as:

San Francisco
Portland
Dallas
Sacramento
Austin (big zip file)
Washington, D.C.

and many, many, more!

Meanwhile, MTA continues to have its lawyers surf the internet, looking for transit developers to threaten with legal action into signing an expensive draconian licensing contract.

What does this mean to MTA customers?:

1. MTA Customers may never be offered FREE third-party transit applications.

I cannot afford to develop StationStops for free (especially in the face of litigation from MTA), but some people can. With MTA’s licensing agreement, you need to pay them $5000 up front – how are MTA passengers supposed to get access to free mobile applications that will inevitably be available to Boston’s MBTA’s passengers by generous developers who have no license overhead?

2. Fewer apps for MTA passengers.

Apps are going to be limited to those foolish enough to sign their licensing contract and pay MTA.

In light of Boston’s latest move, I would not be surprised to see MTA licensees simply drop MTA development for Boston development. Its 10x easier, with updated standardized internet feeds vs snail-mailed CD-ROMS, and its free.

3. Lower-quality apps for MTA passengers.

Under exclusive licensing, you are going to have a handful of licensed developers competing with each other, vs the whole world. Fewer developers, less competition = lower application quality.

4. What incentive is there for developers to write apps for MTA customers at all?

As an application developer, there is very little incentive anymore for me to develop applications for the MTA market. MTA has established an immutable and litigious relationship with transit developers (well, this one anyway), and no one is interested in signing with partners who behave that way.

Business partnerships are for parties with shared goals and a willingness to cooperate and listen to each other. MTA has no expressed one iota of that in my negotiations with them.

I can just as easily write outstanding mobile apps for San Francisco and Boston passengers.

I neither need to live in those cities nor ride their transit systems to do so – I just need the data, a cup of coffee, and an internet connection.

Writing MTA mobile apps without direct access to the raw scheduling data is hard. The MTA licensing contract and data delivery service is horribly unappealing. Writing apps for Boston and San Francisco is neither.

So, MTA passengers – get ready to be left with the crumbs of what developers are still willing to service you if MTA does not get on board with the rest of the US transit industry.

Originally appeared on: StationStops - Metro-North Train Schedules and NYC Commuting Blog See the original post here: BREAKING! Boston’s MBTA Releases Schedule Data Free To Developers – You’re Move MTA!