Geochemical and petrological data pertaining to the eruptive deposits of 1883 caldera-forming eruption of Krakatau (NERC grants NE/L002612/1, NE/N014286/1, NE/T002026/1)
Open data API in a single place
Provided by Czech Geological Survey
Get early access to Geochemical and petrological data pertaining to the eruptive deposits of 1883 caldera-forming eruption of Krakatau (NERC grants NE/L002612/1, NE/N014286/1, NE/T002026/1) API!
Geochemical data has been collected on samples from new exposures of the 1883 deposits, revealed by the 2018 tsunamigenic flank collapse of Anak Krakatau, which provides improved stratigraphic context. Whole-rock data taken by X-ray Florescence shows no systematic stratigraphic correlation. Chemical data for transects across, and spot points on, plagioclase phenocrysts, including some trace element data, all obtained using Electron Probe Microanalysis (EPMA), with Backscatter electron (BSE) images of crystals, obtained using Scanning Electron Microscope, reveal complex zoning profiles. However, chemical data for transects across pyroxene phenocrysts, obtained using EPMA, show this phenocryst phase is largely unzoned. The dataset also includes chemical data for spots on Fe/Ti oxides, included on the rims of pyroxene, and obtained using EPMA. Matrix glass chemistry, obtained via EPMA, shows that the early eruptive ash is more evolved than the pyroclastic material that follows, and that there is a slight overall trend to a more homogenous, less evolved melt composition. The 1883 eruption of Krakatau was a large, cardera-forming eruption that caused approximately 36,000 fatalities. It is also the only eruption of its size to have accompanying written accounts.
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.