jtrosario Posted May 19, 2013 Report Share Posted May 19, 2013 Two issues: 1) This issue occurred on both Green line trains to Ashland/63rd and now Red line trains to Ashland/63rd. The Ashland/63rd station is not showing up as a stop for all SB trains. They all show Ashland/63 as a destination, but not as a stop on their list of stops. Also, they all "disappear" off the map BEFORE they pull into Halsted. All other destinations in train tracker(including Cottage Grove), show up in the station list for their respective train runs. (NB trains are showing up O.K. starting at Ashland/63)SB trains should be showing up when they stop at Halsted and at least part way towards Ashland/63 before disappearing from the map. 2) South of Roosevelt, all SB Red line trains are showing up on the map following the subway towards the Dan Ryan up until about 18th(which is off route), and then "jumping" over to the 35th-Bronzeville-IIT station(which is the correct tracks). SB Red line trains should be showing up on their newly assigned route from Roosevelt to 35th-Bronzeville-IIT. Quote Link to comment Share on other sites More sharing options...
jajuan Posted May 19, 2013 Report Share Posted May 19, 2013 Sounds like issues that I've observed happen early on on Bus Tracker when a reroute is under a long-detour like the Red Line is under now or permanent reroute. Especially issue number 2. Bus icons would be shown following the old route for a short part of the way then suddenly "jump" to the correct route. The glitch would have been corrected after a day or so, no more than a few days. Quote Link to comment Share on other sites More sharing options...
Busjack Posted May 19, 2013 Report Share Posted May 19, 2013 Sounds like issues that I've observed happen early on on Bus Tracker when a reroute is under a long-detour like the Red Line is under now or permanent reroute.... Made me look at an altered route, in this case 71. It was showing buses up to Garfield, but the blue route line was "as the crow flies," while the buses were on State. At least it wasn't the usual "the bus is off route so it disappears." R routes were not there. Quote Link to comment Share on other sites More sharing options...
Busjack Posted May 19, 2013 Report Share Posted May 19, 2013 Two issues: 1) This issue occurred on both Green line trains to Ashland/63rd and now Red line trains to Ashland/63rd. The Ashland/63rd station is not showing up as a stop for all SB trains. They all show Ashland/63 as a destination, but not as a stop on their list of stops..... They do show up as departures from Ashland 63, both on the map and the station pulldown. Is you question that they aren't showing up as arrivals? Quote Link to comment Share on other sites More sharing options...
jtrosario Posted May 19, 2013 Author Report Share Posted May 19, 2013 To clarify Issue #1: 1) A correct Green, listing Cottage Grove as its destination AND last stop. 2) A correct Orange, listing Midway as its destination AND last stop. 3) An incorrect Red, listing Ashland/63 as its destination and Halsted as its last stop (also applies to the train in fron of it) 4) An incorrect Red, listing Ashland/63 as its destination and Halsted as its last stop. This is the furthest West along 63rd ANY train will stay on the map. It will disappear West of here(Stewart & 63rd) before getting to Halsted, a full mile and a half before the Ashland/63 stop. (Of course, why wouldn't it stay on train tracker - Halsted is the last stop) And that's the glitch - Halsted ISN'T the last stop. 5) An incorrect Green - same as #4 - taken late last week. This glitch isn't a Green or Red glitch, it is an Ashland branch glitch. All trains WB on the Ashland branch "fall off the map" 1/2 mile E of Halsted(specifically at Stewart) and are missing Ashland/63 as a scheduled stop. Quote Link to comment Share on other sites More sharing options...
jtrosario Posted May 19, 2013 Author Report Share Posted May 19, 2013 Sounds like issues that I've observed happen early on on Bus Tracker when a reroute is under a long-detour like the Red Line is under now or permanent reroute. Especially issue number 2. Bus icons would be shown following the old route for a short part of the way then suddenly "jump" to the correct route. The glitch would have been corrected after a day or so, no more than a few days. You called it, issue #2 is resolved with train tracker now showing Red line trains moving SB on the correct tracks from Roosevelt to 35th. Quote Link to comment Share on other sites More sharing options...
Busjack Posted May 20, 2013 Report Share Posted May 20, 2013 You called it, issue #2 is resolved with train tracker now showing Red line trains moving SB on the correct tracks from Roosevelt to 35th. And any issue of it not showing arrivals at Ashland-63 seems fixed. Quote Link to comment Share on other sites More sharing options...
jtrosario Posted May 20, 2013 Author Report Share Posted May 20, 2013 It sure is. Reported to customer service in detail yesterday, fixed today. Looks like everyone is keeping on top of any Red Line issues. I'll try the Yellow arrivals at Howard today and we'll see what happens. Quote Link to comment Share on other sites More sharing options...
Around the Horn Posted May 22, 2013 Report Share Posted May 22, 2013 two Purple lines at Division Street just disapeared off the map... Quote Link to comment Share on other sites More sharing options...
jajuan Posted May 24, 2013 Report Share Posted May 24, 2013 Speaking of Purple Line trains on Train Tracker, I noticed that Howard doesn't appear as a next stop arrival when you're looking at the next few upcoming stops for northbound Purple Expresses if you're say for instance you're physically on a train and want to gauge how long it will take you to reach Howard as I was doing Tuesday morning. I wanted to get a feel of how long it would take me to finish some errands I was doing that morning. As I was tracking how far away I was from different stops from a time perspective, I noticed the next few stops approached listed would never go past Belmont, and then once the train actually and passed Belmont list of stops jumped the Evanston stops but never showed Howard and how long before reaching Howard from different positions the train passed. 1 Quote Link to comment Share on other sites More sharing options...
Around the Horn Posted May 24, 2013 Report Share Posted May 24, 2013 Speaking of Purple Line trains on Train Tracker, I noticed that Howard doesn't appear as a next stop arrival when you're looking at the next few upcoming stops for northbound Purple Expresses if you're say for instance you're physically on a train and want to gauge how long it will take you to reach Howard as I was doing Tuesday morning. I wanted to get a feel of how long it would take me to finish some errands I was doing that morning. As I was tracking how far away I was from different stops from a time perspective, I noticed the next few stops approached listed would never go past Belmont, and then once the train actually and passed Belmont list of stops jumped the Evanston stops but never showed Howard and how long before reaching Howard from different positions the train passed. Hmmm...Interesting... Quote Link to comment Share on other sites More sharing options...
TheBrunswickBowler Posted July 1, 2013 Report Share Posted July 1, 2013 I have some proof of errors. I was on train tracker and I clicked on one of the Blue Lines and it said Blue Line #1004 to Forest Park. Quote Link to comment Share on other sites More sharing options...
jajuan Posted July 2, 2013 Report Share Posted July 2, 2013 I have some proof of errors. I was on train tracker and I clicked on one of the Blue Lines and it said Blue Line #1004 to Forest Park. pool 036.JPG pool 037.JPG pool 039.JPG pool 038.JPG I'm not seeing where the error is. The group of stations shown seem to be in the correct order for that direction of travel. Quote Link to comment Share on other sites More sharing options...
Around the Horn Posted July 2, 2013 Report Share Posted July 2, 2013 I'm not seeing where the error is. The group of stations shown seem to be in the correct order for that direction of travel. #1004 is the error,probably meant 104 Quote Link to comment Share on other sites More sharing options...
Busjack Posted July 2, 2013 Report Share Posted July 2, 2013 #1004 is the error,probably meant 104 1004 the Pace subscription L service. Quote Link to comment Share on other sites More sharing options...
jajuan Posted July 2, 2013 Report Share Posted July 2, 2013 #1004 is the error,probably meant 104 Ah ok. Yeah one too many zeroes in the run numbers. Duh. 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.