Splitting the application into separate modules

[rosiste]

First of all a big thank you for this great project. Have you considered splitting the part responsible for data collection and AI evaluation and the part for presenting the results? To make the system more modular.

My point. We're a small town and we're revitalizing natural spots and parks in our area. We'd like to install BirdNet stations in a few places to collect and analyze data and, since we don't have internet access everywhere, send this data, for example, once an hour via the LoRaWAN network we already run, to a central location where we can (on an already appropriately powerful web server) present this data about the diversity of nature around us. If there was a separate layer for data collection and analysis (docker container) and the layer responsible for UI (also as a container), it would help us a lot.

[nobbyneb]

Likewise. I do not know what would be involved to enable this (it sounds significant). We are a small but active village of wildlife enthusiasts looking to use LoRaWAN for remote monitoring. If possible, we'd jump at the chance to do something similar.

Thank you also, @tphakala and the developing team, for all your work on this brilliant project.

[tphakala]

I have no plans of splitting application at the moment, it would be quite significant effort at this point. What could be done instead is to submit detections from BirdNET-Go instances over MQTT to central MQTT broker and have separate application to visualize those.

[nobbyneb]

Thank you, good idea.