Jump to content
Sign in to follow this  
Chris Pawley

Upcoming AIRAC - 1811

Recommended Posts

Chris Pawley

Hello

We are already within the next 28 day sprint to add as many new features, updates and bug fixes to the UK Sector File. I'm using the standard workflow of the previous few releases:

Timeline: (AIRAC +28 means the AIRAC change is 28 days from this moment in our timeline)

✔️AIRAC +28 I will take care of downloading the AIRAC change documents to our local google drive folder (for correct linking in issues) (It is done, located here)

✔️AIRAC +28 -> AIRAC +22 - we take some time to scan through changes proposed from AIP - make issues in Github tagged to 1811 Milestone and ensure that nothing gets missed and linked to the documents from the first step.

[Behind the scenes, I will identify all the other tasks generated by this AIRAC change (non-sector file related) and create a working list of these for me and other members to work on.]

✔️AIRAC +22 -> AIRAC +10 - The Sector File team (you!) complete outstanding issues

✔️AIRAC +8 -> AIRAC +6 - I'll build a DEV version of sector file generated and shared for testing of big or complex changes (and provide the link  here)

[Behind the scenes, the controller pack is also updated in this time]

✔️Approx AIRAC +4 Development Freeze - after this time I like to start packaging things for download.


✔️Approx AIRAC +2 Release versions of SCT/ESE etc. build and double checked

 

✔️Approx AIRAC +1 Forum Posts Updated, Download links Updated, Euroscope's Automated Download Tool Updated

 

As we go through these stages, I'll update this post to show what we're all working on right now.

As ever, if you want to contribute, please do! Find our repo at www.github.com/vatsim-uk/uk-sector-file (especially checkout the contribution guide) and our slack channel #ops_uk_sectorfile

If you have questions, find me on Slack or in the Helpdesk.

 

Chris.

Edited by Chris Pawley

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

  • Similar Content

    • Harry Sugden
      By Harry Sugden
      The Sector File <- Download Link
      You can also use the auto-download feature of EuroScope to obtain the latest version.
      Found a bug while using the new sector file? That’s anything from an auto-handoff that doesn’t work, to a missing position, to a misbehaving agreement… Use the EuroScope department of the helpdesk!
      Alternate ownerships for observing/mentoring
      It's possible for mentors to get the correct sector ownerships without needing to select a primary frequency. Just go to Other settings...Sector ownership setup, click 'select all' and select 'Mentoring TWR/APP' from the list. For mentoring on LON_*_CTR (or SCO_CTR) you will need to select the relevant 'Observing LON_*_CTR' option instead to specify which sector(s) you are interested in.
      The LON_*_CTR can also be used for observing purposes rather than mentoring, but this requires a quick edit of the UK.ese file to tell Euroscope what your log-in callsign for observing will be. (E.g. HS_OBS.) Open UK.ese in Notepad or another text editor and the line to edit is at the top and clearly indicated. There's also an 'Observing London FIR' option that will give you ownership of every sector in the FIR, regardless of who else is online.
      Adjacent airports shown when using the General Setting 'Set active APT by owned sectors'
      There is now an option to choose which departure airports to show, by means of a special runway 00 at '000A Show adjacent departure airports' in the Runway Selector dialogue. This mainly affects London and Scottish Control sectors.
      Option 1, with a selected runway 00 on the right hand side (under DEP or ARR, or both, doesn't matter): the departure list will show departures from all airports within the sector, or immediately adjacent to it.
      Option 2, with no runway 00 selected: the departure list will show departures only from airports for which you have top-down responsibility for TWR services. That is, only when nobody else is covering it. This is the mode of operation found in previous versions of the sector file.
      Contributing to the Project
      Repository
      Contributing Guide
    • Chris Pawley
      By Chris Pawley
      Hello
       
      We are already within the next 28 day sprint to add as many new features, updates and bug fixes to the UK Sector File. I'm using the standard workflow of the previous few releases:
      Timeline (AIRAC +28 means the AIRAC change is 28 days from this moment in our timeline)
      AIRAC +28 I will take care of downloading the AIRAC change documents to our local google drive folder (for correct linking in issues) (It is done, located here)
      AIRAC +28 -> AIRAC +22 - we take some time to scan through changes proposed from AIP - make issues in Github tagged to 1808 Milestone and ensure that nothing gets missed and linked to the documents from the first step.
      [Behind the scenes, I will identify all the other tasks generated by this AIRAC change (non-sector file related) and create a working list of these for me and other members to work on.]
      AIRAC +22 -> AIRAC +10 - The Sector File team (you!) complete outstanding issues
      AIRAC +8 -> AIRAC +6 - I'll build a DEV version of sector file generated and shared for testing of big or complex changes (and provide the link here)
      [Behind the scenes, the controller pack is also updated in this time]
      Approx AIRAC +4 Development Freeze - after this time I like to start packaging things for download.

      Approx AIRAC +2 Release versions of SCT/ESE etc. build and double checked
       
      Approx AIRAC +1 Forum Posts Updated, Download links Updated, Euroscope's Automated Download Tool Updated
       
      As we go through these stages, I'll update this post to show what we're all working on right now.

      As ever, if you want to contribute, please do! Find our repo at www.github.com/vatsim-uk/uk-sector-file and our slack channel #ops_uk_sectorfile
      If you have questions, find me on Slack or in the Helpdesk.
       
      Chris.
    • Chris Pawley
      By Chris Pawley
      Hello
       
      Today I am kicking off the next 28 day sprint to add as many new features, updates and bug fixes to the UK Sector File. I'm using the standard workflow of the previous few releases:
       
      Timeline (AIRAC +28 means the AIRAC change is 28 days from this moment in our timeline)
      AIRAC +28 I will take care of downloading the AIRAC change documents to our local google drive folder (for correct linking in issues) (It is done, located in 4 documents,  one, two, three and four)
      AIRAC +28 -> AIRAC +22 - we take some time to scan through changes proposed from AIP - make issues in Github tagged to 1804 Milestone and ensure that nothing gets missed and linked to the documents from the first step.
      [Behind the scenes, I will identify all the other tasks generated by this AIRAC change (non-sector file related) and create a working list of these for me and other members to work on.]
      AIRAC +22 -> AIRAC +10 - The Sector File team (you!) complete outstanding issues
      AIRAC +8 -> AIRAC +6 - I'll build a DEV version of sector file generated and shared for testing of big or complex changes (and provide the link here)
      [Behind the scenes, the controller pack is also updated in this time]
      Approx AIRAC +4 Development Freeze - after this time I like to start packaging things for download.

      Approx AIRAC +2 Release versions of SCT/ESE etc. build and double checked
       
      Approx AIRAC +1 Forum Posts Updated, Download links Updated, Euroscope's Automated Download Tool Updated
       
      As we go through these stages, I'll update this post to show what we're all working on right now.

      As ever, if you want to contribute, please do! Find our repo at www.github.com/vatsim-uk/uk-sector-file and our slack channel #ops_uk_sectorfile
      If you have questions, find me on Slack or in the Helpdesk.
       
      Chris.
    • George Peppard
      By George Peppard
      Hi,
      I spent this morning working on an alternative SMR for Exeter (EGTE) - my internet was out so it was a good way to kill time 

      Feedback is most welcome.
      George
       
    • George Peppard
      By George Peppard
      I have edited the UK.ese file to include taxiway markings (so I don't need to refer to Navigraph constantly) but they don't seem to appear under "Free Text".
      Here is what I added:
      ;EGKK Gatwick Taxiway labels N051.09.05.617:W000.10.44.543:EGKK Taxiway Labels:08R N051.08.50.549:W000.12.33.307:EGKK Taxiway Labels:08L N051.09.07.806:W000.10.12.142:EGKK Taxiway Labels:AS N051.09.09.580:W000.10.12.536:EGKK Taxiway Labels:AN N051.09.07.268:W000.10.32.227:EGKK Taxiway Labels:AN N051.08.58.156:W000.12.01.297:EGKK Taxiway Labels:J N051.09.03.629:W000.11.21.194:EGKK Taxiway Labels:J N051.09.10.516:W000.10.33.787:EGKK Taxiway Labels:J N051.09.15.349:W000.10.10.671:EGKK Taxiway Labels:J N051.09.18.016:W000.10.39.747:EGKK Taxiway Labels:K N051.09.24.085:W000.10.04.391:EGKK Taxiway Labels:K N051.09.26.878:W000.10.13.345:EGKK Taxiway Labels:KA N051.09.25.936:W000.10.41.399:EGKK Taxiway Labels:L N051.09.22.385:W000.11.09.326:EGKK Taxiway Labels:L N051.09.34.380:W000.10.11.068:EGKK Taxiway Labels:L N051.09.15.349:W000.10.10.671:EGKK Taxiway Labels:M N051.09.18.340:W000.10.21.931:EGKK Taxiway Labels:N N051.09.16.942:W000.10.24.661:EGKK Taxiway Labels:NA N051.09.23.867:W000.10.29.309:EGKK Taxiway Labels:P N051.09.32.639:W000.10.50.603:EGKK Taxiway Labels:Q N051.09.27.498:W000.10.52.184:EGKK Taxiway Labels:QB N051.09.35.517:W000.10.57.048:EGKK Taxiway Labels:R N051.09.21.203:W000.10.57.432:EGKK Taxiway Labels:R N051.09.13.291:W000.10.57.612:EGKK Taxiway Labels:R N051.09.14.798:W000.11.16.170:EGKK Taxiway Labels:S N051.09.10.439:W000.11.47.682:EGKK Taxiway Labels:U N051.09.12.287:W000.10.13.818:EGKK Taxiway Labels:Z However, these do not appear in EuroScope.
      Any help is appreciated
      Thanks,
      George
×
×
  • Create New...