Introduction
Background
Conceptual Design
Regional Correspondents
Database Structure
References
Contact Us |
Conceptual Design of the Atlas and Database
Image: Haim Tsoar
The Atlas
Three components are needed for the successful development of the atlas:
- A database of key Quaternary data (luminescence, radiocarbon, and related geological framework)
- A GIS (for housing spatial and temporal data sets – including maps of dunefields)
- Google Earth and PDF formats (for quick viewing of data and for wider audiences)
The Database
Data required for the atlas is available in many forms, mostly published in the open literature, but other data is available in theses and dissertations, and "grey-literature" reports. In many cases, pertinent information on the luminescence methods used, precise geographical locations (coordinates) is only available in the latter sources, or in data deposited with the original publication.
The density of data points currently varies considerably, from areas that have been intensively studied (e.g. Mojave Desert) to regions where clustered data is available (e.g. some parts of the Australian Desert) to areas for which data are very sparse (most of the Sahara, central Asia). One by-product of this project will be to clearly identify gaps in data coverage and to indicate areas for future research.
In order to maintain a consistent standard for the database, the following are key criteria:
- All paleo-data entries must be point (not area) data
- Data must meet certain standards and there will be different 'data quality' categories defined by information on dating protocols etc (see below)
- All data must be published, with the definition of published allowing inclusion of grey literature (official reports) and graduate theses.
- Data will be entered as is with no interpretation. However, the information included in the metadata will allow interpretations and inferences.
- The database and the GIS will be searchable on the basis of multiple criteria. These will include various contexts of the source site (e.g. dune type), user-defined time-slices, etc.
- All data must relate to aeolian sands or dunes, but this may include paleosol data from dune sequences, dated organic material within dune deposits, etc.
- All data points will have a unique identifying number (UIN)
|