Optimize Cell Footprint Processing with Database Caching

[dcromp]

Currently, the system requires us to provide cell metadata for each time period (day/month/year) we want to process, even though the majority of cells' metadata and footprints remain unchanged. This leads us to recalculating the same cell footprints for each day, which is computationally intensive.

One potential solution could be implementing a database to store cell footprints. This would allow us to maintain a cache of footprint data and only update the calculations when new metadata indicates a change in a cell's properties. We could have the system compare incoming metadata against stored values and trigger recalculations only for cells that have actually changed. Would this approach help reduce the processing overhead.

[steso-nommon]

Thank you for bringing up this topic. We will include it in our to-do list alongside other improvements currently under evaluation. At the moment, our focus for the next releases is on adding new functionalities (such as tourism use cases) and addressing other scalability challenges. However, we will certainly take your idea into consideration for future developments. Thank you for your contribution.