This README.txt file was generated on 25 October 2022 by Claudia Adam ------------------- GENERAL INFORMATION ------------------- 1. Title of Dataset: Direction of linear oceanic features subducting in the Pacific basin, their projection under the subducting plate, and arc volcano density number and volume density along the Pacific ring of fire. Data associated with Adam et al. (2022) published in Geochemistry, Geophysics, Geosystems # # Authors: Include contact information for at least the # first author and corresponding author (if not the same), # specifically email address, phone number, and institution. # Contact information for all authors is preferred. # 2. Author Information First Author Contact Information Name: Claudia Adam Institution:Department of Geology, Kansas State University, Address: Manhattan, KS 66506 USA Email:cadam@ksu.edu Corresponding Author Contact Information Name:Claudia Adam Institution: Department of Geology, Kansas State University, Address:Manhattan, KS 66506 USA Email:cadam@ksu.edu Author Contact Information (if applicable) Name: Valérie Vidal Institution: ENSL, CNRS Address: Laboratoire de Physique, F-69342 Lyon, France Email: Valerie.Vidal@ens-lyon.fr Author Contact Information (if applicable) Name:Pablo Grosse Institution: CONICET and Fundación Miguel Lillo, Address: Tucumán, Argentina Email: pablogrosse@yahoo.com Author Contact Information (if applicable) Name:Mie Ichihara Institution: Earthquake Research Institute, University of Tokyo, Address: Tokyo, Japan Email: ichihara@eri.u-tokyo.ac.jp --------------------- DATA & FILE OVERVIEW --------------------- # # Directory of Files in Dataset: List and define the different # files included in the dataset. This serves as its table of # contents. # Directory of Files A. Filename: trajectories The trajectories directory contains two directories, mean_oceanic and proj_continental, and two kml files, mean_oceanic.kml and proj_continental.kml. The mean_oceanic directory contains 35 files, named track_oc_FeatureName.dat. These files contain the tracks of the subducting linear oceanic features. In each file, the first column is the longitude, the second column is the latitude. FeatureName changes along each trajectory and it provides the name of the subducting feature. The proj_continental directory contains 35 files, named track_cont_FeatureName.dat. These files contain the projection of the subducting feature under the overriding plate, found through the method described in the paper. In each file, the first column is the longitude, and the second column is the latitude along the trajectory. FeatureName changes along each trajectory and it provides the name of the considered subducting feature. All the files are ascii files. The files mean_oceanic.kml and proj_continental.kml contain the previously described trajectories in a kml format, to be uploaded and displayed in GoogleEarth. B. Filename: density The density directory contains 6 files named density_item_segi_50km.dat and 6 files density_vol_segi_50km.dat. i varies from 1 to 6. We have divided the subduction zones encompassed in our study in 6 segments, represented in the figure subduction_segments.png. In the density_item_segi_50km.dat files, the first column is the longitude, and the second column is the latitude of the volcano road. The third column provides the arc volcanoes density number. In the density_vol_segi_50km.dat files, the first column is the longitude, and the second column is the latitude of the volcano road. The third column provides the arc volcanoes volume density. All the files are ascii files. C. Filename: TableS1.xlsx The file TableS1.xlsx contains the geographical locations and volume estimates of the analyzed arc volcanoes around the Pacific basin. (optional) Additional Notes on File Relationships, Context, or Content: # # File Naming Convention: Define your File Naming Convention # (FNC), the framework used for naming your files systematically # to describe what they contain, which could be combined with the # Directory of Files. # File Naming Convention (if not included above): # # Data Description: A data description, dictionary, or codebook # defines the variables and abbreviations used in a dataset. This # information can be included in the README file, in a separate # file, or as part of the data file. If it is in a separate file # or in the data file, explain where this information is located # and ensure that it is accessible without specialized software. # (We recommend using plain text files or tabular plain text CSV # files exported from spreadsheet software.) # ----------------------------------------- DATA DESCRIPTION FOR: [FILENAME] ----------------------------------------- 1. Number of variables: 2. Number of cases/rows: 3. Missing data codes: Code/symbol Definition Code/symbol Definition N/A 4. Variable List Example. Name: Gender Description: Gender of respondent 1 = Male 2 = Female 3 = Other A. Name: Description: Value labels if appropriate B. Name: Description: Value labels if appropriate -------------------------- METHODOLOGICAL INFORMATION -------------------------- # # Software: If specialized software(s) generated your data or # are necessary to interpret it, please provide for each (if # applicable): software name, version, system requirements, # and developer. # 1. Software-specific information: Name: Version: System Requirements: (if available) Executable URL: Source Repository URL: Developer: Product URL: (optional) Additional Notes: # # Equipment: If specialized equipment generated your data, # please provide for each (if applicable): equipment name, # manufacturer, model, and calibration information. Be sure # to include specialized file format information in the data # dictionary. # 2. Equipment-specific information: Manufacturer: Model: (if applicable) Embedded Software / Firmware Name: Embedded Software / Firmware Version: Additional Notes: # # Dates of Data Collection: List the dates and/or times of # data collection. # 3. Date of data collection (single date, range, approximate date) : README_Template.txt Displaying README_Template.txt.