KCRag Forum

Critical_Mass wrote:Minor complaints, but:
Do they do training 'refresher' sessions for existing operators? Most operators are top-notch, but there is one our household refers to as 'ol hurky-jerky lead-foot. Lead-wrist, I guess is accurate. They accelerate in tiny bursts, like a car driver who tap, tap, taps on the gas pedal. You really need to hold on, even if seated.
Retraining could also be an opportunity to reinforce consistent practices. Either stop at every station or don't stop at one if no one is waiting and the button hasn't been pushed. Either open the doors automatically our require the button to open. In each case, pick one and go with it.

Please email operator complaints to info@kcstreetcar.org.

Ah I was under impression that Google Maps and arrival signs were based on GPS reatlime info, not timetables. Timetable method seems like a last century model for high frequency lines in era of automating realtime info, especially given sophisticated GPS tracking like for autos. But it sounds like you didn't catch what I meant from bus rider perspective - wasn't talking about layover point, was talking about expectations are different for over 20min runs (timetable is important) vs under 15 runs (timeframe more important) and regular bus riders experience the difference and plan differently based on line frequency. Keeping streetcar evenly spaced (for under 15min headway lines) should be the goal but the realtime info would have to be tracked if not using a timetable method. Can understand if using same system as bus lines then so it goes.

The bottom line is, a bit too often there are 2 streetcars bunched together at Union Station even during light traffic periods and the end result is that at some stops it can be a 25 minute wait. If driver at US left when seeing car 'behind' at P&L (like using the streetcar tracker web page) instead of waiting for it to get near US, it would help manage the issue.

earthling wrote:The bottom line is, a bit too often there are 2 streetcars bunched together at Union Station even during light traffic periods and the end result is that at some stops it can be a 25 minute wait. If driver at US left when seeing car 'behind' at P&L (like using the streetcar tracker web page) instead of waiting for it to get near US, it would help manage the issue.

I don't understand how you can simultaneously confirm a 25-minute wait at another stop when you're observing two streetcars at Union Station.

So for 3 car runs, two bunched up would be like a 2 car run. At this moment early Sunday morning only 2 cars are running with near zero traffic. The map shows up to 20 min wait after a car leaves any stop, sometimes I've seen 25 min at lunch hour weekdays if 2 bunched up at US with light to avg traffic.

http://kcstreetcar.org/route/streetcar-tracker/

Wouldn't you agree that avoiding bunched up cars should be higher priority than keeping to a schedule? Though understand if the signs are time based then so it goes.

I'll bet anything one car isn't showing on the map but it's running.

earthling wrote:So for 3 car runs, two bunched up would be like a 2 car run. At this moment early Sunday morning only 2 cars are running. The map shows about 20 min wait after a car leaves any stop, sometimes I've seen 25 min at lunch hour weekdays if 2 bunched up at US with light to avg traffic.

http://kcstreetcar.org/route/streetcar-tracker/

Wouldn't you agree that avoiding bunched up cars should be higher priority than keeping to a schedule? Though understand if the signs are time based then so it goes.

If the systems report an arrival over 18 minutes, there's a problem and it's not because there are two vehicles at Union Station (unless that pesky switch is broken or frozen). It's either a missed trip, a blockage, swapping a car out, or passenger-caused delay. All of these can cause the real-time systems to either report incorrectly (missed trip) or longer than planned (blockage).

Also, it's not bunching if two cars happen to be at Union Station at the same time by design. The length of the scheduled layover (always less than 10m) is shorter than the one-way run time (minimum 15m), so you cannot squeeze another run in by eliminating the layover completely AND still give the operator relief.

I can tell you all of these items occur on the bus system (blockages to a lesser degree, obviously) and can impact these systems in the same way.

Will give it benefit of doubt there are more logistical things to consider but when we're returning from lunch in RM and it's a 20+ minute wait then seeing two cars bunched at US... gotta wonder if there's more efficient ways to keep all 3 cars moving more optimally. Not an issue often but a bit more than expected. It's enough to rethink going down to RM for lunch.

earthling wrote:Will give it benefit of doubt there are more logistical things to consider but when we're returning from lunch in RM and it's a 20+ minute wait then seeing two cars bunched at US... gotta wonder if there's more efficient ways to keep all 3 cars moving more optimally. Not an issue often but a bit more than expected. It's enough to rethink going down to RM for lunch.

Understood. You should absolutely report wait times in excess of 18 minutes. It's not supposed to happen, even if it's just a problem with the signs or the app. info@kcstreetcar.org or Twitter @kcstreetcar.

So I've been living in the river market for a few weeks now and have really fallen for the streetcar. Have hopped on for several very quick trips to grab groceries at Cosentino's, Chipotle, etc. and have been pleased. Headways and on-time performance seem improved from my initial experiences within the downtown loop.

Still love the ease of use and accessibility that fareless riding provides - streetcar truly functions as a seamless "pedestrian accelerator" when fareless.

Dave, is there an official KC Streetcar app that shows live location of the trains and other info? I am currently using the unofficial app and find it very useful in timing approximately when to head towards a nearby stop.

^ KCityPost app gives that info. Shows each car movement.

There's no official app. The stops advertise the KCityPost one.

Thank you both, will check it out.

Bookmark this on your phone browser...
http://kcstreetcar.org/route/streetcar-tracker/

Bookmark this

https://itsab.us/tracker/route.php?route=SC

Then you can get to all bus routes too and it's super lightweight

Shelters are in the works for the North Loop stops. Not sure when they'll be installed.

A glowing review from The New York Times: https://www.nytimes.com/2018/07/04/trav ... r-not.html

Sweet.

RIDERSHIP BY MONTH COMPARISONS
JAN 2018: 97,194 | JAN 2017: 89,660
FEB 2018: 106,294 | FEB 2017: 125,935
MARCH 2018: 186,981 | MARCH 2017: 183,077
APRIL 2018: 153,040 | APRIL 2017: 188,171
MAY 2018: 199,102 | MAY 2017: 210,207
JUNE 2018: 223,877 | JUNE 2017: 217,129

http://kcstreetcar.org/wp-content/uploa ... ship-1.pdf

Any guess on the variances? Events? Weather?

Transportation usage varies wildly, which is why the industry often speaks in averages. Weather and events are particularly noticeable with streetcar, but there is a core weekday ridership (~2,500) that's there even in the dead of winter -- assuming there is no service disruption.

earthling wrote:RIDERSHIP BY MONTH COMPARISONS
Any guess on the variances? Events? Weather?

Weather is probably the main day by day modifier regardless of the specific day. If it's pouring rain it doesn't matter if it's a Big 12 game day or a weekday with nothing going on, some percentage just won't go outside who otherwise would.

There being way less events in January than June will play a big part in monthly ridership