-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
adding H1-FPN decoding #27
Conversation
Parses: * Flight Number * Route Status * Departure Airport * Departure Runway * Arrivial Airport * First Waypoint * Message Checksum Does not Parse: * Departure Procedure * Arrival Procedure * Current Route(?) Also does not put multiple 'First Waypoints' into context
expect(decodeResult.formatted.items[3].label).toBe('Aircraft Route'); | ||
expect(decodeResult.formatted.items[3].value).toBe('VECTOR >> DISCO >> RIVET'); | ||
expect(decodeResult.formatted.items[4].label).toBe('Aircraft Route'); | ||
expect(decodeResult.formatted.items[4].value).toBe('TACKE'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is weird, but right now First Waypoint
isn't being taken into context
for(let i=1; i< data.length; i+=2) { | ||
const key = data[i]; | ||
const value = data[i+1]; | ||
// TODO: discuss how store commented out bits as both raw and formatted |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i should probably discuss before putting out a PR, but sometimes i find it easier when there's code to point at
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice first pass here. Approving and merging! Will you follow up with first waypoint fix?
Parses:
Does not Parse:
Also does not put multiple 'First Waypoints' into context