Skip to main content

Resumen

SIMA’s scouting module lets third-party apps register and retrieve field observations — pests, diseases, weeds, and other adversities detected during crop monitoring. The data flows from external scouting tools (sensors, mobile apps, drones) into SIMA, where agronomists can review and act on it.

Mapa de entidades


Paso 1 — Sync the adversity catalog

Before registering observations, sync the adversity catalog (read-only, global). These are the reference entities your observations will point to.

Adversity Kinds

Top-level classification: Insects, Diseases, Weeds, etc.
Filters: name, modified_at_from, modified_at_to, deleted_at_from Response:

Adversity Categories

Sub-classification within each kind.

Adversities

Specific pests, diseases, or weeds with scientific names and descriptions.
Filters: name, scientific_name, adv_category_id, modified_at_from Response:
The adversity catalog changes infrequently. Sync it weekly or on startup, using modified_at_from for incremental updates.

Paso 2 — Consultar sesiones de scouting

Una sesión de scouting representa una visita de campo o evento de monitoreo para una campaña específica. Referencia uno o más IDs de adversidad observados durante esa visita.
La API de Terceros expone scouting en solo lectura (GET). No hay endpoints POST/PATCH/DELETE para crear o modificar monitoreos desde integraciones externas — esos registros se cargan en SIMA vía la app web o móvil.

Listar sesiones de scouting (v3 — recomendado)

Usá filtros de auditoría v3: updated_at_from, deleted_at_from, page, size.

Listar sesiones de scouting (v2 — legacy)

Filters: Response:
Each adversity_id in the array maps to a specific pest or disease from the adversity catalog. An ID can appear multiple times if multiple occurrences were recorded at different locations in the same session.

Patrones de integración típicos

SIMA → plataforma externa de analítica

Extraer datos de scouting de SIMA para análisis o reportes:
  1. Listá campañas de los establecimientos de interés (GET /api/v3/third_party/campaigns)
  2. Consultá GET /api/v3/third_party/scouting?campaign_id={id}&updated_at_from={last_sync} por campaña
  3. Enriquecé con detalles de adversidad cruzando adversity_ids contra tu caché local del catálogo (Paso 1)

App de scouting → SIMA

La API de Terceros no permite crear sesiones de scouting. Si tu app registra observaciones en campo, las opciones son:
  • Cargar los monitoreos en SIMA vía la app móvil/web del productor, y luego sincronizar hacia tu sistema con GET
  • Contactar soporte@sima.ag si necesitás un flujo de escritura automatizado

Frecuencia de sincronización


Próximos pasos

Sync Strategy

Apply audit filters to keep scouting data current

Work Orders

Create treatment orders based on scouting findings