NATS UK & Ireland Standard Routes

[Serge75 24]

I have converted the NATS UK & Ireland Standard Route Document for use with PFPX. I initially did this for my UK based VA however thought others may find it useful so I have uploaded it here:

http://forum.aerosoft.com/index.php?/files/file/2965-nats-uk-ireland-standard-routes/

I will endeavor to update this regularly as NATS release an updated SRD monthly however I can't guarantee it will be every month. Also, although I have attempted to look for and fix errors it is quite difficult as there are over 6000 routes. If you find any please let me know and I will correct as soon as possible.

Regards,

Serge

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the recently released November SRD.

http://forum.aerosoft.com/index.php?/files/file/2965-nats-uk-ireland-standard-routes/

As mentioned in the previous post, I have attempted to look for and fix errors however it is quite difficult as there are over 6000 routes. If you find any please let me know and I will correct as soon as possible.

Regards,

Serge

[jpgmultimodal 61]

Thank you Serge. very useful.

Regards,

JP

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the recently released December SRD.

http://forum.aerosof...tandard-routes/

As mentioned previously, please let me know if you find any errors and I will correct as soon as possible.

Regards,

Serge

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the recently released January 2015 SRD.

http://forum.aerosof...tandard-routes/

Please let me know if you find any errors and I will correct as soon as possible.

Regards,

Serge

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the recently released March 2015 SRD. I skipped the February update as there were no significant changes.

http://forum.aerosof...tandard-routes/

Please let me know if you find any errors and I will correct them as soon as possible.

Regards,

Serge

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the recently released April 2015 SRD.

http://forum.aerosof...tandard-routes/

Please let me know if you find any errors and I will correct them as soon as possible.

Regards,

Serge

[srcooke 422]

Thanks Serge

[Flying Penguin 17]

Hi All,

 

Serge, hope you don't mind me posting this here.... If you want I'll move this to a separate thread, but I thought I'd keep all the SRD info in one place

 

I've uploaded a tool for creating route files from the base SRD file:

 

http://forum.aerosoft.com/index.php?/files/file/3536-pfpx-nats-uk-ireland-standard-route-document-parser/

I only saw this thread as I was nearly done, so I figured I would complete it anyway, in case, god forbid, Serge goes on holiday

 

It's an Excel/VBA tool which doesn't require Acrobat or similar installed, but relies on conversion using a PDF conversion website (full instructions in the file). It was built in Excel 2013, but will most likely work in 2007 onward.

 

I've checked it against the last SRD, and I'll keep an eye on it through the next few releases and update as necessary, but as of now it seems stable, though of course, let me know if anyone spots things amiss.

 

Cheers,

 

Jamie

[Serge75 24]

G'day Jamie,

No worries from me posting in this thread. It's a great tool you have provided and it looks like you have put a lot of work into this. It's always nice to have more options available and like you say I might not always be around.

I also use excel to convert the routes however I'm not that smart when it comes to programming so it's a semi-automatic process. Although I've mashed together some VBA scripts to do most of the work I still need to do a quick manual tidy up before the final parse. It sure would be nice if NATS provided a csv file or something similar to make life easy.

I do have some observations though so I hope you don't mind me commenting. To give it a test run I ran your tool on the latest April SRD (I used the website you recommend for the conversion) and it does a nice job with little user input required. It's a much quicker process than my spreadsheet! Once I complete the output it finishes with 6079 routes (I used the low output level). I then import the txt file into PFPX and it finishes with 6077 routes imported. The 2 routes it loses are routes that contain EGXJ as this airport doesn't exist in the PFPX airport database so no problem there. As a comparison, my April SRD routes file contains 6144 routes so I looked into this and noticed some routes dropped off (eg. there are 3 EGAC - EGBB routes but only 2 made it in) and also some new routes were created which don't exist in the SRD (eg. EGBK - EGSH).

In the first example, here is what's on the SRDDOC tab of your spreadsheet:

EGAC
MC 145 DCT DUFFY L15 PEPOD L603 IOM L10 WAL CHASE1C EGBB
EGAC 145 245 DCT DUFFY L15 AMPIT CHASE2D EGBB
EGAC 245 275 DCT DUFFY L15 MAKUX DCT SOSIM UL15 AMPIT CHASE2D EGBB

It looks like because the first route has EGAC on a separate line the route gets omitted.

In the second example, there was nothing odd on the SRDDOC tab but here is the route output:

EGBKEGSH01;EGBK DCT DTY M605 WOD UL612 XAMAB EGBP MC 245 DCT MALBY L9 CPT DCT BPK DCT BKY DCT EGSH;FLMin:245  FLMax:660  SRD:02 APR 15

It looks like it has combined the EGBK - XAMAB route with the EGBP - EGSH route. Due to this the EGBP - EGSH route is then omitted.

There are a few other examples with issues similar to these however overall it's a small percentage. I'm not sure if this is something you can look at fixing as I know it's difficult to cover all the possible issues that come up with the conversion process but please let me know if I can help with anything.

Thanks again for putting the effort in to create this tool for the community.

Cheers,

Serge

[Flying Penguin 17]

G'day Jamie,

No worries from me posting in this thread. It's a great tool you have provided and it looks like you have put a lot of work into this. It's always nice to have more options available and like you say I might not always be around.

I also use excel to convert the routes however I'm not that smart when it comes to programming so it's a semi-automatic process. Although I've mashed together some VBA scripts to do most of the work I still need to do a quick manual tidy up before the final parse. It sure would be nice if NATS provided a csv file or something similar to make life easy.

I do have some observations though so I hope you don't mind me commenting. To give it a test run I ran your tool on the latest April SRD (I used the website you recommend for the conversion) and it does a nice job with little user input required. It's a much quicker process than my spreadsheet! Once I complete the output it finishes with 6079 routes (I used the low output level). I then import the txt file into PFPX and it finishes with 6077 routes imported. The 2 routes it loses are routes that contain EGXJ as this airport doesn't exist in the PFPX airport database so no problem there. As a comparison, my April SRD routes file contains 6144 routes so I looked into this and noticed some routes dropped off (eg. there are 3 EGAC - EGBB routes but only 2 made it in) and also some new routes were created which don't exist in the SRD (eg. EGBK - EGSH).

In the first example, here is what's on the SRDDOC tab of your spreadsheet:

EGAC
MC 145 DCT DUFFY L15 PEPOD L603 IOM L10 WAL CHASE1C EGBB
EGAC 145 245 DCT DUFFY L15 AMPIT CHASE2D EGBB
EGAC 245 275 DCT DUFFY L15 MAKUX DCT SOSIM UL15 AMPIT CHASE2D EGBB

It looks like because the first route has EGAC on a separate line the route gets omitted.

In the second example, there was nothing odd on the SRDDOC tab but here is the route output:

EGBKEGSH01;EGBK DCT DTY M605 WOD UL612 XAMAB EGBP MC 245 DCT MALBY L9 CPT DCT BPK DCT BKY DCT EGSH;FLMin:245  FLMax:660  SRD:02 APR 15

It looks like it has combined the EGBK - XAMAB route with the EGBP - EGSH route. Due to this the EGBP - EGSH route is then omitted.

There are a few other examples with issues similar to these however overall it's a small percentage. I'm not sure if this is something you can look at fixing as I know it's difficult to cover all the possible issues that come up with the conversion process but please let me know if I can help with anything.

Thanks again for putting the effort in to create this tool for the community.

Cheers,

Serge

Glad you like

I'll take a look at the oddities you noticed. I aim to fix everything that gets spotted, so if you (or anyone) spot anything, just shout! The problem (as I'm sure you found) is snow blindness with the sheer quantity of data!

[Flying Penguin 17]

Serge,

I've just had a tweak and cross checked it against your April SRD file and eliminated the majority of the discrepancies.

v1.2 now gets every airport to airport route, as far as I'm able to tell at this point. It is about 5% over as it can't tell between an endpoint on a new line or a start point on a new line, so there are still a few routes that don't exist, but it's a big improvement in accuracy, at least on "Low" output setting. I have an idea to fix this, but it involves learning all the possible exit points as it goes, which is perfectly achievable but not a trivial enough a task for me to complete tonight, at least without giving myself caffeine poisoning tomorrow!

As an aside, you might want to check the following route pairs:

EGKK-EGMC

EGMC-EGAC

EGNX-EGAC

EGPD-EGNS

In each case I get one less route than you, and in each case a manual check with the SRD seems to agree with my count unless I'm missing something?

Hopefully I can get some time this week to add the learning element to it and that should sort most of the other problems, so hopefully 1.3 will be within a route or two of bang on

Cheers,

Jamie

[Serge75 24]

Thanks for getting on to this so quickly Jamie. I gave it another run today with your latest version 1.2. From my end it appears to fix the issues I reported yesterday however there may be new issues. I am finding lots of routes that depart/arrive at the same airport. Below are some examples.

EGAAEGAA01;EGAA GILTI UL179 LAM UL10 BPK UN601 LESTA UP6 RODOL UM65 TENSO UL603 REMSI DCT MASOP DCT NELBO P6 BEL EGAA;FLMin:245  FLMax:660  Notes: 182 -  259  SRD:02 APR 15
EGAAEGAA02;EGAA PEMAK UT7 LND UN18 PEMOB UM17 VATRY DCT DUB N34 BEL EGAA;FLMin:245  FLMax:660  Notes: 236  SRD:02 APR 15
EGAAEGAA03;EGAA SKESO UN862 BHD DCT STU UM17 VATRY DCT DUB DCT  NEVRI N34 BEL EGAA;FLMin:285  FLMax:660  Notes: 331  SRD:02 APR 15
EGAAEGAA04;EGAA SOVAT L613 SANDY N601 LESTA P6 RODOL L28 PENIL L10  IOM DCT NELBO P6 BEL EGAA;FLMin:195  FLMax:245  SRD:02 APR 15

There are a few more examples of these type of routes from various airports. I wonder if this is a result of a fix for one of the issues I reported yesterday?

Also, regarding the route pairs you identified for me to check, I can't seem to find any issues (using v1.2 of your spreadsheet). For EGKK-EGMC my output, your output and the SRD all have a single route.

EGKKEGMC01;EGKK DCT DET DCT ALKIN DCT EGMC;  FLMin:45  FLMax:55 / NATS SRD 2 Apr 2015

EGKKEGMC01;EGKK DCT DET DCT ALKIN DCT EGMC;FLMin:45  FLMax:55  SRD:02 APR 15

EGKK 45 55 DCT DET DCT ALKIN DCT EGMC

For EGMC-EGAC we all have 4 routes. For EGNX-EGAC we all have 3 routes. For EGPD-EGNS we all have 1 route. I'm not sure why we are seeing different things here. I'm pretty sure I'm following the steps correctly. If it will help I can send you the input and output files I am using with your spreadsheet for you to verify.

Thanks again for the effort you're putting into this. I know it can be frustrating at times.

Cheers,

Serge

[Flying Penguin 17]

Hi Serge,

The first error is the 5% over i mentioned and come from the second half of the document which are routes from non airfield waypoints. They will stop when I've implemented the waypoint learning. The issue is that I can't yet reliably differentiate between a waypoint and a SID in certain specific cases where a route is split over two lines.

I'll double check the extra routes query when I've sorted the waypoint learning issue. Hopefully then there will be less noise.

Thanks again for your help. A second pair of eyes is always useful.

Cheers,

Jamie

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the latest SRD - July 2015.

Please let me know if you find any errors and I will correct them as soon as possible.

Regards,

Serge

[Flying Penguin 17]

It looks like the parser got lost in the forum upgrade, and as I had a couple of PMs asking where the parser went, I've re-uploaded it.  This is the same version as before (though I really should get back to doing the improvements I mentioned! ) 

[Driver170 6]

Does this assign your cruising ALT also or cap it?

[srcooke 422]

No but the available FL range is displayed in the associated route remarks, just the same as annotating your own routes, so you can set the cap yourself.

[Driver170 6]

Ah i see. I was always getting capped FL240 from EGSS to EGPH. EGPH to EGKK and vice versa

[bumblebee 2]

Hi. I have been trying to download the route parser, but the zip file that downloads is empty. Can anyone please provide a working link? Thanks.

[bumblebee 2]

Its working fine now.

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the latest SRD - October 2015.

Please let me know if you find any errors and I will correct them as soon as possible.

Regards,

Serge

[ScottecLEMD 14]

It looks like the parser got lost in the forum upgrade, and as I had a couple of PMs asking where the parser went, I've re-uploaded it.  This is the same version as before (though I really should get back to doing the improvements I mentioned! ) 

Hi James (AKA Flying Penguin)

I have been using your excel parser file for ages now but for the current airac (15-11) for the SRDDOC I have noticed an anomally for flights from EGAA - after running the parser and output, then import to PFPX I notice that there are a few flights that show EGAA-EGAA??  It´s no big deal as I can delete them but wondered if you had noticed similar.

Thanks and appreciate the file.

Regards

[Serge75 24]

I have updated the NATS UK & Ireland Standard Routes for PFPX from the latest SRD - May 2016. Sorry for the big delay between releases and thanks to Ken for the heads up about the latest SRD.

 

Please let me know if you find any errors and I will correct them as soon as possible.

 

Regards,

Serge

 

[srcooke 422]

Once again many thanks Serge, the file is very much appreciated.