-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature request] option "Mass line filter (cluster) function": show number of close positions as single continuous line, calculate and show average velocity; course vector prediction #192
Comments
[Updated 20170613] Additional wish from the ADFC: "Könnt Ihr aus Tracks mittlere Geschwindigkeiten auslesen?" |
I think, that the new https://github.com/criticalmaps/criticalsnake is a partial step towards an implementation of my proposal. Let me add that calculation and display of a predicted course vector (e. g. 15 min, or 30 min) would be a great additional feature for everyone willing to join Critical Mass enroute. |
Course vector prediction
|
My wish is a "mass line filter" function (user option, activated by default), which shows a certain number (programmable, default 16) of close (perhaps as user option: programmable minimum distance) positions as a single continuous line with a separate colour instead of showing the distinct positions.
Different clusters in the map can, for the moment use the same colour, later perhaps, different colours.
Here is a "nice colours" random generator: https://randomcolor.llllll.li/ .
One's own position, regardless whether it is part of the "mass line" or not, should always be shown as it is now.
An additional velocity filter could be perhaps useful to only cluster positions senders within a certain range of velocities.
[Updated 20170613]
Additional wish from the ADFC: "Könnt Ihr aus Tracks mittlere Geschwindigkeiten auslesen?"
Would be nice to have a kind of (min. max, average) velocity information derived from all these clustered positions, which form the clustered line.
The text was updated successfully, but these errors were encountered: