skip to main content
US FlagAn official website of the United States government
dot gov icon
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
https lock icon
Secure .gov websites use HTTPS
A lock ( lock ) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.

Explore Research Products in the PAR
It may take a few hours for recently added research products to appear in PAR search results.


Title: Long-term trends in paleointensity: The contribution of DSDP/ODP submarine basaltic glass collections (Dataset)
Paleomagnetic, rock magnetic, or geomagnetic data found in the MagIC data repository from a paper titled: Long-term trends in paleointensity: The contribution of DSDP/ODP submarine basaltic glass collections  more » « less
Award ID(s):
2126298
PAR ID:
10558646
Author(s) / Creator(s):
Publisher / Repository:
Magnetics Information Consortium (MagIC)
Date Published:
Subject(s) / Keyword(s):
Extrusive Igneous Submarine Volcanic Pillow Volcanic Glass Chilled Margin Sill Basalt 0 164400000 Years BP
Format(s):
Medium: X
Location:
(East Bound Longitude:71.0; North Bound Latitude:-11; South Bound Latitude:-11.0; West Bound Longitude:71.0); (East Bound Longitude:61.0; North Bound Latitude:-13; South Bound Latitude:-13.0; West Bound Longitude:61.0); (East Bound Longitude:118.0; North Bound Latitude:-16; South Bound Latitude:-16.0; West Bound Longitude:118.0); (Latitude:-19.1877; Longitude:9.3858); (East Bound Longitude:-178; North Bound Latitude:-19; South Bound Latitude:-19.0; West Bound Longitude:-178); (East Bound Longitude:-177; North Bound Latitude:-19; South Bound Latitude:-19.0; West Bound Longitude:-177); (East Bound Longitude:178.0; North Bound Latitude:-25; South Bound Latitude:-25.0; West Bound Longitude:178.0); (East Bound Longitude:-11; North Bound Latitude:-26; South Bound Latitude:-26.0; West Bound Longitude:-11); (East Bound Longitude:-5; North Bound Latitude:-27; South Bound Latitude:-27.0; West Bound Longitude:-5); (East Bound Longitude:3.0; North Bound Latitude:-29; South Bound Latitude:-29.0; West Bound Longitude:3.0); (East Bound Longitude:-177; North Bound Latitude:-2; South Bound Latitude:-20.0; West Bound Longitude:-177); (East Bound Longitude:-76; North Bound Latitude:-47; South Bound Latitude:-47.0; West Bound Longitude:-76); (East Bound Longitude:-79; North Bound Latitude:-6; South Bound Latitude:-60.0; West Bound Longitude:-79); (Latitude:1.4348; Longitude:-113.842); (Latitude:11.8902; Longitude:48.2452); (East Bound Longitude:174.0; North Bound Latitude:11; South Bound Latitude:11.0; West Bound Longitude:174.0); (Latitude:12.5; Longitude:-91); (East Bound Longitude:153.0; North Bound Latitude:12; South Bound Latitude:12.0; West Bound Longitude:153.0); (East Bound Longitude:168.0; North Bound Latitude:15; South Bound Latitude:15.0; West Bound Longitude:168.0); (East Bound Longitude:135.0; North Bound Latitude:16; South Bound Latitude:16.0; West Bound Longitude:135.0); (East Bound Longitude:-76; North Bound Latitude:16; South Bound Latitude:16.0; West Bound Longitude:-76); (East Bound Longitude:-59; North Bound Latitude:16; South Bound Latitude:16.0; West Bound Longitude:-59); (Latitude:17.8642; Longitude:146.9343); (Latitude:17.9113; Longitude:145.1795); (East Bound Longitude:133.0; North Bound Latitude:18; South Bound Latitude:18.0; West Bound Longitude:133.0); (East Bound Longitude:156.0; North Bound Latitude:19; South Bound Latitude:19.0; West Bound Longitude:156.0); (East Bound Longitude:-159; North Bound Latitude:19; South Bound Latitude:19.0; West Bound Longitude:-159); (East Bound Longitude:-84; North Bound Latitude:1; South Bound Latitude:1.0; West Bound Longitude:-84); (East Bound Longitude:-104; North Bound Latitude:1; South Bound Latitude:10.0; West Bound Longitude:-104); (Latitude:22.5; Longitude:-43.5); (Latitude:23.0058; Longitude:-113.9952); (East Bound Longitude:-109; North Bound Latitude:23; South Bound Latitude:23.0; West Bound Longitude:-109); (East Bound Longitude:-108; North Bound Latitude:23; South Bound Latitude:23.0; West Bound Longitude:-108); (East Bound Longitude:-46; North Bound Latitude:23; South Bound Latitude:23.0; West Bound Longitude:-46); (East Bound Longitude:-68; North Bound Latitude:25; South Bound Latitude:25.0; West Bound Longitude:-68); (East Bound Longitude:-75; North Bound Latitude:28; South Bound Latitude:28.0; West Bound Longitude:-75); (East Bound Longitude:-118; North Bound Latitude:29; South Bound Latitude:29.0; West Bound Longitude:-118); (East Bound Longitude:161.0; North Bound Latitude:2; South Bound Latitude:2.0; West Bound Longitude:161.0); (East Bound Longitude:-86; North Bound Latitude:2; South Bound Latitude:2.0; West Bound Longitude:-86); (East Bound Longitude:147.0; North Bound Latitude:2; South Bound Latitude:20.0; West Bound Longitude:147.0); (East Bound Longitude:-121; North Bound Latitude:33; South Bound Latitude:33.0; West Bound Longitude:-121); (East Bound Longitude:-42; North Bound Latitude:33; South Bound Latitude:33.0; West Bound Longitude:-42); (East Bound Longitude:-44; North Bound Latitude:34; South Bound Latitude:34.0; West Bound Longitude:-44); (East Bound Longitude:-41; North Bound Latitude:35; South Bound Latitude:35.0; West Bound Longitude:-41); (Latitude:37.77; Longitude:-37.3435); (East Bound Longitude:-35; North Bound Latitude:37; South Bound Latitude:37.0; West Bound Longitude:-35); (East Bound Longitude:-34; North Bound Latitude:37; South Bound Latitude:37.0; West Bound Longitude:-34); (East Bound Longitude:-35; North Bound Latitude:39; South Bound Latitude:39.0; West Bound Longitude:-35); (East Bound Longitude:-30; North Bound Latitude:46; South Bound Latitude:46.0; West Bound Longitude:-30); (East Bound Longitude:157.0; North Bound Latitude:4; South Bound Latitude:4.0; West Bound Longitude:157.0); (East Bound Longitude:-133.3095; North Bound Latitude:5; South Bound Latitude:0.5; West Bound Longitude:-133.3095); (East Bound Longitude:124.0; North Bound Latitude:5; South Bound Latitude:5.0; West Bound Longitude:124.0); (East Bound Longitude:90.0; North Bound Latitude:5; South Bound Latitude:5.0; West Bound Longitude:90.0); (East Bound Longitude:-31; North Bound Latitude:64; South Bound Latitude:64.0; West Bound Longitude:-31); (East Bound Longitude:-13; North Bound Latitude:69; South Bound Latitude:69.0; West Bound Longitude:-13); (East Bound Longitude:165.0; North Bound Latitude:7; South Bound Latitude:7.0; West Bound Longitude:165.0); (East Bound Longitude:-106; North Bound Latitude:9; South Bound Latitude:9.0; West Bound Longitude:-106); (East Bound Longitude:-105; North Bound Latitude:9; South Bound Latitude:9.0; West Bound Longitude:-105); (Latitude:-11.0; Longitude:71.0); (Latitude:-13.0; Longitude:61.0); (Latitude:-16.0; Longitude:118.0); (Latitude:-16.0; Longitude:118.0); (Latitude:-19.0; Longitude:-178); (Latitude:-19.0; Longitude:-177); (Latitude:-19.1877; Longitude:9.3858); (Latitude:-20.0; Longitude:-177); (Latitude:-20.0; Longitude:-177); (Latitude:-25.0; Longitude:178.0); (Latitude:-26.0; Longitude:-11); (Latitude:-27.0; Longitude:-5); (Latitude:-29.0; Longitude:3.0); (Latitude:-47.0; Longitude:-76); (Latitude:-47.0; Longitude:-76); (Latitude:-60.0; Longitude:-79); (Latitude:0.4985; Longitude:-133.3095); (Latitude:1.0; Longitude:-84); (Latitude:1.4348; Longitude:-113.842); (Latitude:10.0; Longitude:-104); (Latitude:11.0; Longitude:174.0); (Latitude:11.8902; Longitude:48.2452); (Latitude:12.0; Longitude:153.0); (Latitude:12.5; Longitude:-91); (Latitude:15.0; Longitude:168.0); (Latitude:16.0; Longitude:135.0); (Latitude:16.0; Longitude:-76); (Latitude:16.0; Longitude:-59); (Latitude:17.8642; Longitude:146.9343); (Latitude:17.9113; Longitude:145.1795); (Latitude:18.0; Longitude:133.0); (Latitude:19.0; Longitude:156.0); (Latitude:19.0; Longitude:-159); (Latitude:2.0; Longitude:161.0); (Latitude:2.0; Longitude:-86); (Latitude:20.0; Longitude:147.0); (Latitude:22.5; Longitude:-43.5); (Latitude:23.0058; Longitude:-113.9952); (Latitude:23.0; Longitude:-109); (Latitude:23.0; Longitude:-108); (Latitude:23.0; Longitude:-108); (Latitude:23.0; Longitude:-108); (Latitude:23.0; Longitude:-46); (Latitude:23.0; Longitude:-46); (Latitude:25.0; Longitude:-68); (Latitude:25.0; Longitude:-68); (Latitude:28.0; Longitude:-75); (Latitude:29.0; Longitude:-118); (Latitude:33.0; Longitude:-121); (Latitude:33.0; Longitude:-42); (Latitude:34.0; Longitude:-44); (Latitude:34.0; Longitude:-44); (Latitude:35.0; Longitude:-41); (Latitude:35.0; Longitude:-41); (Latitude:37.0; Longitude:-35); (Latitude:37.0; Longitude:-34); (Latitude:37.0; Longitude:-34); (Latitude:37.0; Longitude:-34); (Latitude:37.77; Longitude:-37.3435); (Latitude:39.0; Longitude:-35); (Latitude:4.0; Longitude:157.0); (Latitude:46.0; Longitude:-30); (Latitude:5.0; Longitude:124.0); (Latitude:5.0; Longitude:124.0); (Latitude:5.0; Longitude:90.0); (Latitude:64.0; Longitude:-31); (Latitude:69.0; Longitude:-13); (Latitude:7.0; Longitude:165.0); (Latitude:9.0; Longitude:-106); (Latitude:9.0; Longitude:-105)
Right(s):
Creative Commons Attribution 4.0 International
Institution:
Paleomagnetic Lab Scripps Institution Of Oceanography, UCSD, USA
Sponsoring Org:
National Science Foundation
More Like this
  1. ; ; ; ; (, Electronics)
    null (Ed.)
    Blockchain is a developing technology that can be utilized for secure data storage and sharing. In this work, we examine the cost of Blockchain-based data storage for constrained Internet of Things (IoT) devices. We had two phases in the study. In the first phase, we stored data retrieved from a temperature/humidity sensor connected to an Ethereum testnet blockchain using smart contracts in two different ways: first, appending the new data to the existing data, storing all sensor data; and second, overwriting the new data onto the existing data, storing only a recent portion of the data. In the second phase, we stored simulated data from several sensors on the blockchain assuming sensor data is numeric. We proposed a method for encoding the data from the sensors in one variable and compared the costs of storing the data in an array versus storing the encoded data from all sensors in one variable. We also compared the costs of carrying out the encoding within the smart contract versus outside the smart contract. In the first phase, our results indicate that overwriting data points is more cost-efficient than appending them. In the second phase, using the proposed encoding method to store the data from several sensors costs significantly less than storing the data in an array, if the encoding is done outside the smart contract. If the encoding is carried out in the smart contract, the cost is still less than storing the data in an array, however, the difference is not significant. The study shows that even though expensive, for applications where the integrity and transparency of data are crucial, storing IoT sensor data on Ethereum could be a reliable solution. 
    more » « less
  2. ; ; (, CBE—Life Sciences Education)
    Data are becoming increasingly important in science and society, and thus data literacy is a vital asset to students as they prepare for careers in and outside science, technology, engineering, and mathematics and go on to lead productive lives. In this paper, we discuss why the strongest learning experiences surrounding data literacy may arise when students are given opportunities to work with authentic data from scientific research. First, we explore the overlap between the fields of quantitative reasoning, data science, and data literacy, specifically focusing on how data literacy results from practicing quantitative reasoning and data science in the context of authentic data. Next, we identify and describe features that influence the complexity of authentic data sets (selection, curation, scope, size, and messiness) and implications for data-literacy instruction. Finally, we discuss areas for future research with the aim of identifying the impact that authentic data may have on student learning. These include defining desired learning outcomes surrounding data use in the classroom and identification of teaching best practices when using data in the classroom to develop students’ data-literacy abilities. 
    more » « less
  3. ; (, 2019 IEEE 9th Annual Computing and Communication Workshop and Conference (CCWC))
    Recent studies have shown that several government and business organizations experience huge data breaches. Data breaches increase in a daily basis. The main target for attackers is organization sensitive data which includes personal identifiable information (PII) such as social security number (SSN), date of birth (DOB) and credit card /debit card (CCDC). The other target is encryption/decryption keys or passwords to get access to the sensitive data. The cloud computing is emerging as a solution to store, transfer and process the data in a distributed location over the Internet. Big data and internet of things (IoT) increased the possibility of sensitive data exposure. Most methods used for the attack are hacking, unauthorized access, insider theft and false data injection on the move. Most of the attacks happen during three different states of data life cycle such as data-at-rest, data-in-use, and data-in-transit. Hence, protecting sensitive data at all states particularly when data is moving to cloud computing environment needs special attention. The main purpose of this research is to analyze risks caused by data breaches, personal and organizational weaknesses to protect sensitive data and privacy. The paper discusses methods such as data classification and data encryption at different states to protect personal and organizational sensitive data. The paper also presents mathematical analysis by leveraging the concept of birthday paradox to demonstrate the encryption key attack. The analysis result shows that the use of same keys to encrypt sensitive data at different data states make the sensitive data less secure than using different keys. Our results show that to improve the security of sensitive data and to reduce the data breaches, different keys should be used in different states of the data life cycle. 
    more » « less
  4. ; ; ; (, Fostering Data Reusability: Increasing Impact and Ease in Sharing and Reusing Research Data)
    null (Ed.)
    This workshop report tackles one of the most significant barriers to progress in making research data publicly accessible: the hurdles faced by researchers in producing and reusing publicly accessible research data, both in their research practice and in the surrounding ecosystem shaped by external stakeholders. The central challenge in high quality data sharing is to understand how researchers can increase the downstream value of shared data while reducing burden for both data producers and reusers. The report summarizes recommendations and actions from an NSF-sponsored virtual workshop series on Fostering Data Reusability: Increasing Impact and Ease in Data Sharing and Reuse held in June 2021. The series explored what context data reusers need to evaluate and appropriately reuse the data, identified practices that will improve data reusability and reduce the burden in producing and sharing research data, and used a stakeholder alignment approach to identify actions stakeholders could take to foster progress in reducing burden and increasing impact in data sharing and reuse. 
    more » « less
  5. (, Biodiversity Information Science and Standards)
    Two programs that provide high-quality long-term ecological data, the Environmental Data Initiative (EDI) and the National Ecological Observatory Network (NEON), have recently teamed up with data users interested in synthesizing biodiversity data, such as ecological synthesis working groups supported by the US Long Term Ecological Research (LTER) Network Office, to make their data more Findable, Interoperable, Accessible, and Reusable (FAIR). To this end: we have developed a flexible intermediate data design pattern for ecological community data (L1 formatted data in Fig. 1, see Fig. 2 for design details) called "ecocomDP" (O'Brien et al. 2021), and we provide tools to work with data packages in which this design pattern has been implemented. we have developed a flexible intermediate data design pattern for ecological community data (L1 formatted data in Fig. 1, see Fig. 2 for design details) called "ecocomDP" (O'Brien et al. 2021), and we provide tools to work with data packages in which this design pattern has been implemented. The ecocomDP format provides a data pattern commonly used for reporting community level data, such as repeated observations of species-level measures of biomass, abundance, percent cover, or density across multiple locations. The ecocomDP library for R includes tools to search for data packages, download or import data packages into an R (programming language) session in a standard format, and visualization tools for data exploration steps that are recommended for data users prior to any cross-study synthesis work. To date, EDI has created 70 ecocomDP data packages derived from their holdings, which include data from the US Long Term Ecological Research (US LTER) program, Long Term Research in Environmental Biology (LTREB) program, and other projects, which are now discoverable and accessible using the ecocomDP library. Similarly, NEON data products for 12 taxonomic groups are discoverable using the ecocomDP search tool. Input from data users provided guidance for the ecocomDP developers in mapping the NEON data products to the ecocomDP format to facilitate interoperability with the ecocomDP data packages available from the EDI repository. The standardized data design pattern allows common data visualizations across data packages, and has the potential to facilitate the development of new tools and workflows for biodiversity synthesis. The broader impacts of this collaboration are intended to lower the barriers for researchers in ecology and the environmental sciences to access and work with long-term biodiversity data and provide a hub around which data providers and data users can develop best practices that will build a diverse and inclusive community of practice. 
    more » « less
  • Citation Formats
  • MLA
  • APA
  • Chicago
  • BibTeX
  • Save / Share this Record
  • Send to Email