CTA Partners with Google

[Busjack]

Interesting, that the example illustrated on the Home Page is wrong. If you are going from the Forest Glen Garage, one would take the 85 bus from there, rather than walk to the 85A. I guess par for the course for a computerized system.

[Kevin]

Interesting, that the example illustrated on the Home Page is wrong. If you are going from the Forest Glen Garage, one would take the 85 bus from there, rather than walk to the 85A. I guess par for the course for a computerized system.

The first route suggestion advises taking the 85. The 85A routing was suggested by the second alternative. I've updated that screenshot so as not to falsely represent the accuracy of the service.

[Busjack]

I verified that the example works properly, but there are other bugs in the system. Verifying a trip I once made (from the south side via Western to West Ridge), Google Transit has this incomprehenible jump from 82nd and Kedzie to Montrose; the correct route would have been 49 or X49 North to 49B North to 155. Similar results were reached when trying on Ashland, a trip I have not taken, but I assume would be via 9 to 22 at Clark/Southport, and the the suggested route on Clark. I probably would have walked from Clark and Devon rather than take the 155 bus, but it didn't offer the latter option.

For my actual termini at the time, the map appropriately suggests the next bus to the Red Line (in these instances either X55 or 174) and then to Loyola and 155. Unlike in those days, one would have to decide whether to walk to 55th for a 55 or X55 or 57th for 174 (and, of course, whether to walk to Woodlawn for the X55 or get the 55 at University).

[jajuan]

I verified that the example works properly, but there are other bugs in the system. Verifying a trip I once made (from the south side via Western to West Ridge), Google Transit has this incomprehenible jump from 82nd and Kedzie to Montrose; the correct route would have been 49 or X49 North to 49B North to 155. Similar results were reached when trying on Ashland, a trip I have not taken, but I assume would be via 9 to 22 at Clark/Southport, and the the suggested route on Clark. I probably would have walked from Clark and Devon rather than take the 155 bus, but it didn't offer the latter option.

For my actual termini at the time, the map appropriately suggests the next bus to the Red Line (in these instances either X55 or 174) and then to Loyola and 155. Unlike in those days, one would have to decide whether to walk to 55th for a 55 or X55 or 57th for 174 (and, of course, whether to walk to Woodlawn for the X55 or get the 55 at University).

I got similar flaws when testing a trip from my house to Howard Red Line station. The correct trip would have been 12 Roosevelt to the Red Line and the Red Line north. I got the same odd jump to 83rd and Kedzie. Then take 78 to Clark and 22 to Howard. I see the suggested trips are all CTA with no Pace added in. some trips I entered that would be direct if Pace were included came out with CTA trips that would have you traveling practically in a circle to get to your destination

[Busjack]

I see the suggested trips are all CTA with no Pace added in. some trips I entered that would be direct if Pace were included came out with CTA trips that would have you traveling practically in a circle to get to your destination

Pace is definitely not on the system. Entering in something closer to where I live resulted in "Your search for transit directions from ... to ... appears to be outside our current coverage area. Please consult our list of participating public transit agencies. Get driving directions..."

Another anomaly I found is that if you put in something about at Western and Addison to get to Western and Devon, the suggested transfer point from 49 to 49B earlier in the day was Ainsley, but later was Lawrence. In any event, one would think that the proper spot would be the Brown Line terminal (Leland Ave.). And why wait on the next corner, when the 49B is probably sitting at the station?

The transfer point from X49 to 49B is at Foster, which seems to make sense, since the 49B doesn't go into the Berwyn terminal (if I remember correctly).

[jajuan]

Pace is definitely not on the system. Entering in something closer to where I live resulted in "Your search for transit directions from ... to ... appears to be outside our current coverage area. Please consult our list of participating public transit agencies. Get driving directions..."

Another anomaly I found is that if you put in something about at Western and Addison to get to Western and Devon, the suggested transfer point from 49 to 49B earlier in the day was Ainsley, but later was Lawrence. In any event, one would think that the proper spot would be the Brown Line terminal (Leland Ave.). And why wait on the next corner, when the 49B is probably sitting at the station?

The transfer point from X49 to 49B is at Foster, which seems to make sense, since the 49B doesn't go into the Berwyn terminal (if I remember correctly).

No it goes right past it. The southbound 49B stop is right at the terminal though instead of at the corner.

I guess Pace and Metra aren't actively involved. Maybe they should though for those out of towners with relatives in the suburbs who may want to see the city cheaply and without the hassle of sitting in expressway traffic or downtown parking garages.

[Busjack]

No it goes right past it. The southbound 49B stop is right at the terminal though instead of at the corner.

Trying this southbound, the transfer points according to Google are Ainsley (trip 2) or Lawrence (trip 3) to 49 and Foster (trip 1) to X49, not Berwyn in any case.

[westing]

Until bus tracker arrives the "view upcoming departures" feature for bus and rail stops listed on the map is quite handy. I tested it out today, looking out the window and most 62 buses were on-time. You cannot guarantee the accuracy but its easier than estimating between timing points on a CTA schedule.

[jajuan]

Until bus tracker arrives the "view upcoming departures" feature for bus and rail stops listed on the map is quite handy. I tested it out today, looking out the window and most 62 buses were on-time. You cannot guarantee the accuracy but its easier than estimating between timing points on a CTA schedule.

Where did you find this option on Google because I did not see that option.

[Danielsmusic]

Where did you find this option on Google because I did not see that option.

If you zoom in far enough, you will see little bus icons marking each bus stop. If you click on one, it will tell you what routes stop there and when each route's next few departure times are.

[jajuan]

If you zoom in far enough, you will see little bus icons marking each bus stop. If you click on one, it will tell you what routes stop there and when each route's next few departure times are.

I had a suspicion that might be what you were referring to, but it's worded a bit differently on the site. So you live close enough to a bus stop to test this out. Cool thing that the arrivals were really close to accurate.

From the earlier discussion so far it's becoming obvious that this could be a really good alternative for the RTA trip planner for those who mainly use the CTA. And it definitely makes it easier for people who may be visiting the city or who just moved here because of the included maps of the trips. They just have to work out the bugs that were brought up and Pace and Metra should consider joining in so that people will be able to see how to get to suburban locations.

[Kevin]

Chicago is now officially supported in Google Transit. Google has posted a video demo on their site and the CTA has thrown aside the RTA Trip Planner on their home page in favor of Google Maps. According to The Trib, the CTA held a press conference with Da Mare this morning to announce the service.

[Busjack]

... Verifying a trip I once made (from the south side via Western to West Ridge), Google Transit has this incomprehenible jump from 82nd and Kedzie to Montrose; the correct route would have been 49 or X49 North to 49B North to 155....

I redid this, and tried a couple of others on the CTA home page, and while this particular error has been eliminated, the system shows a bias toward somehow getting to the Red Line, instead of using the X49 bus. (Link to trial for today, showing 3 suggested routes, only one of which is directly up Western.) Is this an indication that the latter is not very fast?