Add Gundi v2 push receiver for ICU and normalized data model
ICU now pushes camera events via a Gundi-v2-compatible API instead of dropping file triplets into S3. The new gundi-receiver service accepts them directly, so images are in the system within seconds instead of waiting out the 90s age gate + poll interval. OCR of the burnt-in camera timestamp stays mandatory (ICU only sends server times; OCR detects drifting camera clocks) but now runs asynchronously after ingest. The push path writes a normalized model that separates what the legacy metadata table conflates: camera_status (status time series), image (image properties) and detection (classifications), plus the image_with_status view as the portal's migration target. A repeatable, batched migration splits existing metadata/category rows into it. The legacy poller is unchanged and keeps writing metadata/category until the portal is switched over. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -20,3 +20,8 @@ PG_DSN=postgresql://USER:PASSWORT@HOST:PORT/meles?sslmode=require
|
||||
# --- DeerMapper API (nur noetig, wenn app.enable_deermapper_api: true) ---
|
||||
DEERMAPPER_API_URL=https://webapp.deermapper.net/api/icu
|
||||
DEERMAPPER_API_KEY=__NEUEN_API_KEY_EINTRAGEN__
|
||||
|
||||
# --- Gundi-Receiver (Push-Schnittstelle fuer ICU) ---
|
||||
# Diesen Wert bekommt ICU als "apikey". Mind. 24 Zeichen, z.B.:
|
||||
# python3 -c "import secrets; print(secrets.token_urlsafe(32))"
|
||||
GUNDI_API_KEY=__NEUEN_API_KEY_EINTRAGEN__
|
||||
|
||||
Reference in New Issue
Block a user