Why do you need markers for the route? The whole point of removing them was to fix the problem you're talking about.
These markers are necessary to check parameters at some points of the route on the map, like speed, battary, .. etc without the need to search in a very long table (which also by the way may cause performance issues). Paging can be added to this report table to avoid performance issues.
I think that something else can be done if we don't display all markers to avoid performance problems, like adding a click listener on the map when a click occured then the nearest point can be selected on the route by searching in DB with (Lat & Lng of the clicked pointon map) from DB, then adding a marker on the route and its paramters will be displayed in the state block to the left.
I like the idea of searching for closest point. Feel free to send a pull request.
Unfortunately, I don't use Github. Could you add it by yourself?
Unfortunately I have too many other things to work on.
Hello!
When displaying route report with "display markers" option checked, with even one device at specific zoom level map becomes unresponsive on different browsers.
I think that, the high amount of data produced by even one device when generating routes report for periods such as two or three days can make any browser unresponsive.
Can the implementation of markers clustering reduce the load on browser? if yes then how this can be implemented? is it a big effort?