You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disclaimer:
This pertains to a source data issue, not necessarily a bug in the app itself. I am reporting this on Github because I received an error when attempting to report through the app's built-in feedback (#1054) but please let me know if there is a more appropriate channel.
Summary:
A San Diego MTS bus stop was previously removed (mid-2019?) but the stop still shows in OneBusAway. The stop is shown in the main map, trip/route progress, and selecting the stop shows ETAs for buses that will not actually be stopping. Google Maps also show this erroneous stop, so perhaps the issue is stemming from GTFS data? I can confirm that on November 18, 2020 there are no poles, signs, or anything else at the location shown on the map.
Stop number: 99191
Stop Location: Viewridge Avenue and Balboa Avenue (East Bound)
Bus Route: 60
Screenshots:
The text was updated successfully, but these errors were encountered:
mds08011
changed the title
San Diego MTS Removed Stop Still Showing
Removed stop still shown (San Diego MTS)
Nov 20, 2020
@mds08011 Thanks for the report! If the in-app issue reporting is having problems, the next best approach would be to do in main navigation drawer "Send feedback->Contact Customer Service", which should lead you to the [email protected] option for SDMTS.
Disclaimer:
This pertains to a source data issue, not necessarily a bug in the app itself. I am reporting this on Github because I received an error when attempting to report through the app's built-in feedback (#1054) but please let me know if there is a more appropriate channel.
Summary:
A San Diego MTS bus stop was previously removed (mid-2019?) but the stop still shows in OneBusAway. The stop is shown in the main map, trip/route progress, and selecting the stop shows ETAs for buses that will not actually be stopping. Google Maps also show this erroneous stop, so perhaps the issue is stemming from GTFS data? I can confirm that on November 18, 2020 there are no poles, signs, or anything else at the location shown on the map.
Screenshots:
The text was updated successfully, but these errors were encountered: