INBOVeg - Vegetation surveys of the polder of Kruibeke, Bazel and Rupelmonde in Flanders, Belgium

This data was collected in function of the 2000-2002 "Vegetation mapping of the polder of Kruibeke, Bazel and Rupelmonde" project. The report written about this project can be found here (in Dutch): https://pureadmin.inbo.be/admin/files/5937810/Vandevoorde_etal_2002_VegetatiekarteringPolderKruibekeBazelRupelmonde.pdf

This report contains the context and full methodology of the vegetation surveys. The entire project was carried out in Dutch, accordingly the accompanying report is also in Dutch. In the data, under 'Occurrence remarks', the vegetation layer is noted. The 'Original Londo scale' used for 'organismQuantity' can also be found in the above linked report.

This dataset comes from INBOVEG, the INBO vegetation record database (also part of the "Global Index of Vegetation-plot databases" and the "European Vegetation Archive". The GBIF dataset is the same as the data in INBOVeg. The relevant identification code is IV2014062311501652.

It is possible that some of this data has been previously published on GBIF as part of the FLORABANK1 bulkdata publication (https://doi.org/10.3897/phytokeys.12.2849) at either a 1 km² or a 4 km² scale. Here, they are published as specific locations (with 30m² uncertainty).

To allow anyone to use this dataset, we have released the data to the public domain under a Creative Commons Zero waiver (http://creativecommons.org/publicdomain/zero/1.0/). We would appreciate however, if you read and follow these norms for data use (http://www.inbo.be/en/norms-for-data-use) and provide a link to the original dataset (https://doi.org/10.15468/gouexm) whenever possible. If you use these data for a scientific paper, please cite the dataset following the applicable citation norms and/or consider us for co-authorship. We are always interested to know how you have used or visualised the data, or to provide more information, so please contact us via the contact information provided in the metadata or via [email protected].