Pollinator Threat Network
Cross-Farm Pollinator Corridor Intelligence
Spray drone operations carry a risk of harming pollinator populations when beneficial insect corridors are not dynamically identified and protected. The FPTN engine (M219) maps RFC 7946 GeoJSON pollinator corridors using Jordan curve ray-casting for point-in-polygon classification, combines them with EPPO-coded beneficial insect observations, and produces NO_SPRAY_ZONE flags that cascade through the IPM decision and nozzle valve planning layers.
Capability specification
- 01
RFC 7946 GeoJSON pollinator corridor ingestion with Jordan curve point-in-polygon classification
- 02
EPPO-coded beneficial insect density mapping per corridor and grid cell
- 03
NO_SPRAY_ZONE flag generation that takes precedence over pest pressure in the IPM engine
- 04
Cross-farm corridor continuity signals via hashed region prefix (KURAL 23)
- 05
46-test green suite covering polygon edge cases, EPPO validation, and cascade precedence
How it works
Corridor Registration
Operators register GeoJSON polygon corridors representing known pollinator habitats. Each polygon is stored with EPPO-coded species association and validity period.
Point-in-Polygon Classification
For every grid cell, the engine evaluates whether the cell centroid falls inside any registered corridor using Jordan curve ray-casting. Cells inside corridors receive a NO_SPRAY_ZONE classification.
IPM Cascade
NO_SPRAY_ZONE flags are passed to the IPM decision engine where they take absolute precedence over ETL/EIL pest pressure. The nozzle valve planner maps NO_SPRAY_ZONE cells to CLOSED valves.
Standards we follow
- STD-01
RFC 7946 — GeoJSON (corridor polygon format)
- STD-02
EPPO PM 1 — Pest Risk Taxonomy (beneficial species EPPO codes)
- STD-03
NIST FIPS 180-4 — Secure Hash Standard (chain hash)
Areas served
This capability is deployed across 14 operational regions. Regulatory alignment details vary by jurisdiction — consult engineering for jurisdiction-specific deployment guidance.
Frequently asked questions
Can a high pest count override the NO_SPRAY_ZONE flag?
No. The NO_SPRAY_ZONE classification from a registered pollinator corridor is evaluated before the ETL/EIL pest-pressure matrix and cannot be overridden by pest count alone. This hard precedence is structurally enforced in the decision matrix and is verified by test invariants on every CI run.
Talk to engineering
For capability evaluation, integration guidance, and deployment scoping, submit a brief to the engineering team.
Submit engineering brief