usSEABED: Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) offshore surficial sediment data release
usSEABED: Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) Offshore Surficial Sediment Data Release By Brian J. Buczkowski, Jane A. Reid, Chris J. Jenkins, Jamey M. Reid, S. Jeffress Williams, and James G. Flocks Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government U.S. Geological Survey Data Series 146 2006, Version 1.0 U.S. Department of the Interior U.S. Geological Survey U.S. Department of the Interior Gale A. Norton, Secretary U.S. Geological Survey P. Patrick Leahy, Acting Director U.S. Geological Survey, Reston, Virginia For Additional Information: http://woodshole.er.usgs.gov/project-pages/aggregates/ http://walrus.wr.usgs.gov/nearshorehab/ http://walrus.wr.usgs.gov/usseabed/ Telephone: 508-548-8700 Feedback on usSEABED is appreciated, both in usefulness and in error detection. Please use the following contact information for issues, questions and (or) data to contribute to the growing usSEABED information system in the U.S. EEZ. Jane A. …
Download the original document · Plain text (TXT) · Browse the archive · How this archive works
Original source: https://pubs.usgs.gov/ds/2006/146/images/pdf/report.pdf
SHA-256 892b0ae98e73cc085b8c6de773973ed116c494cddb2d6c042d2a8d397e60e016
Re-using this document
work of the United States Government, 17 USC 105, public domain
Our description, tagging, arrangement, extracted text and machine transcripts are released under CC0 1.0. We assert nothing about the document itself.
Archive identifier LF-892b0ae98e73
Document text
usSEABED: Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) Offshore Surficial Sediment Data Release By Brian J. Buczkowski, Jane A. Reid, Chris J. Jenkins, Jamey M. Reid, S. Jeffress Williams, and James G. Flocks Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government U.S. Geological Survey Data Series 146 2006, Version 1.0 U.S. Department of the Interior U.S. Geological Survey U.S. Department of the Interior Gale A. Norton, Secretary U.S. Geological Survey P. Patrick Leahy, Acting Director U.S. Geological Survey, Reston, Virginia For Additional Information: http://woodshole.er.usgs.gov/project-pages/aggregates/ http://walrus.wr.usgs.gov/nearshorehab/ http://walrus.wr.usgs.gov/usseabed/ Telephone: 508-548-8700 Feedback on usSEABED is appreciated, both in usefulness and in error detection. Please use the following contact information for issues, questions and (or) data to contribute to the growing usSEABED information system in the U.S. EEZ. Jane A. Reid: for information about the Benthic Habitats project and (or) adding Pacific Coast, Alaska or Hawaii data USGS, Pacific Science Center 400 Natural Bridges Drive Santa Cruz, CA 95060 Chris J. Jenkins: for information about the dbSEABED program as well as adding global data University of Colorado Institute of Arctic and Alpine Research 1560 30th Street Campus Box 450 Boulder CO, 80309-0450 S. Jeffress Williams: for adding Atlantic Coast and (or) Gulf Coast data and information about the Marine Aggregates project USGS, Woods Hole Science Center 384 Woods Hole Road Woods Hole, MA 02543-1598 For more information on the USGS—the Federal source for science about the Earth, its natural and living resources, natural hazards, and the environment: World Wide Web: http://www.usgs.gov Telephone: 1-888-ASK-USGS Although this report is in the public domain, permission must be secured from the individual copyright owners to reproduce any copyrighted material contained within this report. 2 Contents Abstract .........................................................................................................................................................................6 Contents.........................................................................................................................................................................7 Introduction ...................................................................................................................................................................7 Future Plans, Updates and Online Usage in a GIS....................................................................................................8 Applications..............................................................................................................................................................8 Marine Aggregate Resources....................................................................................................................................8 National Benthic Habitats Studies.............................................................................................................................9 usSEABED Data.....................................................................................................................................................10 How usSEABED is Built........................................................................................................................................10 Sources of Data.......................................................................................................................................................11 Data Themes and Output Files................................................................................................................................11 Output files.......................................................................................................................................................... 11 Source data (SRC)............................................................................................................................................... 12 Extracted (EXT) and Parsed data(PRS).............................................................................................................. 12 Calculated data (CLC)........................................................................................................................................ 13 Component/feature (CMP) and Facies data (FAC)............................................................................................ 13 Quality Control........................................................................................................................................................14 Spatial and Temporal Uncertainties.........................................................................................................................14 dbSEABED...................................................................................................................................................................14 Introduction .............................................................................................................................................................14 Data Import Methods...............................................................................................................................................15 The Numeric Data Type ..........................................................................................................................................15 The Linguistic Data Type ........................................................................................................................................16 Calibration........................................................................................................................................................... 16 Expansion of Data Coverage ...................................................................................................................................19 Summary of the onCALCULATION methods used in dbSEABED.................................................................. 19 Data Catalog.................................................................................................................................................................23 Data Files.................................................................................................................................................................25 Sources................................................................................................................................................................. 25 usSEABED Gulf of Mexico and Caribbean Data................................................................................................ 26 Base Map Layers.................................................................................................................................................. 26 Legends................................................................................................................................................................ 26 Color .................................................................................................................................................................... 26 Roughness............................................................................................................................................................ 27 References .....................................................................................................................................................................27 Acknowledgments .........................................................................................................................................................28 Frequently Asked Questions (FAQs) about dbSEABED ..............................................................................................28 dbSEABED...............................................................................................................................................................28 Output files ...............................................................................................................................................................29 Linguistic data versus numeric data..........................................................................................................................29 3 Grain size................................................................................................................................................................29 Color.......................................................................................................................................................................30 Data import methods...............................................................................................................................................30 Data processing methods ........................................................................................................................................30 How to ....................................................................................................................................................................30 dbSEABED.............................................................................................................................................................30 What is dbSEABED?.......................................................................................................................................... 30 What kind of outputs does dbSEABED produce?............................................................................................... 30 What quality control measures are in place for dbSEABED? ............................................................................ 31 Output files ..............................................................................................................................................................31 What is the SRC file output? .............................................................................................................................. 31 What is the function of the output CMP and FAC files?.................................................................................... 31 What is the CMP file output for?........................................................................................................................ 31 What is the meaning of the data in the FAC output file?.................................................................................... 32 What do all the “-99”'s mean? ............................................................................................................................ 32 Why are there negative values for seabed strength and critical shear strength?................................................. 32 Compared to values given in some scientific papers, the output values from dbSEABED are quite rounded. Why?........................................................................................................................................... 32 What is the "Rock" membership?....................................................................................................................... 32 What is the meaning of the SeaBedClass and ClassMembership?..................................................................... 33 What is the "Weed" membership?...................................................................................................................... 33 Hydrographic Bottom Type (HBT) codes can be output. What do they mean?................................................. 33 What does the Roughness code mean? ............................................................................................................... 33 Why do some points plot on the land?................................................................................................................ 33 Can the same sample or analysis be represented more than once in the data collection? .................................. 33 Why are the Kurtosis and Skewness not reported from the database? ............................................................... 34 Linguistic data versus numeric data.........................................................................................................................34 How does dbSEABED make word data conformable with numerical data?...................................................... 34 What if a user doesn't want to use the word-based data for mappings?............................................................. 34 Which form of data should I trust more? Numeric-value analyses or word-based descriptions? ....................................................................................................................................................... 34 How does word-based descriptive data relate to numeric-value analytical data? .............................................. 34 Grain size.................................................................................................................................................................35 Why are values of grain size only given to 1 decimal place, and percent, sand etc., given as integers? .............................................................................................................................................................. 35 How are the grain sizes extracted from data? ..................................................................................................... 35 Are detailed grain size analyses used to output textural statistics like mean and sorting?................................. 35 Why would a sample that is known to have had a detailed grain size analysis not appear in the output data?................................................................................................................................................... 35 How are the outputs for the grain size fractions gravel, sand, mud extracted? .................................................. 35 Are grain size scales other that Wentworth used? .............................................................................................. 35 How is one central grain size recovered from diverse data that may present mean, median and other graphical grain sizes?.......................................................................................................................... 36 How are the central grain size and sorting estimated in the CLC process of the database?............................... 36 Data processing methods .........................................................................................................................................36 4 What is Fuzzy Logic and how does it work?...................................................................................................... 36 What is the method of attributing sub-bottom depths to samples from cores?................................................... 36 How are the shear strengths derived? ................................................................................................................. 36 What is the method for arriving at the SHEPARD and FOLK classes?............................................................. 37 What relationships are used to estimate the Critical Shear Stress values? ......................................................... 37 How are the porosity values obtained? ............................................................................................................... 37 What is the basis for the data on compressional (p-wave) sound speeds?.......................................................... 37 How are the sorting values arrived at?................................................................................................................ 38 Carbonate values: how are they arrived at? And Organic Carbon?.................................................................... 38 Data import methods................................................................................................................................................38 How does dbSEABED hold the basic data? ....................................................................................................... 38 Why does dbSEABED hold its underlying data in documents rather than a relational database like Oracle? .......................................................................................................................................... 38 What is involved in importing data sets into dbSEABED?................................................................................. 39 How is metadata treated?..................................................................................................................................... 39 Why are sediment descriptions and biological names held as abbreviations?.................................................... 39 Color........................................................................................................................................................................39 Where can I find more information on the Munsell color code?........................................................................ 39 How are the color Munsell codes derived?......................................................................................................... 39 How to .....................................................................................................................................................................40 How can I map the coded information on Color and Roughness in a GIS? ........................................................ 40 How can I use the Critical Shear Stress in a practical application?..................................................................... 40 References ...............................................................................................................................................................40 Tables A-E.....................................................................................................................................................................41 5 U.S. Geological Survey Data Series 146, usSEABED: Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) Offshore Surficial Sediment Data Release By Brian J. Buczkowski, Jane A. Reid, Chris J. Jenkins, Jamey M. Reid, S. Jeffress Williams, and James G. Flocks usSEABED data for the Gulf of Mexico and Caribbean showing locations of the extracted (EXT) and parsed (PRS) outputs. The PRS data consist of word-based descriptions. The EXT data consist of numeric, lab-based analyses. Abstract Over the past 50 years there has been an explosion in scientific interest, research effort and information gathered on the geologic sedimentary character of the United States continental margins. Data and information from thousands of publications have greatly increased our scientific understanding of the geologic origins of the shelf surface but rarely have those data been combined and integrated. This publication is the first release of the Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) coastal and offshore data from the usSEABED database. The report contains a compilation of published and previously unpublished sediment texture and other geologic data about the sea floor from diverse sources. usSEABED is an innovative database system developed to bring assorted data together in a unified database. The dbSEABED system is used to process the data. Examples of maps displaying attributes such as grain size and sediment color are included. This database contains information that is a scientific foundation for the USGS Marine Aggregate Resources and Processes Assessment and Benthic Habitats projects, and will be useful to the marine science community for other studies of the Gulf of Mexico and Caribbean continental margins. 6 CITATION: This document should be cited as: Buczkowski, B.J., Reid, J.A., Jenkins, C.J., Reid, J.M., Williams, S.J., and Flocks, J.G., 2006, usSEABED: Gulf of Mexico and Caribbean (Puerto Rico and U.S. Virgin Islands) Offshore Surficial Sediment Data Release: U.S. Geological Survey Data Series 146, version 1.0. Online at http://pubs.usgs.gov/ds/2006/146/ This publication is divided into ten sections: Home, Introduction, Content, usSEABED (data), dbSEABED (processing), Data Catalog, References, Contacts, Acknowledgments and Frequently Asked Questions. Use the navigation bar on the left to navigate to specific sections of this report. Underlined topics throughout the publication are links to more information. Links to specific and detailed information on processing and those to pages outside this report will open in a new browser window. Contents The Introduction provides a brief overview of usSEABED and its purposes and describes two USGS projects (Marine Aggregates and Benthic Habitats) for which usSEABED data are currently used. The section on usSEABED (data) describes the database, including its construction, sources of data, data themes, output files, quality control, information on spatial and temporal uncertainties within the data, as well as future plans and updates. The types and contents of the output files are explained in detail. The dbSEABED (processing) section explains the dbSEABED information processing system as it relates to data import and processing methods. It describes the differences between the numeric and linguistic data types as well as information on how accuracy can be assessed through calibrations and statistical analyses. The Data Catalog is the heart of the publication and contains the six output files (EXT, PRS, CLC, CMP, FAC and SRC). The data are presented within compressed (zip format) with the data held as shapefiles and comma delimited text files. It also includes several basemap layers for use with the data. The Data Catalog Section includes examples of how to visualize the data and two ArcView legends: Munsell color and Seabed Roughness. The References section contains the references cited. The Contacts section lists the names, and contact information for various issues such as how to contribute data, data processing questions, project related information and questions about sediment data collection or laboratory and analysis. The Acknowledgments section recognizes the many people and organizations who have contributed to this publication. The Frequently Asked Questions section provides a list of questions commonly asked by users of the data. Introduction This data release publication provides an improved and robust integrated database (usSEABED) of seabed characteristics for the Gulf of Mexico continental margin of the United States and the Caribbean (Puerto Rico and U.S. Virgin Islands) that fulfills a need for information about seabed characteristics for use by geologists, ecologists, biologists, resource managers, and national defense investigators. usSEABED provides a digital, integrated database of existing physical data and information from the sea floor, including textural, statistical, geochemical, geophysical, and compositional information. It uses the dbSEABED data mining and processing software to extend the coverage of information into areas where data coverage is more descriptive than quantitative. The data coverage includes the U.S. Gulf of Mexico waters from Port Isabel, Texas and the Mexican Border to Key West, Florida, including Lake Ponchartrain, Mobile Bay, the coastal zones of Puerto Rico and the U.S. Virgin Islands, beaches, rivers and estuaries, and extends seaward across the continental shelf and slope. More than 130 different data sources containing over 300,000 data points are currently contained in usSEABED for the Gulf of Mexico and Caribbean. The usSEABED data in DS 146 are an integral component of the Louisiana Sedimentary and Environmental Database (LASED), a combined effort of the USGS and academic researchers to assemble and manage decades of geologic data collected from studies in the Louisiana coastal zone. The development of the geodatabase is in response to a growing need for the USGS and collaborators to efficiently access coastal geologic data for coastal zone management issues. The database incorporates a wide range of data types: sediment-sample descriptions and analyses, geophysical profiles, raster -image basemaps and logbooks. The data are integrated with spatial and attribute information to provide processing and visualization capabilities using standard GIS and web browsing tools. Presently, limited functionality of LASED is available via the Internet to registered users using a standard web browser at: http://coastal.er.usgs.gov/lased/. USGS collaborators interested in accessing the LASED database can contact Jim Flocks at jflocks@usgs.gov. This data-series publication is the second in a set of similar publications that cover the entire Exclusive Economic Zone of the United States (U.S. EEZ). Available now is the companion publication of usSEABED data from the Atlantic (Reid, and others, 2005), and in press is the Pacific Margin usSEABED data set, USGS DS 182 (Reid, and others, 2006). Planned companion publications will include data for the Alaskan margin and Hawaii. 7 These publications will be updated as significant amounts of new data are included in usSEABED. This publication contains information on the usSEABED data collection, the dbSEABED program and processing, as well as a Data Catalog where the data are included (within zipfiles) as GIS layers and comma-delimited text files. The overall usSEABED database holds data for the entire U.S. EEZ and is an ongoing task of the Marine Aggregates Resources and Processes and National Benthic Habitat Studies (Pacific) projects, carried out by the USGS Coastal and Marine Geology teams in Santa Cruz, CA, Woods Hole, MA, and St. Petersburg, FL, and the University of Colorado. As a caution in using the usSEABED database in depicting seabed sedimentary character or creating sea floor geologic maps, users should be aware that all sea floor regions are by their nature dynamic environments and subject to a variety of physical processes such as erosion, winnowing, reworking and sedimentation or accretion that vary on different spatial and temporal scales. In addition, as with any such database, usSEABED is comprised of samples collected, described and analyzed by many different organizations and individuals over a span of many years, providing inherent uncertainties between data points. Plotting the data can also introduce uncertainties that are largely unknown at this time. In addition, there are uncertainties in data quality associated with both extracted data (numeric/analytical analyses) and parsed data (word-based descriptions). The authors are aware that on occasion, grain-size analyses are done solely on the sand fraction, excluding coarse fractions such as shell fragments and gravel, while word descriptions of sediment samples can emphasize or de-emphasize the proportion of fine or coarse sediment fraction, or disregard other important textural or biological components. The authors have done their best to select the best quality data for inclusion in usSEABED and encourage users to view the provided metadata files for information about individual sources' limitations, date of collection, and other pertinent information. Future Plans, Updates and Online Usage in a GIS It is expected that usSEABED will continue to expand throughout the U.S. EEZ by the incorporation of new data sets and by the utilization and mining of the data in new and different ways. As significant changes are made, we expect to reissue usSEABED as updated publications. Data contributions and (or) additional partners are welcomed. For information, please see the contacts page. Published usSEABED data from this region and others are accessible online (using ESRI® ArcIMS) at http://coastalmap.marine.usgs.gov/regional/contusa/index.html. Data layers will also be submitted for viewing and download through Geodata.gov. Applications The usSEABED database is a very large compilation, containing complex assortments of data and geologic information on the geology of the sea floor. Although this database was developed for use in conducting studies of offshore sedimentary character for assessing marine aggregates and characterizing benthic habitats, it has much greater potential for application by the marine science community and other users. Users are encouraged to generate their own queries and extract information to meet specific needs. Other potential applications for data and maps from usSEABED follow: • Research ocean observation and monitoring • Coastal zone/ocean management and planning • Homeland security, military applications • Sea floor engineering planning and design • Ocean disposal site placement, monitoring • Cultural resources • Fisheries mangement, marine protected areas • Seabed roughness, bedform distribution, critical shear stress, sediment transport flux • Public education • Sea floor bottom friction values for calibration of modeling processes, such as the effects of storm waves on sediment mobility and transport Marine Aggregate Resources Continental margins are products of complex geologic processes. They comprise submerged landforms that offer a variety of natural functions such as: benthic habitats for fisheries, navigation, home-land security, and engineering activities. Continental shelves also contain hard-mineral deposits, such as sand and gravel that are potential aggregate resources. Coastal erosion, resulting from a combination of natural processes (storms, sea-level rise, sediment starvation, land subsidence) and anthropogenic factors (dams, dredging, coastal engineering structures), is pervasive in most U.S. coastal regions. Development in the coastal zone continues to increase and demographic projections show that the trend of people moving to the coast will likely continue, placing more people and development at increasing risk from coastal hazards. With the prospects of future global climate change likely to cause changes in storminess and accelerated global sea-level rise, coastal regions are likely to experience even greater erosion, inundation, and storm-surge flooding in the near future. 8 Beach nourishment, a practice of placing sand dredged from offshore areas onto eroding beaches, is increasingly viewed as a cost-effective and environmentally acceptable method for mitigating coastal erosion, reducing storm and flooding risk, and restoring degraded coastal barrier island ecosystems for developed coasts (Williams and others, 2003). For beach nourishment to be viable, however, it is necessary to locate highquality sand; the sand bodies must ideally be reasonably close to beaches being considered for nourishment, and the sand volumes must be sufficient to meet recurring nourishment requirements for 50 years or longer. Sand bodies on inner continental shelf regions are often the most suitable sand sources for beach nourishment. Examples of marine sand bodies are shown in the following figures: Marine sand bodies, having diverse origins and evolutionary histories, can be buried or exposed on continental shelves and often have been greatly modified by marine processes associated with the Holocene transgression. Nearshore marine sand bodies of the types shown above may offer the best potential sources for high quality sand for beach nourishment. (Williams and others, 2003) Because of the increasing importance of offshore areas, comprehensive, up-to-date and integrated databases that can be used as sources for modern Geographic Information Systems (GIS) are needed to produce base maps displaying thematic information such as sea floor geology, sediment character and texture, sea floor roughness, and engineering properties. Digital geologic maps, based on unified national data sets and showing the sedimentary character of U.S. continental margins, are critical for scientists to better understand and interpret the geologic history and evolutionary processes of continental margins. These products are also useful to managers for protecting and managing coastal and marine environments (Poppe and others, 2005). The USGS, in collaboration with other Federal agencies (Navy/Office of Naval Research (ONR), Minerals Management Service (MMS), U.S. Army Corps of Engineers (USACE), National Oceanic and Atmospheric Administration (NOAA)), state agencies, and universities, is leading a nationwide effort to gather legacy marine geologic data for use in conducting assessments of offshore sand and gravel resources and for producing GIS map products of sea floor geology that can serve many additional needs. Assessments are being conducted in offshore Louisiana, the New York Bight (New York-New Jersey) (Williams and others, 2006), and the Gulf of Maine regions. The GIS maps and usSEABED database from this study are providing fresh scientific insights into the geologic character and development of U.S. continental margins and useful information about the quality and potential availability of offshore sand and gravel aggregates. Additional details are available at: http://woodshole.er.usgs.gov/project-pages/aggregates/index.htm. National Benthic Habitats Studies The quality and protection of natural environments is a high priority for the Nation. This includes Federal lands in the coastal and marine realm where a variety of human activities stress natural systems and resources. The 9 USGS is a lead scientific agency conducting research on the Atlantic, Gulf of Mexico, and Pacific margins to better understand marine sea floor environments. This research on benthic habitats is conducted under the general topic of “habitat geoscience,” which is defined as the study and classification of seabed habitats in the context of their geologic framework, their response to seabed processes, and their function as substrate for invertebrates and fish, is underway in all three regions. This research requires close collaboration between geologists, biologists, and oceanographers. High-resolution and detailed knowledge of bottom characteristics and sediment distribution, a goal of the usSEABED database, is fundamental to these studies. Habitat research in the Gulf of Mexico is presently conducted within and offshore Tampa Bay and the Suwannee River Basin, Florida, in Mobile Bay, in the Texas-Louisiana Shelf, in Pulley Ridge, and in Flower Garden Banks National Marine Sanctuary in collaboration with many Federal and State agencies and academic institutions. Habitat studies are based on high-resolution sea floor imagery (bathymetry, backscatter) and groundtruth data (video and photo imagery, and geological and biological samples). These data sets are used to produce interpretive maps that show surficial and subsurface geology, habitats as classified into different ecologic types, the distribution of fauna and flora, and the effects of seabed processes. Applications of research results include fishery management, habitat disturbance and recovery studies, impacts of invasive species, studies of deep-water coral habitats, the fates of contaminants from coastal sources, location and monitoring of disposal sites, the routes of cables and pipelines on the seabed, and the location of aggregate deposits having potential for use for beach nourishment. For more information on benthic habitat studies, see: http://marine.usgs.gov/, http://woodshole.er.usgs.gov/, and http://walrus.wr.usgs.gov/nearshorehab/. usSEABED Data The usSEABED database differs from a traditional relational database (RDB) because the data are processed and extended to maximize density and usability, making them more comprehensive for mapping and analysis. A traditional RDB often creates simplistic and sparse data summary coverages with thinly populated and unwieldy tables. The usSEABED database not only treats the usual forms of numerical data, but it also contains a vast store of data about the sea floor in word-based descriptions that can be rich in information, but difficult to quantify, map, plot, or use in comparative analyses or models. The usSEABED database provides numeric values for typical seabed characteristics that are based on these descriptive data as well as numeric analytical data. The usSEABED database also differs from other marine databases in that it incorporates a wide variety of information about sea floor sediment texture, composition, color, biota, and rocks, sea floor characteristics such as hardness or sediment ripples, acoustic properties, and geochemical and geotechnical analyses. The usSEABED output files are produced in comma-delimited text for ease of use in many software applications, and are ready for inclusion into many different GIS, RDB and other software applications. How usSEABED is Built The usSEABED database is built using the dbSEABED processing software created at the University of Sydney (Australia) and the University of Colorado. It has companion databases built along similar lines: auSEABED for Australia, balticSEABED, and a global database, goSEABED. Each of these databases relies on pre- existing data from a variety of sources to mine and extrapolate useful information about the seabed. The dbSEABED program allows these source data sets to be compiled in a standardized format and integrates information across a series of data themes (Table A) and equipment: physical sampling equipment (grabs, cores, or probes) or remotely sensed sampling (photographs, videos, geophysics, soundings). These data may be numeric lab- or instrument-based textural, acoustic, geochemical, and geophysical data and (or) verbal (linguistic) descriptions of grabs, cores, or photographs, or a combination of any of these. In the usSEABED database, most data held in these reports are queried for additional information that increases the data density over the seabed, allowing for more complete information. Few source reports contain all data reportable in usSEABED; null values are given in those fields that do not contain reliable information. 10 Sources of Data The usSEABED database relies on previously existing and newly collected data, both published and unpublished, from federal, state, regional, and local agencies and consortiums, as well as research institutions. For the Gulf of Mexico and Caribbean, many of the data are from the USGS, including the previously published continental margins data from the early 1960s, and more recent (1990s, 2000s) data published by the USGS. Data gathered by NOAA/ the National Ocean Service (NOS) during their many sounding surveys during the 1960s to 1990s are included, as archived by the Smithsonian Institution and provided by the National Geophysical Data Center (NGDC). USACE reports, including several from the USACE Coastal Hydraulics Laboratory (formerly CERC), Environmental Protection Agency (EPA) data sets, educational institutions' reports and theses, State geological survey reports, and NOAA reports are also included. Two large data compilations archived at NGDC are included: the '073' data compilation, which is primarily from U.S. Navy reports, and the Deck41 data set, which is from a wide variety of data sources. A complete reference list (gmx_sources.html) of information for the Gulf of Mexico and Caribbean is included. Data duplication may exist within the input Gulf of Mexico and Caribbean data sets. Data from the same cruise or site may be published in more than one report or data compilation. Efforts have been made to reduce data duplications in usSEABED. In other instances, data from different sources for a given site may be included if significant additional data are included (for example, one source may report only grain size for a particular site, but another source may include geophysical properties for the same sites/sample). Data Themes and Output Files Seabed data come in a variety of forms, which have information in different parameters. For example, textural analyses may have information for percentages of gravel, sand, mud (silt and clay); statistical measurements such as mean, median, sorting, skewness, and kurtosis often accompany the textural information. Acoustical measurements include various velocities and derived densities. Benthic habitat studies may include a short description of the sea floor sediment type and a numerical survey of animals and plants on the sea floor, or evidence of them. The original seabed information in usSEABED is entered into different data themes. A list of data themes is given in Table A. The thematic basis of the values found in the outputs can be found in field 11 (' DataType' ) of the extracted (EXT), parsed (PRS), and calculated (CLC) output files. Information on the contribution of each source report is in the accompanying metadata files. Output Files This publication provides six usSEABED output data files for the Gulf of Mexico and Caribbean. usSEABED Output files EXT Extracted (numeric, lab-based) PRS Parsed (word-based) CLC Calculated (calculated variables) CMP Components (content and features) FAC Facies (components only) SRC Source 11 These files are downloadable from the Data Catalog. An additional output file type, although unpublished, provides quality control for the data and was used extensively prior to publication to debug and test the data. Field parameters for the data files are listed in Table B. Relational keys The usSEABED data file types are linked relationally by the foreign keys: DataSetKey (for individual data sets), SiteKey (for individual sites), and the SampleKey (for individual analyses). The DataSetKey field gives the relationship of the data to the original source. The tables can be loaded into a RDB, relationships may be constructed, and the tables may be joined using the keys. Source data (SRC) Information about the original data are in the source (SRC) file, including links to metadata about the original data. Each of the output data files discussed below is linked to the SRC file by the DataSetKey field. Textural and other basic information (EXT, PRS, CLC) Textural, statistical, geochemical, geophysical, dominant component, and color information are held in three separate, but similar, data files, based on the type of data: EXT, PRS, CLC. The three data file types have the same fields (Table B) and can be combined for more extensive coverage of the sea floor. It is important for users to understand the inherent limitations of each type of file in order to choose the best data file, or combination of data files appropriate for a particular use. Other dbSEABED programs can combine the three files in a variety of ways, by concatenation or by telescoping, before they are mapped or used for other types of analysis. For access to these files, please see contact page. Extracted data (EXT) The data file with the EXT tag is the "extracted" data: those data from strictly performed, lab-based, numeric analyses. Most data in this file are listed as reported by the source data report; only minor unit changes are performed or assumptions may be made about the thickness of the sediment analyzed based on the sampler type. Typical data themes include textural classes and statistics (TXR: i.e., gravel, sand, silt, clay, mud, and various statistics), phi grain-size classes (GRZ), chemical composition (CMP), acoustic measurements (ACU), color (COL), and geotechnical parameters (GTC). The EXT file is based on rigorous lab-determined values and form the most reliable data sets. Limitations however exist due to the uncertainty of the sample tested. For example, were the analyses performed on whole samples or only on the matrix, possibly ignoring larger particles? Parsed data (PRS) Numeric data obtained from verbal logs from core descriptions, shipboard notes, and (or) photographic descriptions are held in the parsed data set (PRS). The input data are maintained using the terms employed by the original researchers and are coded using phonetically sensible terms for easier processing by dbSEABED. Longer descriptions may have the data divided by theme (Table A). The descriptions often include information on associated biota, sea floor features, and structure. Typical data themes for the parsed data set are lithologic descriptions (LTH), biology (BIO), color (COL), and (or) sea floor type (SFT, descriptions from photos or videos). The values in the parsed data file are calculated using the dbSEABED parser that assigns field values based on the form and content of a description. See the section on dbSEABED processing and fuzzy set theory for a more complete explanation. The parsing process has been tested and calibrated by comparing the outputs against analytical results for the same samples. Due to the nature of visual descriptions by observers and the use of fuzzy set theory in the parser, the output data variously show the degree of representation in the sample, or percent abundance values. An assumption in the process is that the output degrees of representation reflect absolute abundances to some degree of accuracy. The calibrations provide information on that accuracy. Although at first sight the descriptive results in the parsed file may seem less accurate than measured values in the extracted file, they are frequently more representative of the sample and seabed as a whole, as they include description of objects such as shells, stones, algae, and other objects (Table C) that are a textural component of the seabed and which are often left out of laboratory analyses, particularly when a machine analysis is employed. 12 Calculated data (CLC) For the extracted and parsed data, some values are not reported by the original source, but can be calculated directly or estimated by standard derivative equations using assumptions (See Frequently Asked Questions) about the conditions or variables. These values are reported in the calculated (CLC) data files. Although the calculated (CLC) data can be combined with the extracted and the parsed (Table B), they are the least reliable of the three data file types and should be used with caution. Component/feature and Facies data (CMP, FAC) Two usSEABED data files contain information about the presence of certain sea floor features, compositional content, biota, and sediment structure. These files use major synonyms defined by the thesaurus in the dbSEABED parsing software, which clusters comparable descriptive terms together, i.e., granite represents granite, aplite, granodiorite, pegmatite, while laminated represents laminated, laminations, or lamina. Individual components and features (i.e., terms like feldspar, phosphorite, bivalves, seagrass, and wood) are held in the CMP data file (Table D). Appropriately combined components are held in the 'facies' (FAC) data files (Table E). As with the parsed data files, the values held within the CMP and FAC files are the results of filters based on fuzzy set membership to chosen sets, and represent a measure of truth about the attribute, not percentages or defined values. These files only indicate presence, not absence, of material; e.g., it is rare that a report might state, "no bivalves" or "no phosphorite". The CMP file contains information about compositional content (individual minerals, rocks), genesis (terrigenous, carbonate), and certain biota. These components are internally evaluated and the value for each attribute is based solely on the relationships of attributes within the original description. The flora and fauna included in the compositional components are those that may have an effect on textural determinations in the PRS data file, such as halimeda, bivalves, or foraminifera (Table C). The values within these attribute fields range between 0 (no membership, probably due to no information), to 100 (complete membership, i.e., shell hash = 100 to the shell debris set). The CMP file also includes information on sea floor features such as bedforms, fissures, internal structure (bedding, bioturbation), and other flora and fauna. Unlike the compositional content information, which is construed as an abundance within the sample, these attributes are an intensity of development or density of occurrence relative to scales of development or density of occurrence observed elsewhere. The flora and fauna included in the feature category are soft-bodied, for example those that do not have an input on the textural determination within the PRS data files, such as kelp, ophiuroids, or annelids. Values within the attribute fields range from 0 (no membership, possibly due to no information) up to 100% (maximum development). In contrast to the situation with component abundances, the sum of feature intensities in a sample is allowed to exceed 100%. The 100 most common components (number limited by dbSEABED processing software) in the U.S. EEZ are given in the CMP file, and those attributes with "_F" denote features. Table D lists the components and gives basic forms of descriptive terms that may trigger membership for each. Included in this file are 27 components that are included in the facies (FAC) file only. The dbSEABED thesaurus used for usSEABED is also used for the sister data compilations (auSEABED, BalticSEABED, goSEABED), and the list of trigger terms may include some that are not known in U.S. waters. The second file, the facies file (FAC), is created from components only, similar to the CMP file. This file configures multiple components into appropriate groups or facies, such as igneous, metamorphic, ooze, foraminifera, and others. The dbSEABED processing software is restricted to a maximum of six components per facies. Table E lists the facies type and the components that comprise each facies group. Again, these files only indicate presence, not absence, of material; e.g., it is rare that a report might state, "no bivalves" or "no phosphorite". The values within this attribute field range between 0 (no membership, probably due to no information), to 100 (complete membership, for example, schist = 100 to the metamorphic set). Relationship between the PRS and CMP outputs 13 The dbSEABED processing software recognizes that many skeletonized biota, such as halimeda, rhodoliths, shells (broken and unbroken), and others often comprise a sediment sample. Such biological terms are included in the parsing of the textural values. To see the selected biota with textural implications, see Table C . When using the parsed data, it may be important to cross-check with the component file using the relational foreign keys (SiteKey, SampleKey) to determine if biota are to be included in the textural outputs. Within the PRS file, the "seabed class" and "class membership" fields indicate the dominant compositional class and the fuzzy set membership of a sample to that class. Other components and mined information may also be listed for that sample in the CMP file, linked by the relational keys. Quality Control Quality control over the data is an iterative process implemented using criteria in the following steps. First, graphical plots of site locations and parameter values are used to detect outliers and edit them appropriately. Each data set is viewed in a GIS to ensure that data locations are reasonable relative to survey extents; those sites with unresolvable location issues or known incomplete analyses are deactivated and are not included in the usSEABED output files. (Note: usSEABED does contain a small number of onshore samples.) This step may be optional depending on the data set. Older sets may require more scrutiny at this step whereas newer or well exercised data sets require less. Second, built-in filters in the dbSEABED processing software detect implausible values for numeric fields, unknown verbal terms, incomplete analyses (i.e., Gravel-Sand-Silt Clay (mud) (GSSC(m)) greater than 100% or less than 95%), and incorrect field types (string or number). The software also detects samples that seem to belong to a core though they are described as independent samples. For the parsing of verbal descriptions, all terms must be known to the dbSEABED data processing program, with values assigned; those analyses that fail this test have null values given to all appropriate fields. Edits are made to the data (i.e., at the level of the usSEABED input data files) and metadata are entered explaining the changes. The edits (or deactivations) are then taken into account in the next dbSEABED program run. Finally, output data are analyzed in a GIS to test whether the data outputs "make sense" for a given geographic area. Users of the output data should, however, note the limitations imposed by the source data sets as to navigational precision, sampler type, and analytical technique. See the dbSEABED section and the Frequently Asked Questions for details about the usSEABED data mining program and the application of fuzzy set theory. As issues about the data or the data processing may be discovered, errata will be posted on the usSEABED website. Corrections will be included in the next version of the publication. Spatial and Temporal Uncertainties Users of usSEABED data are reminded that many sea floor regions are, by their nature, dynamic environments subject to a variety of physical processes, such as erosion, winnowing, reworking, and sedimentation or accretion that vary on different spatial and temporal scales, and sea-floor samples may represent a only moment in time. Although usSEABED is comprised of samples collected, described, and analyzed by many different organizations and individuals over a span of years, metadata are provided for each source report, linked through the list of data sources, and DataSetKey field in the output files. In cases where original metadata are not available from the data source, metadata were created based on available information accompanying the data. Of particular importance, site locations are as given in the original sources, with uncertainties due to navigational techniques and datums ignored in the usSEABED compilation. As many reports are decades old, users of usSEABED should use their own criteria to determine the appropriateness of data from each source report for their particular purpose and scale of interest. In addition, there are uncertainties in data quality associated with both the extracted data (from lab-based analytical analyses) and parsed data (word-based descriptions). It may be that grain-size analyses are done solely on the sand fraction, excluding coarser material, such as shell fragments and gravel, while word descriptions of sediment samples may emphasize or de-emphasize the proportion of fine or coarse sediment fraction or disregard other important textural or biological components. Detailed information about issues such as these are noted in the source metadata files, and known incomplete data are decommissioned in usSEABED. Users are encouraged to view the entire document before downloading the data files in the Data Catalog and should refer to the provided metadata files for information about individual sources' limitations, date of collection, and other pertinent information. dbSEABED Introduction The dbSEABED processing system was developed by Jenkins (1997, 2002, 2003) in collaboration with the USGS and others over the past decade. Currently, there is no open-source code for the program. This explanation of the system is intended to give information and guidance about how the data are compiled, integrated, and processed in the usSEABED database. 14 The dbSEABED system aims to produce a unified mappable database from the multitude of data sets dealing with the seabed. The primary objective of the dbSEABED system is to produce integrated data that can be mapped, analyzed, and visualized. Data sets include both legacy and modern collections, involving data from samplings, and visual inspections. Filtering routines within dbSEABED unify marine geologic data that originally may be disparate in purpose, function, style, and collection or analytical techniques. It works on data files that hold the source data in their original values (except for minor unit changes and phonetically sensible word codes) and provides standardized output data. It is important that users of the PRS and CLC output files understand the parsing process, the meanings of field values, and the limitations of the usSEABED output. More information about the dbSEABED software can be found on the dbSEABED Web site or in the Frequently Asked Questions section of this publication. Data Import Methods Incoming data files number in the hundreds and are diverse in content and format. The process of import begins with manual re-formatting, which usually involves rearranging the data in columns specific to each parameter, such as color, percent sand, seabed description, or multisensor core logger acoustic velocities. These columns are arranged according to a template specific to dbSEABED. Most data are pre-arranged by columns, but in some cases sections of prose may need to be cut into their constituent parts. New parameters are sometimes encountered as a data set is imported. These new parameters are added to the template at the ends of the appropriate data theme, and the dbSEABED processing software is modified to take the new parameter(s) into account if possible. For future reference and to help editing, the original data are often held as commentary metadata alongside the active data. Some data that are not useful to dbSEABED are held only as commentary metadata. After import, the data are held in a type of written log arranged according to the nested sequence: data set/ site/ subbottom depth/ subsample. Sites are specified by each new sampling operation. The written log structure is unusual for a database, having more in common with XML-format structure than relational databases. It has distinct advantages for dealing with sea floor sampling data sets, such as: (i) an algorithm can perform highly useful calculations on the data for each sample, which has made it possible to meet user demands in a timely way despite the complexity and size of the data holdings (ii) data that are human readable, especially if metadata are interspersed (iii) it conforms with data structures that are generated by core-loggers at sea and in the laboratory (iv) it is efficient to import (v) it is able to cope with variable data quality and incompleteness (vi) it is low maintenance, nonproprietary, and programs that address it have low cost of entry and are highly adaptable. The disadvantage of the written log structure is that specialized programs such as those in dbSEABED are needed for conversion to the flat-file formats that most users require. These flat-file formats are provided in this publication. The Numeric Data Type A primary function of the processing programs is to read, quality-check, and then report numerical data that have been obtained from laboratory analyses of grain size, composition, color, shear strength and other parameters. Although we describe these data as "numeric," it also includes coded data such as Munsell color codes. In many cases, the numeric data can be echoed unchanged to outputs (in EXT files), for instance, in percent sand, average grain sizes, carbonate, and porosities. Checks are performed, however, on whether a value is properly numeric or string, and if it is within plausible ranges. Problems are reported to a diagnostics file that is a basis for quality and completeness checks, with possible corrective edits to the data file (along with explanatory metadata). Data items are often deactivated if they are suspected as incorrect. The numeric data output to EXT files have had minimal manipulation. The data in grain size analyses (held at their original phi intervals) are summed into gravel, sand, silt, and clay percentages; the median, average 15 and standard deviations are calculated. If grain density is available, bulk densities and water contents are converted to porosities, with the porosity parameter adopted by dbSEABED. Many parameters that are available in the data are not reported to the EXT files, for instance skewness and kurtosis. They may however be obtained from RDB renderings of the data (not available on this publication). The dbSEABED output of Central Grain size is a composite of median (preferred), moment average, and graphical averages. Currently, only the second moment (standard deviation) is directly transferred to the sorting field. The reporting of consistent mappable values for geotechnical and acoustic parameters is not an easy task. The results of physical property tests are very dependent on experimental setup, such as strain rates, sample preparation, equipment dimensions, and detection of behavioral thresholds for the materials. The shear strength reported from dbSEABED is a composite of penetrometer and vane shear values (undrained, unconfined) in the un- remolded states (i.e., for initial failure). Also included for the sake of maximizing mappability are the cohesions from shear box and low-pressure triaxial experiments. P-wave acoustic velocities are reported without regard to the frequencies of measurement. In both cases investigators wanting more specific information on the analyses can refer to the original data and metadata. The extracted outputs based on numeric and coded data are put out separately from the parsed and calculated results of dbSEABED. It is recognized that some investigators will choose one over the other - or may wish to combine them in different ways. It must also be recognized that rarely can a sensible coverage of the seabed be obtained from the extracted data alone, as it is too sparse. The Linguistic Data Type A feature of dbSEABED is its ability to parse word-based descriptive data such as "brown fine sand with abundant shells; seagrass and some pebbles; whiff of h2s". These types of data are held using their original terms although some abbreviation and coding is necessary. Thus dbSEABED is not a natural language parser even for the noun phrase constructions, such as the above description. The ability to handle word-based data greatly extends the power of the system to map the seabed, because on a global average, approximately 85% or more of data characterizing the seabed are word based. Calibrations are performed to validate this process relative to analytical data on the same sediments. A simplified description of the parsing functions is included in this publication. The dbSEABED program applies these concepts to geological descriptions, using: • a parser that divides the descriptions into arithmetic equations • a thesaurus that attaches meanings and memberships to the quantifiers, modifiers, and objects • a linear weighted assembly of the numerical totals In the dbSEABED program, word memberships can be defined across many parameters, not just grain size. Fuzzy memberships are best thought of as a measure of truth or possibility (note: not probability). The outputs are fuzzy memberships of parameters such as mud, grain sizes, carbonate, organic carbon, grain types, sedimentary features, rock and weed coverages, and engineering strengths. Statistical comparisons can be made between the EXT and PRS data outputs, resulting in calibrations which are an overall guide to the accuracy of the regional mappings, and a highlighting of areas and issues in the data where improvements can be made. Calibration dbSEABED is an information processing system, that can perform statistical and individual tests of accuracy across the range of output parameters. Issues of accuracy and reliability become apparent as soon as data are integrated. Tools for monitoring the integration process are required, with feedback to the input data, so that improvements can be made in the system. Basic uncertainties exist in all the incoming data that cannot be reduced and integrative systems cannot proceed past that uncertainty. Parallel studies in dbSEABED have determined on the basis of replicate analyses that analytical data such as grain size analyses (Syvitski and others, 1991) has 1-sigma uncertainties on the order of 4% of the total parameter range, or 0.8 phi. With good maintenance of the data, the outputs from dbSEABED approach those levels of reliability. 16 Statistical Tests In the case of the thousands of samples where both analytical and descriptive data exists, a statistical comparison can be made between the EXT and PRS data outputs. The results of this calibration are an overall guide to the accuracy of the regional mappings, and a highlighting of areas and issues in the data where improvements can be made. Those improvements involve both the analytical and descriptive raw input data. For example, grain size analyses that appear to be the whole sediment, but are actually the sand fraction or analyses where gravel / shell have been omitted from an analysis. The EXT and PRS outputs are imported into MS Access and links are created between the two files (based usually on the SampleKey). Entries with null values (-99) in either EXT or PRS are eliminated through a query. This query is brought into MS Excel and used to calculate the frequency distribution of deviations (+ and absolute) and plotted for inspection. Percentile statistics are calculated using the absolute deviation at the 50% (Median Absolute Deviation (MAD)), 68% and 95% percentiles (1s, 2s). Examples of the outputs are shown in the description of usSEABED. For most data sets the percentile statistics are 0.4, 0.8 and 4 phi for the 50, 68, and 95% levels, which may be acceptable over such a diverse set of input data sets but can be improved. An example of this analysis is shown in Figure 1 for a data set which is under improvement. Figure 1. Statistical calibration of outputs for grain sizes, shown using a frequency plot of the deviations between PRS and EXT data, using the improving Atlantic data set. Deviations are the result of inaccuracies in EXT and PRS input data, as well as to identifiable issues in the data as highlighted below and in Fig. 2. The 50, 68, and 95 percentile confidences are 0.8, 1.3, 4.3 phi, respectively. A second way of statistically evaluating the results uses a cross-plot between the EXT and PRS output data in the figure below. This type of plot serves to highlight some of the issues that may reduce the accuracy of dbSEABED with incoming data sets. At the locations A-D these common issues are identified in populations of points: • PRS coarser than GRZ, apparently due to outsized shells/ clasts being omitted from lab grain size analyses; • sediment described as very fine in PRS, but only the sand fraction is represented by the EXT analysis data; • detailed analyses of grain sizes does not go beyond coarsest class of about -2.5 phi; • descriptive PRS data does not distinguish grades of sand, and is apparently dominated by reports of very large clasts, such as cobbles or shell, that were not analyzed. 17 Figure 2. Cross-plot of the EXT and PRS output data for a region, not in US waters. A-D represent populations of data that have commonly encountered problems. With the detection and fixing of these problems the accuracy of outputs is substantially improved over that shown here. Notice that overall PRS extend further in coarse grades, and EXT further in fine grades, reflecting their common observational biases. Individual Tests The programs of dbSEABED have been equipped to detect problematic data, whether by values falling outside plausible limits, or by mismatches between EXT and PRS results. These tools normally do not prevent the problem values being output, but they do report detections to a diagnostics file that is particularly useful in the preparation and cleaning of incoming data sets. The statistical data shown in Figure 1 is employed to set the filters, usually at the 68% (1s) level. The original data can then be revisited, checked for issues such as those shown in Figure 2, and can be corrected, deactivated or left alone as appropriate. 18 Expansion of Data Coverage A summary of the theoretical or empirical relationships that are used by dbSEABED to expand the coverages of seabed parameters (often not directly measured or calculated in individual reports) is given in the onCALCULATION document. Summary of the onCALCULATION Methods Used in dbSEABED The module onCALCULATE performs a small amount of modeling to extend the outputs of dbSEABED to reasonable estimates of sea floor properties. This is particularly useful for geoacoustic and other physical properties which have no practical mappable data distribution based on actual analyses. The modeling is based on theoretical or empirical relations that are documented below. The chosen relationships may be replaced by others in the future as further physical properties research is published and onCALCULATION results are validated. Users of dbSEABED may choose whether to use these lower accuracy estimates in mappings or to work with map data coverages that are less reliable because they contain fewer data. A couple of principles have guided the selection of relationships and their implementation: (a) the methods should be transparent, well documented, and not complex; (b) they may be built on extracted or parsed parameter inputs but not on values that are themselves onCALCULATED; (c) they might apply only to certain sections of the input parameter range; (d) they preferably are published relationships, but if not then (e) should be supported by the analysis of a substantial amount of data from a wide range of sediments. The modelling methods that are currently implemented are: 1. Grain size / Sorting from Gravel:Sand:Silt:Clay and Gravel:Sand:Mud Ratios Gvl:Snd:Slt:Cly and Gvl:Snd:Mud (GSSC, GSM) ratios are in effect short grain size-fraction histograms for the sediments. An estimate of AV and SD grain size can be made from them as follows. Each class is assigned a central grain size value based on examinations of large USGS and other data sets in Excel. These GSSC(M) class central values result: -3, 2, 5, 7, (8) in phi. A weighted mean and weighted standard deviation are formed across the GSSC or GSM classes, leading to an estimate of the average grain size and sorting of the sediment. A method of validation and uncertainty calculation is available by comparison of the results for samples where a mean/ sorting is already measured. 2. Hydrographic Chart Bottom Type code This code, described in UKHO (2005) and NOS (1997), has the form "Cy.S.Co", and is essentially the same as the US NOS codes. The calculation is mostly a matter of assigning textural classes in front-significant order based on the GSSC(M) ratios, but also with special classes "R", "Wd" where rock and weed memberships are significant. Thus, the output codes are minimal codes. 3. Folk and Shepard Classifications These classifications for grain size have been implemented following the schemes in Poppe and others (2000). 4. P-wave Velocities for Consolidated Materials Based on Time-Average Model This calculation is performed only where there is an indication of cementation or consolidation in the material, usually expressed by measured or parsed Shear Strength >50 kPa or porosity <35%, and where the porosity has been measured. Then: mVp = (1 - Poros) / VelSol + Poros / VelFlu where Poros is the fractional porosity of the material and VelSol and VelFlu are the solid and fluid phase P-wave velocities. The constants are: VelSol = 5000, VelFlu = 1520 (these are measured values, different from those optimized for models such as Biot Theory; see Thorsos and others (2001)). The relation is associated with data over the whole range of porosities ( Fig. 3). The time average model is attributed to Wyllie and others (1963). 19 Figure 3. The distribution of sediments by their Porosity and P- and S-wave Velocity values. Several separate populations are apparent. For P-wave velocities, the loose sediments with low velocities from 34% porosity and following the Gassmann function; consolidated sediments following the Time-average relation; apparently cemented sediments with anomalously high velocities for the porosity. The S-wave populations have yet to be explained. 5. Porosity Based on Mud Content of Loose Sediments A compilation of many published analysis results (Fig. 4) supports the empirical relationship: mPor = 0.4 * mud + 43 for mud% > 7%. It appears to hold equally for terrigenous and carbonate sediments. Figure 4 illustrates the relationship for sediments of the Mississippi-Alabama-Florida (MAFLA) shelf. 20 Figure 4. Empirical data supporting the Mud%-Porosity relation where mud fraction is >7%. The plotted data are a mix of terrigenous, carbonate, loose and consolidated samples, Mississippi-Alabama-Florida (MAFLA) shelf. 6. Porosity Based on Average Grain size Richardson and Briggs (1993) proposed a relationship between porosity and average grain size (AvGrsz, phi units) based on their measurements of muddy and sandy sediments. The relation is inverted for the onCALCULATION, and is applied only in the range AvGrsz > 0 phi: Por = 26.92 + 5.92 * AvGrsz The form is less accurate than methods where the percent of mud is known, and is not used in those cases. 7. Coarse Fraction and the P-wave Velocity Related to the porosity-mud fraction function is another between coarse fraction and Vp: mVp = 0.0009 * SpG³ + -0.14 * SpG² + 8.56 * SpG + 1512.76 where SpG is the percent coarse fraction. This polynomial is a poor fit and further work is required. 8. Wood-Gassmann Equation for P-wave Velocity in Loose Sediments This method of estimating Vp is applied to sediments with no evidence of consolidation. It depends on assumed values for some acoustic constants of the sediments: (a) the Bulk Moduli K for solid, fluid, frame (Ko1Sol, Ko1Flu and Ko1Fra 3.6E+10, 2E+09 and 4E+08, MKS units); and (b) the Rigidities for solids and frame (RigidSol, RigidFra 2.2E+07, 1E+07). The sediment Bulk Modulus and Density are: Ko1 = (1-fPor)/Ko1Sol + fPor/Ko1Flu SedDens = (1-fPor)*DenSol + fPor*DensFlu . And the p-wave velocity is calculated as: Qgass=Ko1Flu*(Ko1Sol-Ko1Fra) (fPor*(Ko1Sol-Ko1Flu)) Kgass=Ko1Sol*(Ko1Fra+Qgass)/(Ko1Sol-Qgass) VPgass=√(Kgass+4/3*RigidFra )/SedDens) Gassmann (1951). VPgass is output as the estimate of Vp. 21 The Wood-Gassmann relation is one of several that have been proposed between porosity and the acoustic velocities. As can be seen on Figure 3, the relation has an associated population of data ranging only between 35-80% porosity. In the dbSEABED on-calculation it is applied only where porosity is known and >35%, and where there is no indication of consolidation. 9. Roughness from Grain Protrusion for Gravels and Coarser Kirchner and others (1990) offer a method for the calculation of grain protrusion (PnKir) above a sediment surface: EnKir=0.5*(DnKir-D50Kir+(DnKir+D50Kir)*cos(F100nKir)) PnKir=EnKir+pi*D50Kir/12 where D50Kir and DnKir are the median and nth percentile grain sizes, and F100nKir is the Friction angle with a test grain of the 100-nth grain size percentile. In onCALCULATION, the estimation is done only using the central and the coarsest grain sizes (CSESTsz; either PRS or EXT) for D50Kir and DnKir. PnKir is output as an estimate of roughness. 10. Roughness Metric from Outsized Clasts This metric was employed as an early measure of seabed roughness; it is based on an idealized arrangement of the sediment clasts and particles. The coarsest grain size is logged from previous processing of grain size analysis and descriptive data inputs or is estimated from the average plus 2 times the SD (sorting) where both are known. The vertical roughness is estimated as half the clast size (D) with allowance for natural oblateness: dZ=0.5 * D * CSF where CSF is the Corey Shape Factor to account for non-sphereicity. (In naturally worn materials CSF is about 0.7; e.g., Jimenez and Madsen 2003.) The spacing of the clast grain size is assessed as half the repeat distance implied by the fractional linear abundance PL of the outsized clast with size D. Linear abundance is related to areal and volume (most common) abundances PA and PV as: PL=PA 1/2, PL=PV 1/3 . The clast protrusion and half-spacing are output as the vertical and horizontal roughness scales. 11. Critical Shear Stress If the material shows evidence of consolidation, then the Critical Shear Stress (CSS, N/m²) is set equal to the reported Shear Strength (kPa). Whitehouse and others (2000, p. 27) discuss the relationship, which is interim in the onCALCULATION. For loose sediments, the functions related to grain size (AvGRZ) were investigated on the basis of data from many studies (Fig. 3). This work was done in conjunction with IOW, in Germany. The conclusions were: (i) with-fine grained loose sediments where density or porosity are known, use the relationship of Mitchener, and others (1996, in Whitehouse, and others (2000)); (ii) else for those sediments use a generalized value of 0.5 N/m²; (iii) for loose coarse grained sediments use a log-linear relationship as shown in Fig. 3, log10(CSS)=log10[1.04-AvGRZ*0.6]. Bioturbation and bioconsolidation were not recognized in the estimation process for fine sediments, though they can be important (see Black, and others (2002)). A correction of minor importance compared to the overall uncertainties is applied in the onCALCULATION. 22 Figure 5. A compilation of Critical Shear Stress results by sediment grain size over the gravel to clay range. Over 24 references were used referring to marine and river sediments, field and laboratory experiments, on unaltered and manipulated natural sediments Data Catalog The data supplied on this CD-ROM are made available with geographic coordinates to allow the data to be incorporated into a Geographic Information System (GIS). The data layers along with additional base map layers have been compiled into an ArcViewTM project file (usSEABED_GoMex.apr), which is located at the top-level directory of this publication. The project file serves to provide an example of how the data can be displayed in a GIS. It contains several views including one which shows the Munsell Color legend on the PRS data. A variety of basemap layers that can be used to accompany these data can be found on the Coastal and Marine Geology Program's U.S. Gulf of Mexico Region Map Server (http://coastalmap.marine.usgs.gov/regional/contusa/gomex/index.html). Several have been included below and are used in the project file. Other examples of ways to visualize these data are also included below: 23 Example 1. Munsell Color using the extracted (EXT) and parsed (PRS) outputs, Mississippi Fan and Louisiana region. Example 2. Grain size (phi) using the extracted (EXT) output, Louisiana to Alabama region. 24 Example 3. Sand content using the extracted (EXT) output file, West Florida Shelf. For those who do not have the ESRI software or a compatible GIS data browser available on their computer, a free viewer, ArcExplorer, is available from ESRI . Please note that the ArcExplorer software is limited to the Microsoft Windows operating systems. Clicking on the layer name under the column header "Data Layer Name & Description" in the table below will open a new window with a graphical representation of that layer. Federal Geographic Data Committee (FGDC) metadata are included with data layers in three formats in the table below: (HTML, FAQ, and text). A downloadable zip archive file containing the elements that comprise the ArcView shapefile for each data layer is also provided. Each zip file includes: 1. ArcView shapefile for each layer (with associated files) 2. comma-delimited text version of the data file 3. all three versions of the metadata 4. browse graphic of the data layer The zip files were created using WinZip v. 8.1. Users may obtain a free copy of the software from http://www.winzip.com. In addition to the ArcView shapefile, the usSEABED data layers are available in an ASCII text format as an alternate way to view and examine the data sets. The first record of the ASCII file contains the name of the data fields for that file. Data Files Sources GMX_SRC – A comma-delimited text file containing a list of sources included in the output files. Also included is a list of all sources of data with links to associated metadata where available. Clicking on the DataSetKey will open a new window showing a browse graphic of that particular data set. Clicking on the DataSet name will open a new window showing the HTML metadata for that particular data set. 25 usSEABED Gulf of Mexico and Caribbean Data Data Layer Name & Description Metadata Files File Size gmx_ext - usSEABED extracted data for the entire Gulf of Mexico and Caribbean HTML FAQ txt gmx_ext.zip 2.51 MB gmx_prs - usSEABED parsed data for the entire Gulf of Mexico and Caribbean HTML FAQ txt gmx_prs.zip 3.45 MB gmx_clc - usSEABED calculated data for the entire Gulf of Mexico and Caribbean HTML FAQ txt gmx_clc.zip 5.48 MB gmx_cmp - usSEABED component data for the entire Gulf of Mexico and Caribbean HTML FAQ txt gmx_cmp.zip 4.19 MB gmx_fac - usSEABED facies data for the entire Gulf of Mexico and Caribbean HTML FAQ txt gmx_fac.zip 0.51 MB Base Map Layers Data Layer Name & Description Metadata Files File Size NOS80K - Medium Resolution Digital Vector Shoreline (Source: NOAA) PVIshrpl - Vectorized Shorline of Puerto Rico and the U.S. HTML Virgin Islands (Source: NOS & NGS) FAQ MB HTML FAQ txt nos80k.zip 25.9 MB Coastal Relief Model Bathymetry - Image representation of CRM bathymetry (MrSid format) for the Caribbean (Source: NOAA) HTML PVIshrpl.zip 1.11 FAQ txt txt car_grd.zip 1.86 MB U.S. EEZ Boundary - Boundaries of the Exclusive Economic Zone (EEZ) (Source: NOAA) HTML FAQ txt useez.zip 156 KB State Boundaries - internal U.S. State boundaries (Source: USGS/CMGP) HTML FAQ txt state_bounds.zip 1.76 MB Legends To map the coded information on Color and Roughness in a GIS, load the ArcView legends "munsell3.avl" or "rgh_pt.avl" which are available with the database. ArcView legends may be imported into ArcGIS. To make your own legends for other applications, employ a classification that uses a "unique value" process Color Color of sediment is described either in terms (brown, light greenish gray) or in Munsell color codes given in values of hue (spectral content), value (lightness), and chroma (saturation). Munsell codes are explained in a publication of the Geological Society of America (Goddard, and others, 1951).The dbSEABED program converts the former into average values of Munsell codes, rounded to increments of 5 in hue, 3 in value, and 3 in chroma (Jenkins, 2003). An ESRI® ArcView legend is included for ease of mapping. 26 Coastal Relief Model Bathymetry - Image representation of CRM bathymetry (MrSid format) for the Gulf of Mexico (Source: NOAA) HTML FAQ txt gmx_grd.zip 0.92 MB Roughness This is a coded output representing the V:H of the seabed roughness element which is observed with greatest aspect ratio. That feature may be fixed roughness like a cobble, or moveable roughness like ripples. The outputs can only report observed roughness elements, so are influenced by the size scales of samplers and observations. The V and H values are the centimeter values of the height and horizontal dimensions written in integer log 2 (base 2). For example "4:6" represents 16 cm height over length scale of 64 cm. Powers <0 are set to zero (i.e., scales <1 cm are not considered). The horizontal length H are the length of expression of a feature, rather than wavelength of repetition. Where a feature is elongated, H is taken normal to elongation (i.e., equals ripple wavelength). ArcView Legends: Munsell Color Roughness: | AVL JPG References Cited Black, K.S., Tolhurst, T.J., Paterson, D.M., and Hagerthey, S.E., 2002, Working with natural cohesive sediments: Journal of Hydraulic Engineering, v. 128, no. 1, p. 2-8. Folk, R.L., 1954, The distinction between grain size and mineral composition in sedimentary rock nomenclature: Journal of Geology, v. 62, no.4, p. 344-359. Folk, R.L., 1974, The petrology of sedimentary rocks, Austin, Tex., Hemphill Publishing Co., 182 p. Gassmann, F., 1951, Elastic waves through a packing of spheres: Geophysics, v. 16, no. 673-685. Goddard E.N., Trask, P.D., de Ford, R.K., Rove, O.N., Singewald, J.T. and Overbeck, R.M., 1951, Rock Color Chart: Geological Society of America. 6 p. Jenkins, C.J., 1997, Building offshore soils databases: Sea Technology, v. 38, no. 12, p. 25-28.* Jenkins, C., 2002, Automated digital mapping of geological colour descriptions: Geo-Marine Letters, v. 22, no. 4, p.181-187.* Jenkins, C., 2003, Data management of MARGINS geologic data, with emphasis on efficiency, quality control and data integration: MARGINS Newsletter 10, Spring 2003, p. 8-10.* Jimenez, J.A., and Madsen, O.S., 2003, A simple formula to estimate settling velocity of natural sediments: Journal of Waterway, Port, Coastal and Ocean Engineering, March/April 2003, p. 70-78. Kirchner, J.W., Dietrich, W.E., Iseya, F., and Ikeda, H., 1990, The variability of critical shear stress, friction angle, and grain protrusion in water-worked sediments: Sedimentology, v. 37, p. 647-672. Mott, J.L., Kandel, A., and Baker, T.P., 1986, Discrete mathematics for computer scientists and mathematicians (2nd ed.): Reston Publishing Co., 751 p. Nafe, J.E. & Drake, C.L., 1960, Physical properties of marine sediments, in Hill, M.N., ed., The Sea, v. 3, p. 794-815. National Ocean Service (NOS), 1997, Chart no. 1, United States of America, Nautical chart symbols, abbreviations and terms: US National Ocean Service [Chart]. Poppe, L.J., Eliason, A.H., Fredericks , J.J., Rendigs, R.R., Blackwood, D., and Polloni, C.F., 2000, Grain size analysis of marine sediments: methodology and data processing, in Poppe, L.J., and Polloni, C.F., eds., USGS east-coast sediment analysis; procedures, database, and georeferenced displays: U.S. Geological Survey Open-File Report 00-358, CD-ROM. Poppe, L.J., Williams, S.J., and Paskevich, V.F. (Editors), 2005, USGS east-coast sediment analysis: procedures, database, and GIS data: U.S. Geological Survey Open-File Report 2005-1001, DVD. Online at http://woodshole.er.usgs.gov/openfile/of2005-1001/. Reid, J.A., Reid, J.M., Jenkins, C.J., Zimmermann, M., Williams, S.J., and Field, M.E., 2006, usSEABED: Pacific Coast offshore surficial sediment data release: U.S. Geological Survey Data Series 182, version 1.0. Online at http://pubs.usgs.gov/ds/2005/182/. Reid, J.M., Reid, J.A., Jenkins, C.J., Hastings, M.E., Williams, S.J., and Poppe, L.J., 2005, usSEABED: Atlantic Coast offshore surficial sediment data release: U.S. Geological Survey Data Series 118, version 1.0. Online at http://pubs.usgs.gov/ds/2005/118/. Richardson , M.D. and Briggs, K.B., 1993, On the use of acoustic impedance values to determine sediment properties: Proceedings of Instuments of Acoustics, v. 15, p. 15-24. Shepard, F.P., 1954, Nomenclature based on sand-silt-clay ratios: Journal of Sedimentary Petrology, v. 24, p. 151-158. Syvitski, J.P.M., LeBlanc, K.W.G. and Asprey, K.W., 1991, Interlaboratory, interinstrument calibration experiments, in Syvitski, J.P.M., ed., 1991, Principles, methods, and application of particle size analysis: Cambridge, Cambridge University Press, Cambridge, p. 174-193. 27 Thorsos, E.I., Williams, K.L., Jackson, D.R., Richardson, M.D., Briggs, K.B., and Tang, D., 2001, An experiment in high-frequency sediment acoustics; SAX99: IEEE Journal of Oceanic Engineering, v. 26, p. 4-25. UK Hydrographic Office (UKHO), 2005, Chart symbols & abbreviations: Chart BA 5011 [Booklet], UK Hydrographic Office, 38 p. Wentworth, C.K., 1922, A scale of grade and class terms for clastic sediments: Journal of Geology, v. 30, p. 377-392. Whitehouse, R., Soulsby, R., Roberts, W., and Mitchener, H., 2000, Dynamics of estuarine muds; A manual for practical applications: London, Thomas Telford, 209 p. Williams, S.J., Arsenault, M.A., Poppe, L.J., Reid, J.A., Reid, J.M., and Jenkins, C.J., 2006, Surficial sediment character of the New York-New Jersey offshore Continental Shelf region: a GIS Compilation. Online at http://pubs.usgs.gov/ofr/2006/1046. Williams, S.J., Jenkins, C., Currence, J.M., Penland, S., Reid, J., Flocks, J., Kindinger, J., Poppe, L., Kulp, M., Manheim, F., Hampton, M., Polloni, C., and Rowland, J., 2003, New digital maps of U.S. continental margins; Insights to sea floor sedimentary character, aggregate resources and processes: Proceedings of the International Conference on Coastal Sediments 2003: Corpus Christi, Tex., World Scientific Publishing Corporation and East Meets West Productions, CD-ROM. Williams, S.J., Reid, J.M., and Manheim, F.T., 2003, A bibliography of selected references to U.S. marine sand and gravel mineral resources: U.S. Geological Survey Open-File Report 2003-300. Online at http://pubs.usgs.gov/of/2003/of03-300/ Wyllie, M., Gardner, G., and Gregory, A., 1963, Studies of elastic wave attenuation in porous media: Geophysics, v. 27, p. 569-589. *Please contact Chris Jenkins at chris.jenkins@colorado.edu for reprints of these articles. Acknowledgments Reviews by VeeAnn Cross, Jodi Harney, Debbie Hutchinson, Don Woodrow, Rob Thieler, Kathy Scanlon, Matthew Arsenault, and Valerie Paskevich are greatly appreciated. We thank the following USGS interns for their assistance in data entry, coding, and data testing: Viness Ubert, Emma Mitchell, Emily Denham, Shea Quinn and Ariadne Prior-Grosch, Tara Kneeshaw, April Villagomez and Monica Iglecia. We'd also like to thank John Goff and Matt Arsenault for their quality-control testing of the data and their formats. dbSEABED has benefited from the contributions of many people and institutions. It is a community structure, currently managed from the University of Colorado. Funding from the Australian Department of Defence, Commonwealth Scientific and Industrial Research Organisation (CSIRO) Australia, Geosciences Australia, Institute of Arctic and Alpine Research (INSTAAR) / University of Colorado, Institute fur Ostseewissenschaften- Warnemunde (IOW, Germany), Lamont Doherty Earth Observatory, NOAA National Geophysical Data Center (Boulder), ONR: Office of Naval Research, and Victorian DNR (Australia). Mike Field and Jim Gardner who first arranged to apply dbSEABED to the US EEZ, in 1999. Ideas for development of dbSEABED have been contributed in discussions by L. Hamilton and P. Mulhearn (Defence Science and Technology Organization (DSTO)), G. Rawson, A. Short (Univ. Sydney), P. Sliogeris (Royal Australian Navy METOC Services (Australia)), T. Wever (Forschungsanstalt der Bundeswehr für Wasserschall und Geophysik, Germany (FWG)), J. Harff, B. Bobertz and B. Bohling (IOW), P. Morin (Univ. Minnesota), M. Kulp and S. Briuglio (Univ. New Orleans), J. Goff (Univ. Texas), G. Sharman and C. Moore (NOAA/NGDC), the URS Corporation, the Smithsonian Institution, J. Kindinger, C. Holmes, C .Polloni (USGS) and the coauthors of this report. Frequently Asked Questions (FAQs) about dbSEABED dbSEABED What is dbSEABED? What kind of outputs does dbSEABED produce? 28 What quality control measures are in place for dbSEABED? Output files What is the SRC file output? What is the function of the output CMP and FAC files? What is the CMP file output for? What is the meaning of the data in the FAC output file? What do all the “-99”'s mean? Why are there negative values for seabed strength and critical shear strength? Compared to values given in some scientific papers, the output values from dbSEABED are quite rounded. Why? What is the "Rock" membership? What is the meaning of the SeaBedClass and ClassMembership? What is the "Weed" membership? Hydrographic Bottom Type (HBT) codes can be output. What do they mean? What does the Roughness code mean? Why do some points plot on the land? Can the same sample or analysis be represented more than once in the data collection? Why are the Kurtosis and Skewness not reported from the database? Linguistic data versus numeric data How does dbSEABED make word data conformable with numerical data? What if a user doesn't want to use the word-based data for their mappings? Which form of data should I trust more? Numeric-value analyses or word-based descriptions? How does Word-Based Descriptive data relate to numeric-value analytical data? Grain size Why are values of grain size only given to 1 decimal place, and percent sand etc given as integers? How are the grain sizes extracted from data? Are detailed grain size analyses used to output textural statistics like mean and sorting? Why would a sample that is known to have had a detailed grain size analysis not appear in the output data? How are the outputs for the grain size fractions gravel, sand, mud extracted? Are grain size scales other that Wentworth used? How is one central grain size recovered from diverse data that may present mean, median and other graphical grain sizes? How are the central grain size and sorting estimated in the CLC process of the database? 29 Color Where can I find more information on the Munsell color code? How are the Munsell color codes derived? Data import methods How does dbSEABED hold the basic data? Why does dbSEABED hold its underlying data in documents rather than a relational database like Oracle? What is involved in importing data sets into dbSEABED? How is metadata treated? Why are sediment descriptions and biological names held as abbreviations? Data processing methods What is Fuzzy Logic and how does it work? What is the method of attributing sub-bottom depths to samples from cores? How are the shear strengths derived? What is the method for arriving at the SHEPARD and FOLK classes? What relationships are used to estimate Critical Shear Stress values? How are the porosity values obtained? What is the basis for the data on compressional (p-wave) sound speeds? How are the sorting values arrived at? Carbonate values: how are they arrived at? And Organic Carbon? How to How can I map the coded information on Color and Roughness in a GIS? How can I use the Critical Shear Stress in a practical application? dbSEABED What is dbSEABED? • dbSEABED makes a single integrated data set from seabed sample information that has been collected over many years by ocean expeditions and research programs. • dbSEABED is an “Information Processing” system that produces outputs that are compatible with Geographic Information System (GIS), Relational Database (RDB), as well as several other highly useful kinds of outputs. The outputs can be used in many end-user software applications. What kind of outputs does dbSEABED produce? • For mapping in Geographic Information Systems, dbSEABED produces a number of flat-files that are comma delimited. Those files give the 20 most useful parameters, and information on grain types and 30 sedimentary features. These outputs can be enhanced in various ways, for instance by combining analytical and descriptive outputs, assigning gridded water depth values where not present, and re- arranging the data by its position within the sea floor. • For use in Relational Database Systems like Oracle, MySQL or MS Access, dbSEABED produces a set of tables that are linked at the levels of sea floor site or sample using a system of numeric keys. What quality control measures are in place for dbSEABED? Quality control is implemented at many stages in dbSEABED: • initially, by selecting which data sets to enter; • by personnel scrutinizing the data at time of import, virtually item-by-item, for example for implausible values and positions not conforming to a report's survey pattern on a map; in some cases special filtering programs are written, for example to detect implausible ship speeds between stations; • by testing in programs whether the data entries are text (string), numeric or a special formatted code as specified in the data model; • in programs, testing if values lie within their plausible ranges, for example between -8 and 12 phi for grain sizes; • by comparing site locations to land areas; • in a more sophisticated way, comparing reported site water depths to a regional or global topography (such as etopo2); • screening the program output values, also using plausibility filters; • by having end-users of the data report any problems and having them fixed at source; As each new data set is entered, it is tested in programs of dbSEABED to seek errors, etc. The program detections of problems are highlighted on screens during run time and are also reported to logs. As errors are detected, edits are made in the structured data files, complete with metadata explaining the edits. In some cases data will be deactivated (flagged out), again with metadata explaining. Output files What is the SRC file output? • The “Source” (SRC) file gives basic information on the survey and data set that a sample belongs to, including the collector and institution, confidentialities, number of samples, dates, region, etc. What is the function of the output CMP and FAC files? • The CMP files provide information on the abundances (or prominence) of grain types, sedimentary features, and other components of the sea floor, for example of Halimeda algal grains, of ripples, and of hydrogen sulfide odor. • The FAC file synthesizes these data by applying a Fuzzy Set operator and creating a superset across a selection of components/features – a geologic facies. For example, a calcareous pelagic facies is defined as the FST membership across samples that show nannoplankton, planktic foraminifera, or pteropod remains, or are described as calcareous ooze. What is the CMP file output for? • Geologists and others frequently describe the presence and abundance of components in a sediment, like shell debris, quartz, heavy minerals, etc. They do this by grain counts or in their descriptions. dbSEABED assesses the abundances of these components and outputs some of them in the CMP file. Users of the software can select which components will be output. Counting grains (and gauging 31 their volumes or weights) is not an accurate process, and neither is conveying the abundance of a component in a description. The results in the CMP file are therefore only an approximate guide to abundances. • The CMP file also carries fuzzy membership values for some features of the seabed, like odors (e.g., H2S), and bioturbation and ripples. What is the meaning of the data in the FAC output file? Once the Memberships (Abundances) of components are calculated, they can be combined into an assessment of the membership a sample shows to a range of sedimentary, rock or ecologic facies. Each Facies is typified by components Af,Bf,... with memberships af,bf,..., for example a CalcareousPelagic facies as "pfrm nan ptr cal_ooz ; 1 1 1 1 0 0". The components are senior synonyms from the parsing dictionary. Given a set of components in a sample As,Bs,... with memberships as,bs,..., the sample membership of each facies is calculated as MIN(ac,af)+MIN(bc,bf)+... for each case of a coinciding component. In Fuzzy Set Theory this is a set intersection - an AND. Of course, the Facies output is possible only from the parsed word-based data. Because not all studies report grain components, it is advisable to plot these results as point symbols only, not areal griddings. What do all the “-99”'s mean? • “-99” is the null value for numeric fields output by dbSEABED. Null values will be found only in the output tables. • We have to specify null values because otherwise some end-user mapping and analysis applications make decisions about what a blank field in the table represents. • The value “-99” is used because it almost never occurs in real data. It does for longitudes however, and for latitude/longitude the null is “-999”. The null for output string (text) data are “-“. Why are there negative values for seabed strength and critical shear strength • These parameters are given in terms of their logarithm (base 10). A negative value implies a strength or shear stress less than 1. Compared to values given in some scientific papers, the output values from dbSEABED are quite rounded. Why? • Studies of uncertainty show that accuracies on most sediment parameters are of order 1-3% of the total parameter range even under favorable laboratory conditions. The significant figures in dbSEABED outputs reflect the observed uncertainties. What is the "Rock" membership? • Many observations of the sea floor report the presence of rock, loose and as bedrock. This output statistic is meant to convey the degree of exposure of rock which is coarser than cobble (-8 phi). Loose rocks and bedrock which are partly covered by sediment give memberships of less than 100%. • Terms which have rock memberships include: basalt, granite, limestone, rock, boulders, lithified, hard, hard bottom, reef, rock platform, greywacke, where they occur in LTH or SFT themes, that is are not part of a grain-type description as in a PET theme line. For output data on specific rock types like basalt, refer to the CMP output file. • Note that samples which have only loose sediments recorded are given a value of zero rock membership in CLC outputs. 32 What is the meaning of the SeaBedClass and ClassMembership? These columns put out the facies showing the largest membership value for each sample, and that largest membership. The memberships are calculated as described in the FAQ about the FAC file. Output occurs only provided that the membership is greater than or equal to 0.33. Of course, this output is possible only from the parsed word-based data. What is the "Weed" membership? • Many observations of the sea floor report the presence of soft algae, seagrasses in general terms or specific to a taxon. Depending on the associated abundance terms like sparse, abundant, meadows, scattered, etc, the weed is given a membership which is reported to outputs (PRS). There are no EXT outputs for weed membership. Calcareous algae like Halimeda and Lithothamnion are not included. • Terms which have weed memberships include: Zostera, seagrass, soft algae, kelp, Cladophora, weed. These data are usually in a SFT theme line. For specific data on seagrasses, refer to the CMP output file. Hydrographic Bottom Type (HBT) codes can be output. What do they mean? • Many navies and engineering groups use these codes. The British Admiralty set used here (British Admiralty, 1973) are not very different from US usage within USCG and NOAA. Some users of dbSEABED will find the codes familiar and helpful. Note that the terms at the front of the code are the most significant (abundant). For the clearest plottings, use the no-overlap options in your GIS and plot only the surficial seabed samples of an area. • The codes output in EXT are either passed direct from naval/engineering HBT codings or re-codings of the lithological types that scientists have described in sediment samples. The codes output in CLC refer only to the gravel, sand, mud, rock and weed components present in a sediment or at a site. Note: Data for Hydrographic Bottom Type have not been included in this publication. What does the Roughness code mean? • This is a coded output representing the V:H of the seabed roughness element which is observed with greatest aspect ratio. That feature may be fixed roughness like a cobble, or moveable roughness like ripples. The outputs can only report observed roughness elements, so are influenced by the size scales of samplers and observations. • The V and H values are the centimeter values of the height and horizontal dimensions written in integer log 2 (base 2). For example "4:6" represents 16 cm height over length scale of 64 cm. Powers <0 are set to zero (i.e., scales <1 cm are not considered). The horizontal length H is the length of expression of a feature, rather than wavelength of repetition. Where a feature is elongated, H is taken normal to elongation (i.e., equals ripple wavelength). Why do some points plot on the land? • Some of the data collections we used contain data in estuaries, rivers and lakes; others contain data for coastal dunes, beaches, even coal mine pits. We could have culled these data, especially the ones that are obviously not marine. But the accuracy of maps of the national shoreline is not good enough to do a cull based on position of samples alone. And some people will find the dune, river, and lake data useful. Therefore we left all the data in. Can the same sample or analysis be represented more than once in the data collection? • Yes, when there is a good reason. For instance, the same sample may be described by two different labs, or be re-analyzed years later. Or an analysis may be expressed in a different way by later work. These 33 duplicate results are all valid, and should be included in the database for mapping. (Note that the duplicate analyses may not carry exactly the same sample names.) Why are the Kurtosis and Skewness not reported from the database? • These higher order moments are not only rarer in data sets, but to be accurately reported require a higher standard of data and calculation than lower moments. Statistical moment and graphical measures are also very difficult to reconcile, exacerbating the shortage of available data on which to base outputs. Linguistic data versus numeric data How does dbSEABED make word data conformable with numerical data? • dbSEABED software attaches Fuzzy Set Theory memberships to word terms through a look-up dictionary table. The memberships are summed across a description and the totals are output. Some words like “slightly” only adjust the memberships. Other words adjust the character of another, for instance “fine” in “fine sand”. For more detail, see Jenkins, 1997. • dbSEABED also recognizes if a word is not in its dictionary, if the meaning is unknown. For example: “zyzgy” is not in the dictionary and will be labeled an ‘unknown' It also recognizes if a word if neutral for a question. For example: “sediment” is neutral on the question of color. What if a user doesn't want to use the word-based data for mappings? • Users have a choice: if only numerical analytical data are required, then the ‘extracted' (EXT) form of output should be used; if word data only, then the ‘parsed' (PRS) form. Some users will not want to use the ‘calculated' (CLC) outputs which have a higher level of uncertainty than these, and that is possible too. If a user wants to integrate these to achieve the best possible coverage in a region, then they can be added or telescoped together using two other formats (ALL and ONE formats respectively; not included in this publication). Which form of data should I trust more? Numeric-value analyses or word-based descriptions? There are several issues that users must consider in deciding which form of data to use: • Issue 1. Descriptive data are more representative of the seabed, the shells, coral, rocks and other items that will not fit in laboratory bottles or analytical instruments but which have a power effect on erodibility, acoustics and habitat. It is also essential for dealing with the creatures of the bottom, burrows and other structures, sediment strength, odors, color, etc. • Issue 2. To get enough data to make a map with a useful number of points, you will have to use word-based data, which account for 85% of all available data in usSEABED. • Issue 3. Analytical data are more precise, often precise as to within 2% of the full parameter range. And it is repeatable, given the same instrument unlike descriptions which may vary between observers, even trained ones. However it may not be accurate for the sea floor, as it usually only deals with the seabed matrix – those materials fine enough to fit inside the instrument tubes / apertures. How do word-based descriptive data relate to numeric-value analytical data? • The values of grain size, percent gravel, carbonate, etc., that are calculated from word-based data are based on Fuzzy Set Theory calculations. They are memberships, reduced to a single value. An analysis is also a single realized value of the Fuzzy Set. • Sometimes word-based and numeric-value results are available for the same sample, and then an inter-calibration of the two forms of output can be made. 34 Grain size Why are values of grain size only given to 1 decimal place, and percent sand, etc., given as integers? • Work in the dbSEABED project has established the typical accuracies on measurements of these parameters. Those accuracies, even for careful work are of the order of 2-5% of half the total range of the parameter. The table outputs are designed to be brief to restrict data volumes and make mapping faster and easier, and to carry the data at a precision that is appropriate to measurement accuracies. How are the grain sizes extracted from data? • By a simple reporting of the average grain size, median grain size, Inman Mean, and Folk Graphic Mean grain sizes. A comparison of data sets shows that these reflections of ‘central' grain size are not significantly different within usual error bounds on sampling then analysis. (On the other hand, sorting values are significantly different and cannot be combined in the same way.) Are detailed grain size analyses used to output textural statistics like mean and sorting? • Yes. The percentages in each fraction are summed to output the percent gravel, sand, mud and clay. • A weighted average and standard deviation is also calculated, leading to output of central and sorting grain sizes. Standard moment statistics (see Blatt and others, 1980) are used. Why would a sample that is known to have had a detailed grain size analysis not appear in the output data? • Grain size analyses are scanned to check that they are in good order, and some are rejected. An analysis with any phi interval is acceptable, provided it is fine enough to resolve those fractions. Analyses that have a significant weight percent in the finest and coarsest classes are treated as suspect because this implies that the part of the sediment that was analysed probably does not represent the whole sediment. How are the outputs for the grain size fractions gravel, sand, mud extracted? • Many data sets contain these values (based on Wentworth scale), and in those cases the values are passed through to outputs (EXT). In some cases the data are presented in the form of a detailed grain size analysis – such as at ½ phi intervals. dbSEABED assembles grain size analysis streams into G:S:M fractions by assigning each analysis class to its fraction (or proportioning if the class straddles a fraction boundary). Note: Many grain size analyses techniques range only through sand and mud, and gravel is not analyzed. In these cases the database reports the gravel percent as null in outputs. Are grain size scales other that Wentworth used? • Generally no. However, an option does exist for users to report percent mud from values of ‘engineering' grain size mud (i.e., finer than #200 Sieve, 75µm). 35 How is one central grain size recovered from diverse data that may present mean, median and other graphical grain sizes? • The database adopts mean moment grain size as the standard for its measure of a sediment's central grain size. Studies show that the median, Inman ‘mean', and Folk ‘mean' grain sizes fit this quite well for a wide variety of sediments. However mode grain sizes do not, and are not included in ‘central grain size'. How are the central grain size and sorting estimated in the CLC process of the database? • Many sediments have gravel:sand:silt:clay (g:s:s:c) or gravel:sand:mud (g:s:m) ratios reported, but are without basic grain size statistics. Some users of dbSEABED requested that ‘best estimates' of the statistics be made by modeling grain size distributions. This is done by creating a weighted mean and standard deviation from the g:s:s:c and g:s:m ratios of the samples. • The class statistics underpinning the modeling were arrived at by examining the most common values for single phase sediments in USGS data sets (e.g., just silt). The values were for central grain sizes g:s:(m):s:c -3.0: 2.0: (7.0): 5.0: 8.0 . Typical values of sorting were also applied: for g:s:(m):s:c 1.4: .0.9: (2.1): 3.0: 5.8. These values may be adjusted in the future. Data processing methods What is Fuzzy Logic and how does it work? • “Fuzzy Logic” (more properly “Fuzzy Set Theory”) allows an object to belong partially to a set. In classical ‘Crisp' Set Theory objects are either in a set or not. FST suits words because they are often partial carriers of meaning. For example, ‘warm' is partially hot and partially cold. A formal arithmetic for Fuzzy Sets was discovered by Zadeh, (1965). A good reference is Mott, and others, (1986). What is the method of attributing subbottom depths to samples from cores? • Ideally a sample from a core will have a subbottom depth assigned in terms of meters below the sediment surface. However this is not always the case. While this information may have to be left unknown if not given by the original researchers, some limits can be placed if the sampler type is known. For example a Shipek Grab usually has only 5 cm of penetration. Then a subbottom range of 0-0.05m can be assigned. In cores that may be several meters long, therefore the limitation is less strict. How are the shear strengths derived? Shear strength values are obtained either from actual measurements held in the database, or assessed from descriptions that convey lithification or consolidation. • These measures of strength are accepted: hand penetrometer strength, (maximum, unremolded) vane shear strength, cohesion values from triaxial and shear box tests, compressive shear strength at low confining pressures, and cone resistances. Obviously, uncertainties arise not only from measurements themselves but by combining the different methodologies. • Many descriptions refer to a sediment or rock being “soupy”, “loose”, “soft”, “cohesive” (“firm”), “stiff”, “friable”, “cemented”, “lithified” or “hard”. These terms are indications of the mechanical state of the materials and are transferred to a Shear Strength value in PRS outputs. They are (respectively): 2, 25, 50, 100, 500, 1000, 5000, 8000, 10000. 36 What is the method for arriving at the Shepard and Folk classes? • The original Shepard (1954) and Folk (1954) ternary classifications have had to be modified in a couple of ways: (a) Where the silt and clay breakdown of mud is not available, the silt-clay domains in the classifications are merged under one name; and (b) Because these schemes refer only to sediments, an extra class “SOLID” is added for dbSEABED to classify all lithified materials (rock). The aim of (a) was to have a class attached to a greater number of samples. Very few samples in the database have silt: clay specified. What relationships are used to estimate the Critical Shear Stress values? Depending on the quality of inputs and nature of the sediment, several relationships are used to predict Critical Shear Stresses. The details and supporting references are given in the onCALCULATION document. The relationships include: • Where the consolidation is known and substantial, the CSS is set equal to the value of the Shear Strength. • For unconsolidated granular sediments a compilation using hundreds of experimental results from the field and laboratories suggests a linear relationship with phi grain size. • For unconsolidated fine-grained sediments (>5 phi grain size) where there is information on density or porosity, the CSS is based on the density using published relationships. • For unconsolidated fine grained sediments without information on density or porosity, a general value is used. <>No regard to the effects of bio-consolidation or bioturbation is made. How are the porosity values obtained? • First, values that are in the database are passed to the EXT outputs. In addition, where bulk or dry densities, void ratios, or moisture contents are present, they are transferred to a porosity value. Where this requires a grain density, this may be available, or is assumed to be 2.5 g/cm3 which is suitable for a wide range of materials. • To predict porosities for unconsolidated sediments we use an empirical relationship between porosity and grain sizes described by Richardson and Briggs' (1993): AvGrsz=-4.55+0.169*Por, with R2 of 0.81 in the range 0-12 phi. We use the inverted form: Por=26.92+5.92*AvGrsz . These results appear in the CLC outputs. Other unpublished relationships of higher accuracy are available. What is the basis for the data on compressional (p-wave) sound speeds? Although there are some direct measurements of compressional sound speeds for areas of the seabed, they are few and far between. dbSEABED reports any direct measurements in the EXT outputs, including the average of those data which recognize velocity anisotropy. One difficulty with sound speeds is that they do depend on the frequency, pressure and temperature of the measurement. The outputs make no allowance for these factors, though conditions of the original measurements are recorded in the underlying raw data of the database. Several users of dbSEABED requested that estimated sound speeds be provided wherever possible. This is done as follows. • Where the material is consolidated and a measured porosity is available, then the time average equation is employed (Nafe and Drake (1960)). Consolidation is judged to be when the ShrStrs based on measurement or a parsing of compaction/cementation is > 50kPa, or the porosity is < 33%. These values for constants were adopted: solids and fluid densities 2500 and 1025 kg/m3, respectively; sound speed of solids and fluids 5000 and 1520 m/s, respectively. • Alternatively, where the material is a loose sediment the velocity is calculated based on the relationships of Richardson and Briggs (1993): Vb/Vw=1.18-0.034*Mz+0.0013*Mz2 with an R2 of 0.82, where Vb/Vw is the ratio of sea floor sediment and bottom water p-wave velocities. For an absolute output velocity, this result is combined with the bottom water velocity (assumed 1520 m/s). 37 Other unpublished relationships of higher accuracy are available. The method makes no allowance for the consolidation of a sediment below the sea floor, for example in a core. How are the sorting values arrived at? • Values of moment sorting are simply passed through to output. Graphical measures of sorting such as those of Inman and Folk are not generally compatible with moment measures and at present do not contribute to outputs. Carbonate values: how are they arrived at? And Organic Carbon? • Carbonate measurements that have been made on the complete sediment are simply reported in the EXT outputs. Many sediments have had carbonate determined on just the sand or mud fractions: those results are not output because they do not represent the whole sediment. • Carbonate values are also output from the parsing process. The carbonate parts of sediment are summed in quantity, as are the non-carbonate and unknown carbonate parts (like ‘mud'). If the sum of unknowns is less that 5% then a carbonate membership is reported in PRS outputs. The accuracy of this result is not as good as for analysis data. • Organic carbon data are treated the same way. However, because OC values are typically small in sediments (~1%), the accuracies in the PRS results are not good and should be treated with caution at this stage. Data import methods How does dbSEABED hold the basic data? • Data sets for processing are held in structured documents that are called “Data Resource Files” (DRF). They set out data in the form of a written geological core-log, in a tree structure that nests the data according to expedition, the sample site, the sample, and finally phase inside the material. This format is processed by programs to produce other formats that are compatible with GIS and RDB. Why does dbSEABED hold its underlying data in documents rather than a relational database like Oracle? This is one of the most successful features of dbSEABED. • First, it is more efficient to bring in data sets from geologists in the form of written core-logs rather than tables, especially as tables and sub-tables. This is how dbSEABED has been able to quickly absorb a million data sites. • Second, it is not possible (easily, inexpensively) to do some sedimentological operations on the data in software like Oracle. For example, parsing the word-based descriptions. • Third, in the documents, it is possible to have data which was obtained at the same time (such as replicates, suites of analyses) to be kept right next to each other. The same is true for the metadata; a person can read the data and the metadata about it easily and at the same time. • Fourth, it keeps the data very faithfully in its original form. Relational databases require that data be shuffled and diced, and to obey sets of rules before the data can be entered. Data are kept faithful to that of the original observers. • Relational Databases are just one type of data structure. There is no reason why dbSEABED shouldn't be able to generate others too, like XML, and Spreadsheets and GIS tables. 38 What is involved in importing data sets into dbSEABED? • This depends on the structure and idiosyncrasies of the original data. Many data sets are simple to import into the Data Resource File (DRF) format. Others have proven to be most difficult. It is usually done by arranging data items by column in EXCEL according to a template that sets out the field locations for each data item (such as latitude, sampler type, phi grain size, and Munsell color code). Different types of data are divided between themes such as geotechnical, texture, or color. Some themes allow for a sample to be from the subbottom (as in a core). Others such as sea floor type which is dedicated to surficial sediment surveys such as those by divers and remote vehicles, treat only the sea floor surface. • Although dbSEABED tries to hold data as close as possible in its original terms, this is not always possible. In the case of numeric data items, if a simple conversion of units is desirable – for instance from cm into m – then that can be done at data import stages. In the case of word descriptions, it would be unwieldy to hold or process the descriptions in original long words and words are therefore converted to abbreviations. Note that this does not change the terms, it is NOT a re-classification. Terms such as “lithothamnion”, “scattered”, “low water content” are abbreviated to “lthmn”, “scatrd” and “lo_watr_cntnt”. This speeds processing, allows importing staff to check the data for spelling errors, allows us to use foreign languages (e.g. “sabb(IT) for “sabbiosi”), and permits homonyms to be distinguished (eg: dens_ab” and “dens” for abundance and geotechnical densities). It also allows the data to be read more easily on computer screens. How is metadata treated? • Metadata are treated at several levels. First, over-arching metadata have been compiled for the processed outputs of dbSEABED (see “http://instaar.colorado.edu/~jenkinsc/dbseabed/resources/ db9_MetadataFGDC.txt”). Second, the USGS and others have compiled metadata for individual data sets as they are entered into dbSEABED. Third, metadata describing measurement techniques, features and problems in the data, edits that we have made in dbSEABED, who collected and analysed the data, etc is held in direct association with the data in the DRF files. This most detailed metadata are best viewed in the RDB structure, which also puts out reports when data values are beyond plausible limits, for example a grain size of 14 phi. Why are sediment descriptions and biological names held as abbreviations? • To make the parsing (and dictionary lookup) computationally faster, to make long descriptions shorter and more readable, to give flexibility in handling homonyms, and to better distinguish active data from metadata in the structured documents. Color Where can I find more information on the Munsell color code? • Refer to the Geological Society of America “Color Rock Chart,” or to the company GretagMacbeth which is the modern-day custodian of Munsell's color technologies. How are the color Munsell codes derived? • This process is fully described in Jenkins (2002). Munsell codes are explained in a publication of the Geological Society of America (Goddard, and others, 1951). The essential steps in the treatment of colour data are as follows: • If data are available in Munsell Code form then that is transferred to outputs. • Where a color description like “light greenish gray” is available, then that is parsed by a weighted summing of the hue (color), chroma (colour intensity) and value (greyness) of the terms. From these components a Munsell Code is formed. The process is calibrated using the GSA scales and others. • Outputs are stepped at intervals of 5 in hue, and 3 in chroma and value. Otherwise the full range of >3240 possible natural codes would not be mappable. This stepping arrangement reduces the number 39 to about 40, as seen in the ready-to-use legend that is available with this publication. That legend was constructed by adjusting the RGB values of the symbols to match their Munsell colors as seen on a computer screen. How to How can I map the coded information on Color and Roughness in a GIS? • Load the ArcView legends “munsell3.avl” or “rgh_pt.avl” which are available with the database. ArcView legends may be imported into ArcGIS. • To make your own legends for other applications, employ a classification that uses a “unique value” process. How can I use the Critical Shear Stress in a practical application? • The CSS and grain size are essential components for calculating the Shields criterion of sediment erosion, between the Shields Parameter and the Grain Reynolds Number. Those parameters can be calculated once the flow characteristics, fluid velocities and densities, etc are known. See standard textbooks on sediment erosion for more information (e.g., Soulsby (1997)). FAQ References: Blatt, H., Middleton, G.V. and Murray , R.C., 1980, Origin of sedimentary rocks (2nd ed), Prentice-Hall, Inc., 782 p. British Admiralty, 1973, Chart 5011. Symbols and abbreviations used on Admiralty Charts (new series). The British Hydrographic Office, Taunton , UK. Folk, R.L., 1954, The distinction between grain size and mineral composition in sedimentary rock nomenclature: Journal of Geology, v. 62 n.4, p. 344-359. Folk, R.L., 1974, The petrology of sedimentary rocks, Austin, TX, Hemphill Publishing Co., 182 p. Goddard E.N., Trask, P.D., de Ford, R.K., Rove, O.N., Singewald, J.T. and Overbeck, R.M., 1951, Rock Color Chart. Geol Soc Am, Colorado. Mott, J.L., Kandel, A., and Baker, T.P., 1986, Discrete mathematics for computer scientists and mathematicians (2nd ed.), Reston Pub Co, 751 p. Nafe, J.E. & Drake, C.L., 1960, Physical properties of marine sediments. In: Hill, M.N. (ed), The Sea, v. 3, p. 794-815. Poppe, L.J., Eliason, A.H., Fredericks , J.J., Rendigs, R.R., Blackwood, D., and Polloni, C.F., 2000, Grain size analysis of marine sediments: methodology and data processing. In: Poppe, L.J., and Polloni, C.F. (eds.) USGS East-Coast sediment analysis: Procedures, database, and georeferenced displays, U.S. Geological Survey Open-File Report 00-358, CD-ROM. Poppe, L.J., Williams, S.J., and Paskevich, V.F. (Editors), 2005, USGS east-coast sediment analysis: procedures, database, and GIS data: U.S. Geological Survey Open-File Report 2005-1001, DVD. Online at http://woodshole.er.usgs.gov/openfile/of2005-1001/. Richardson , M.D. and Briggs, K.B., 1993, On the use of acoustic impedance values to determine sediment properties: Proc. Inst. Acoust., v. 15, p. 15-24. Shepard, F.P., 1954, Nomenclature based on sand-silt-clay ratios: Journal of Sedimentary Petrology, v. 24, p. 151-158. Soulsby, R., 1997, Dynamics of marine sands, Thomas Telford, London , UK, 249 p. Zadeh, L.A., 1965, Fuzzy sets: Information and Control, v. 8, p. 338-353 40 Tables A-E Table A. Key to data themes in usSEABED output files Acronym Meaning ACU Acoustic properties BIO Biota descriptions CMP Sediment composition analyses COL Sediment color GRZ Grain size analyses GTC Geotechnic properties LTH Lithologic descriptions MSL Multisensor core logger analyses PET Grain petrographic analyses SFT Sea floor type descriptions TXG Graphical texture statistics TXR Texture statistics Table B. Field parameters, format, units, range, meaning, and comments for EXT, PRS, CLC data files Field Name Parameter Data Format Units, Range, Meaning Comment Latitude Latitude Decimal 00.00000 Decimal degrees, 90° to -90° range WGS 84 Spheroid. Longitude Longitude Decimal 000.00000 Decimal degrees, - 180° to 180° range WGS 84 Spheroid. WaterDepth Water depth Integer 00000 Meters Not always tidally correct. SampleTop Sample top Decimal 000.00 Meters below seabed surface Sample top as noted in source report. SampleBase Sample base Decimal 000.00 Meters below seabed surface Sample bottom as noted in source report. SiteName Site name Character XXX: XXX Survey or laboratory code for the sampling site Not unique; site name as given in report; sometimes linked to cruise name or other information to decrease site name overlap. DataSetKey Data set number key Integer 000 For audit only Relational key to SRC file; SRC file contains links to source metadata. SiteKey Site number Integer For audit only Relational key to other data 41 key 0000000 files. Each site counted sequentially as total output; core data may have more than one sample per site. SampleKey Sample number key Integer 0000000 For audit only Relational key to other data files. Each site counted sequentially as total output; Multiple samples may be at each site (i.e., in core). Sampler Sampler type Character Xxxxxxxx.... Type of sampling device As given in source report; recovery (rcvy) or penetration (‘pen') length appended if given in source report. For more complete information on sampler, see source metadata. DataType Data types Character XXX: XXX For audit principally Source data types (Table A). Gravel Gravel Integer 000 Gravel grain size fraction, % Textural class. Sand Sand Integer 000 Sand grain size fraction, % Textural class. Mud Mud Integer 000 Mud grain size fraction, % Textural class. Clay Clay Integer 000 Clay grain size fraction, % Textural class; output for 'EXT' only, as clay value can be determined only by analysis. grain size grain size Decimal 00.00 Phi characteristic grain size Consensus of mean and median grain sizes. Sorting Sorting Decimal 0.00 Phi grain size dispersion Standard deviation, sorting only. SeafloorClass Sea floor class Character Xxxxx... That class (or ' facies ' ) with the maximum fuzzy membership, if above 30% Output for 'PRS' table only. ClassMbrshp Class membership Decimal 000 Fuzzy membership (%) of the class (or 'facies'), noted above Output for '_PRS' table only. Folk classification; Shepard classification Folk classification; Shepard classification Character xx.XX... RockMbrshp Rock index Integer 000 Fuzzy membership (%) Membership of sample to ‘rock' fuzzy set'; reported only in PRS data WeedMbrshp Weed index Integer 000 Fuzzy membership (%) Membership of sample to weed fuzzy set; reported only in PRS data Carbonate Carbonate Integer 000 %; may be Fuzzy 42 membership (PRS) MunsellCode Munsell Color code Character XXXXX Standard alphanumeric coding of color partitioned into Hue, Value, and Chroma Ex: '5YR 6/4', See "Rock-Color Chart", Geological Society of America, 1991. OrganicCarbon Organic carbon Integer 000 % Minimum value from descriptions (PRS tables) is 0.1%. ShearStrength Log shear strength Decimal 00.0 kiloPascals, undrained, unconfined From a variety of instrumentation. Porosity Porosity Decimal 00.00 % P- waveVelocity P-wave velocity Decimal 00.0 m/sec Usually not corrected for P/T effects. Bottom roughness Roughness Decimal 0000.00 Coded to express the height and length of the bottom feature with greatest aspect ratio. In a coding that expresses the height and length of the bottom feature with greatest aspect ratio; a coded output representing the V:H of the roughness element with greatest aspect ratio, values expressed as (rounded) integer log2. Critical shear stress Log critical shear stress Decimal 0000.00 Log10 of Tau in kPa, Log 10 of Tau in kPa, being the shear stress required to initiate easily observable erosion and transport, whether by traction or suspension; taken from a compilation of published relationships ranging from large boulder to muds, through a range of grain shapes (eg. shell). Sample phase Where in sample the data are from Character Xxxxx.... Where sample is from Records whether the results are for the whole, bulk sediment or just to some special part like: inside a nodule, burrow-infill, the sand fraction, porewater (chemistry), a layer in the core, a gradient observed in the core, badly preserved, a layer that is not properly located, or sample with questionable location; also may report a type of analysis or observation if that is special or potentially unrepresentative (e.g., XRD, smear slide). Output is as a word-based description that may involve numerics. This field will need to be selected against when GIS mappings of the bulk sedient characters are 43 being mapped. Only blank entries should be included in such a mapping. Table C. Most frequently occurring biological components that may have textural implications (U.S. waters only) barnacles coralline algae fish debris_F pteropods serpulids bivalves corals forams radiolaria shells brachiopods crabs halimeda razor clams sponges_F bryozoa crustaceans molluscs reefs worm tubes_F calcareous algae diatoms nannofossils scaphopods clypeasts echinoids Table D. Components (Features_F) processed within usSEABED Only the descriptive terms found in source reports are defined in the dbSEABED thesaurus. Conversely, as usSEABED uses the same thesaurus as its sister data compilations (auSEABED, goSEABED), some terms listed below may not occur within U.S. waters. Only one of possible variations is listed below, e.g., laminated (laminae, lamination); mollusc (mollusk, mollusca), etc. Major synonym Triggering words (word variations not included) andest andesite, augite andesite, benmoreite, trachyandesite anmne_F anemone, tube anemone, cerinth, cerianthid, coryanactid annld_F annelid, arenicola, beachworm, bloodworm, bristleworm, funnelworm, nereid worm, polychaete, polynoid aren_frm arenaceous foraminfera, agglutinated foramifera, ammobaculite, ammodiscus, textularid foraminfera artif_F artificial, soot, anchor, brass, cinder, coal, contaminated, lumber, obstruction, petroleum, oil-gas, rubber band, snag, tar, wood chip, wreck asterd_F asteroid, basket star, briseaster, sea star, starfish barit barite (-concretion -vein) baslt basalt, diorite, metabasalt, scoria, trap rock, trachybasalt bioturb bioturbation bitumn bitumin biv bivalve, arctica, astarte, cardium, chama, chione, chlmys, clam (-shell -flat material -hash -valves), cockle (-anadara -shell), donax, glycymeris, katalysia, lamellibranch, macoma, mercenaria, mulinia, mussel (-bed - bank -shell), mya, mytilus, nucula, pelecypod, quahog, rangia, seep mytilid, slipper shells, surf clam, tellina, tellinid, venerid, venus clams, vesicomyid, yoldia bluschst blue schist, crossite-albite schist, crossite-quartz schist, glaucophane, 44 quartz crossite schist, quartz glaucophane schist bnth_frm benthic foraminfera, archaias, bolivina, bulimina, coralline forams, discorbis, eponides, homotrema, hyaline, lenticulina, loxostema, miliolid, nodosirid, nonien, notosirid, peneroplis, porcellanous, rotaiid, uvigerina borng_F boring, bioeroded brach brachiopod, lingula brncl barnacle bryz bryozoa, polyzoa burw_F burrow, chondrite, clam siphon, crab hole, lebensspurren, Thalassinoides c_alg calcareous algae, purple algae, red algae calc_ooz calcareous ooze, nannofossil -mud -ooze, pteropod -mud -ooze, foraminiferal -marl -ooze -mud, globigerina -mud -ooze calcrst calcareous crust, tufa calct calcite (-cement -core -filling -veinlets) carb allogenic grain, authigenic carbonate, biogenic, calcareous, calcilutite, calcarenite, calcirudite, calcareous biogenic, carbonate, limey, marl, skeletal micrite chrcoal_F charcoal, fire debris chrt chert, flint, porcellanite claymin clay mineral, bentonite, chlorite, collophane, illite, kaolinite clypeast clypeasteriod, sand dollar coal coal, lignite, bituminous coralgl algal coral, coralgal crab crab, hermit crab, sand crab, spider crab, swimming crab crinod_F crinoid, basket star crl coral, Acropora palmata, brain coral, Dendrophyllia, Madrepore, Manicina, Porite, sea twig crl_dbr coral debris crlrf coral reef, coral heads, shingle bank, reefal shoal crnalg coralline algae, calcareous algae, lithothamnion crustac crustacea, decapods, lobster, shrimp shell defrmn_F deformation, convolute, flame structure, flow structure, load -cast - structure, pull apart diat diatom, diatomite/diatomaceous dolmt dolomite, ankerite, molar magnesium carbonate echnd echinoid, heart urchin, keyhole urchin, sea urchin, spiny urchin echndrm_F echinoderm 45 fault_F fault fces feces, coprolite ferug ferruginous, iron fragment, iron (-cement -streak -flake -stain), iron stone, laterite, limonite flasr_bed_F flaser bed fld feldspar, albite, andesine, anorthorite, K-feldspar, labradorite, orthoclase, plagioclase frm calcareous foramifera, foraminifera, globigerina bit, planktonic gas foamy, gas gbbro gabbro, diabase, diorite, dolerite, meta-dolerite, monzodiorite, monzonite, quartz diorite glacl glacial, diamicton, erratic, moraine, till glauc glauconite, greensand gniss gneiss, diorite gneiss, granite gneiss gradd_F coarsening upward, fining upward, increasing grain size, normally graded, reverse graded granit granite, aplite, granodiorite, pegmatite grnschst greenschist gstrpd gastropod, cerithium, conch, turitella, snail, nassarius, olivella, tenebrae, turitella h2s hydrogen sulfide, hydrogen sulfide -odor -smell, sulfur odor halmda halimeda, Peyssonnelia holoth holothurian, sea cucumber hvy_min heavy mineral, anatase, andalusite, apatite, black sand, brookite, cassiterite, clinozoisite, corundum, dumortierite, epidote, garnet, ilmenite, jadeite, kyanite, leucoxene, magnetite, monazite, ore mineral, piedmontite, rutile, sillimanite, sphene, spinel, staurolite, titanomagnetite, titanite, tourmaline, topaz, zircon, zoisite hydrt hydrate, gas hydrate ign_rck igneous rock, acidic rock, alkali basinite, augite plagioclase porphyry, augite porphyry, basic rock, dacite, felsite, olivine plagioclase clinopyroxene, olivine plagioclase phyric, plagioclase andesite porphyry, plagioclase augite porphyry, plagioclase porphyry, plutonic rock, porphyry, rhyolite, syenite, trachyte klp_F kelp, brown algae, ecklonia, M. vertebralis, red brown algae lamintd_F laminated lenticlr_bed lenticular bed, lenticular mass limstn limestone, beach rock, bioclastic -floatstone -grainstone -limestone - rudstone, boundstone, bryozoan -floatstone -grainstone -rudstone, calcareous -chip -rubble -rock, coral limestone, floatstone, grainstone, packstone, rudstone, wackestone lmp_F lump, aggregate, ball, cast, clump, compact clot, intraclast, pellet, pisolitic, peloid 46 lrg_frm large foram, foraminferal gravel, amphistegina, heterostegina, macro foraminifera, marginopora maf mafic, actinolite, aegirite, amphibole, augite, (brown- green- basaltic-) hornblende, bronzite, clinopyroxene, ferromagnesian, hypersthene, olivine, orthopyroxene, oxyhornblende, pyroxene, titanaugite, titaniferous, tremolite met metamorphic, calcsilicate, granitized, mylonite, porphyroblast, saussurite methne methane metlif metalliferous mica mica, biotite, chlorite, muscovite, sericite, talc mlsc mollusc mn_crst manganese crust, manganese iron oxide crust, manganese nodule, manganese pavement, manganese phosphate material mn_nod manganese nodule, iron manganese nodule, manganese concretion, micronodule mnoxd manganese oxide, iron-manganese (-coat -stain -veneer), iron-manganese oxide motl_F mottle, chickwire mottle mudlmp_F mud lump, armored mud ball, silty lump, clay (-aggregate -ball -chip - clast -gall -lump -mass -pod), mud (-aggregate -ball -chunk -clump -clot -clast -lump -pebble -pellet, claystone -chip -gall), sandstone fragment, soft pebble, shale (-fragment -concretion) mudstn mudstone, calcareous (-mudstone- siltstone), clay (-rock -shale -stone), marlstone, mud (-rock -stone), pelite, shale, siliceous shale, siltstone nan nannofossil coccolith, nannofossil (-coccolith -ooze), silicoflagellate nod_F nodule, concretion odr odor, anoxic, fetid, foul, fishy, organic, sewage, smell oil oil, oil glob, oil sheen ool oolite, sporbo ooz ooze ophiurd_F ophiuroid, brittle star, ophiomusium orgcbn organic carbon, carbonaceous, organic (-streak -detritus -matter -mud -content -enriched -material -part -paricle -rich -rimmed), sapropel oyst oyster, jingle shell peat peat, lignite pelag pelagic, hemipelagic, planktic, planktonic phspht phosphate, phosphorite pit_F pit, crater, feeding depression, hole, pockmark, mound, resting trace planr_bed_F planar bed plnk_frm planktonic foramifera, globerina, globorotalid, planktic foraminfera 47 plnt_F plant, mangrove, root, vegetation, weed, root ptr pteropod pumc pumice, ash pyrt pyrite, marcasite qtz quartz, arkosic sand, calcareous quartz sand, milky vein quartz, quartz (-content -fragment -grain -granule -groundmass -mass -rich -vein -veinlet -crystal), quartzose, quartzite (-cobble -gravel -pebble), sandstone (-chunk -fragment), silica rad radiolaria ripl ripple, bedform rlct_F relict root_struct root structure, root clast, root trace rzr_clm razor clam, ensis, pinna, pteria, pelecypod schst schist, (-albite -chlorite -epidote), (-albite -chlorite), (-albite -mica), (-albite -quartz -chlorite), (-biotite -quartz), (-chlorite -albite), (-chlorite -quartz -albite), (-chlorite), (-phyllitic), (-quartz -albite), (-quartz -albite -chlorite), (-quartz -biotite), (-quartz -chlorite) scllp scallop, astropecten, pecten, placopecten scour scour, crag and tail, erosional, lag deposit scphpd scaphopod, dentalium seagrs_F seagrass, acetabularia, amphibolis, batophora, eel grass, grass, halophila, heterozostera, phyllospadix, posidonia, sargassum, strap grass, syringodium, manatee grass, thallassia, zostera sft_alg_F soft algae, algal (-scum -filament -mush -strand), Bossea, green algae, macrophytic, red algae sftcrl_F soft coral, alcynacian, ascidian, coelentrate, gorgonian, hydrozoa shl shell, shell (-bed -bank -carpet -fraction -content -material), shellfish, valves shl_dbr shell debris, shell hash, coquina, shell (-bit -conglomerate -fragments -festoon -grit -lag -mash -material -piece -particle) shrmp_F shrimp, amphipod, ampelisca, copepod, isopod, tanid sidrt siderite, siderite nodule sil_ooz siliceous ooze, siliceous mud slte slate, phyllite, quartzite, metamorphic rock sndstn sandstone, gritstone, graywacke, labile sandstone, sandstone reef, wacke sol_crl solitary coral, cup coral, disc coral, horn coral, lophelia coral spng_F sponge, calcareous sponge, glass sponge, hard sponge, hexactinellid sponge, porifera, Thalassodendron sponge spoil_F spoil, brick, coke, dumped sediment srpul serpulid, serpulid tube, serpulid worm tube sulf sulfide, chalcopyrite 48 trail_F trail, trace (animal), track trrg terrigenous, lithic, inorganic umafic ultramafic, amphibolite, anorthosite, dunite, greenstone, harzburgite, lherzolite, norite, orthopyroxenite, periodotite, picrite, pyroxenite, serpentinite, troctolite, wehrlite vol_rck volcanic rock, volcanic (-cobble -pebble) volgls volcanic glass, obsidian, hyaloclastite, pyroclastic, quenched, vitric, subvitreous volrck volcanic rock, welded tuff volsed volcanic sediment, ash, tuff, lapilli wood wood, bark, twig wrm_F worm, chordate, echiurid, fan (-flat -glob -juicy -long -sand -tube worm), maldanid, pogonophora, priapulida, sliverfish, siphunculid, tunicate wrm_tbe_F worm tube, agglutinated worm tube, amphipod tube, annelid worm tube, arenicola, chitinous worm tube, diopatra worm tube, polychaete worm tube, pogonophoran tube worm, vestimentiform tube worm wavy_bed_F wavy bed Table E. Facies and their component makeup Facies values are determined by a combination of components and their mined values from word-based descriptions. Numeric textural, geochemical, and geophysical information held in PRS data files. Values represent memberships to fuzzy sets, given as percents. A minimum of 30% component presence is required to trip a given facies, and a component may trip more than one facies. See FAC files for actual data, and table D for component information. Facies notes presence only, not absence. Field name Parameter Data format, units Information/triggering components Latitude* Latitude Decimal 00.00000 Decimal degrees, 90° to -90° range Longitude* Longitude Decimal 000.00000 Decimal degrees, -180° to 180° range WaterDepth* Water depth Integer 00000 Meters SampleTop* Sample top Decimal 000.00 Meters below seabed surface SampleBase* Sample base Decimal 000.00 Meters below seabed surface SiteName* Site name Character XXX: XXX Survey or laboratory code for the sampling site DataSetKey* Data set number key Integer 000 Relational key to SRC file; SRC file contains links to source metadata SiteKey* Site number key Integer 0000000 Relational key to other data files. Each site counted sequentially as total output; core data may have more than one sample per site. SampleKey* Sample number key Integer 0000000 Relational key to other data files. Each site counted sequentially as total output; Multiple samples may be at 49 each site (i.e., in core). Terrigenous Terrigenous (%) Fld, hvy_min, maf, mica, qtz, trrg Carbonate Carbonate (%) Calcrst, calct, carb, dolmt, limstn, sidrt Igneous Igneous (%) Andest, baslt, gbbro, granit, ign_rck, umafic Volcanic Volcanic (%) Baslt, pumc, vol_rck, volgls, volrck, volsed Metamorphic Metamorphic (%) Bluschst, gniss, grnschst, met, schst, slte Mineralized Mineralized (%) Barit, metlif, phspht, pyrt, sulf AuthFeMn Authigenic Fe Mn (%) Mn_crust, mn_nod, mnoxd, ferug Ooze Ooze (%) Ooz, calc_ooz, sil_ooz Carbon Carbon (%) Coal, bitumn, orgcbn, peat GeochemSignal Geochemical signal (%) Gas, h2s, hydrt, methne, odr, oil Forams Forams (%) Aren_frm, bnth_frm, frm, lrg_frm, plnk_frm OtherCalcPelag Other calcareous pelagics (%) Nan, ptr, calc_ooz SilcPelag Siliceous pelagics (%) Diat, rad, sil_ooz Shell Shell (%) Shl, shl_dbr Coral Coral (%) Crl, crl_dbr, crlrf, sol_crl HardPlant Hard plants (%) C_alg, coralgl, crnalg, halmda 50