--- title: "Mosquito and vector surveillance | Nexus Observatory" description: "Dengue, malaria, West Nile and other vector-borne diseases follow mosquitoes, and mosquitoes follow heat, rain and standing water." url: https://observatory.global/industries/health/vector-surveillance/ publisher: Nexus Observatory Inc. updated: 2026-11-02 --- [Nexus Observatory](https://observatory.global/) / [Health](https://observatory.global/industries/health/) / [Specialized fields](https://observatory.global/industries/health/fields/) / **Mosquito and vector surveillance** # Mosquitoes counted before they spread disease. Dengue, malaria, West Nile and other vector-borne diseases follow mosquitoes, and mosquitoes follow heat, rain and standing water. Counting traps that report daily, with weather and water sensing, show where populations are growing so control teams act before cases rise. [Plan a deployment](https://observatory.global/contact/deployment/) How it works [Station Builder](https://observatory.global/studio/builder/) **Industry**: Health **Measurements**: 4 **Sources cited**: 3 1. Health · Mosquito and vector surveillance Disease follows the mosquito Dengue, malaria, West Nile and other vector-borne diseases follow mosquitoes, and mosquitoes follow heat, rain and standing water. Invasive species are spreading into new areas. Manual trap counts arrive weeks late, after populations have grown and control is harder. Measurement turns that risk into decisions made in time. 2. What is measured Counts, weather and water Counting traps across suburbs and wetlands count mosquitoes every day and group them by type. Weather stations in the network measure temperature, humidity and rain, and level sensors at drains, ponds and storm channels show where water stands long enough for breeding. InstrumentsCounting traps · Weather stations · Standing water sensors 3. The base node Pulses forecast The node turns daily counts into population trends, links them with heat, rain and standing water, forecasts the next breeding pulse and ranks areas for control teams, so effort goes where populations are about to grow. Nothing is lost when a link drops; the node keeps it. 4. Radio and links Suburbs and wetlands Traps and sensors across suburbs and wetlands reach gateways over a low-power link, on batteries and small solar panels. Gateways and the node send data over cellular to the health authority and its control teams. Each link is chosen for the place, not from a catalogue. LinksLoRaWAN · Public cellular 5. How it works From heavy rain to targeted control Heavy rain fills storm channels in two districts and warm nights follow. Standing water sensors stay high and the node forecasts a breeding pulse within days. Control teams clear and treat the channels; the next counts stay flat where the pulse was due. 6. From order to operation · Order Scope with the health authority The scope reads the authority's vector species, diseases, past outbreaks, existing traps and control teams. Nexus Observatory Inc. returns the trap network, forecasting design and a price per area and per year. Every assumption in the scope is written down and priced. [Plan a deployment](https://observatory.global/contact/deployment/) 7. From order to operation · Survey Survey breeding sites Crews and entomologists survey breeding sites, trap positions by habitat and housing, standing water, gateway coverage and access. Findings are mapped with photographs. Every finding is kept with the site record for the crews who follow. Findings shape the kit for each site before anything is built. 8. From order to operation · Permits Land and community notice Land owners and the city approve trap and sensor sites, and communities are told what the traps do. Every approval is kept with the area record. Approvals are tracked site by site, so nothing waits unseen. No crew goes to site before its approvals are in place. 9. From order to operation · Build Build and validate Counting traps are validated against manual identification, weather and water sensors calibrated, radios paired and the node configured and enrolled with its identity. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together. [Open the Station Builder](https://observatory.global/studio/builder/) 10. From order to operation · Install Install the network Crews install traps, weather stations and water sensors, raise gateways on rooftops and set up the node at the health authority. Every point is mapped and photographed. The site record is updated before the crew leaves. Crews follow the site safety plan throughout the work. 11. From order to operation · Commission Commission against manual counts Each node proves its identity. Trap counts are compared with entomologists' manual identification over several weeks, and alerts are tested with control teams. Results are signed and kept with the site record. Acceptance is recorded with the owner before handover. 12. From order to operation · Operate Target control Health authorities see populations by area and the conditions behind them. Control teams are sent where populations are growing, breeding sites are cleared after rain, and every action is recorded with later counts. Reports for owners and funders come from the same record. 13. From order to operation · Maintain Service and revalidate Traps are serviced and revalidated against manual counts each season, batteries replaced, sensors recalibrated and software updated in rings. Every change is kept with the area record. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life. [Book field services](https://observatory.global/contact/field-service/) 14. Data products For authorities and control teams Health authorities and entomologists receive mosquito population trends; control teams receive areas ranked for control; public health planners receive breeding pulse forecasts; regional and international surveillance receive vector records, each tied to trap, area and date. Each product carries its site, time and quality flags. [See the data products](https://observatory.global/data-products/) 15. Evidence Surveillance to guidance Surveillance follows the invasive mosquito guidelines and supports the global vector control response, and records support reporting under the international health regulations. Every count keeps its trap and validation, and every action its later counts. Records are open to the people who must check them. Drawn againstGuidelines for the surveillance of invasive mosquitoes in Europe · Global Vector Control Response 2017-2030 · International Health Regulations (2005) 16. What you get Environmental exposure monitoring for health programmes Heat, air and water exposure measurements around facilities and communities; no diagnosis or treatment. Delivered as managed service and data licence, for health authorities, hospital networks, employers. Scale: City to national. Service levels are written as numbers you can measure on your own dashboard. [Talk to sales](https://observatory.global/contact/sales-enquiry/) 17. Next step Plan mosquito and vector surveillance with us Tell us the site, the measurements and the rules it answers to. We reply with a survey proposal, a design and a scope for mosquito and vector surveillance. An engineer replies with a survey proposal and a scope, and the plan grows from one site to the network you need, at your pace. [Plan a deployment](https://observatory.global/contact/deployment/) [Open the Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) **01** The place and its hazards ## Where it runs, and what can go wrong. Operating contextThe global vector control response calls for strengthened surveillance, invasive mosquito surveillance in Europe follows published guidelines, and countries report public health events under the international health regulations. Manual trap counts are slow and sparse, and arrive after populations have grown. Hazards - Mosquito populations growing unseen - Invasive species spreading into new areas - Rain and heat that trigger breeding - Manual trap counts arriving weeks late - Control spread thinly instead of targeted **02** What must be measured ## What, where, how often, and under which rules. Each measurement names where it is taken, how often, and the public standard or regulation behind it. Numbers in the sources column open the cited source below. | Measurement | Where | Cadence | Sources | | --- | --- | --- | --- | | Mosquito counts by trap | Counting traps across the area | Daily, with species groups | 12 | | Temperature, humidity and rainfall | Weather stations in the trap network | Every fifteen minutes | 2 | | Standing water | Level sensors at drains, ponds and storm channels | Hourly | 1 | | Control actions and outcomes | Every treatment and later counts | Each action | 23 | **03** The observation stack ## From one base unit to a network. The same blocks at every scale: instruments and a base node, a site with its radio, a fleet run as one, and a network federated on the open protocol. 1. **01** Base unit A trap: a counting trap with a low-power radio and its own battery. [Build a station →](https://observatory.global/studio/builder/) 2. **02** Site An area: traps, weather and water sensors, a gateway and a node. [Plan a site →](https://observatory.global/contact/deployment/) 3. **03** Fleet Every area of a health authority on one vector view. [Managed offers →](https://observatory.global/industries/health/solutions/) 4. **04** Network Authorities share vector records with regional and international surveillance. [The open protocol →](https://observatory.global/protocol/) - **01** Compact weather station - **02** Water level gauge - **03** LPWAN endpoint - **04** LoRaWAN gateway - **05** Edge node (Wedge) - **06** Cellular modem/router - **07** Solar array Radio and links ### LoRaWAN Traps and sensors across suburbs and wetlands reach gateways over a low-power link. Radio and links ### Public cellular Gateways and the node send data over cellular. Edge computeThe node turns trap counts into population trends, links them with heat, rain and standing water, forecasts breeding pulses and ranks areas for control teams. PowerTraps and sensors run on batteries and small solar panels. **04** How it works ## From the instrument to the product. One observation's path, tier by tier, with the interface on every link and a bill of materials below; then how the one node grows to a site, a fleet and federated networks. Mosquito and vector surveillance: data path – of 08 01 Instruments Measurement with sensor identity andcalibration 02 Field radio 03 Gateway 04 Node – Wrap in an observation envelope with timequality– Measure quality and uncertainty, attachquality flags– Buffer locally (store-and-forward when thelink drops) 05 Backhaul Commit with transactional outbox andpublish, delivered at least once 06 Site Consumer inbox deduplicates and applieseach record once into governed data 07 Data store Governed product through API, map orexport, correction-aware 08 Products OGC SensorThings APIDarwin CoreMQTT 09 Power and structure Supplies 12 V DC, 24 V DC, 48 V DC to thefield equipment 01 Compact weather station SDI-12 · RS-485 · Ethernet 02 Water level gauge SDI-12 · RS-485 · Ethernet Counting mosquito traps withLoRaWAN radios Not in the reference kit 03 LPWAN endpoint Analogue I/O · SDI-12 · RS-485 04 LoRaWAN gateway Ethernet · RF · GNSS antenna 05 Edge node (Wedge) Ethernet · Fibre · USB · RS-485 ·BMC 06 Cellular modem/router Ethernet · USB · RS-232 Site MQTT 5 with Sparkplug B Governed data store Versioned, correction-aware Mosquito population trends Areas ranked for control Breeding pulse forecasts Vector records 07 Solar array RS-485 SDI-12 SDI-12 LoRaWAN LoRaWAN Ethernet Ethernet LTE/NR From the instrument to the published product: each band is a tier, each connector names its interface, and the numbers match the bill of materials. Hover or focus a block to trace its path; scroll or step to follow one observation. | Item | Equipment | Data ports | Protocols | Power in | | --- | --- | --- | --- | --- | | 01 | **Compact weather station** All-in-one or compact station for temperature, humidity, pressure, wind and rain at a site. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 02 | **Water level gauge** Radar, pressure or float gauge for river, lake, reservoir or tide level. | SDI-12RS-485Ethernet | SDI-12, Modbus, MQTT 5, OGC SensorThings API | 12 V DC | | 03 | **LPWAN endpoint** Battery-powered endpoint on LoRaWAN, NB-IoT or LTE-M that carries one or more sensors. | Analogue I/OSDI-12RS-485 | LoRaWAN, OMA LwM2M, CoAP | Internal battery, Energy harvesting | | 04 | **LoRaWAN gateway** Multi-channel LoRaWAN gateway that forwards uplinks to a network server and schedules downlinks within duty limits. | EthernetRFGNSS antenna | LoRaWAN, MQTT 5 | PoE, 12 V DC | | 05 | **Edge node (Wedge)** Rugged edge node that boots from signed media, attests itself and establishes a site cell from little or no infrastructure. | EthernetFibreUSBRS-485BMC | MQTT 5, DMTF Redfish, IEEE 1588 PTP, NTP with NTS, OPC UA | 12 V DC, 24 V DC, 48 V DC, AC mains | | 06 | **Cellular modem/router** LTE or NR modem or router that uses a public carrier or private network as backhaul. | EthernetUSBRS-232 | 3GPP E-UTRA air interface, 3GPP NR air interface, OMA LwM2M | 12 V DC, PoE | | 07 | **Solar array** PV modules with charge controller sized to the site's load and climate. | RS-485 | Modbus | — | How it scales 01 Instruments Arbitrary qualified sensors and instruments whosemeasurements are ingested with calibration, units,geometry, time, custody and uncertainty. ×n 02 Node The minimum useful deployable unit: server, ruggedappliance, radio node, sensor gateway, satelliteterminal, AI, scientific, vehicle or virtual node. Node Node agent 03 Site The minimum independently operable localgovernance and failure domain: one or more nodesplus local network, identity, policy, evidence,storage, products and operator surfaces. SITE Node Node Node ×n 04 Cluster An optional scale or specialisation domain forscheduling, shared storage, accelerators or datalocality. CLUSTER ×n 05 Fleet Coordinates plans, acknowledgements,convergence evidence, update campaigns andcorrection propagation across nodes and sites. FLEET Fleet controller ×n 06 Federation An exchange of products, capabilities, events orwork across approved, independently administeredtrust domains, using explicit trust, policy,data-locality, version and correction contracts. TRUST DOMAIN TRUST DOMAIN TRUST DOMAIN ×n Verifier Applications Data in the field Telemetry Control Data upstream Control Data upstream Control Exchange Evidence Events Exchange The smallest deployable unit is one node; the same unit is replicated to meet the demand. Nodes form a site, sites may form a cluster, sites and clusters are coordinated as a fleet, and fleets exchange across independently administered trust domains. Each plane is a separate channel with its own open binding. **Data in the field**: MQTT 5 with Sparkplug B; connectors for LoRaWAN, OPC UA and instrument buses. **Telemetry**: OpenTelemetry OTLP. **Control**: TLS 1.3 with mutual authentication; protobuf messages over gRPC or HTTP/2. **Data upstream**: At-least-once publication with repeat-safe keys over the control channel or NATS JetStream; QUIC MAY be used on lossy links. **Evidence**: DSSE-signed in-toto statements; SLSA provenance; SCITT transparency receipts. **Events**: Event envelopes mapped to CloudEvents 1.0; channels described in AsyncAPI 3. **Exchange**: OpenAPI 3.1; the OGC API family; SensorThings; STAC; WIS 2.0. **05** From order to operation ## Every step, from the first call to a running site. The same crew and the same record carry the work from scope to maintenance. 1. 01 Order Scope with the health authority The scope reads the authority's vector species, diseases, past outbreaks, existing traps and control teams. Nexus Observatory Inc. returns the trap network, forecasting design and a price per area and per year. Every assumption in the scope is written down and priced. 2 2. 02 Survey Survey breeding sites Crews and entomologists survey breeding sites, trap positions by habitat and housing, standing water, gateway coverage and access. Findings are mapped with photographs. Every finding is kept with the site record for the crews who follow. Findings shape the kit for each site before anything is built. 1 3. 03 Permits Land and community notice Land owners and the city approve trap and sensor sites, and communities are told what the traps do. Every approval is kept with the area record. Approvals are tracked site by site, so nothing waits unseen. No crew goes to site before its approvals are in place. 4. 04 Build Build and validate Counting traps are validated against manual identification, weather and water sensors calibrated, radios paired and the node configured and enrolled with its identity. Test results travel with the kit to the site. Nothing ships until the whole kit has passed its tests together. 5. 05 Install Install the network Crews install traps, weather stations and water sensors, raise gateways on rooftops and set up the node at the health authority. Every point is mapped and photographed. The site record is updated before the crew leaves. Crews follow the site safety plan throughout the work. 6. 06 Commission Commission against manual counts Each node proves its identity. Trap counts are compared with entomologists' manual identification over several weeks, and alerts are tested with control teams. Results are signed and kept with the site record. Acceptance is recorded with the owner before handover. 1 7. 07 Operate Target control Health authorities see populations by area and the conditions behind them. Control teams are sent where populations are growing, breeding sites are cleared after rain, and every action is recorded with later counts. Reports for owners and funders come from the same record. 2 8. 08 Maintain Service and revalidate Traps are serviced and revalidated against manual counts each season, batteries replaced, sensors recalibrated and software updated in rings. Every change is kept with the area record. Spares and procedures travel with the crews. Maintenance history stays with each site for its whole life. 1 **06** Data products and integration ## What it delivers, to whom, and into which systems. Data products - **Mosquito population trends** Health authorities and entomologists - **Areas ranked for control** Control teams - **Breeding pulse forecasts** Public health planners - **Vector records** Regional and international surveillance Integration - **Disease surveillance** Vector data join case surveillance. - **Control operations** Ranked areas reach control teams' plans. - **Cities** Standing water alerts reach drainage teams. Exchanged through OGC SensorThings API, Darwin Core, MQTT. **07** Questions buyers ask ## Before you scope it. Does it identify species? It counts and groups; entomologists validate species. Does it replace manual surveillance? No. Manual counts validate it. Can it forecast outbreaks? It forecasts mosquito pulses; outbreaks also depend on cases. Who acts on it? Health authorities and control teams. **08** Resources ## The sources behind this page. Public standards, regulations and guidance, cited where they apply. Each applies only where its jurisdiction or scope does. 1. **1** [Guidelines for the surveillance of invasive mosquitoes in Europe](https://www.ecdc.europa.eu/) European Centre for Disease Prevention and Control · 2012 2. **2** [Global Vector Control Response 2017-2030](https://www.who.int/) World Health Organization · 2017 3. **3** [International Health Regulations (2005)](https://www.who.int/) World Health Organization · 2005 **09** Related ## Use cases and solutions. [Solution Environmental exposure monitoring for health programmesHeat, air and water exposure measurements around facilities and communities; no diagnosis or treatment.Solutions for health →](https://observatory.global/industries/health/solutions/#exposure-monitoring) [Solution Sensing as a ServiceObservation networks designed, installed, operated and maintained for a monthly fee: weather, hydromet, air, seismic and environmental stations, with data delivered under a licence.Solutions for health →](https://observatory.global/industries/health/solutions/#sensing-service) [Solution Biodiversity and habitat monitoringAcoustic sensors, camera traps that exclude people, eDNA sampling logistics and EO habitat change for nature programmes and disclosures.Solutions for health →](https://observatory.global/industries/health/solutions/#nature-monitoring) **10** Health: specialized fields ## Other fields of this industry. [Specialized field Heat and healthStreet, home and care-home heat sensing linked to heat-health warnings, so health services reach the people most at risk before a heatwave peaks.The full field →](https://observatory.global/industries/health/heat-health/) [Specialized field Hospital environmentsVentilation, pressure, temperature, medical gases and pharmacy storage in hospitals, watched continuously so critical rooms stay within their limits and every excursion is on record.The full field →](https://observatory.global/industries/health/hospital-environments/) [Specialized field Wastewater surveillanceFlow-proportional sampling, flow and water quality at treatment plants and in sewers, giving public health early, anonymous signals of infections in a community.The full field →](https://observatory.global/industries/health/wastewater-surveillance/) ### Bring us the site. Plan a deployment, configure a station, model it in the Studio or talk to sales. The form names who receives your details. [Plan a deployment](https://observatory.global/contact/deployment/) [Station Builder](https://observatory.global/studio/builder/) [Open the Studio](https://observatory.global/studio/) [Talk to sales](https://observatory.global/contact/sales-enquiry/) [Request a quote](https://observatory.global/contact/hardware-quote/) [Nexus Observatory](https://observatory.global/)**Health** . Exposure, measured where people live.[Talk to us](https://observatory.global/contact/) Health - [Overview](https://observatory.global/industries/health/) - [Explainer](https://observatory.global/industries/health/explainer/) - [Specialized fields](https://observatory.global/industries/health/fields/) - [Use cases](https://observatory.global/industries/health/use-cases/) - [Solutions](https://observatory.global/industries/health/solutions/) - [Platforms](https://observatory.global/industries/health/platforms/) - [Resources](https://observatory.global/industries/health/resources/) - [Contact](https://observatory.global/industries/health/contact/) Platforms - [Observatory Protocol](https://observatory.global/protocol/) - [Protocol & Grid](https://observatory.global/grid-services/) - [Software](https://observatory.global/software/) - [Hardware & power](https://observatory.global/hardware/) - [Sensors & instruments](https://observatory.global/sensors/) - [Connectivity](https://observatory.global/connectivity/) - [Edge compute & AI](https://observatory.global/edge-ai/) - [Earth observation & GeoAI](https://observatory.global/earth-observation/) - [Space and satellite systems](https://observatory.global/space/) - [Digital twins and simulation](https://observatory.global/digital-twins/) - [Data & licensing](https://observatory.global/data-products/) - [Field services](https://observatory.global/field-services/) - [Frontier labs](https://observatory.global/labs/) Solutions - [Early warning](https://observatory.global/use-cases/street-flood/) - [Wildfire and fire weather](https://observatory.global/use-cases/wildfire-camera/) - [Environmental compliance](https://observatory.global/use-cases/methane-fenceline/) - [Asset monitoring](https://observatory.global/industries/infrastructure/) - [Private networks](https://observatory.global/connectivity/private-5g/) - [Remote power and sites](https://observatory.global/use-cases/remote-microgrid/) - [Climate and resilience](https://observatory.global/industries/climate/) - [Site twins](https://observatory.global/digital-twins/) - [Data licensing](https://observatory.global/data-products/) Industries - [Public safety](https://observatory.global/industries/public-safety/) - [Government](https://observatory.global/industries/government/) - [Cities](https://observatory.global/industries/cities/) - [Civil resilience](https://observatory.global/industries/resilience/) - [Communities](https://observatory.global/industries/communities/) - [Humanitarian](https://observatory.global/industries/humanitarian/) - [Climate](https://observatory.global/industries/climate/) - [Water](https://observatory.global/industries/water/) - [Nature](https://observatory.global/industries/nature/) - [Oceans](https://observatory.global/industries/oceans/) - [Agriculture](https://observatory.global/industries/agriculture/) - [Energy](https://observatory.global/industries/energy/) - [Telecom](https://observatory.global/industries/telecom/) - [Transport](https://observatory.global/industries/transport/) - [Infrastructure](https://observatory.global/industries/infrastructure/) - [Mining](https://observatory.global/industries/mining/) - [Industry](https://observatory.global/industries/industry/) - [Research](https://observatory.global/industries/research/) - [Education](https://observatory.global/industries/education/) - [Health](https://observatory.global/industries/health/) - [Insurance and finance](https://observatory.global/industries/insurance/) - [Events](https://observatory.global/industries/events/) Products - [Field Deployment Studio](https://observatory.global/studio/) - [Station Builder](https://observatory.global/studio/builder/) - [Field services](https://observatory.global/field-services/) - [Data products](https://observatory.global/data-products/) - [APIs and SDKs](https://observatory.global/protocol/developers/) - [Edge runtime and fleet](https://observatory.global/software/) - [Hardware catalogue](https://observatory.global/hardware/) - [Reference designs](https://observatory.global/protocol/reference-designs/) Resources - [Learn](https://observatory.global/learn/) - [Stories](https://observatory.global/stories/) - [Environments](https://observatory.global/environments/) - [Network scenes](https://observatory.global/environments/networks/) - [Observatories atlas](https://observatory.global/observatories/) - [Earth and maps](https://observatory.global/earth/) - [Technologies](https://observatory.global/technologies/) - [Countries](https://observatory.global/countries/) - [Spectrum](https://observatory.global/spectrum/) - [Specification](https://observatory.global/protocol/specification/) - [Conformance](https://observatory.global/protocol/conformance/) - [Open source](https://observatory.global/open/) - [Data credits](https://observatory.global/credits/) Company - [About](https://observatory.global/about/) - [Open governance](https://observatory.global/consortium/) - [Security and trust](https://observatory.global/security/) - [Contact sales](https://observatory.global/contact/) - [Privacy requests](https://observatory.global/privacy-request/) © 2026 Nexus Observatory Inc. [Security and trust](https://observatory.global/security/) [Privacy choices](https://observatory.global/privacy-choices/) [Accessibility](https://observatory.global/legal/accessibility/) [Privacy](https://observatory.global/legal/privacy/) [Terms](https://observatory.global/legal/terms/)