Skip to content
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

Draft PR: Live Visualization #11

Merged
merged 6 commits into from
Aug 13, 2023
Merged

Draft PR: Live Visualization #11

merged 6 commits into from
Aug 13, 2023

Conversation

noodnik2
Copy link
Owner

@noodnik2 noodnik2 commented Jul 19, 2023

Live Visualization

Description

Draft PR to capture & review work in progress toward "Live Visualization" functionality (see docs/wishlist).

Planned Phases

  1. Direct support for building tracks by "flight ID" instead of "tail number and cutoff date."
  2. Implement server & endpoint to periodically poll the current position of a given flight (by "flight ID") and return marginal "Live" KML updates based upon interpolation of previous and current positions and speed (similar to how it's done in Pilot Path Recorder.)

Notes

  • Step 2 is a big one and should be broken down further, as it involves the "live" orchestration with the KML targets (which IIRC was tricky to get right in Pilot Path Recorder)

@noodnik2 noodnik2 marked this pull request as ready for review August 13, 2023 22:31
@noodnik2
Copy link
Owner Author

I'm proposing pushing this through even thought it only has "Phase 1" completed, and spinning off a new PR if/when we get to doing the work described in the original Draft PR as "Phase 2."

@noodnik2
Copy link
Owner Author

Before merging, I'd like to try it out - as sort of an "integration test."

I picked some pattern practice that someone did at Paramus Flying Club. Here's the command I used:

$ fviz tracks --tailNumber N6189Q --cutoffTime 2023-08-12T13:30:00-04:00 --verbose \
  --flightCount 1 --saveArtifacts --artifactsDir artifacts --layers camera,path,vector

Watching the "Camera View" was a pretty satisfying experience; however, I wanted it to get closer to the runway during the pattern practice. I looked at the recorded altitudes retuerned by FlightAware and indeed, the lowest it goes is 300', so we can't do any better than that. ;-)

cat artifacts/fvt_N6189Q-1691858479-adhoc-798p.json \
  | jq -c ".positions[] | {altitude: .altitude, timestamp: .timestamp}" | more

So overall, from this (albeit limited) "integration test", I'm approving this merge request.

@noodnik2 noodnik2 merged commit ffdfca8 into main Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant