Categories
Share On
July 2023
The TripShot product team released rider app improvements to vanpool boarding, instance naming, trip planning screen refreshing, license plate error messaging and more.
This month, the TripShot product team has released rider app improvements to vanpool boarding, instance naming, trip planning screen refreshing, license plate error messaging and more. There have also been improvements to admin web interfaces related to SFMTA credentials, stop tags and resource rules.
iOS Updates
Rider App - 2023-07-23
Improve
- Driver initiated vanpool boarding. Vanpool Drivers can now add Vanpool passengers via the TripShot Rider app using the “Add Passenger” button. When adding a new vanpool group, there is now a checkbox "Allow Drivers to add Vanpool Passenger". The list of members in the Vanpool Group will be visible to Vanpool Drivers as they are adding vanpool passengers.
- Add accuracy to vanpool endpoints and omit location/accuracy in more places. Adjusting behavior to improve accuracy.
- Wrap instance display name on public system picker screen and drawer header (iOS). Adding the ability to wrap instance name for improved display.
- Show secondary instance display names in rider apps. This is front-end related work to effectively update the TripShot Rider App display names of available transit systems. Now the available transit systems will be the advertised name of that system, rather than a secondary default name used only internally at TripShot.
Rider App - 2023-07-27
Improve
- Prevent double refresh on trip planner screen when saving trip options. Correcting behavior where the network call is being made twice when trip options are saved.
Fix
- Clean up license plate error messaging. Correcting behavior when saving a vehicle with license plate field blank. Now we will display “License Plate Required” replacing a 400 error.
- Fix crash caused by large info windows. The crash caused by large info windows in the Map view, is occurring due to recent device OS updates or possibly Google API modifications that we were not notified on. Regardless, we have identified the issue and in order to address this crash we made some minor improvements/fixes to the Stop and Vehicle info screens on the Map as follows: Cap name lengths at 32 characters. This includes route names, stop names, and headsigns. Wrap all text in the info window to 256px. Cap the font size at 22pt.
- Fix crash when saving trip options on iOS 17 beta. The crash when saving trip options is occurring due to an iOS bug introduced in a recent device iOS update under iOS 17 beta. And in order to address this crash we made some minor improvements/fixes. We are monitoring any future iOS 17 releases and suspect this will also be fixed on their end.
Android Updates
Rider App - 2023-07-23
Improve
- Driver initiated vanpool boarding. Vanpool Drivers can now add Vanpool passengers via the TripShot Rider app using the “Add Passenger” button. When adding a new vanpool group, there is now a checkbox "Allow Drivers to add Vanpool Passenger". The list of members in the Vanpool Group will be visible to Vanpool Drivers as they are adding vanpool passengers.
- Add accuracy to vanpool endpoints and omit location/accuracy in more places. Adjusting behavior to improve accuracy.
- Show secondary instance display names in rider apps. This is front-end related work to effectively update the TripShot Rider App display names of available transit systems. Now the available transit systems will be the advertised name of that system, rather than a secondary default name used only internally at TripShot.
Web Updates
Admin Web - 2023-07-14
Improve
- Use directions.txt to help determine nominalTripHeadsign. TripShot has improved back-end behavior for API sharing purposes related to how the GTFS directions.txt file information is stored for headsign / directional changes within the Routes tab. This is a backend-only change that should not be visible to end users.
- Support new required SFMTA fields in the backend. There are multiple changes to the SFMTA API integration TripShot shares with multiple clients. These changes should not be felt by end users.
- Support new required SFMTA fields in the front end. With the latest API changes from SFMTA, new fields have been added to Route and Route Service Details. When creating a new Route (or clicking the Details link of an existing Route), there is now a new input field with a ‘Default SFMTA Route Name’ label below the Short Name field under the Route Details pop up. While creating a new Route Service (or clicking on an existing Route Service), there is a new input field with a ‘Default SFMTA Route Name’ label that will be displayed next to the Name field under the Route Service button.
- Add new SFMTA fields to the SFMTA report. In conjunction with recent SFMTA API updates, there will now be additional columns and data available within the SFMTA Submissions Report: ‘Route Type’, ‘Run ID’, ‘Route Identifier’ & ‘Run Occupancy’. These columns will be unchecked by default.
- Add bundled query parameter to /v1/shared/ride/:day/:tripId (and public equivalent). This is a back-end-only change for how we store and call endpoints for GTFS-related data. This should not be felt by end users.
- GET /v1/shared/route/{routeId} (shared route details) needs to include vehicle information. Adding more information to our route detail response.
- Post Pay Balance Notifications | Frequency. Post-pay balance notifications will now exclude weekends.
- Collapse direction and direction_name in output, favoring direction_name if present. This update will alleviate client confusion of having two options for what to call the direction in gtfs. We will collapse direction and direction_name into a single value when outputting in the sharing api.
- Add "Region" column to the Reservations report. Added a checkbox within the Column selector for “Region” within Reservations Report.
Fix
- Removing Vehicle Information from GTFS RT. Client specific. Fix for GTFS RT implementation that affected their AVAS announcement system.
- Better handling of unknown stops in commutePlan endpoint. Updating how to handle unknown stops to prevent a 500 error.
- Reading rows from NotificationMethod must not fail with an invalid email. This release will correct an issue experienced while running the Rider Notifications report when an applicable rider has an invalid email address. This report will now run without error when there is an invalid email address tied to the user.
Beta
- Optimize passing small differences in a large chunk of json. With this release, multiple backend updates have been made available, with several noticeable UI components: Conflicts in a shift will now appear above the list of Activities. Clicking on the Activities details of the trip (under Shifts) will be highlighted in the adjacent map. Improved scroll bar behavior in the P&A Fixed Routes tab. Incremental changes will now save as large-scale changes are Saved (within the Fixed Routes tab). Messages in the banner are now available in the right-hand hidden column. When a long-running operation is occurring, there will be an indicator that it’s saving/running.
- Insights team integration with the ExaTMS Admin. This is an internal-only ticket to support Dev environments maintained by Data Analytics. Note: while we don’t usually post our internal dev task tickets, this felt like a fun one to share as the advancement of out Data & Analytics team is of the utmost excitement!
- Convert the Optibus CSV start/end times to proper ExtendedTimeOfDay. For users that will utilize the Optibus Import functionality within TripShot, the ‘Export as CSV’ option for a Migrated Plan will now convert the end time in the .csv export to an ExtendedTimeofDay timestamp. As an example, any .csv export of a migrated Optibus plan will now display end times as 24:30 and 24:45 for end times previously displayed as 00:30 and 00:45.
Admin Web - 2023-07-27
New
- Add Stop tags to Resource rules - Front End. This will allow users to create resource rules that use the stop tag. This will require the Experiment Flag (policyBuilder).
- Add Rider tags to Resource rules - Front End. This will allow users to create resource rules that use the rider tag. This will require the Experiment Flag (policyBuilder).
- Store FixedRoute journey events. We'll produce a table that marks arrivals and departures for the Analytics team to work on the NTD report.
Improve
- Allow blocklisting specific instances from transaction receipt. A new configuration setting allows us to block specific instances from receiving notifications.
- Support Wallet for Parking Reservations - Post Pay. Wallet improvements to allow for post-pay handling of parking reservations.
- Parking Reservations | Require License Plate When Booking Reservation. Improving behavior to require license entry to the license plate field.
- Replace secondaryDisplayNames with advertisedNames. This is back-end related work to effectively update the TripShot Rider App display names of available transit systems. Now the available transit systems will be the advertised name of that system, rather than a secondary default name used only internally at TripShot.
- Provide reports to capture historical ETAs for fixed route trips. This is an internal-only. Events-based report to gather ETAs for current/future Analytics and Dashboarding needs. This may become a report available in the front end in the future but is currently not viewable by admin users.
- GET /v1/shared/route returning routes that are part of a route group. Correcting behavior to display only Route Group name when Route Group is present.