Dataset: B-GOOD WP3 Field Data

Dataset from the B-GOOD project, containing field data obtained from the implementation of the Field Protocols 1, 2, and 3 from WP3
Published: 2025-03-17
Compliance with FAIR* principles
Findable
Accessible
Interoperable
Reusable
See https://www.go-fair.org/fair-principles for more information about FAIR principles
Data Quality
Good
Data

Dataset tables

Columns

Table Description Rows Data Points Downloads
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON
Metadata Raw CSV JSON

Supplemental Files

Any supplemental files, not containing data.

Columns

File Name Description File Details
Dataset Report
This file contains in detail the structure of the dataset.
This is a generated file.
Licence
This file contains dataset licencing information.
This is a generated file.
Readme
The file contains basic information about the dataset.
This is a generated file.
About

Abstract

The dataset contains field data on floral resources from 3 locations in 2020-2021 in Belgium, Poirtugal and United Kingdom. It was published by Alves da Silva A, Lopes S, Parreira T, Castro S, Bouuaert DC, McVeigh A, Alves J, Sousa JP (UCOI) on the B-GOOD Bee Health Data Portal as part of the B-GOOD project (grant agreement 817622), funded under the EU Horizon 2020 Research and Innovation Programme.

Executive summary

Data overview

The data was published by Alves da Silva A, Lopes S, Parreira T, Castro S, Bouuaert DC, McVeigh A, Alves J, Sousa JP (UCOI) on the B-GOOD Bee Health Data Portal as part of the B-GOOD project (grant agreement 817622), funded under the EU Horizon 2020 Research and Innovation Programme. It contains field data obtained from the implementation of the field protocols 1 (Assessment of plant species composition), 2 (Assessment of Phenology of Floral Resources), and 3 (Assessment and quantification of floral resources as well as flowering species characterization) in Belgium, Portugal and the United Kingdopm, developed under B-GOOD and described in Milestone MS15.

Data value

The objectives of the B-GOOD project were: (1) Facilitate decision making for beekeepers and other stakeholders by establishing ready-to-use tools for operationalising the HSI; (2) Test, standardise and validate methods for measuring and reporting selected indicators affecting bee health; (3) Explore the various socio-economic and ecological factors beyond bee health; (4) Foster an EU community to collect and share knowledge related to honey bees and their environment; (5) Engender a lasting learning and innovation system (LIS); (6) Minimise the impact of biotic and abiotic stressors.

Data description

n/a

Data application

Currently, the data integrated from the B-GOOD Bee Health Data Portal contains major issues and does not comply with the FAIR Guiding Principles for scientific data management and stewardship applied on the EU Pollinator Hub. More descriptive information about the context, quality and condition, or characteristics of the data (e.g. protocols, measurement devices used, units of the captured data, or any other details about the study) must be provided. More metadata in the form of accurate and relevant attributes (e.g. metadata that describes the scope of the data has been described, any particularities or limitations about the data that other users should be aware of, specification of the date of generation/collection of the data, the lab conditions, who prepared the data, the parameter settings, the name and version of the software used, specification of whether it is raw or processed data, explanation of all variable names are explained if they are not self-explanatory) must be provided. Tha dataset requires major revisions by the data provider.

Unresolved issues

n/a

Introduction

n/a

Material and methods

Data acquisition

All raw data files were downloaded from the B-GOOD Bee Health Data Portal on 2024-09-26 18:16:28.

List of raw data obtained from the data provider.

  1. File field-data-protocol-1-be.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  2. File field-data-protocol-1-pt.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  3. File field-data-protocol-1-uk.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  4. File field-data-protocol-2-be.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  5. File field-data-protocol-2-pt.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  6. File field-data-protocol-2-uk.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  7. File field-data-protocol-3-part-1-be.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  8. File field-data-protocol-3-part-1-pt.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  9. File field-data-protocol-3-part-1-uk.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal
  10. File field-data-protocol-3-part-2-be-pt-uk.xlsx, accessed on 2024-09-26 18:16:28, provided by B-GOOD Bee Health Data Portal

Metadata was obtained from the dataset's web page.

Data preparation

All files in the zip-archives were extracted using File Explorer (Microsoft Corporation, version 22H2).

Files field-data-protocol-1-be.xlsx, field-data-protocol-1-pt.xlsx and field-data-protocol-1-uk.xlsx were opened with MS Excel (Microsoft Corporation, version 2409). The worksheets were exported to data files in CSV format (UTF-8 encoding) and imported into Notepad++ (version 8.7) where missing values were substituted by {NULL} using regular expressions, decimal points were converted to a baseline dot using regular expression ((?<=\d),(?=\d) replaced with .) and the first row of each data file containing information related to the header row was transferred into as separate header file. The data file was unpivoted using the Python script UnpivotToCsv.py while the header file was rotated using the Python script TransposeCsv.py. The data in both files was subsequently merged using a SQL database (MariaDB foundation, server version 10.4.32) running in an XAMPP environment (BitRock, version 5.2.1).

Files field-data-protocol-2-be.xlsx, field-data-protocol-2-pt.xlsx and field-data-protocol-2-uk.xlsx were opened with MS Excel (Microsoft Corporation, version 2409). The worksheets were exported to data files in CSV format (UTF-8 encoding) and imported into Notepad++ (version 8.7) where missing values were substituted by {NULL} using regular expressions, decimal points were converted to a baseline dot using regular expression ((?<=\d),(?=\d) replaced with .) and the first 2 rows of each data file containing information related to the header row was transferred into as separate header file. The data file was unpivoted using the Python script UnpivotToCsv.py while the header file was rotated using the Python script TransposeCsv.py. Dates were parsed to the required YYYY-MM-DD format using the python script ParseDates.py. The data in both files was subsequently merged using a SQL database (MariaDB foundation, server version 10.4.32) running in an XAMPP environment (BitRock, version 5.2.1).

Files field-data-protocol-3-part-1-be.xlsx, field-data-protocol-3-part-1-pt.xlsx and field-data-protocol-3-part-1-uk.xlsx were opened with MS Excel (Microsoft Corporation, version 2409) where missing colums were added and the first rows of each data file containing information related to the header row was deleted, as it contained no information that was considered necesary to be included in the data file. The worksheets were exported to data files in CSV format (UTF-8 encoding) and imported into Notepad++ (version 8.7) where missing values were substituted by {NULL} using regular expressions, decimal points were converted to a baseline dot using regular expression ((?<=\d),(?=\d) replaced with .). Dates were parsed to the required YYYY-MM-DD format using the python script ParseDates.py.

File field-data-protocol-3-part-2-be-pt-uk.xlsx was opened with MS Excel (Microsoft Corporation, version 2409) where the first row containing information related to the header row was deleted, as it contained no information that was considered necesary to be included in the data file. The worksheet was exported to a data file in CSV format (UTF-8 encoding) and imported into Notepad++ (version 8.7) where missing values were substituted by {NULL} using regular expressions, decimal points were converted to a baseline dot using regular expression ((?<=\d),(?=\d) replaced with .).

Data was then exported to the respective preparatory files and uploaded to the EU Pollinator Hub according to SOP-017 (Dataset integration.

Data validation

No data validation was performed.

Data analysis

No data analysis was performed.

References

  1. Alves da Silva A., Lopes S., Parreira T., Castro S., Bouuaert D., McVeigh A. et al. 2022 Field data obtained from the implementation of the Field Protocols 1, 2, and 3 from WP3. B-GOOD Bee Health Data Portal. [2024-10-30] beehealthdata.org
Issues
Unresolved quality issues for Field Data Protocol 1 BE
  1. For column Plant community it is unclear, which taxonomy (data standard) has been used for the attributes describing the various plant communities. The data provider is requested to make this information available.
  2. For column ID it is unclear, what the identifier refers to. The data provider is requested to make this information available.
  3. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  4. For column lifeform it is unclear, which taxonomy (data standard) has been used for the attributes describing the life form of a particular plant species. The data provider is requested to make this information available, if possible.
  5. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 1 PT
  1. For column Sampling it is unclear, what it contains. The data provider is requested to make this information available.
  2. For column Plant community it is unclear, which taxonomy (data standard) has been used for the attributes describing the various plant communities. The data provider is requested to make this information available.
  3. For column ID it is unclear, what the identifier refers to. The data provider is requested to make this information available.
  4. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  5. For column lifeform it is unclear, which taxonomy (data standard) has been used for the attributes describing the life form of a particular plant species. The data provider is requested to make this information available, if possible.
  6. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 1 UK
  1. For column Plant community it is unclear, which taxonomy (data standard) has been used for the attributes describing the various plant communities. The data provider is requested to make this information available.
  2. For column ID it is unclear, what the identifier refers to. The data provider is requested to make this information available.
  3. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  4. For column lifeform it is unclear, which taxonomy (data standard) has been used for the attributes describing the life form of a particular plant species. The data provider is requested to make this information available, if possible.
  5. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 2 BE
  1. For column Replica it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  2. For column Individual it is unclear what it describes. The data provider is requested to make this information available.
  3. For column Latitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  4. For column Longitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  5. For column Elevation it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  6. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  7. For column BBCH 60 it is unclear what it describes. The data provider is requested to make this information available.
  8. For column BBCH 65 it is unclear what it describes. The data provider is requested to make this information available.
  9. For column BBCH 69 it is unclear what it describes. The data provider is requested to make this information available.
  10. For column Sampling it is unclear what it describes. The data provider is requested to make this information available.
  11. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 2 PT
  1. For column Replica it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  2. For column Individual it is unclear what it describes. The data provider is requested to make this information available.
  3. For column Latitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  4. For column Longitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  5. For column Elevation it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  6. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  7. For column BBCH 60 it is unclear what it describes. The data provider is requested to make this information available.
  8. For column BBCH 65 it is unclear what it describes. The data provider is requested to make this information available.
  9. For column BBCH 69 it is unclear what it describes. The data provider is requested to make this information available.
  10. For column Sampling it is unclear what it describes. The data provider is requested to make this information available.
  11. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 2 UK
  1. For column Replica it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  2. For column Individual it is unclear what it describes. The data provider is requested to make this information available.
  3. For column Latitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  4. For column Longitude it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  5. For column Elevation it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide this information.
  6. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  7. For column BBCH 60 it is unclear what it describes. The data provider is requested to make this information available.
  8. For column BBCH 65 it is unclear what it describes. The data provider is requested to make this information available.
  9. For column BBCH 69 it is unclear what it describes. The data provider is requested to make this information available.
  10. For column Sampling it is unclear what it describes. The data provider is requested to make this information available.
  11. For column value it is unclear, what the reported variable actually is and in which unit it is provided.
Unresolved quality issues for Field Data Protocol 3-1 BE
  1. For column Sampling Polygon ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  2. For column Sampling Point ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  3. For column Sampling point LAT it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  4. For column Sampling point LONG it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  5. For column Elevation (m) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  6. For column Date it is may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  7. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  8. For column Plant habit (Layer) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information, in particular a reference to the nomenclature that has been used.
  9. For column Quadrat_PC it is unclear what it describes. The data provider is requested to make this information available.
  10. For column Plant cover (%) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information..
  11. For column Quadrat_FA it is unclear what it describes. The data provider is requested to make this information available.
  12. For column No Flowers it is unclear what it describes. The data provider is requested to make this information available.
  13. For column Area (m2) it is unclear what it describes. The data provider is requested to make this information available.
Unresolved quality issues for Field Data Protocol 3-1 PT
  1. For column Landscape window it is unclear what it contains. The data provider is requested to provide this information.
  2. For column Polygon ID it is unclear what it contains. The data provider is requested to provide this information.
  3. For column Polygon Type it is unclear what it contains. The data provider is requested to provide this information, in particular the nomenclature that has been used.
  4. For column Polygon Type_1 it is unclear what it contains. The data provider is requested to provide this information.
  5. For column Sampling Polygon ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  6. For column Sampling Point ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  7. For column Sampling point LAT it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  8. For column Sampling point LONG it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  9. For column Elevation (m) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  10. For column Date it is may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  11. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  12. For column Plant habit (Layer) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information, in particular a reference to the nomenclature that has been used.
  13. For column Quadrat_PC it is unclear what it describes. The data provider is requested to make this information available.
  14. For column Plant cover (%) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  15. For column Flowering Plant cover (%) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  16. For column Quadrat_FA it is unclear what it describes. The data provider is requested to make this information available.
  17. For column No Flowers it is unclear what it describes. The data provider is requested to make this information available.
  18. For column Area (m2) it is unclear what it describes. The data provider is requested to make this information available.
Unresolved quality issues for Field Data Protocol 3-1 UK
  1. For column Polygon Type it is unclear what it contains. The data provider is requested to provide this information, in particular the nomenclature that has been used.
  2. For column Sampling Polygon ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide a more precise information.
  3. For column Sampling Point ID it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  4. For column Sampling point LAT it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  5. For column Sampling point LONG it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  6. For column Elevation (m) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  7. For column Survey (7) it is unclear what it describes. The data provider is requested to make this information available.
  8. For column Month (March - September) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  9. For column Date it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  10. For column Species it is unclear, if a particular nomenclature has been used for the names of the species. The data provider is requested to make this information available, if possible.
  11. For column Plant habit (Layer) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information, in particulare a reference to the nomenclature that has been used.
  12. For column Quadrat_PC it is unclear what it describes. The data provider is requested to make this information available.
  13. For column Plant cover (%) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  14. For column Quadrat_FA it is unclear what it describes. The data provider is requested to make this information available.
  15. For column No Flowers it is unclear what it describes. The data provider is requested to make this information available.
  16. For column Area (m2) it is unclear what it describes. The data provider is requested to make this information available.
Unresolved quality issues for Field Data Protocol 3-2 All
  1. For column No. Plants sampled it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  2. For column No. of Anthers/flower it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  3. For column No. Of pollen grains/anther it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  4. For column No. Of pollen/flower it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  5. For column No. Of pollen/inflorescence it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  6. For column No. of flowers per flower cluster/catkin it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  7. For column Number of samples it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  8. For column Nectar volume/flowers (uL) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
  9. For column Sugar concentration/flower (% Brix) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information. The data provider is also requested, which unit has been used (°Bx or %).
  10. For column Sugar concentration/flower (ug) it may be guessed, but it is not explicitly stated what it describes. The data provider is requested to provide more information.
Properties

Unique identifier

[BGDWP194.0.0]

EUPH IRI

https://app.pollinatorhub.eu/dataset-discovery/BGDWP194.0.0

Status

Quality Validated

Peer review

No peer review was requested.

DOI

No DOI available.

Published

2025-03-17

Access rights

Open

Keywords

abundance, cover, floral resources, flower, nectar, phenology, plant, pollen, species composition

Regions, the data was collected in

Belgique/België, Portugal, United Kingdom
Citation
B-GOOD Bee Health Data Portal Dataset from the B-GOOD project, containing field data obtained from the implementation of the Field Protocols 1, 2, and 3 from WP3. EU Pollinator Hub. [2026-02-24] app.pollinatorhub.eu
Share
Contact
No public contact details available.
You need to login in order to be able to send a direct message to Author
Dataset rating
You need to be registered in order to give a rating. No ratings available yet.
Metrics

Total views

62

Total downloads

4