Andreas Mandel

obs lite has a own firmware

Not sure if you saw https://github.com/openbikesensor/OpenBikeSensorFirmware/issues/216 - I would still stick with our current solution and close the linked issue - might be you have a different opinion?

So we keep the current definition of the privacy areas. On the portal side there there might be the possibility to define different shapes in the future.

Can this region areas be derived from some data already available in/via open street map? (Not sure if such a thing exists but I would expect this)

Cool, does this also include an hierarchy so that we could (auto) label the tracks with "city:Stuttgart" "state:Baden-Württemberg" "country:Germany" might be "county:Stuttgart" / "district:Heslach". No sure - I bet you...

For a web based flasher I've created also a container that hosts all static content, can be directly exposed as https://install.openbikesensor.org/ or might be integrated into the portal? We need...

So the image with the installer is now at ghcr.io/openbikesensor/openbikesensorflasher:main build with https://github.com/openbikesensor/OpenBikeSensorFlasher - with every commit.

I did not contribute to the portal part of OBS but we should have one license for all sub-projects. I would also vote for a MIT license for the source...

Empty files with no data or header data only should not be generated any more since a while now. You might get files with a low number of lines or...

Quick answer points to https://github.com/openbikesensor/OpenBikeSensorFirmware#updating and https://github.com/openbikesensor/OpenBikeSensorFirmware/blob/master/docs/software/firmware/initial_flash.md#initial-esp-flashing I can try to give it a better start but for now this is what I have 8-)