Machine-readable observation plan export

Hi,

Sometime back in late 2024, the column headers of the exported Telescopius Observing List CSV were slightly changed, which in turn broke NINA’s ability to import them. This has been addressed in the development branch of NINA, however the occasional user still reports it because they remain on the stable release train. This will be fully resolved for stable-branch users when the current development branch becomes the new stable in the future; a date that has not yet been determined.

Given the fragility of CSV files as a way to transfer data between applications, it seems that this would be a good opportunity to consider a format that is more reliable for these purposes, such as JSON. It would allow you to extend the content of the observing list exports without the danger of breaking functionality. To take this further, an API that could be used by external apps to directly retrieve such lists would be useful; removing the need for a user to manually take a file and feed it to other applications. If such a feature already exists, I must have missed it.

Indeed, CSV is not a good format for integrations. This is a reasonable request, I’m adding it to the backlog. Thank you for your suggestion!