rvspt
commented
7 years ago Sorry for the late reply, have you been able to tackle this? If not, 2 quick pointers:
Rendering depends of the browser. If too many points/info to display, the browser may crash (or eventually your QV desktop as well). Regarding to the sorting, maybe you can force it on the dimension definition (possibly for both Latitude and Longitude). If you get the sorting right, I suspect you might have the strange line behavior corrected as well as a "side-effect".
Hi,
I have just discovered your extension and wanted to use it to visualize captured GPS locations as a route. I have already used QlikMap, but it is somehow limited and I want to evaluate other options of geovisualization.
If I don't limit the row count (there are about 150k records, which are filtered depending on the current dataset), QV crashes after loading the data. If I limit the row count, the map works, but shows some strange lines, which I did not encounter with QlikMap:
The data is sorted by time, so the order should be correct. For drawing lines in QlikMap, I generated two-point coordinates (x,y x,y) and passed this field, but your extension expects seperate lon/lat values. The strange lines may appear due to errors inside my load script, but the loading problem is something more severe.
Do you have an idea what causes this behaviour and did you also experience on-load-crashes - might there be a way to mitigate them?
Best regards