JeTDoG

This may have already been asked, but has there been any clear specification of what the cut-ins on the opposite corners (northwest and southeast) of the 14th and 15th floors relate to? I've seen them in the renderings, and they are apparent in the framing, but it's not clear what purpose they serve other than artistic detail.

Did they drop something?

I sense hostile architecture incoming. When they closed off the front entrance to create their smokers' patio, they also created a space for downtown's unhoused population to seek haven from the elements between the planters. I suspect enough complaints have been lodged that more action is being taken. Or maybe I'm just cynical.

surf, where did you see this?

clvlndr, I have to ask, and I mean this sincerely -- given this incident, what more information, specifically, would have helped you and/or changed your mind about using RTA on that day, at that time? I'm asking because I can advocate for better information, if I know what that better information, from a rider's perspective, needs to be. Simply saying "more" or "better" isn't nearly as helpful.

Having just passed through there last night, I can tell you that the MLK project involves the total replacement of the westbound track bed bridge well, a large price of (I believe) precast concrete over MLK, just west of the Cedar - University Rapid Station. There's no way that construction could have been accomplished without removal of the overlying track structure. It's similar in scope to what's happening in Tower City on Track 8, albeit on a MUCH smaller scale.

As a trial application, it is currently visual inspection validation only. Simply show the generated QR code for an activated fare to any gate attendant (at Tower City, the center swing gate used for wheelchair access), and you'll be permitted through. Similarly, displaying the code to a fare enforcement officer on the Red Line or HealthLine, or the bus operator as you're boarding any other bus, proves fare payment.

Incorrect. The B-Line trolley will run between the two terminals from 5am-1am, and those east side buses that run 24 hours will have their routes extended between 1am and 5am to service the stop at Frankfort and West Roadway: http://www.riderta.com/service-alerts/downtown-riders-convention-reroutes

Please send all feedback about the RTA CLE app to [email protected]. Complaints/feedback posted on this forum will NOT be logged for that purpose. Let's keep everything in one proper place. Remember -- this is a trial run being conducted at no cost to the Authority. Your feedback will be important to any future development of the app customized to our wants and needs.

Thanks JetDog for your responses. I am extremely pleased to hear that you encourage outside developers to utilize the GTFS files. I've noticed that you're (RTA) are updating the GTFS files (thank you again!) and fixed one error that I noticed in a more recent issue. A couple questions: I assume that (DNU) in the stops file means 'Do Not use'? Is this correct? Also, Who should I contact for other GTFS questions in the future? We update those files... periodically. I can't say there's a regular schedule to the updates, but I will say we update in advance of any major quarterly change. I'm working on a set this week that will incorporate the changes to the Red Line that are coming May 8 (removal of the slow zone westbound from W 25 to W 65). Unfortunately, due to the rate at which Google processes the updates, the changes will not be reflected in trip plans until about May 11, or three days after they become effective. This is atypical. Usually, we update no later than 10 days before the service change, so that the new information becomes available about 4 days before the change. You are correct in your assessment of the meaning of DNU. These are stops that exist in our system, but are pending removal. We alter the stop assignments for DNU-coded stops so that they are not used in the trip-planning process. Unfortunately, such filtering does not take place in NextConnect, so any real-time inquiries will still list the DNU stops as available options. I'm probably your best source for GTFS-related questions. I've been working with the GTFS files since we started supplying them to Google in 2008 (I was the point man for making that process happen).

A few responses to what's been shared so far (and my apologies for not having this posted sooner): I'm going to temporarily set aside the discussion of the fares, how to ride, and how to pay pages. Not because I think they're unimportant - nothing could be further from the truth. I actually want to spend a little more time collecting not only my thoughts, but the thoughts of other folks who more closely work with our fare collection on a daily basis. Something I'd like to clarify in that regard -- we need to concentrate on accurately describing the system as it exists today. Suggestions on how the system might be refined, simplified, or improved, while valid, are not within the scope of this conversation. For purposes of this conversation, assume that the system as it currently exists cannot be changed. System maps: Yes, it is still true that the PDF system map, due to limited resources, is updated no more than annually. Change is coming, in multiple forms. My personal impression of PDFs has always been that they have limited utility on web, and on the mobile web, even less so. However, in an organization that for so many years was, and all too often continues to be, print-centric, PDF is "easy". That doesn't make it right. It needs to be fixed, and it will be fixed. I don't have an exact timetable, but your complaints about the rail system map have been heard. Something that complicates the implementation of this physical map is the fact that it exists in multiple media, displayed at multiple aspect ratios, with multiple depths of information, across multiple locations. Standards are great -- we've got dozens of them ;-). I'm keeping abreast of this one, and will let you know what transpires. A diagrammatic frequency map, or some adaptation thereof, is being looked at. One issue with frequency maps is that, especially in a system like ours, frequencies are not static. They vary by time of day, with some routes peaking to high frequency only at rush hour. The interlining of our routes, to achieve peak utilization of the limited resources we have, can also sometimes result in irregular peaks and valleys in the frequency. A question I posit to you is: in a frequency map, how close is "close enough" when stating a route's frequency? As far as an app is concerned: we, as an organization, need to be able to reach out to the broadest audience possible. Websites are the original cross-platform app. Our website is improving steadily in the information it provides, and the manner in which it provides that information. We encourage outside app developers to remix our schedule data, available at http://www.riderta.com/sites/default/files/gtfs/latest/google_transit.zip, into their own apps. Beyond that, we do not presently have a real-time API available to outside developers. Smartcard/smartphone tickets: Stay tuned. Watch for an announcement of a pilot project coming soon. Text-heaviness of the site: Yes. It is. I agree 100%. A portion of this is related to our requirement to be ADA Section 508 compliant as far as accessibility is concerned. Again, as with PDF, text is "easy". This may not make it right, and writing for the web is far different, even in an accessibility situation, than writing for hardcopy. Your concerns, and suggestions, have my support. I think this initially addresses most or all of the non-fare, non-how-to-pay, non-how-to-ride concerns. More to follow. FYI, I will be out of town and likely offline the week of 5/8.

None of what is intuitive? Please be specific about who and what you are responding to.

327, we're not going to debate the merits of the proof of payment system, or adjudicate your particular case, in this thread. Let's stay on topic, please. Straphanger, I appreciate your well-phrased comments. I'll have some responses later today or tomorrow.

Straphanger, I'm going to confine my response to your one area of concern that is within my power to most directly affect. I'd love to know more about what aspects of our website(s) you don't feel to be "decently designed". You can choose to continue the conversation here, or , as I think the mods might prefer to lessen clutter, you can email your concerns and suggestions to [email protected]. Messages to that box come to me directly. This same offer applies to all readers of this forum. Dialogue is the first step to improvement. Thanks JeTDoG[/member] . I've outlined several specific suggestions in this space over the past couple years, but I know this isn't the best way to relay info to you. Note, the suggestions refer to the content of the website, not its functionality, so "poorly designed" probably wasn't the best way to describe the issue. I can be in touch via email, but unless Mods disagree, I'd like offer suggestions in a new thread here to open the process up to other RTA users as well, so I'll try that first. I'd be happy to use either venue. There is a certain amount that design can contribute to ease of content updating and content consumption, so I'll take the hit on that where it's due. Based on suggestions, I'll "fix" what I can, shepherd along and encourage what I can, and try to offer alternatives for anything that doesn't fit the first two handling methods.

Straphanger, I'm going to confine my response to your one area of concern that is within my power to most directly affect. I'd love to know more about what aspects of our website(s) you don't feel to be "decently designed". You can choose to continue the conversation here, or , as I think the mods might prefer to lessen clutter, you can email your concerns and suggestions to [email protected]. Messages to that box come to me directly. This same offer applies to all readers of this forum. Dialogue is the first step to improvement.