You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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
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
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
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?
The text was updated successfully, but these errors were encountered: