NEON - National Ecological Observatory Network
Explore opportunities for collaboration with NEON (http://www.neoninc.org), currently in development. They plan to be fully operational in 2017.
The NEON observatory collects and provides high-quality, standardized data from its 106 sites (60 terrestrial, 36 aquatic and 10 aquatic experimental) across the U.S. (including Alaska, Hawaii and Puerto Rico) using instrument measurements and field sampling. The sites have been strategically selected to represent different regions of vegetation, landforms, climate, and ecosystem performance. NEON will combine site-based data with remotely sensed data and existing continental-scale data sets (e.g., satellite data) to provide a range of scaled data products that can be used to describe changes in the nation’s ecosystem through space and time.
#1 Updated by Laura Moyers over 8 years ago
- NodeIdentifier set to urn:node:NEON
- Target version set to Deploy by end of Y2Q1
- MN Description set to NEON is a continental-scale ecological observation facility sponsored by the National Science Foundation to gather and synthesize data on the impacts of climate change, land use change and invasive species on natural resources and biodiversity.
- Base URL set to http://www.neoninc.org/
Most recent meeting Friday 21 August 2015. See notes: https://epad.dataone.org/pad/p/NEON_and_DataONE
#5 Updated by Laura Moyers almost 8 years ago
Note from Christine Laney at NEON 3/2/16:
This email is to introduce you to Joe Zoller, our software engineer who will be standing up the DataONE API here at NEON. I wanted to put you in touch for any questions that you may have for one another. EML progress continues as well; we hope to have some valid documents ready in the next couple of weeks.
From Joe Zoller at NEON 3/3/16:
I’ll be meeting with our IT folks today to spec out an internal test VM, and a DMZ VM for the Member Node. Since we’re a Java shop using Oracle’s flavor of CentOS, we are planning on using Metacat (at least to start with).
There will be more questions as we get into the process, but the online docs seem good. For the moment, is there any technical advice that you have for the team here?
I’m following the Member Node Deployment Checklist, but it’s pretty high level. Other than actually setting up the API, what deliverables that need to be fulfilled during this process?
#12 Updated by Laura Moyers over 7 years ago
- Target version changed from Deploy by end of Y2Q4 to Operational
- Status changed from In Review to Operational