Winds aloft injection -- just an idea ...

[Hardy Heinlin]

Good morning,

on the Instructor weather pages we have the option to copy & paste an entire METAR text of an external source directly into the edit field of a local weather zone in PSX. The parameters inside the simulation will then slowly change to the injected data.

I'm thinking of a similar copy & paste feature for aloft wind & OAT data. Of course, there are public NOAA services where huge GRIB files can be downloaded. But every download means additional stress to the servers, and every partial GRIB data extraction requires CPU power. In our scenario, however, we just want our simulation to agree with our flight plan data. That's all. So why building a huge additional resource when the resource already exists in our flight plan in human readable form?

There are various flight plan programs, like PSX.Net.Dispatch, or PFPX etc.

The user may mark the weather related text parts in the flight plan, and copy & paste it into a special edit field in PSX. PSX will then parse the text and process the data. The parser just needs to detect what flight plan format has been pasted.

So my question is: Could someone post a sample of a copied & pasted text block where wind & OAT at a route waypoint is indicated, and which flight plan program has generated this text?

By the way, copy & paste in PSX also works with the mouse: Just drag any marked text into an edit field in PSX, or vice versa from PSX off to an external program.


Regards,

|-|ardy

[G-CIVA]

Hardy,

PFPX has the capability to reproduce many different real world OFP formats ... as a long time beta tester of the software I am going to give you the three examples of wind data output here - I do not know if this will cause you issues but 'forewarned is forearmed' as they say.

I hope this helps.

Format One:



Format Two:



Format Three:

[Hardy Heinlin]

Thanks, Steve.

The NOAA data is public domain, so I don't think there can be any issues. Also, I won't implement any formats; I just want to provide a paste edit field like any other text editor does.


Cheers,

|-|ardy


Edit: Steve, does "copy & paste" work with these texts? I need the plain text, not the screenshot. The forum software provides "code" tags for ASCII formatting.

[cagarini]

Steve,

just generated   on PFPX as well and the OFP shows, for a cruise FL 380:

Code Select Expand

WIND INFORMATION - OBS 25/JUL 00:00
--------------------------------------------------------------------------------
(CLIMB)             OGERO               (DESCENT)         
FL370  256/076 -49  FL420  262/073 -56  FL370  268/072 -49 
FL300  256/038 -36  FL400  261/078 -54  FL300  267/029 -37 
FL220  249/018 -17  FL380  261/078 -50  FL220  264/019 -17 
FL150  247/011  -1  FL360  260/070 -47  FL150  251/012  -2 
7000  305/001 +13  FL340  260/060 -43   7000  189/007 +15

How can I generate the other formats ?


Edit HH: Quote in code format

[brian747]

Good morning, Hardy,

I use PFPX for flight planning, and recall looking into this question a few years ago. IIRC (possibly) I found that the default format for a PFPX flight plan gives you only the variation from ISA — for example M05 (minus) or P05 (plus). I have therefore been using a different template, that I think I downloaded from somewhere or other on the 'net.

But my point is that since the PFPX flight plan format is configurable by means of user-adjustable templates, I would imagine that it should also be possible to come up with a format specifically to suit the needs of PSX, if required. The new format could then simplify the required copy and paste operation, once you have established the data fields you wish to be filled.

(There is a whole separate manual for PFPX template formatting, which is downloadable from http://forum.aerosoft.com/applications/core/interface/file/attachment.php?id=97834).

Cheers,

Brian

[Hardy Heinlin]

Thanks, jcomm. How is this format called? Does it have a name?

Thanks, Brian, for the tips!


Cheers,

|-|ardy

[G-CIVA]

But my point is that since the PFPX flight plan format is configurable by means of user-adjustable templates, I would imagine that it should also be possible to come up with a format specifically to suit the needs of PSX, if required. The new format could then simplify the required copy and paste operation, once you have established the data fields you wish to be filled.

Brian,

Without sounding churlish .... this would render the hundreds of hours (literally) that others - some of whom are regular contributors to this forum (including me) have spent building relationships of trust with professionals in the aviation industry in order to access the very sensitive subject of real world flight operational data, once that is established we have & still are then able to reproduce operational flight plan templates for 'simmers' to use with programmes like PFPX in order to make their experience evern more realistic.

But lets just bin that idea shall we?

Hardy,

I am just opening up my PFPX computer ... I will have the PFPX syntax for you shortly.

[cagarini]

How is this format called? Does it have a name?

|-|ardy

This is just a copy/paste of the "WIND INFORMATION" section from a PFPX OFP for an LPPT-LEMD flight.
Further info is available in the Flightplan, at the various waypoints in the form "ISA WND/SPD", like:

Code Select Expand

--------------------------------------------------------------------------------
AWY      WAYPOINT   MT    ALT MSA FREQ    TAS  LEG  FUEL REM / USED   LEG   ACC
-FIR     NAME                 ISA WND/SPD  GS  REM  POSITION          ETO / ATO
--------------------------------------------------------------------------------
         LPPT/35          374 031                       19.5 /   0.5           
         LISBON                                338  N3845.9 W00907.9 ...../.....

IDBI2N   PT412     063   *CLB 031                9      17.8 /   2.4   04  00.04
                              P14 298/004      329  N3849.9 W00858.8 ...../.....



[G-CIVA]

Hardy,

Close PFPX down.

Create a new .txt file on your desktop & save it as TEXT.txt

Inside it paste the following information contained inside but not inclusive of the dashed lines:

-----------------------------------

<&WindDataBlock_Begin>
<&WindData[0]:65>
<&WindDataBlock_End>

WindData[0]

<&WindData[0]:65>

WindData[1]

<&WindData[1]:65>

WindData[2]

<&WindData[2]:65>

WindData[3]

<&WindData[3]:65>

-----------------------------------

Save this file & then cut & paste it into the root folder of your PFPX installation as follows:

C:\Users\Public\Documents\PFPX Data\FlightplanTemplates

You can then re  boot PFPX & once you have 'planned' a flight & arrived at the results page you can select the TEST option from the Flight Plan (OFP) box & it will show you the various outputs.

The output altitudes are very much 'driven' by the user entered altitudes manually entered during the actual 'data entry' part of the process or alternatively they are automatically calculated by PFPX using a combination of the aircraft performance file & the manually entered payload, alternate details, fuel policy & EROPS policy if one is utilised.

I have asked the developer for a 'default' wind data block output as used in real life buy a commercial flight planning source (Brian take note)  but I have not yet heard back from the developer.

[cavaricooper]

Hardy-

As this topic is finally being discussed I wanted to interject that for me it is important that PSX NOT INJECT FROM A STATIC SOURCE. By that I mean that the difference between PFPX's PREDICTED winds aloft/Wx and the ACTUAL winds aloft/Wx are important (to me).

It is more realistic (for me) to have the "snapshot" that PFPX generates, and then watch the Wx/winds as the populate IN REAL TIME FROM REAL TIME METAR DATA. THAT IS KEY- REAL WINDS AND TEMPS ALOFT so that PFPX data is the beginning and RW evolution follows as the hours tick away.

The DIFFERENCES, some small, some NOT SO SMALL; add in no small amount to the experience of Real Flight Simulation.

One thought- no more.

Best- C

[Bastien]

Hi Hardy,

Please find an another exemple from Simbrief flight plan in LIDO format

Code Select Expand


--------------------------------------------------------------------
WIND INFORMATION
----------------
CLIMB T O C WKE30 YOROI
350 357/031 -40 330 338/027 -34 330 322/028 -34 330 322/028 -34
310 352/024 -29 310 329/023 -29 310 313/026 -29 310 313/026 -29
200 348/023 -06 290 322/022 -25 290 306/025 -24 290 306/025 -24
150 358/023 +03 270 318/022 -20 270 303/026 -20 270 303/026 -20
100 350/011 +11 250 314/023 -15 250 300/027 -15 250 300/027 -15
KABTO DASSY WKE LUMIN
330 322/028 -34 330 322/028 -34 330 322/028 -34 330 308/032 -34
310 313/026 -29 310 313/026 -29 310 313/026 -29 310 300/030 -29
290 306/025 -24 290 306/025 -24 290 306/025 -24 290 295/030 -24
270 303/026 -20 270 303/026 -20 270 303/026 -20 270 292/030 -20
250 300/027 -15 250 300/027 -15 250 300/027 -15 250 290/030 -15
LIKON DITOR ULMIK SOKMU
330 293/038 -34 330 289/046 -35 330 279/056 -35 330 276/067 -35
310 290/035 -29 310 285/041 -30 310 275/052 -30 310 273/062 -30
290 288/034 -25 290 282/038 -25 290 272/048 -25 290 270/058 -25
270 287/033 -20 270 280/037 -20 270 272/044 -20 270 266/054 -21
250 285/032 -16 250 279/036 -16 250 271/040 -16 250 262/050 -16


Thanks
Bastien

[G-CIVA]

Hardy,

In light of the fact that there are variations in format could the solution be to opt for the GRIB download?

To the best of my knowledge the Wind Uplink Data available to many operators is only updated every six hours during the 24hr cycle.

I am therefore visualising one initial download on PSX start up - from which users could initialise their wind data 'uplink' into the FMS taken from the most recent of the PSX automatic downloads - see below:

Then further PSX automatic downloads occur at the 0001z, 0600z, 1200z & 1800z timings (I dont know if this eases the load on severs etc) which the user then could 'uplink' if they require should their flight duration continue into those periods.

Just a thought.

This way you can pick your format ... perhaps like this one in use by a large flight plan provider today ....

Regardless of flight profile flown this information is always produced for all ofps in the following format:



I wonder if the raw GRIB data can be extrapolated to create something like it?

[Hardy Heinlin]

Hardy,

Close PFPX down.

I don't have PFPX.

I'm just looking for text snippets of various flight plan formats to train my parser. No GRIB, no binary, no hacking ...


Bastien, thank you. That's the stuff that I mean :-)

Carl, a little randomization might be possible.

[Hardy Heinlin]

Hardy,

In light of the fact that there are variations in format could the solution be to opt for the GRIB download?

No, I'm sorry. See initial post.

[G-CIVA]

Hardy,

Okay apologies, I must have misunderstood ...

Here are the three PFPX formats ......

Code Select Expand


(CLIMB)                NICHO                  NOSHO             
FL310  161/021 -45     FL360  121/017 -52     FL360  045/019 -50
FL250  148/016 -31     FL340  126/020 -52     FL340  056/019 -51
FL190  145/015 -18     FL320  127/019 -48     FL320  056/019 -47
12000  147/013  -5     FL300  128/018 -43     FL300  056/019 -42
6000  139/011  +5     FL280  125/018 -39     FL280  059/019 -38

NANZA                  NOLTI                  NULUK             
FL360  010/038 -49     FL360  359/061 -48     FL360  345/049 -48
FL340  014/036 -50     FL340  001/060 -48     FL340  346/050 -46
FL320  013/038 -46     FL320  001/052 -45     FL320  347/046 -42
FL300  013/039 -42     FL300  002/043 -41     FL300  348/042 -37
FL280  014/033 -37     FL280  003/040 -36     FL280  348/038 -33

NATES                  NIKLL                  NIPPI             
FL370  314/032 -53     FL370  256/027 -53     FL400  307/037 -54
FL350  311/027 -47     FL350  250/026 -47     FL380  309/038 -51
FL330  305/022 -42     FL330  245/025 -41     FL360  305/036 -47
FL310  290/018 -37     FL310  242/025 -36     FL340  300/034 -42
FL290  279/017 -33     FL290  241/025 -31     FL320  289/031 -37

NOGAL                  NUBDA                  ALICE             
FL400  359/030 -54     FL400  047/042 -54     FL400  041/049 -54
FL380  002/029 -50     FL380  049/044 -50     FL380  043/049 -49
FL360  004/028 -45     FL360  049/043 -45     FL360  043/047 -44
FL340  007/028 -39     FL340  049/042 -39     FL340  044/045 -38
FL320  000/020 -34     FL320  050/037 -34     FL320  041/042 -34

HPE                    GTC                    NESKO             
FL400  032/050 -54     FL400  028/048 -54     FL400  029/036 -54
FL380  032/049 -49     FL380  027/047 -49     FL380  027/036 -49
FL360  032/046 -44     FL360  026/044 -44     FL360  026/036 -43
FL340  032/043 -38     FL340  025/040 -38     FL340  025/036 -38
FL320  030/040 -33     FL320  025/038 -33     FL320  025/037 -33

SAMON                  SAPRA                  (DESCENT)         
FL400  047/023 -54     FL400  111/017 -54     FL350  157/020 -41
FL380  046/023 -49     FL380  113/016 -49     FL280  170/013 -23
FL360  044/025 -44     FL360  114/016 -44     FL210  190/010  -7
FL340  041/027 -38     FL340  114/015 -39     14000  204/010  +5
FL320  036/029 -33     FL320  110/013 -34      7000  223/012 +17

----------------------------------------------------------------------------

              24000    30000    34000    36000    38000    41000
PANC        17018M27 18021M42 18025M52 18022M53 18020M54 18014M52
TED         17018M27 18021M42 18025M52 18022M53 18020M54 18014M52
NODLE       15015M28 16020M43 17022M52 16020M52 16017M53 16012M51
NICHO       12016M29 13018M43 13020M52 12017M52 11014M51 10010M50
NOSHO       06019M28 06019M42 06019M51 05019M50 04020M49 03021M49
NEONN       04017M28 04019M43 03019M50 03022M49 02025M49 02028M48
NANZA       02020M28 01039M42 01036M50 01038M49 01040M48 01040M48
NOLTI       00033M26 00043M41 00060M48 36061M48 36061M47 36053M49
NAYLD       36031M25 36045M39 35060M47 35059M48 35058M48 35050M50
NULUK       35027M24 35042M37 35050M46 35049M48 34048M49 34041M51
NANDY       33028M22 35034M36 34033M46 34030M49 33028M51 33022M54
NATES       27017M21 28017M35 31025M45 31030M50 31035M55 31023M57
NIKLL       24024M20 24025M33 25025M44 25026M50 26028M56 26023M58
NYMPH       24030M20 23031M33 23032M44 24033M50 24033M56 24028M58
NUZAN       22046M20 22054M34 22065M44 22066M50 23067M55 24050M57
NRKEY       24039M20 27031M33 30034M43 30035M47 30036M52 29035M55
NIPPI       25037M19 28029M33 30034M42 31036M47 31038M51 30036M55
NOGAL       29011M15 34013M29 01028M39 00028M45 00029M50 36030M56
NUBDA       04018M14 05031M28 05042M39 05043M45 05044M50 04042M56
NANNO       05022M15 05034M28 05045M39 05046M45 05046M50 05045M56
ALICE       03032M14 04039M28 04045M38 04047M44 04049M49 04049M56
LIDEL       03034M14 04039M28 04045M38 04047M44 04049M49 04050M56
MQE         03035M14 03040M28 04045M38 04048M44 04050M49 03051M56
HPE         03034M14 03038M28 03043M38 03046M44 03049M49 03051M56
HANKA       03034M14 03037M28 03043M38 03046M44 03049M49 03051M56
MAMRO       03033M14 03037M28 03042M38 03045M44 03048M49 03050M56
GTC         03031M15 02034M28 03040M38 03044M44 03047M49 03049M56
NESKO       02028M14 03038M27 03036M38 03036M43 03036M49 03036M56
SAMON       03026M13 03030M28 04027M38 04025M44 05023M49 05023M57
DRIPS       03024M13 04027M28 05025M38 05023M44 06021M49 06021M56
SAPRA       08009M13 10012M28 11015M39 11016M44 11016M49 11017M56
BULGA       10007M13 13014M28 14015M39 13016M44 13017M49 12018M56
KPO         12006M13 13014M28 14015M39 14017M44 13018M49 13018M56
ELAPI       15006M13 15013M28 15014M39 15016M44 15018M49 14017M56
CUN         18007M13 16012M28 16014M39 16017M44 15019M49 15017M56
BIGOB       18008M13 16013M28 16014M39 16017M44 16019M49 15017M56
BASEM       19009M13 17013M28 16014M39 16017M44 16020M49 16017M56
GUKDO       19010M13 18015M28 17016M39 17018M44 17021M49 16017M56
KAKSO       20011M13 18017M28 17017M39 17019M44 17021M49 16017M56
SI857       20012M13 19018M28 17018M39 17020M44 17022M49 17017M56
SI921       20012M13 19019M28 17018M39 17020M44 17022M49 17018M56
SI922       20012M13 18019M28 17018M39 17020M44 17022M49 17018M56
SI923       20012M13 18018M28 17018M39 17020M44 17022M49 16018M56
SI924       20012M13 18018M28 17018M39 17020M44 17022M49 16018M56
SI925       19012M13 18019M28 17018M39 17020M44 17023M49 16018M56
PULUN       20013M13 18021M28 17021M39 17023M44 17024M49 17019M56
RKSI        20015M13 19023M28 18024M39 18024M44 18025M49 17019M56

N6110.3W14959.9 PANC   102     1      P16
N6110.0W14957.6 TED    278    59      P11  17020  18021  18023  18025
N6117.0W15200.0 NODLE  271   116      M24  16018  16020  16021  17022
N6115.0W15600.0 NICHO  271   203  320 M48  13018  13018  13019  13020
N6107.0W16300.0 NOSHO  254    61  320 M47  06019  06019  06019  06019
N6049.3W16500.6 NEONN  252    95  320 M47  04018  04019  04019  03019
N6018.4W16802.5 NANZA  250   125  320 M46  01033  01039  01038  01036
N5932.7W17154.1 NOLTI  248    77  320 M45  00040  00043  00052  00060
N5903.1W17412.4 NAYLD  247    99  320 M43  36041  36045  36053  35060
N5822.9W17706.1 NULUK  245   201  320 M42  35038  35042  35046  35050
                                            290    310    330    350   
N5649.9E17720.8 NANDY  240   214      M41  35033  35034  34033  34032
N5456.0E17158.4 NATES  235   120  330 M42  28017  29018  30022  31027
N5344.7E16913.9 NIKLL  241    41  330 M41  24025  24025  25025  25026
N5324.5E16814.3 NYMPH  240   198  330 M41  23031  23031  23032  24032
                                            300    320    340    360   
N5139.4E16338.6 NUZAN  236   151      M42  22054  22060  22065  22066
                                            320    340    360    380   
N5012.4E16022.6 NRKEY  234    50      M43  28032  30034  30035  30036
N4942.6E15920.8 NIPPI  233   330  360 M47  29031  30034  31036  31038
N4613.0E15300.2 NOGAL  228   331  360 M45  00020  01028  00028  00029
N4223.4E14728.5 NUBDA  224    40  360 M45  05037  05042  05043  05044
N4154.9E14651.5 NANNO  246   163  360 M45  05040  05045  05046  05046
N4044.7E14335.8 ALICE  236    21  360 M44  04042  04045  04047  04049
N4032.5E14312.6 LIDEL  235    71  360 M44  04043  04045  04047  04049
N3951.9E14157.0 MQE    236    46  360 M44  04043  04045  04048  04050
N3926.0E14108.0 HPE    227    36  360 M44  03040  03043  03046  03049
N3901.0E14033.6 HANKA  228    17  360 M44  03040  03043  03046  03049
N3850.0E14017.8 MAMRO  227    77  360 M44  03040  03042  03045  03048
N3757.4E13906.8 GTC    246   125  360 M44  03038  03040  03044  03047
N3705.9E13643.2 NESKO  245   119  360 M43  03037  03036  03036  03036
N3614.5E13430.1 SAMON  238    38  360 M44  04029  04027  04025  05023
N3554.5E13350.1 DRIPS  269   152  360 M44  04026  05025  05023  06021
N3549.4E13043.4 SAPRA  279    44  360 M44  11013  11015  11016  11016
N3556.1E12949.3 BULGA  278    17  360 M44  13015  14015  13016  13017
N3558.6E12928.4 KPO    306    37  360 M44  14014  14015  14017  13018
N3620.2E12850.8 ELAPI  305    31  360 M44  15013  15014  15016  15018
DESC                                   FL   90     180    310    360
WIND                                       21010  20007  18016  17019


Hardy plse disregard this next piece.

Just in case anybody is even thinking of suggesting the use of another 'popular' simulator developers .WX file that PFPX can produce - here is the .WX that was parsed from the EXACT same wind predictions I have posted from the same ofp I used to create the formats above:

Code Select Expand


PANC 132@005(+6) 149@012(+0) 152@016(-5) 152@020(-15) 160@020(-28)
165@020(-42) 160@024(-52) 161@016(-54) 171@008(-50) 160@004(-50)
TED 132@005(+6) 149@012(+0) 152@016(-5) 153@020(-15) 159@020(-28)
166@020(-42) 160@024(-52) 162@016(-54) 171@008(-50) 160@004(-50)
NODLE 145@013(+6) 148@014(+1) 147@014(-5) 140@013(-15) 145@014(-28)
154@020(-43) 144@023(-52) 141@014(-53) 142@007(-50) 117@004(-50)
NICHO 072@005(+6) 100@008(+1) 114@011(-5) 129@016(-15) 121@019(-29)
118@022(-43) 106@025(-51) 106@014(-51) 073@007(-49) 057@007(-49)
NOSHO 065@012(+6) 079@014(+1) 074@015(-5) 051@015(-15) 064@017(-28)
063@018(-43) 066@016(-51) 034@020(-49) 025@022(-48) 025@020(-49)
NEONN 065@010(+5) 080@012(+1) 070@013(-5) 042@015(-15) 041@016(-28)
045@016(-43) 037@017(-51) 021@026(-48) 018@029(-48) 020@024(-49)
NANZA 076@006(+5) 069@007(+1) 050@008(-4) 024@013(-14) 020@018(-28)
016@037(-42) 015@040(-50) 009@040(-47) 009@040(-48) 013@031(-50)
NOLTI 010@004(+5) 015@009(+2) 013@012(-3) 009@018(-13) 007@031(-26)
004@037(-41) 001@047(-49) 359@058(-46) 001@046(-50) 006@034(-52)
NAYLD 342@005(+5) 003@008(+2) 005@014(-2) 004@026(-12) 002@035(-25)
358@043(-40) 358@062(-46) 355@058(-47) 356@043(-51) 002@031(-53)
NULUK 316@003(+6) 350@009(+4) 352@015(-0) 352@025(-11) 351@033(-24)
351@048(-38) 353@054(-46) 348@047(-48) 349@035(-53) 356@026(-54)
NANDY 307@015(+10) 318@020(+6) 322@022(+1) 328@025(-9) 339@028(-23)
354@028(-37) 353@030(-45) 347@025(-51) 341@016(-55) 358@012(-57)
NATES 277@023(+12) 280@022(+8) 281@022(+2) 282@024(-9) 289@019(-21)
306@020(-35) 315@026(-45) 318@031(-56) 305@008(-57) 334@002(-58)
NIKLL 238@024(+12) 239@025(+8) 238@025(+2) 236@024(-9) 251@019(-20)
262@016(-34) 284@021(-44) 282@026(-57) 264@014(-59) 251@005(-59)
NYMPH 230@027(+12) 229@028(+8) 228@028(+2) 226@027(-9) 239@023(-20)
247@019(-33) 266@023(-44) 267@027(-57) 249@016(-59) 239@008(-59)
NUZAN 211@044(+11) 216@047(+6) 219@047(+1) 221@045(-8) 216@045(-20)
212@050(-34) 211@058(-44) 225@060(-57) 232@032(-58) 239@015(-58)
NRKEY 213@046(+11) 217@047(+7) 220@048(+2) 223@048(-8) 223@046(-20)
222@039(-34) 234@037(-44) 243@042(-55) 261@029(-56) 273@017(-58)
NIPPI 214@045(+11) 217@047(+7) 220@047(+2) 223@045(-8) 226@042(-20)
231@036(-34) 242@036(-43) 258@035(-53) 277@029(-56) 287@018(-58)
NOGAL 199@026(+12) 203@027(+10) 207@024(+5) 219@016(-4) 294@013(-16)
359@019(-30) 005@040(-39) 003@037(-52) 351@033(-60) 352@023(-62)
NUBDA 025@008(+13) 031@008(+11) 041@009(+7) 056@011(-3) 035@024(-15)
046@038(-28) 040@051(-39) 039@052(-52) 030@045(-61) 035@032(-64)
NANNO 025@010(+14) 028@011(+11) 037@012(+7) 053@014(-3) 038@029(-15)
049@042(-28) 041@054(-39) 041@055(-53) 032@049(-60) 037@034(-64)
ALICE 037@011(+15) 036@016(+11) 039@020(+6) 044@028(-4) 028@039(-14)
033@045(-28) 038@051(-38) 036@055(-52) 026@056(-62) 035@039(-65)
LIDEL 038@011(+15) 036@017(+11) 038@022(+6) 042@030(-4) 027@040(-14)
031@045(-28) 036@051(-38) 034@055(-52) 026@056(-62) 035@040(-65)
MQE 041@011(+16) 037@017(+11) 037@024(+6) 037@034(-4) 025@040(-14)
027@044(-28) 032@049(-38) 030@055(-52) 025@057(-62) 035@040(-65)
HPE 044@008(+16) 035@015(+11) 034@021(+6) 035@034(-4) 024@037(-14)
021@040(-28) 028@045(-38) 028@052(-52) 024@055(-62) 035@040(-65)
HANKA 048@007(+16) 034@014(+11) 033@021(+6) 034@034(-4) 023@036(-14)
019@038(-27) 025@044(-38) 027@051(-52) 024@054(-63) 036@040(-66)
MAMRO 047@007(+16) 033@013(+11) 032@021(+6) 033@033(-4) 022@035(-14)
018@037(-27) 024@043(-38) 026@050(-51) 024@053(-63) 036@040(-66)
GTC 023@005(+17) 025@013(+12) 027@020(+7) 029@031(-3) 021@031(-14)
016@032(-27) 020@039(-38) 025@046(-51) 026@049(-63) 037@038(-66)
NESKO 036@004(+18) 022@011(+13) 025@016(+7) 031@024(-3) 020@028(-14)
024@037(-27) 023@032(-38) 028@032(-51) 031@033(-63) 044@030(-67)
SAMON 270@001(+19) 032@006(+14) 038@011(+8) 043@018(-2) 026@024(-13)
036@029(-28) 048@024(-38) 060@020(-51) 054@022(-64) 057@025(-68)
DRIPS 280@003(+19) 038@004(+14) 047@009(+9) 049@017(-2) 032@022(-12)
041@026(-28) 059@024(-38) 077@020(-51) 064@021(-64) 062@024(-68)
SAPRA 296@002(+19) 309@002(+14) 038@002(+9) 074@009(-2) 098@009(-13)
117@014(-28) 113@020(-39) 118@020(-51) 110@019(-63) 086@021(-68)
BULGA 253@002(+18) 258@003(+14) 221@001(+8) 096@007(-1) 116@007(-13)
135@018(-28) 131@020(-39) 128@021(-51) 122@019(-63) 094@019(-67)
KPO 229@003(+18) 241@004(+14) 210@002(+9) 109@006(-1) 126@007(-13)
133@017(-28) 133@019(-39) 132@022(-51) 124@018(-63) 096@018(-67)
ELAPI 235@006(+18) 229@007(+14) 210@005(+9) 151@006(-1) 157@008(-13)
134@014(-28) 138@016(-39) 143@022(-51) 132@016(-62) 100@015(-67)
CUN 235@009(+18) 226@009(+14) 211@008(+9) 176@008(-1) 176@009(-13)
142@012(-28) 139@015(-39) 153@022(-51) 137@013(-62) 101@013(-67)
BIGOB 234@010(+18) 225@009(+14) 212@009(+9) 181@008(-1) 180@010(-13)
146@012(-28) 140@015(-39) 155@022(-51) 138@013(-62) 102@012(-67)
BASEM 231@011(+18) 224@010(+14) 212@009(+9) 187@009(-1) 184@011(-13)
151@012(-28) 143@015(-39) 159@023(-51) 140@012(-62) 102@011(-67)
GUKDO 229@012(+18) 222@011(+14) 212@010(+9) 191@010(-1) 188@012(-13)
162@013(-28) 152@016(-39) 164@024(-51) 142@011(-62) 101@010(-67)
KAKSO 227@011(+18) 220@011(+14) 212@011(+9) 193@010(-1) 190@012(-13)
168@014(-28) 158@017(-39) 168@024(-51) 144@011(-62) 101@010(-67)
SI857 224@011(+18) 219@012(+14) 212@011(+9) 196@010(-1) 192@013(-13)
175@016(-28) 164@018(-39) 172@024(-51) 147@010(-62) 102@009(-67)
SI921 221@011(+18) 218@012(+14) 212@011(+9) 196@010(-1) 192@013(-13)
175@016(-28) 165@018(-39) 172@025(-51) 146@010(-62) 102@009(-67)
SI922 221@011(+18) 218@012(+14) 211@011(+9) 194@010(-1) 191@013(-13)
174@016(-28) 163@018(-39) 170@025(-51) 144@011(-62) 101@009(-67)
SI923 221@011(+18) 217@012(+14) 211@011(+9) 193@010(-1) 190@013(-13)
172@016(-28) 162@018(-39) 169@025(-51) 143@011(-62) 100@009(-66)
SI924 220@011(+18) 217@012(+14) 210@011(+9) 191@010(-1) 189@013(-13)
171@016(-28) 160@018(-39) 168@025(-51) 141@011(-62) 100@009(-67)
SI925 219@011(+18) 216@012(+14) 209@012(+9) 190@010(-1) 187@013(-13)
170@016(-28) 159@018(-39) 167@025(-51) 139@011(-62) 099@010(-66)
PULUN 218@011(+18) 216@012(+14) 210@012(+9) 195@011(-1) 190@014(-13)
175@019(-28) 169@022(-39) 173@026(-51) 144@011(-62) 101@009(-67)
RKSI 217@010(+18) 217@011(+14) 212@011(+9) 200@012(-1) 195@015(-13)
181@022(-28) 178@026(-39) 180@028(-51) 153@011(-62) 105@008(-66)


If you take the time to check through the parsed data you will find that the .WX file DOES NOT contain forecasted wind data for the flight plan .... therefore it is not of any use .... an issue I have been telling people about until I have gone blue in the face for years ... literally.

[cavaricooper]

Carl, a little randomization might be possible.

HH- That would add immensely to the realism. 

I would only follow that up with- in the same way as we strive for FMC functionality realism, aerodynamic rotation realism and the myriad other ways PSX strives to "exactly" mimic real 744 behavior- we must move in the direction of REAL Wx aloft, for THAT IS WHAT THE BENCHMARK IS.

If for now, the RANDOMIZED PFPX output is the best possible, then it is what it is.  My hope, is that in the same way that you have pursued even the tiniest nuance of 744 behavior, attempting to achieve perfection, you will eventually arrive at a solution for REAL Wx ALOFT.

At the moment, JP's (WIDE PSX) and Gary & Mark's (PSX.NET) are two solutions that allow for the working of injected Wx- thereby allowing for the intrinsic variability of FORECAST vs. REAL.  They work brilliantly!

If PSX were to evolve in this area- an already superlative simulation would only grow in accuracy and appeal. After all, whilst departure and approach simulation is a big part of the professional simulation market, as tech evolves, simulating enroute electronic comms and procedurals will become more important to cost effectively simulate for professional training departments.

My additional 2 cents

Best- C

[cagarini]

While I perfectly understand HH's notes on the subject of not going GRIB, and actually find the kind of approach he mentioned an easier but effective one, specially if the loaded winds / temps are then propagated and merged with PSX's own Global Weather Model data, I would nonetheless leave an "open door" for some 3rd party approach to easily feed this data into PSX.

Say in the future someone builds a standalone even more detailled tool for winds / temps / turb and other Sigmet / Gamet info injection based on a sequence of waypoints and their ETAs or even to fill the whole virtual PSX Globe at given time intervals ( based on GFS or ECMWF Global models...). Any solution and code adaptation that is now going to be written would be even more profitable if a "protocol" was designed that could easily be followed by such applications to communicate with PSX's weather system.

[Hardy Heinlin]

Steve, thank you for the three samples. So now we have the one from Simbrief, and three variants from PFPX. How are these three variants called when you chose them from a menu?

[G-CIVA]

How are these three variants called when you chose them from a menu?

Herin lies the issue Hardy.

You can't.

The format lies within syntax contained within the particular flight plan template you have chosen.  The flightplan template file could have any name ... most are named in after the airline they refer too to keep it simple.

But I think there is an easy solution for your requirement from PFPX anyway.

Am I correct in thinking that all you want the user to do is copy the data into a .txt format or just have the ability to copy the data in order to paste it?

If this is so I can post a screenshot of the solution taken from the PFPX screen.

With regard to Simbrief - speaking as someone who does not use this online tool ARE WE ABSOLUTELY SURE that Sim Brief ONLY produces one Wind Data output format?

Or, like PFPX is a user able to select differing flightplan formats?

I am only asking to prevent Hardy from working toward a direction only to be told something different after some considerable hours of toil & labour.

[Hardy Heinlin]

If there are no names, -- not important -- I just call them Huey, Dewey, and Louie.

Not so complicated, Steve. No files. Just an optional "copy & paste" action into a new edit field on Instructor > Situation > Weather > Planet.

Maybe it will be finished in December this year. I've got a lot of things on my todo list ...


|-|


Are those three formats the most popular ones?