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

Archival file format ...? #4

Closed
jmhayes-table opened this issue Mar 4, 2019 · 1 comment
Closed

Archival file format ...? #4

jmhayes-table opened this issue Mar 4, 2019 · 1 comment

Comments

@jmhayes-table
Copy link

As this library grows and supports more message types, it might be nice to be able to go back to archived data and re-run a decoder on previously not-decoded messages (cf your comment about being "lazy" :) about AFN messages in the closed issue). What would you think about adding an archive output format that could "save" what has been demodulated for later analysis but an as-yet-unreleased decoder?

@szpajder
Copy link
Owner

szpajder commented Mar 4, 2019

Output files are not produced by libacars but by applications using it (dumpvdl2, JAERO, etc). Hence, libacars is not a place for such a feature. It should be implemented in the abovementioned apps.

On the other hand - I often decode messages from archived logs. I just extract the text part from ACARS messages of interest (using a script) and then pass it to decode_acars_apps or decode_arinc. So it's already possible. I see no need for having an additional log format for this purpose.

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

No branches or pull requests

2 participants