fe51
fe51
Hi there ✋ ## Feature Know when (by whom, and how) an alert/event was seen ## Motivation As of today, knowledge of how events are taken into account by users...
The link to api doc via Heroku is dead : http://pyronear-api.herokuapp.com/docs, it should be either deleted or updated to the relevant one. Thanks a lot !
Thanks to the documentation effort, this repo is much more accessible than in the past. Thanks @frgfm :) We now have a diagram from [dbdiagram.io](https://dbdiagram.io/home) describing our database in the...
Hi there, Using the route alerts, I realize the max response size for /alerts/ongoing is limited to 50 If it can be guessed from the [code](https://github.com/pyronear/pyro-api/blob/eb4fcc1d60ae2d9ac8f3aac372fb974112521337/src/app/api/endpoints/alerts.py#L139 ), it would be...
We've regularly had to create cameras with default values (not yet knowing (precisely) the location, height, angle of view) -> encountered in Chile in particular, where a lot of setups...
Hi there, Thanks a lot for the recent PR leading to the new data model logic ! I have the feeling that the README is not up to date. Would...
# Pitch Occlusion masks allow users to define areas that generate recurring false positives. (occlusion masks are related to a defined position of a camera) -> https://github.com/pyronear/new-pyro-platform/issues/85 or https://github.com/pyronear/new-pyro-platform/pull/103 give...
# Pitch The concept of a site appears frequently in discussions with business stakeholders. We also use it implicitly in various contexts (engine, frontend, and streaming). As a result, we...
# Pitch Following discussion in https://github.com/pyronear/pyro-api/issues/504 and on Slack, we agreed on changes to the data model to introduce new table which will enable us to develop new features that...
# Motivation Currently, the /api/v1/detections/ POST endpoint allow to create detections but the creation date (created_at) is imposed (= now) While this may have been satisfactory for a while, detections...