InterpolateHeatmapLayer VS location-history-visualizer

framebufferFactor: number between 0 and 1. In short, if the framebuffer factor is around 0, the computation will be faster but less accurate and the opposite if it's around 1. The default value is 0.3. Take a look at the readme file of the GitHub project if you want to know what exactly this parameter is.

https://locationhistoryvisualizer.com/heatmap/ similar thing, is free

If you have an android phone (and thus lots of Google location data) you can use this instead: https://locationhistoryvisualizer.com/heatmap/ It's open source and somewhat customizable but more importantly it's a heatmap so you can see where you've been AND the relative frequency of you going there.

https://locationhistoryvisualizer.com/heatmap/ is one. But the problem is, unless you are actively tracking, it will be just location dots, not a full GPS track. Sometimes it just doen't pick up on locations either.

Using this: https://locationhistoryvisualizer.com/heatmap/

If you have an android phone, you can do the same here: https://locationhistoryvisualizer.com/heatmap/

Does anybody have any ideas how to solve this issue? Maybe there is a way to create a heatmap in a tool like "Google My Maps" by manually exporting the data from the more detailed day view? I would also be open to other workarounds. Location History Visualizer seems to be based only on the inaccurate data from the month/year view.