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

Feature request: Ability to configure additional/third party data exports aka Generic Feeder #248

Open
Romeo-Golf opened this issue Oct 3, 2016 · 1 comment

Comments

@Romeo-Golf
Copy link

I spoke to a potential user who mentioned exporting data to their own VRS, would it be possible to add an option in the setup/install script to add an additional 'custom' export destination, ideally allowing this to be selected or de-selected along with the existing well known data collection projects?

@Romeo-Golf Romeo-Golf changed the title Ability to configure additional/third party data exports during setup Feature request: Ability to configure additional/third party data exports during setup Oct 27, 2016
@Romeo-Golf
Copy link
Author

I have spoken to another user who is exporting data to adsb-exchange from a elderly piaware instance, but not MLAT data, and would be happy to upgrade to using the adsb-receiver image provided that an existing data export can be accommodated without to much manual intervention...

Would this be feasible without having say a centralised config file (#262) to store details of any third party data exports along side the currently bundled export sources/software ?

@Romeo-Golf Romeo-Golf changed the title Feature request: Ability to configure additional/third party data exports during setup Feature request: Ability to configure additional/third party data exports aka Generic Feeder Jan 16, 2017
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

1 participant