Differences

This shows you the differences between two versions of the page.

--- greater-lynchburg-transit-company [2024/02/29 22:08] – 73.40.101.133
+++ greater-lynchburg-transit-company [2024/10/03 01:07] (current) – [Stops] 67.163.111.48
@@ Line 16: / Line 16: @@
 According to general manager, GLTC has 791 stops as of 2024-02-29. In the past there were as many as 1200 stops. For comparison, Richmond, a much larger city, has 1600 stops in their bus system.
+Had conversation with Josh Moore (General Manager) and learned that any stops installed after ~2000 must be fully ADA compliant and have a logical connection to the rest of the sidewalk network or a nearby business. This is why they are so hesitant to cut down on stops. If they change their mind and want the stop back, it could cost them tens or hundreds of thousands of dollars in land acquisition, construction, etc. There is also a "notice of proposed rulemaking" at [I believe] the Federal Transit Authority (FTA) which would require all stops [in FTA-funded systems, I presume] to be fully ADA-compliant. That would trigger a mass-removal of GLTC stops. In that case, I suppose they would just sink money into fairly widely spaced, high-quality stops, but the short term effect would certainly be bad for riders.
 =====Fleet=====
@@ Line 21: / Line 23: @@
 As of 2024-02-29, GLTC has 32 fixed-route buses. They need 16 buses to operate current service (14 after microtransit replaces routes 6 and 7. Around 2024-08 they will be retiring 12 buses purchased in late 2000's that are beyond their useful life. 9 new buses from Gillig will enter operation. A partial table of GLTC buses can be found here: https://www.nathanwyand.com/2022/10/21/central-virginia-transit-fleets.html
+====Bus allocations====
+| Route | Bus count | Headway |
+| 1A | 1 | 60m |
+| 1B | 1 | 60m |
+| 2 | 1 | 30m |
+| 3A | 1 | 60m |
+| 3B | 1 | 60m |
+| 4 | 3 | 30m |
+| 5 | 0.5 | 120m |
+| 8 | 1 | 60m |
+| 9 | 1 | 60m |
+| 10 | 1 | 60m |
+| 11 | 0.5 | 120m |
+| 12 | 1 | 60m |
+Not sure where 14th bus goes. Extra?
 =====Microtransit=====
@@ Line 30: / Line 49: @@
 Currently, average bus dwell time is 44 seconds. With mobile fare collection, average dwell time should decrease to 22 seconds.
+=====Vendors=====
+Trillium software is used for producing GTFS files (and possibly maintaining stops/routes generally)
+UTA is passenger counter system
+Remix is planning software for planning routes and stops
+=====GTFS Data=====
+February GTFS: http://gltconline.com/wp-content/uploads/2024/02/GTFS_GLTC.zip
+GTFS-RT data is behind some weird abuse prevention URLS so just click the buttons on https://gltconline.com/reports-studies/ to download.
 =====Debugging possibly conflicting live bus data=====
@@ Line 38: / Line 71: @@
 Bus 3B on the sign is showing one bus and 39 minutes and another one in 44 minutes so doing the same thing where it's showing two buses coming right next to each other most likely the one on the 39 minutes is not going to happen bus 3A is showing one bus and 614 minutes and another and 669 minutes those aren't even useful times at  all I mean who needs to know that a bus will be here in 10 hours and 13 minutes which would be at 8:15pm.
+Relevant article: https://busride.com/greater-lynchburg-transit-company-selects-equans-masabi-and-transit-app-to-deliver-transit-technology-upgrade/
 All right here's a conundrum we've got bus eight arriving right this minute the sign says that one will arrive in 3 minutes and another in 8 minutes it is currently 10:07 a.m. which means that we should have one at leaving at 10:15 but it does one will be here in 3 minutes when one is arriving right this second. The transit app says bus 8 will be here in 6 minutes it is sitting here right this minute maybe that's the departure time but either way it's not particularly useful.