Can anyone revive AviationWX, PilotWX, or TAF

sdetweil

@FSAHD is the problem just the use of request?
that can be fixed w very little code change

FSAHD

@sdetweil that is what I believe it it, also what the AI helped me deduce.

I attempted to solve that but was unsuccessful. I believe that was the problem with all 3 modules I mentioned.

I tried using npm install request. that didnt work.

Then I attempted to update the code to use axios

sdetweil

@FSAHD OK, let me look at them

sdetweil

@FSAHD well every url changed, and all the data
changed. some has to be calculated (avg airport delay) or that info display deleted.

too much work for me., given my avaliable time

FSAHD

@sdetweil I appreciate you looking into this. ill take some time and see wat I can do!

sdetweil

@FSAHD I got the metar to work, then the faa data is all different not by airport request. and all the variable names have changed too

don’t know if the data is different for display

and the data is xml

FSAHD

@sdetweil I know the airport delay item is last on the wish list.

I can take over and update variables and such. wherever you left off ill be happy to take over!

sdetweil

@FSAHD ok, let me finish the faa data . I was working on it this morning

sdetweil

@FSAHD ok, here is the partially updated MMM-aviationwx

there is a file of the output sent back from the node_helper( this morning) in formatted json (sample-data.txt)

so you can see the field names and values…

I marked in the MMM-aviationwx.js in getDom() where all this needs to be corrected with correct variable names and values…

as an example

      var icao = airport.id;

airport.id is now airport.station_id
“station_id”: “KSFO”,

FSAHD

@sdetweil Thanks again for the help.

I think I have all the variables updated. Im c urrently working on trying to get the dependencies to install on my pi so I can test.

You were a big help and I see where I went wrong in a lot of places when I was trying to build from scratch. It was a lot of simple mistakes lol