Provide a clear and concise description of what you want to happen.
The alerting jobs (alerts created in the frontend) is quite old and should be revamped.
In particular, we still use raw, unsiplified geojson boundaries, which means that an alert over Mozambique as a whole ends up taking 18mb in the DB.
This feature is not really used at the moment and the app has evolved a lot since the first implementation. It will be worthwhile to take a step back and truly understand how the alerting feature should evolve. With 2 big chunks of current changes to have in mind : PMTiles and the admin dashboard.
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
No response
Provide a clear and concise description of what you want to happen.
The alerting jobs (alerts created in the frontend) is quite old and should be revamped.
In particular, we still use raw, unsiplified geojson boundaries, which means that an alert over Mozambique as a whole ends up taking 18mb in the DB.
This feature is not really used at the moment and the app has evolved a lot since the first implementation. It will be worthwhile to take a step back and truly understand how the alerting feature should evolve. With 2 big chunks of current changes to have in mind : PMTiles and the admin dashboard.
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
No response