Handle routes with no time

[adeebshihadeh]

Since openpilot 0.9.7 removed RTC support, some routes can have no time (e.g. the device just booted up and didn't get a GPS fix during the route).

Since openpilot's uploader guarantees that routes are uploaded in the order they were created, we can still show all routes in the correct sequence using the create_time attribute of the route.

Requirements

• hide the date/time
• show "timeless" routes in the correct order with the rest of routes

[eshaanrathi2]

I would like to work on this. @adeebshihadeh

[incognitojam]

The /v1/devices/:dongleId/routes_segments endpoint we are using has limit and end params we use to seek backwards through the list of routes. I think we need a new endpoint which sorts by create_time on the server side instead of filtering by the "route end time" (I don't know how this is determined for the timeless routes).

[tybo9]

I forked about this project and would like to have some clarification on where to start.

[adeebshihadeh]

The /v1/devices/:dongleId/routes_segments endpoint we are using has limit and end params we use to seek backwards through the list of routes. I think we need a new endpoint which sorts by create_time on the server side instead of filtering by the "route end time" (I don't know how this is determined for the timeless routes).

@sshane can you add this new endpoint and take care of anything else needed on the backend for shipping new connect?

I think we want to add a v1.1 version of this endpoint, then just remove the old one once connect is deprecated. Nothing should use start/end time anymore (unless it's just for UI).

[incognitojam]

probably doesn't need to change to v1.1 as it's not a breaking change