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

Vertical angle in procedures #803

Closed
albar965 opened this issue Oct 17, 2021 · 5 comments
Closed

Vertical angle in procedures #803

albar965 opened this issue Oct 17, 2021 · 5 comments

Comments

@albar965
Copy link
Owner

albar965 commented Oct 17, 2021

Extract vertical angle for procedure legs.

For X-Plane, Navigraph and MSFS.

Add rate of descent for angles, glidepaths and glideslopes in progress.

Definition/Description: The “Vertical Angle” field defines the
vertical navigation path prescribed for the procedure. The
vertical angle should cause the aircraft to fly at the last coded
altitude and then descend on the angle, projected back from the
fix and altitude code for that fix at which the angle is coded.
Vertical Angle information is provided only for descending
vertical navigation. The angle is preceded by a “–” (minus
sign) to indicate the descending flight.

@Gulliver54
Copy link

Gulliver54 commented Oct 19, 2021

Hi Alex,
Good idea.
If you have calculated the vertical descend angle can you also show the corresponding vertical decent rate?
Pe; 3° descend: 180kias is 900ft/min. 120kias is 600ft/min. descend rate.
I admit this is not 100% correct because the calculated speed for descend rate should be "Groundspeed". Perhaps you can use the groundspeed that's calculated and shown with "user aircraft"
So, maybe that is something to bare in mind.

@albar965
Copy link
Owner Author

Can do and display this in the progress tab. Groundspeed is always available this is no issue.
But first #768 has to be implemented since the progress tab is getting too crowded.

albar965 added a commit to albar965/atools that referenced this issue Oct 22, 2021
albar965 added a commit to albar965/atools that referenced this issue Oct 22, 2021
albar965 added a commit that referenced this issue Oct 22, 2021
…re search.

Added tooltips for procedure search header.
#803
albar965 added a commit that referenced this issue Oct 22, 2021
…ent flight path angle to elevation profile map and tooltip.

Vertical profile calculation now considers vertical path requirements.
Showing vertical path and required descent rate in aircraft progress in descent and approach phase.
Optimizations using QStringBuilder for all information and progress displays.
#803
@albar965
Copy link
Owner Author

Spot the changes. 🙂
This needs an updated Navigraph database (not yet available) or X-Plane. Once released it will work with MSFS and the others too, of course.
grafik

@Gulliver54
Copy link

Hi Alex,
Great work, you even calculated "vertical speed" taking in account the deviation.
Question, does this calculation also works with "Created approach"? The required angle is available there too.

Is it possible to cram these 2 values (deviation and vertical speed) inside the little window "Flight plan Elevation..." also?
Required "angel 3" occupies 2 rows now. One row could be deleted imo.
Gradus

@albar965
Copy link
Owner Author

Great work, you even calculated "vertical speed" taking in account the deviation.
Question, does this calculation also works with "Created approach"? The required angle is available there too.

Thanks. The deviation was there before but angle and sink rate were missing. This works with all approaches since the value is calculated for the plan and shown throughout the whole descent phase. The yellow angles are required by a procedure (like an altitude restriction) and prescribe the flight path. Other angles are calculated and optional.

Is it possible to cram these 2 values (deviation and vertical speed) inside the little window "Flight plan Elevation..." also?
Required "angel 3" occupies 2 rows now. One row could be deleted imo.

Into the tooltip or as an aircraft label? Maybe both. The tooltip in the shot is also filled with debug information ([ ... ]) making it bigger than the release version. Will see.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants