Mapy.cz
Nástroje pro vývojáře
Is there a limit of saving trips in one folder?
Frank Koblischek
včera 17:16
Hello, I am just redrawing, recording and saving my old bicycle trips which I have done in the past decades (before I was using mapy.cz) in one folder. Now I have recorded far more than 200 routes and over 60.000 km. Unfortunately when I open the folder with the big world map it opens very slowly and sometimes I cannot move it anymore. Is this because there is limit of saving space on mapy's server or is it rather a problem of little work space of my desktop pc or due to slow internet?
Thanks for your advice.
Thanks for your advice.
Jan Buriánek
včera 20:17
There is essentially no limit to the number of tracks in folders. The main issue is your PC’s performance. The internet speed has almost no impact on this.
When you open a folder, all the tracks in it are rendered on the screen. The track data is fetched over the internet in a simplified format (coordinates only for 2D rendering), so the data size is smaller compared to GPX files. Additionally, the data is downloaded only once each time you open the folder, which is not a big issue - you just wait for a moment.
The problem arises with the JavaScript that processes and renders all the tracks onto the map. It has to redraw all the tracks every time the map is moved. That is the biggest bottleneck. In your case, the number of track points (coordinates) likely reaches millions, which takes time, even on a decent computer.
The number of CPU cores won’t help, as JavaScript in browsers runs on a single thread.
A powerful graphics card won't help either, as it isn't used to render the track on the map. Instead, it uses 2D Canvas rendering, which is calculated entirely by a single CPU thread.
The only solution is to split the tracks into several folders, for example, by year.
When you open a folder, all the tracks in it are rendered on the screen. The track data is fetched over the internet in a simplified format (coordinates only for 2D rendering), so the data size is smaller compared to GPX files. Additionally, the data is downloaded only once each time you open the folder, which is not a big issue - you just wait for a moment.
The problem arises with the JavaScript that processes and renders all the tracks onto the map. It has to redraw all the tracks every time the map is moved. That is the biggest bottleneck. In your case, the number of track points (coordinates) likely reaches millions, which takes time, even on a decent computer.
The number of CPU cores won’t help, as JavaScript in browsers runs on a single thread.
A powerful graphics card won't help either, as it isn't used to render the track on the map. Instead, it uses 2D Canvas rendering, which is calculated entirely by a single CPU thread.
The only solution is to split the tracks into several folders, for example, by year.
