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
The map view for each bus/tram timetable should show the route of the service on the map with the different stops plotted to the maps. See https://www.figma.com/file/0EvvTWMZXlKDrQ9WcINGsn/Station-and-Stops?node-id=534%3A16080. There are currently some issues with data inconsistencies for the latitude and longitude points of the stations when getting the sequence data from the APIs so this will require some backend support to find and fix the issues.
APIs
Polyline coordinates for bus/tram routes: journeyplanner.networkwestmidlands.com/api/TimetableStopApi/getRouteMap/:stateless/:version/:direction/:when/Tfwm-Api/Line/:lineid/Route/sequence/:direction
Route sequence with stop coordinates: api.wmnetwork.co.uk/Tfwm-Api/Line/:lineid/Route/sequence/:direction
Example coordinate inconsistencies with 11 bus route:
Example with route showing correctly (tram):
The text was updated successfully, but these errors were encountered:
What
The map view for each bus/tram timetable should show the route of the service on the map with the different stops plotted to the maps. See https://www.figma.com/file/0EvvTWMZXlKDrQ9WcINGsn/Station-and-Stops?node-id=534%3A16080. There are currently some issues with data inconsistencies for the latitude and longitude points of the stations when getting the sequence data from the APIs so this will require some backend support to find and fix the issues.
APIs
Polyline coordinates for bus/tram routes:
journeyplanner.networkwestmidlands.com/api/TimetableStopApi/getRouteMap/:stateless/:version/:direction/:when/Tfwm-Api/Line/:lineid/Route/sequence/:direction
Route sequence with stop coordinates:
api.wmnetwork.co.uk/Tfwm-Api/Line/:lineid/Route/sequence/:direction
Example coordinate inconsistencies with 11 bus route:
Example with route showing correctly (tram):
The text was updated successfully, but these errors were encountered: