Problem
The parent issue to this one broadly covers GPS route editing Add stop address editing for GPS mileage. This issue is specifically about supporting route editing before an expense is created, and not after. The latter will be handled in the parent issue as it requires saving gps coordinates on expenses.
Solution
Implement GPS route editing during the in app creation flow and ensure the expense is saved as edited by the backend.
This comment contains an explanation of the plan for how this should be implemented, which is roughly as follows:
- The user drags a slider to trim the GPS route in-app.
- The waypoints are edited to discard any after the edited stop point
- Update the last waypoint to be exactly the stop point
- Trim the GPS coordinates to exclude all after the stop point.
- Add the last waypoint to the GPS coordinates
- The backend should generate the route from the exact edited GPS points.
I would also like to note that we should save a copy of the original GPS coordinates and send them to the backend so that they can be saved on the expense in the future when that is built out. Saving the original will allow users to both trim and un-trim the route, which will be a nice feature to have.
Issue Owner
Current Issue Owner: @GCyganek
Problem
The parent issue to this one broadly covers GPS route editing Add stop address editing for GPS mileage. This issue is specifically about supporting route editing before an expense is created, and not after. The latter will be handled in the parent issue as it requires saving gps coordinates on expenses.
Solution
Implement GPS route editing during the in app creation flow and ensure the expense is saved as edited by the backend.
This comment contains an explanation of the plan for how this should be implemented, which is roughly as follows:
I would also like to note that we should save a copy of the original GPS coordinates and send them to the backend so that they can be saved on the expense in the future when that is built out. Saving the original will allow users to both trim and un-trim the route, which will be a nice feature to have.
Issue Owner
Current Issue Owner: @GCyganek