Skills

Environmental Monitoring Data Collection

6 weeks · 0 milestones

Collect real environmental monitoring data from a specific named location using a documented methodology: air quality (PM2.5, NO₂, CO₂), water quality (pH, dissolved oxygen, turbidity, conductivity), biodiversity count, temperature, or equivalent environmental parameter. Document location coordinates, measurement dates and times, equipment or method used, and any data quality flags. For students without field access or equipment, monitoring data from named open government or citizen science networks is accepted: NOAA monitoring stations, EPA Air Quality System (free), OpenAQ (free), iNaturalist (for biodiversity), or Copernicus atmospheric data — but the provenance (station name, coordinates, data version) must be fully documented. The proof is a real documented dataset with full provenance — not a description of what you would measure, but actual data from an actual named location. Reviewed by an environmental scientist who examines the methodology for sampling bias and asks how the monitoring protocol would need to change to answer a specific environmental question.

Part of: Natural Sciences · Proves for: UG, Engineers

Milestone map

3 milestones

Design a Monitoring Protocol and Collect a Dataset

2–3 weeks

Design a rigorous environmental monitoring protocol for a specific variable (air quality, water quality, biodiversity, climate, or soil chemistry). Define: the variable, spatial and temporal sampling design, measurement method, detection limits and uncertainty, and data management plan. Collect data either through original field measurements or — equally valid — by accessing and downloading an appropriate publicly available dataset using the protocol's spatial and temporal criteria. Using public data sources is explicitly encouraged and equivalent in rigor to original collection when properly documented.

Proof required

Submit: (a) your monitoring protocol document (minimum 800 words) covering all five elements: variable, sampling design, measurement method, detection limits/uncertainty, and data management plan, (b) the collected dataset with clear labelling of source, spatial coverage, temporal coverage, measurement method, and any quality control applied — if using public data, include the download URL and the specific query or filter used, and (c) a data quality assessment confirming the dataset meets the protocol's criteria (completeness, accuracy, consistency). Free public sources: NOAA CDO, EPA AQS, OpenAQ, NASA Earthdata.

What gets checked

Protocol is specific and reproducible — another scientist reading it should be able to replicate your data collection exactly
Dataset is clearly attributed — source, download date, and any subset/filter criteria are documented
Data quality assessment addresses completeness, accuracy, and consistency — not just 'data looks good'

Common mistakes

Monitoring protocol is generic — 'measure air quality at multiple locations' is not a protocol; named sites, specific methodology, and temporal sampling schedule are all required
Using a public dataset but not documenting the specific query used to extract it — reproducibility requires knowing exactly what was downloaded

Resources

What a verifier looks for

Check that the protocol is genuinely specific: does it state the exact measurement variable, sampling locations (coordinates or named locations), temporal sampling interval, and measurement method?
If public data is used, verify the download URL works and the data matches what the protocol specified — confirm spatial and temporal coverage aligns with the stated criteria.

You'll sign in first, then come straight back here.

Statistical Analysis of Environmental Monitoring Data

2–3 weeks

Apply appropriate statistical methods to detect patterns, trends, or anomalies in your dataset. Environmental monitoring analysis typically requires: time-series analysis for trend detection, spatial analysis for hotspot identification, or comparative analysis for before-after or treatment-control designs. Use free open-source tools (R or Python) for all analysis. Document every analytical decision in a reproducible analysis script.

Proof required

Submit: (a) your analysis script (R or Python) with comments explaining each analytical decision, (b) the key outputs including at minimum one trend or pattern analysis with statistical significance values, (c) a results narrative (minimum 600 words) explaining what the analysis found in plain language and its implications, and (d) a peer review from an environmental data scientist or statistician (minimum 150-word written review) confirming the statistical approach is appropriate for the data structure and stated research question.

What gets checked

Analysis script is commented and reproducible — a reviewer should be able to run it on the same dataset and get the same results
Statistical significance is reported with p-values or confidence intervals — not just descriptive statements about trends
Peer review is from someone with quantitative environmental science training

Common mistakes

Analysis uses only Excel charts without statistical tests — environmental monitoring data requires statistical tests that Excel cannot reliably perform
Missing value treatment is not documented — all real environmental datasets have missing values and how they are handled significantly affects results

Resources

What a verifier looks for

Review the analysis script: is each analytical decision documented with a comment explaining why that choice was made? Well-documented scripts show the submitter understands what they are doing.
Check the statistical approach: does the test chosen match the data structure? Time-series data with autocorrelation requires different tests than independent cross-sectional samples.

You'll sign in first, then come straight back here.

Produce a Data Report and Present to Scientific Peer

2 weeks

Produce a full data report documenting your monitoring protocol, dataset, analysis, and findings in a format that could be shared with environmental decision-makers or published as a technical report. Present to at least one environmental scientist or policy professional and respond to methodological questions about your sampling design and analytical choices.

Proof required

Submit: (a) the full data report (minimum 2,500 words with sections: introduction, monitoring protocol, dataset description, analysis methods, results, limitations, and conclusions), (b) an attendance record for the review session (reviewer name, qualifications, date), and (c) a Q&A log (minimum 300 words) documenting at least two methodological challenges from the reviewer and your responses.

What gets checked

Report covers all seven required sections — not just results and conclusions
Limitations section is honest and specific — 'PM2.5 data has higher uncertainty at low concentrations due to monitor detection limits' not 'some uncertainties exist'
Q&A log shows the reviewer challenged the methodology, not just the findings

Common mistakes

Data report is written as an essay about the environmental topic rather than as a technical methods and results document
Review session involves someone without scientific background — peer review requires a reviewer who can challenge methodology

Powstik Guide

A full data report, challenged by a scientific peer.

Steps

Assemble protocol, dataset, analysis and findings into one report.
Check every number traces to a calculation.
Book a qualified reviewer.
Log at least three challenges and your answers.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and credentials:

Challenge 1 (your protocol or data quality):
  What they asked:
  My answer:
  Did it hold?
Challenge 2:
  What they asked:
  My answer:
  Did it hold?
Challenge 3:
  What they asked:
  My answer:
  Did it hold?

What I will change because of this session:

What gets sent back

A reviewer who doesn't meet the stated bar.
Notes without the reviewer's name and role.
Report under 2,500 words.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Your most valuable questions challenge design choices: 'Why did you choose weekly rather than daily sampling?' or 'How did you handle the fact that your monitoring period overlaps with a seasonal change that might confound your trend analysis?'
Provide a written review (minimum 150 words) confirming your qualifications, the specific questions you asked, and whether the submitter demonstrated genuine understanding of the methodology.

You'll sign in first, then come straight back here.

Part of

Environmental Science & Ecology →Environmental Engineering →

Related outcomes

Milestone map

3 milestones

Design a Monitoring Protocol and Collect a Dataset

2–3 weeks

Proof required

What gets checked

Protocol is specific and reproducible — another scientist reading it should be able to replicate your data collection exactly
Dataset is clearly attributed — source, download date, and any subset/filter criteria are documented
Data quality assessment addresses completeness, accuracy, and consistency — not just 'data looks good'

Common mistakes

Monitoring protocol is generic — 'measure air quality at multiple locations' is not a protocol; named sites, specific methodology, and temporal sampling schedule are all required
Using a public dataset but not documenting the specific query used to extract it — reproducibility requires knowing exactly what was downloaded

Resources

What a verifier looks for

Check that the protocol is genuinely specific: does it state the exact measurement variable, sampling locations (coordinates or named locations), temporal sampling interval, and measurement method?
If public data is used, verify the download URL works and the data matches what the protocol specified — confirm spatial and temporal coverage aligns with the stated criteria.

You'll sign in first, then come straight back here.

Statistical Analysis of Environmental Monitoring Data

2–3 weeks

Proof required

What gets checked

Analysis script is commented and reproducible — a reviewer should be able to run it on the same dataset and get the same results
Statistical significance is reported with p-values or confidence intervals — not just descriptive statements about trends
Peer review is from someone with quantitative environmental science training

Common mistakes

Analysis uses only Excel charts without statistical tests — environmental monitoring data requires statistical tests that Excel cannot reliably perform
Missing value treatment is not documented — all real environmental datasets have missing values and how they are handled significantly affects results

Resources

What a verifier looks for

Review the analysis script: is each analytical decision documented with a comment explaining why that choice was made? Well-documented scripts show the submitter understands what they are doing.
Check the statistical approach: does the test chosen match the data structure? Time-series data with autocorrelation requires different tests than independent cross-sectional samples.

You'll sign in first, then come straight back here.

Produce a Data Report and Present to Scientific Peer

2 weeks

Proof required

What gets checked

Report covers all seven required sections — not just results and conclusions
Limitations section is honest and specific — 'PM2.5 data has higher uncertainty at low concentrations due to monitor detection limits' not 'some uncertainties exist'
Q&A log shows the reviewer challenged the methodology, not just the findings

Common mistakes

Data report is written as an essay about the environmental topic rather than as a technical methods and results document
Review session involves someone without scientific background — peer review requires a reviewer who can challenge methodology

Powstik Guide

A full data report, challenged by a scientific peer.

Steps

Assemble protocol, dataset, analysis and findings into one report.
Check every number traces to a calculation.
Book a qualified reviewer.
Log at least three challenges and your answers.

Template

Review session log
Date:            Duration:
Reviewer name:
Reviewer role and credentials:

Challenge 1 (your protocol or data quality):
  What they asked:
  My answer:
  Did it hold?
Challenge 2:
  What they asked:
  My answer:
  Did it hold?
Challenge 3:
  What they asked:
  My answer:
  Did it hold?

What I will change because of this session:

What gets sent back

A reviewer who doesn't meet the stated bar.
Notes without the reviewer's name and role.
Report under 2,500 words.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

Your most valuable questions challenge design choices: 'Why did you choose weekly rather than daily sampling?' or 'How did you handle the fact that your monitoring period overlaps with a seasonal change that might confound your trend analysis?'
Provide a written review (minimum 150 words) confirming your qualifications, the specific questions you asked, and whether the submitter demonstrated genuine understanding of the methodology.

You'll sign in first, then come straight back here.