E4Warning Mosquito Surveillance Data

Open data API in a single place

Provided by Zenodo

Get early access to E4Warning Mosquito Surveillance Data API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2024.05.27 00:00
Created
2024.01.01
Available languages
English
Keywords
vector, surveillance, mosquito
Quality scoring

Dataset description

Field Details Partner Indicates the name of the partner institution that conducted the fieldwork. Acronym Institution Provides the acronym of the responsible partner institution. Curator Specifies the names of the individuals who carried out the field work, analyzed the samples in the laboratory, and curated the data. Experiment or Surveillance Options = SIT, MRR, SURV. Indicates if the data are from a surveillance (SURV) or from experiments like SIT or MRR. Country This field specifies the country from which the data were collected. Admin Unit (NUTs3) This could refer to a specific administrative division, such as a district or province. Trap ID [E(ovitraps) or A(BGS traps) + location name + numbering]: Each trap is assigned a unique identifier, which could be a combination of letters and numbers. This identifier might also indicate the type of trap used: 'E' signifies the use of an ovitrap, while 'A' indicates a BG-trap for adult mosquitoes. Latitude The geographic UTM coordinates indicating the location of the trap. Longitude The geographic UTM coordinates indicating the location of the trap. Trap type This variable indicates what kind of trap has been used defining three different options: “Ovitrap”, “BG-Sentinel” or “BG-Pro”. Attractant This variable indicates what kind of attractant has been used with the trap defining different options: “BG-Lure”, “CO2”, “CO2+lure”, “lights + lure”, but add as much details as possible. Company names, in particular for chemical attractants, are helpful. Explicitly state if not attractant was used. Start date Date of the start of the sampling with a YYMMDD format. Start time hh:mm format of the time of trap activation. End date Date of the end of the sampling with a YYMMDD format. End time hh:mm format of the time of trap deactivation. Trapping effort (days) Number of days that the trap has been activated. Trapping effort (hours) Number of hours that the trap has been activated. Total number of eggs on tongue depressor Numeric value that refers to the total number of mosquito eggs found on the oviposition substrate (tongue) of the ovitrap. Mosquito species The species of mosquitoes identified collected in the trap. Provide the scientific name avoiding abbreviations. Write “Aedes albopictus” instead of “Ae. Albopictus”. Number per species Total number of individuals per species captured in the trap. The value must be the sum of the number of females and males captured when the life-stage identified is adult. When using ovitraps we need to use a way to record and analyze the number of eggs for each mosquito species using for that a formula that comprises: the total number of eggs collected, the number of eggs that were selected for a sub-sample and hatched to identified the species in the laboratory from larvae or adults; and finally, the sum of all individuals from the sub-sample that were successfully hatched and analyzed. The formula calculates the proportional representation of hatched individuals from the sub-sample relative to the total number of hatched individuals. It reflects the hatching success and viability of the eggs collected adjusted for the size of the sub-sample analyzed. This value is important for understanding species-specific reproductive success and potential impact on the mosquito population dynamics. Life-Stage identified Indicates the life stage of the mosquitoes identified, with options being “adult”, “larva”, or “egg”. Number of females Number of females counted in the trap. Number of males Number of males counted in the trap. Number of blood-fed females Number of blood-fed females counted in the trap. Data validity 1-invalidates data; 2-Reduces data quality, 3-Add info or interesting observations to interpret results; 4-no comment. Comment sample Possible additional comment about the sample.  
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks