Restore line previews. Find some other kind of marker for bend problems.
Is it possible to make a button/panel to find all curves with radius less then "insert number", as those are the ones that I would adjust for smooth riding in RGT? Thanks in advance.
Involves direction changes v. distance changes across whole track (window calc).
Have radius and angle change sliders. This will allow people to look only for hairpins, say.
Add the radius slider to Bend Problems tab, backwards compatible at small radius. NB, can easily fast-forward "nearly straight" sections.
This should be a neat two-way merge sort of track points based on distance from start.
We have interpolation code in Flythrough (and Curve Former), so it's a doddle.
Applies elevation relative to start elevation, of course.
Option to have "cross-fade" at the end (possibly hundred of metres).
Uses the TP.index here to see if they are adjacent on the route rather than just by chance.
Better, still too many now. Need closer look at Dan's test file.
: All covered by V3.
At least three similar forms of new Track creation.
Don't copy information into ViewContext that doesn't belong there.
Only Flythrough?
Safer & easier to pass through the data needed.
Now I know how to write type signatures that don't require the whole Main.Model!
Switch currentPoint to : Int, avoid stale state worries.
E.g. separate info tabs from edit tabs. Find some themes, or contexts.
Seems easy now we have spatial index, SVG charts, OnHover.
https://package.elm-lang.org/packages/ianmackenzie/elm-3d-camera/latest/
Need a "buildPreview" method on tools so they can construct their data once only.
Currently repeated for each preview style, and (sometimes) in the View (!).
Change Track.spatialIndex to be road-based, so we can re-use for Terrain?
It may remove any "misses" in click detection btw. Note that intersection testing relies on incremental build of its own index! Also last point becomes special case and much ugliness ensues.
Visual Styles options layout not wrapping. Turns out to be Safari!
Investigate derivatives of Vector3d and see if anything useful emerges.
This will be editing "blind". Could be fun. Limiting 1st or 2nd derivatives.
Investigation Use of Canvas.
Happy now with spatial index.
- https://github.com/joakin/elm-canvas
- https://package.elm-lang.org/packages/ianmackenzie/elm-3d-camera/latest/
Profile click detect should not do a linear search.
It's just not necessary. It's stupidly fast anyway.
Timestamps: Is it possible to preserve GPX time stamps? DO THIS Obvs certain edits will largely invalidate, but we could preserve any we read in. 97.4 2021-10-28T07:53:33Z
Try electron for native wrapper. See if multiple windows possible.
Strava segment blend elevation rather than just Paste (optional).
Working offline? (Mongoose server?)
Touch screen.
LIDAR.
Flythrough to respect any azimuth & elevation applied when stationery.
--- Also not doing, as unlikely to be any better than Bezier apprx.
Consider colouring TP by curvature. This may lead to way of identifying (e.g.) sweeping bends, straights, hairpins. That might then lead to more intelligent automated smoothing, specialised by region.
Start by computing "circle of curvature" for each non-end track point. (Trivial with elm-geometry.) Via Visual Options or a new view, visualise these circles (or just current node, so we can see movement).
Is it right or reasonable to assert that the centre of these circles should move continuously, and further that we should limit the rate at which it moves (or accelerates)? This is more general than thinking about track regions. (It's closer to Dan C's idea of using equiangular spirals as the basic construct.)
May require some GA/GP search to find an approximation that is suitably close (by what measure) to the route. But this revives the idea of the user being able to control preferences.
BTW, should consider uphills different to downhills; it's track as function of time, not distance.