Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more FPN parsing #29

Merged
merged 9 commits into from
Feb 23, 2024
Merged

Conversation

makrsmark
Copy link
Collaborator

  • adding procedures
  • adding company route
  • making routes in H1_M1BPOS and H1_POS consistent

- adding procedures
- adding company route
- making routes in H1_M1BPOS and H1_POS consistent
expect(decodeResult.formatted.items[5].label).toBe('Message Checksum');
expect(decodeResult.formatted.items[5].value).toBe('0xc8b5');
expect(decodeResult.formatted.items[3].label).toBe('Company Route');
expect(decodeResult.formatted.items[3].value).toBe('EWRDFW01(17L): >> SAAME > J6 > HVQ > Q68 > LITTR >> MEEOW >> FEWWW');
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a little funky, open to suggestions to changes in route_utils.ts

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is fine for now. Once we see how the formatted versions look on Airframes and AcarsHub and/or get other feedback, we can always refine it. I'll keep you posted.

lib/plugins/Label_H1_FPN.test.ts Show resolved Hide resolved
* added test case with comments in errors
* fixed partial message notification
});

// https://app.airframes.io/messages/2372685289
const text = 'FPN/TS140017,021724/RP:DA:EHAM:AA:KMSP..N55064W000477..N55163W001141..ERAKA..N60000W020000..N61000W030000:WS:N61000W030000,370..N61000W040000..N60000W050000..URTAK:WS:URTAK,380..LAKES:WS:LAKES,400..N57000W070000..N54300W080000..N49000W090000..DLH..COLDD:A:BAINY3:AP:ILS30L(30L)/PR4356,344,360,1060,,,13,,,30,,,P50,M40,36090,,3296,292/DTKMSP,30L,172,215117156D';
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this one is a beast - not sure how to approach it. adding it as a reference

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how you added a comment to the URL of the message for further info if we need it later.

Yeah, this is huge.

POS and #M1BPOS messages can have the same information embedded in it. Will update in a future PR
Copy link
Contributor

@kevinelliott kevinelliott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was a BEAST, whoa. A lot going on here. The extraction to utility classes is nice. The FPN and additional H1's looks good, can't wait to dig in there.

});

// https://app.airframes.io/messages/2372685289
const text = 'FPN/TS140017,021724/RP:DA:EHAM:AA:KMSP..N55064W000477..N55163W001141..ERAKA..N60000W020000..N61000W030000:WS:N61000W030000,370..N61000W040000..N60000W050000..URTAK:WS:URTAK,380..LAKES:WS:LAKES,400..N57000W070000..N54300W080000..N49000W090000..DLH..COLDD:A:BAINY3:AP:ILS30L(30L)/PR4356,344,360,1060,,,13,,,30,,,P50,M40,36090,,3296,292/DTKMSP,30L,172,215117156D';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how you added a comment to the URL of the message for further info if we need it later.

Yeah, this is huge.

expect(decodeResult.formatted.items[2].label).toBe('Company Route');
expect(decodeResult.formatted.items[2].value).toBe('PERMEL001');
expect(decodeResult.formatted.items[3].label).toBe('Destination');
expect(decodeResult.formatted.items[3].value).toBe('YMML..MEMUP,S33451E120525.Y53.WENDY'); //TODO - pull out route
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't this item the Destination? It would be an ICAO, right?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it should be just YMML - and then there's the route that's "how to get there"

>> MEMUP(33.451 S, 120.525 E) > Y53 > WENDY)

I'm not sure where to put the route right now because if you look above, there can be more route information - i probably should merge but punted on the hard stuff right now

lib/utils/flight_plan_utils.ts Show resolved Hide resolved
@kevinelliott
Copy link
Contributor

Looking good. Seems like there's a couple of conflicts, but once those are fixed, merge away. Thanks @makrsmark !

@makrsmark
Copy link
Collaborator Author

@kevinelliott - merged master

@makrsmark makrsmark merged commit 0bf8b2a into airframesio:master Feb 23, 2024
1 check passed
@makrsmark makrsmark deleted the h1-fpn-procedures branch February 23, 2024 21:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants