The National Ecological Observatory Network (NEON) is a continental-scale environmental observation facility funded by the U.S. National Science Foundation (NSF) and operated by Battelle. It runs standardized instrumentation and field sampling protocols at 81 field sites across 20 eco-climatic domains of the United States, including Alaska, Hawaii, and Puerto Rico, and is designed to operate for 30 or more years. For a researcher, the practical distinction that matters most is this: NEON is a data-generating observatory, not a records aggregator. It produces its own long-term, standardized measurements rather than collecting and republishing data that other institutions have already gathered, which is the model used by aggregators such as GBIF.
What Is NEON?
NEON was built to answer a problem that site-specific ecological studies cannot solve on their own: understanding how ecosystems across an entire continent respond to climate change, land-use change, invasive species, and shifting water availability requires measurements that are collected the same way, with the same instruments and protocols, at many locations over decades. A single university field station can produce excellent local data, but its methods, instruments, and sampling calendar are rarely identical to the station down the road, which makes rigorous cross-site comparison difficult. NEON addresses this by operating one observatory with one set of standardized protocols across all 81 sites, so that a soil temperature reading from a site in the Pacific Northwest and one from the Southern Plains are directly comparable rather than needing to be reconciled after the fact.
The observatory is an NSF major facility; NSF provides the funding and sets the scientific mission, while Battelle, a nonprofit applied-science and technology organization, holds the operating contract and runs the day-to-day field and data operations. This funder/operator structure is worth knowing because it explains why NEON data carries no cost or licensing negotiation for researchers: as an NSF-funded public facility, NEON data products are free and openly available.
How NEON Collects Data
NEON organizes its measurements into three collection systems, each producing a different kind of data:
- Airborne Observation Platform (AOP) — a fixed-wing aircraft carrying imaging spectrometer, high-resolution camera, and LiDAR instruments that overflies each site on a rotating schedule, producing remote-sensing data on vegetation structure, canopy chemistry, and land cover.
- Instrument System (IS) — automated sensors mounted on towers, in soil arrays, and in streams and lakes that continuously log physical and chemical measurements such as air and soil temperature, precipitation, wind, CO2 and water-vapor flux, and stream discharge.
- Observational System (OS) — field technicians following standardized protocols to sample and identify organisms and materials by hand, covering groups such as plants, small mammals, birds, ground beetles, mosquitoes, ticks, soil microbes, and aquatic macroinvertebrates.
Because all three systems run the same protocols at every site, a researcher can pull a given measurement type from any subset of NEON’s sites and know it was collected the same way, which is the foundation of NEON’s value for cross-site and long-term comparative work.
What Data Products NEON Provides
NEON publishes over 180 data products spanning atmospheric, soil, hydrological, biological, and remote-sensing measurements — everything from wind speed and albedo to microbial community composition, tree canopy water content, and small-mammal capture records. Each product is documented against a standardized methods and quality-assurance protocol, and most are structured around Ecological Metadata Language (EML) for dataset-level description, the same metadata standard widely used across ecological and environmental science repositories.
Data are released on two tracks. Provisional data are published quickly after collection and may still be corrected or revised as quality checks continue — useful for near-real-time monitoring but not guaranteed to be reproducible if downloaded again later. Release data are fixed, versioned snapshots (e.g., an annual “RELEASE” tag) that do not change once published and are each assigned a citable DOI, which is the version researchers should use and cite in any publication where reproducibility matters.
NEON vs. GBIF: Sensor Network vs. Occurrence Aggregator
NEON and GBIF are both major sources of open ecological data, and researchers new to either often assume they overlap more than they do. They serve different purposes and are frequently used together rather than as substitutes for one another.
| NEON | GBIF | |
|---|---|---|
| What it is | A single, NSF-funded observatory that operates its own field sites and instruments | An aggregator that republishes species-occurrence records contributed by thousands of independent institutions |
| Data origin | Generates its own standardized measurements at 81 fixed sites | Ingests and republishes existing records: museum specimens, herbaria, citizen-science observations, monitoring programs |
| Data type | Sensor and instrument readings, remote sensing, plus standardized organism sampling — abundance, condition, and environmental context, not just presence | Primarily occurrence records — where and when a taxon was recorded, formatted to Darwin Core |
| Geographic scope | 81 fixed U.S. sites (including Alaska, Hawaii, Puerto Rico) across 20 eco-climatic domains | Global, wherever a contributing institution has published data |
| Standardization model | One observatory, one protocol per measurement, applied identically everywhere | Depends on the contributing institution mapping its own records onto the shared Darwin Core standard |
| Temporal design | Built for continuous, long-term (30+ year) monitoring at the same locations | A continuously growing archive; temporal coverage depends entirely on what has been contributed and when |
In practice, a researcher studying a shift in a species’ range might use GBIF to assemble historical and crowd-sourced occurrence records across a broad geography, then use NEON’s standardized environmental sensor data from the sites that fall within or near that range to explain the climatic and soil conditions associated with the shift. The two are complementary, not competing, sources.
Practical Use Cases for Ecological Researchers
- Long-term trend detection. Because instrumentation and protocols stay constant across NEON’s 30-year design lifespan, researchers can detect genuine environmental trends (e.g., soil moisture decline, shifting phenology) without needing to control for methodological drift between measurement periods.
- Cross-site comparative ecology. Studies comparing ecosystem response across biomes — for example, how carbon flux differs between desert and forest domains — depend on measurements being collected identically at every site, which is exactly what NEON’s standardized protocols provide.
- Calibrating and validating remote sensing. NEON’s Airborne Observation Platform data is frequently used alongside satellite imagery to ground-truth vegetation and land-cover classifications at a resolution most satellite products cannot match on their own.
- Training and testing ecological forecasting models. NEON data underpins community forecasting exercises such as the NEON Ecological Forecasting Initiative, where researchers submit near-term predictions (e.g., for phenology or tick abundance) that are scored against NEON’s subsequent observations.
- Contextualizing occurrence data. As above, pairing NEON’s environmental sensor readings with occurrence records from GBIF or other biodiversity databases lets researchers explain, not just document, where and why organisms occur.
Accessing and Citing NEON Data
NEON data is freely available through the NEON Data Portal, which allows browsing and download by data product, site, and date range, and through a public API for programmatic access. R and Python users typically pull data with the neonUtilities package, which handles the multi-file downloads NEON’s data products are often split into and can retrieve a standardized citation for the specific product and Release version used. Because NEON is public infrastructure, there is no cost or data-use license to negotiate, but NEON does require citation: researchers using Release data should cite the specific data product and its DOI; researchers using Provisional data (which can change) are expected to archive the exact version they used and cite that archived copy, since a later download of “the same” provisional product is not guaranteed to be identical. This matters directly for data management plans that name NEON as a data source: a DMP or methods section should specify which Release (or archived Provisional snapshot) was used, not just “NEON data,” to keep the work reproducible.
Frequently Asked Questions
Is NEON data free to use?
Yes. As an NSF-funded facility, all of NEON’s published data products are free and openly available with no access fee, though NEON asks that publications using its data include the specified citation and, where relevant, an acknowledgment of NSF funding.
Does NEON only cover species occurrences, like GBIF?
No. Species observations are only one part of NEON’s Observational System; NEON also produces continuous atmospheric, soil, and hydrological sensor data and airborne remote-sensing imagery, none of which GBIF collects. GBIF, in turn, aggregates occurrence records from thousands of institutions worldwide, far beyond NEON’s 81 sites, but does not operate sensors or generate its own primary measurements.
How many NEON sites are there, and where?
81 field sites spread across 20 eco-climatic domains of the United States, including Alaska, Hawaii, and Puerto Rico, chosen to represent the country’s major ecosystem types.
How long has NEON been collecting data, and for how long will it continue?
NEON was designed as a long-term observatory intended to operate for 30 years or more, specifically so that researchers can distinguish genuine long-term ecological trends from short-term variability.
What format is NEON data published in?
Data products are documented and structured around standardized methods documentation and, for dataset-level metadata, Ecological Metadata Language (EML). Tabular sensor and observational data are typically distributed as CSV files bundled by site, date, and data product, most easily retrieved with the neonUtilities R or Python package rather than manual download for anything beyond a small, single-site query.
