This dataset consists of behaviour and distribution data of Lepidoptera at the Stonehenge World Heritage Site in Wiltshire, UK, between 2010-2011. A long term landscape scale grassland restoration and re-creation project has been underway at the site since 2000. 200m long transects were located in the centre of different grassland re-creation fields of different ages, arable land, chalk grassland fragments on slopes and on ancient burial mounds, and semi-improved pasture. Transects were surveyed on three occasions spread across the field season (June to September), and throughout the day and were selected ad-hoc for survey in order to minimise the effect that the time of year and day would have on results. During the survey, the transect was walked at a slow, steady pace allowing five minutes for each 20m section of transect and the number and species of Lepidoptera present 5m either side and ahead were recorded. If Lepidoptera were observed feeding, then the nectar plant species was also recorded. Habitat quality, defined in terms of vegetation characteristics and nectar resources, was quantified throughout each transect by sampling quadrats in each 20m segment of the transect. Vegetation characteristics were measured as vegetation height and density and the percentage cover of bare ground and dead vegetation. Nectar resources were measured in terms of the number and percentage coverage of flowering units, the total number of nectar flowering units and of relevant families (Dipsacaceae, Fabaceae and Asteraceae). The data were collected as part of a PhD project funded by the Natural Environment Research Council and the National Trust. Full details about this dataset can be found at https://doi.org/10.5285/a384bdfb-0bf2-4c3e-80ab-e171f38d503d
Build on reliable and scalable technology
FAQ
Frequently Asked Questions
Some basic informations about API Store ®.
Operation and development of APIs are currently fully funded by company Apitalks and its usage is for free.
Yes, you can.
All important information such as time of last update, license and other information are in response of each API call.
In case of major update that would not be compatible with previous version of API, we keep for 30 days both versions so you will have enough time to transfer to new version. We will inform you about the changes in advance by e-mail.