!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content
MorSe Dude

How to create an 'Oceanic' Section in PFPX

Recommended Posts

Hello, 

 

Does anyone know how to provide a sort of 'Oceanic' section in a FP?

So something like this:


ROUTING: 
ROUTE ID: KJFKEDDF
KJFK/04R KJFK DCT MERIT DCT HFD J42 BOS J575 TUSKY N117B SCOTS
N199A NICSO DCT 48N050W 50N040W 51N030W 52N020W DCT LIMRI
DCT XETBO DCT CRK DCT EVRIN L607 KONAN UL607 SPI T180
UNOKO UNOK2G EDDF/25L
 

but then only the Oceanic part:

 

OCEANIC ROUTING: 
NICSO DCT 48N050W 50N040W 51N030W 52N020W DCT LIMRI Mach .85 FL350

 

preferably with the time when reaching the entry point.

grazie mille,

 

27MD (Serge) 
 

Share this post


Link to post
Share on other sites

For the waypoints:

 

<&NavLog_Begin><&OceanicFix_Begin><&NextFixIdent><&OceanicFix_End><&NavLog_End>

 

returns:

 

PIKIL   5720N   5830N   5840N   5650N   JANJO   MOFAT

 

Not sure if the single speed and oceanic altitude can be extracted.

 

 

Share this post


Link to post
Share on other sites

Super, that's exactly what i want!
speed and altitude would be nice, but this is already the biggest improvent, thx @srcooke!

 

just out of curiosity, is there a way to make the appearance of a caption (like 'OCEANIC ROUTE') only appear when there are oceanic fixes?

 

grtz,
Serge

Share this post


Link to post
Share on other sites

Try:

 

    <&OceanicSection_Begin>Oceanic Route:
    <&NavLog_Begin><&OceanicFix_Begin><&NextFixIdent><&OceanicFix_End><&NavLog_End><&OceanicSection_End>

 

returning:

 

    OCEANIC ROUTE:
    PIKIL   5620N   5630N   5540N   5350N   RIKAL   TOPPS   ENE

Share this post


Link to post
Share on other sites

Still not quite right Serge as it captures waypoints after oceanic exit.

 

This is closer:

 

    <&OceanicSection_Begin>Oceanic Route:
    <&NavLog_Begin><&OceanicFix_Begin><&FixIdent[0]> <&OceanicFix_End><&NavLog_End><&OceanicSection_End>

Share this post


Link to post
Share on other sites

Yeah, that's already a lot closer, great work already!
but both still give a weird difference.

if you take the route EBBR-CYYZ, eg, then you get by using both pieces of code:

 

OCEANIC ROUTE: 5220N   5230N   5340N   5350N   NEEKO   

OCEANIC ROUTE:  LIMRI 5220N 5230N 5340N 5350N

 

while the correct route should be: LIMRI 5220N 5230N 5340N 5350N NEEKO

 

so the actual goal looks a bit like a combo of the two.

but this is already very nice to have!

 

grtz,
Serge 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...