Closed glynhudson closed 5 years ago
Hi @glynhudson,
Thanks for this rather extensive issue! Always good to see people investigating beforehand. :smiley:
I don't see an obvious reason for this just yet. Please try the following, in this order:
Show location history (line)
is checked - weird stuff happens sometimes :smile:Console
tab in the devtools for warnings or errorsDoh, only Latest Location was checked in Layer Settings. Checking lines/points/heat map all work now. I'm testing on Chrome and it seems to work fine 👍
Although the app does take a long time to load and is unresponsive for 20s or so when I try to view multiple days of data. I guess this is since there is just so many points to load. Maybe in the future the app could choose to only load x number of points when viewing a large dataset over a long period. I would love to be able to view 1yr of data! Thanks a lot for your help.
Although the app does take a long time to load and is unresponsive for 20s or so when I try to view multiple days of data. I guess this is since there is just so many points to load. Maybe in the future the app could choose to only load x number of points when viewing a large dataset over a long period. I would love to be able to view 1yr of data!
Sure, being able to view a large amount of data is a priority. Some things to consider here:
I guess noting this in a modal and asking for user approval if more than x points should be rendered as circles would be a good improvement. For now, just turn off "points" and it should be no problem!
Just wanted to comment on large dataset rendering. I think there are a few ways of dealing with this:
When I select a date time frame using the data pickers the trace data for that time period is not shown.
The data is available as shown on the Recorder web view:
Inspecting the network page I can see that it looks the frontend successfully obtained the data for the requested period but the data was not displayed on the map:
I'm running the latest docker version of the frontend: