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

IVAO centers coverage #426

Closed
ChickenDipper1 opened this issue Jun 25, 2019 · 4 comments
Assignees
Milestone

Comments

@ChickenDipper1
Copy link

@ChickenDipper1 ChickenDipper1 commented Jun 25, 2019

Would it be possible to add the same indication of coverage of towers, approach, centers that is shown on the: https://webeye.ivao.aero map?

You will see that each one has the exact distance of coverage and a shape for example this image shows OBBB Center as a shape with a specific size of cover, in LittleNavMap this would be a circle, even when checking the boxes under Option>Map Display Online>Use Size.

image

@albar965

This comment has been minimized.

Copy link
Owner

@albar965 albar965 commented Jun 25, 2019

Partially duplicate of #236, especially part:

Allow to assign airspace to online centers by name.

But the new centers will not make it into 2.4. Too much work, sorry.

Have to see if I can get access to the center polygons. Maybe #236 helps a bit.

Alex

@albar965 albar965 self-assigned this Jun 25, 2019
@albar965 albar965 added this to the Release 2.6 milestone Jun 25, 2019
@ChickenDipper1

This comment has been minimized.

Copy link
Author

@ChickenDipper1 ChickenDipper1 commented Jun 25, 2019

Thanks, sorry for partial duplicate.

@albar965

This comment has been minimized.

Copy link
Owner

@albar965 albar965 commented Jun 25, 2019

No prob. I have to see if I can add all the functionality of #236 that at least allows to read the center polygons if available.
Alex

@albar965 albar965 modified the milestones: Release 2.6, Release 2.4 Jul 18, 2019
@albar965

This comment has been minimized.

Copy link
Owner

@albar965 albar965 commented Jul 18, 2019

Covered in #236 . LNM now optionally tries to find boundaries by matching callsign vs. user airspace name and/or filename.
Only need to get ahold of the data now.

@albar965 albar965 closed this Jul 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.