Individual fish trajectories visualization issues

[QuentinMaz]

Hi @danielfdsilva ,

I have been working on the addition of data for the webapp (namely, the Pollock species), and upon testing the application locally, I observed that the individual trajectories are not correctly displayed.

I identified two cases:

1. With short fish tracks: the pdfs are too big. It might be a correct behavior, even though I would say though that maybe there might be a "scaling"/"size" there.
2. For long tags (with the Pollock data, the longest tag includes 440 days), the pdfs are simply not shown. Moreover, each time step takes about 1 second (even though once again no pdf is shown 😅). finally, I get this error [Violation] 'requestAnimationFrame' handler took <N>ms at each time step.

Please find below two screenshots showing the issues mentioned above:

Important notes:

1. Despite @danielfdsilva's support, I have local issues with the visualization of the quarterly data. As such, some of the issues might be bound/caused to my local own case.
2. For it is worth noting, as you can see on the screenshots, the trajectories are quite intertwined... I have little knowledge about how the trajectories and pdfs are rendered but it might be due to this 🤔?

In any case, I am eager to help!

[QuentinMaz]

Quick update about the "local issues" mentioned earlier @danielfdsilva: I confirm that the issue with the visualization of the quarterly regrouped data is due to the Chrome browser. I have installed Firefox and it indeed works!

However, the rendering of the fish trajectories are the same (i.e., curiously "big" pdfs for small tags and no pdf at all for long tags).

[QuentinMaz]

Final note on the issue with the quarterly regrouped data. I added mine and it turned out that:

1. On Firefox, both existing and new data work.
2. On Chrome, only the new data work... (❓)

[danielfdsilva]

Did some digging and have some notes:

• short fish tracks are behaving as expected. The resolution of the grid is the same, but looks bigger because the track covers a very small area. Perhaps a on/off toggle for the layer would be useful.
• For the long fish tracks: It seems that the data on those tracks is hourly, which is not supported by the app. We had agreed that the data would be averaged by day. (cc @yellowcap ). That's why it doesn't show.
• Still have to understand what's going on with the quarterly.

[QuentinMaz]

Thanks a lot for the investigations @danielfdsilva!

I did not know that the data of fish track individuals are expected to be daily-indexed!
I have revised the scripts that produce this data accordingly and I can confirm that once daily-aggregated, the new data is flawlessly rendered by the app 🚀

Should I close the issue or would you like to keep it to deal with the quarterly issue?