I think I'll just do it with elevation on the third place, to make the design cleaner and more future proof: Code: lat;lon;elevation;distance;enabled;name;alert If elevation is empty, modRana would count the distance in 2D, if it is filled in, it would count the distance in 3D.
lat;lon;elevation;distance;enabled;name;alert
Good idea ! You are right that the labels are not really usable at low zoomlevels and this handles the issue quite nicely. Another possible, but more complicated future solution, would be to group nearby markers and just show a single marker with the label displaying the number of markers in the group. Clicking the label would show a list of the grouped marker or something similar.
Well, why not. It would be good to add and "icon" column to the database so that POIs can have both an icon and a full description, but this should work in the meantime.
Oh, I've finally got it ! Like this, you know how accessible the points are from your position, with you current speed ? Nice idea !
Unfortunately yes, modRana just draws all points that were designated as visible, even if they are outside of the viewport. Also, I think the most costly is actually not the drawing but the calculations needed to compute the screen coordinates from the geographic ones and the distance, which currently happen every time the screen is redrawn. Therefore, just looking what points should be visible doesn't help as you still have to iterate over all the points and check if they are visible, would not help due to all the unnecessary comparisons and coordinate conversions.
Of course, there is place for optimizations (the basic idea is to somehow reduce the number of points you have to work with at a time), the first one from the top of my head : calculate the bounding box of the current viewport in screen coordinates (I think a bounding box represented by geographic coordinates might not actually be a rectangle) then calculate a "border" bounding box, say 2x times larger check what markers are in the "border" bounding box as long as the viewport bounding box is inside the "border" bounding box, you can ignore markers that are outside once you detect that the viewport bounding box is outside of the "border" bounding box, you recalculate a new "border" bounding box and check what markers are contained within I'm sure there are also other ways how to optimize this.
I don't understand what you mean, can can you clarify ?
I'm using it for quite some time already, without issues. Still, I remember the Saera developer mentioning some issues with the camera UI in CSSU. Anyway, thanks for the changes ! I'll check them out & integrate them to the upstream source code in the coming days.