[DRAFT] Allow enabling/disabling the (weather) Risk Validation for alert generation (site-level, ideally camera-level)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 29
- Forks
- 14
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 5
Description
Desc
be able to enable /disable the "Risk Service" used for alert generation, ideally at the site level (or camera level).
By default, the Risk Service should remain enabled.
This is useful for sites with a limited visibility perimeter or where fire starts are largely independent of weather conditions, making the Risk Service less relevant and potentially risky.
To be detailed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the alert-generation path and its Risk Service integration, then determine whether configuration belongs at site or camera scope. Done means the Risk Service remains enabled by default and can be disabled at the supported scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100