Skip to content

West Africa + FSS/CTR Splits for FIMM/FSSS #985

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

Closed
wants to merge 15 commits into from

Conversation

notbxno
Copy link
Contributor

@notbxno notbxno commented May 14, 2025

Description of changes

  • Adds missing sectors which don't fall under the GO* or DG* naming convention (GQQQ, GAAA, DXXX)
  • New definitions for FIMM and FSSS, with original FIR boundaries now designed as Oceanic (FSS takes full FIR, CTR takes defined)
  • Extended GOOO to also cover GLRB and DIII
  • Removed GLRB/DIII off AFRW FSS list since this would be covered by GOOO anyway as a result of the extension

Reason and motivation

  • These positions can't usually be represented accurately or correctly, i.e. Bamako or Nouakchott, since they fall in the Dakar FIR (GO* but don't follow that naming convention), like Lagos Control (DNMM_CTR).
  • Better coverage for CTR/FSS, prevents someone calling about 1000nm out from where they should be calling if in Mauritius or Seychelles
  • GOOO has always covered GLRB and DIII for us, but this was never represented on vatSPY so that adds that fix in aswell.

Approved contributior?

  • I am on the approved contributers list
  • I have sent an request by email to get approved
  • Someone on the approved contributer list will review this request

@notbxno
Copy link
Contributor Author

notbxno commented May 14, 2025

Before the question does get asked, this part is by design. (DXXX/DGAC border at the north)

image

Copy link
Collaborator

@daniluk4000 daniluk4000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

image

image

@Adrian2k
Copy link
Collaborator

GAAA sector is not alligned - here are some examples (but more of the points are not alligned):
image
image
image

Same applies to the DXXX and FIMM - would be great if we can use the excisting FIR boundaries

@daniluk4000
Copy link
Collaborator

I really need to look better on those...

@notbxno
Copy link
Contributor Author

notbxno commented May 15, 2025

Fixed. I don't see any gaps on my end now.

@Adrian2k
Copy link
Collaborator

Thanks - still spotted some misallignments in the following areas:
image

image

@notbxno
Copy link
Contributor Author

notbxno commented May 17, 2025

Long live my eyesight

Copy link
Collaborator

@daniluk4000 daniluk4000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Misaligments, rescheduled for next airac

@notbxno
Copy link
Contributor Author

notbxno commented May 25, 2025

Right, I've just had a look. To me, they all are aligned. The Lome border is flush with the Accra, unless I'm missing something? Same with Bamako

@daniluk4000
Copy link
Collaborator

@Adrian2k current state looks good to me. Misaligments are either gone or very, very minor. Correct me if I'm wrong.

@Adrian2k
Copy link
Collaborator

Adrian2k commented Jun 5, 2025

I am still showing the eastern border of DXXX not being aligned.

Here are just some examples - but from what I have seen so far, every coordinate is not alligned with the excisting border.
image
image
image
image
image

@notbxno
Copy link
Contributor Author

notbxno commented Jun 12, 2025

Right, so I found the issue. It's DNMM and not DXXX. Fixing that border then now

@ziplock1
Copy link
Contributor

ziplock1 commented Jul 4, 2025

@notbxno seems like DNMM is still misalligned...
image
image

@notbxno
Copy link
Contributor Author

notbxno commented Jul 7, 2025

yeah I think i might aswell scrap and redraw again, ouch

Copy link
Collaborator

@daniluk4000 daniluk4000 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Misaligments again

Honestly I would start over and edit inner borders only, or change editing program, etc

@notbxno
Copy link
Contributor Author

notbxno commented Jul 12, 2025

Yeah, I'll restart over. Bigger chance of me finishing a flight in FS2024 than these borders being right

@Adrian2k
Copy link
Collaborator

Will close this then.
For any new PR the following info applies:
A new contributer policy went in effect today - please read the new policy and reapply for contributer status.

@Adrian2k Adrian2k closed this Jul 18, 2025
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.

4 participants