Step 2

[JordanBurrows-zz]

In this journey - https://staging-i6.i6clouds.com/dp/#/telemetry/session/view/572223dfc0d25d2b798b4567/  (my journey home yesterday) there are the following issues

1. The times for each journey are wierd - the first one says I started at 1553 (which was when I left so that is correct) and finished at 1605 (i was still driving then but may have stopped at a junction for a bit). I think this is related to offline caching of the captured data on the tablet since when i lost wifi i was offline all the way home. There is then a big jump in time until I got home (1824) and connected to my wifi network but this was only 12 mins long (1826) which is the journey timeout setting. All the data is good for the whole journey (https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/5722474bc0d25d05358b4567/) once you press into it is really interesting and has the whole journey (OBD and GPS but no acceleration) but this is timestamped as starting when it got connection back not the timestamps in the cached data.
2. This page (https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/5722474bc0d25d05358b4567/) takes ages and ages to load because there are so many data points to plot on the map. We need a spinner as the minimum and to find a way of optimising the load time.
3. There are lots of journeys on this one - anything after 1820 (all whilst the tablet was sitting logged in, with signal on my desk) - May be related to wandering position bug in Android app - but the righthand panel does not scroll if they extend off the bottom of the screen.
4. Extended data view for the 1824 to 1836 journey (https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/extended/5722474bc0d25d05358b4567/?page=4) is odd as there is no data on the pages for position until page 4 but there is OBD data on page 1. I think we need to look at how we paginate this data - users will expect them to line up. This is probably the unification bug we have already for position and motion data.
5. I love the data and graphs here - https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/extended/5722474bc0d25d05358b4567/?page=1 you can even see when I stopped for a break and some fuel. The last few pages are all zeros - we need to do some checking so that we do not fill journey\'s up with data when it is all the same (0 because we are stopped with the engine off but still connected to the OBD). Only update when there is a change from zero etc.
6. On the same page there is a graphing issue which is messy -
7. 
8. Fuel level - https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/extended/5722474bc0d25d05358b4567/?page=1 need to check the data since after my stop I filled the car completely and it is only showing 40% level.
9. RPM - there is no point plotting negative RPM - https://staging-i6.i6clouds.com/dp/#/telemetry/journey/view/extended/5722474bc0d25d05358b4567/?page=1

These all need solving since at LHR they will be running from 0500-2359 nominally so we\'ll have loads of journeys to manage.

[JordanBurrows-zz]

➤ Eryk Warren commented:

Les mois de l'année sont:

• janvier
• février
• mars
• avril
• mai
• juin

[JordanBurrows-zz]

➤ Eryk Warren commented:

• juillet
  • août
  • septembre

[JordanBurrows-zz]

➤ Eryk Warren commented:

• octobre
  • novembre
  • décembre

[JordanBurrows-zz]

➤ Eryk Warren commented:

Repeat