Physical Geography Fieldwork and Skills
What this domain tests
This domain tests the full fieldwork cycle: planning, sampling, data collection, presentation, analysis and evaluation. It rewards precise method descriptions and honest limitations, not generic 'human error' statements.
Core rules and concepts
- A hypothesis is a testable statement, e.g. 'Velocity increases downstream.' An aim states what the study investigates.
- Sampling: random reduces bias; systematic (e.g. every 10 m) detects change along a transect; stratified represents subgroups. Record sample size and why it was chosen.
- Data can be quantitative (numbers) or qualitative (descriptions, photographs, field sketches).
- Controls keep conditions comparable: same float, same distance, same observer, same weather.
- Present data appropriately: bar charts for categories, scatter graphs for relationships, cross-sections for channel shape, located symbols on a map.
- Analysis should describe the pattern, quote data, explain it with process knowledge and identify anomalies.
- Evaluation distinguishes accuracy (closeness to true value), reliability (repeatability) and validity (whether the method measures what it claims).
Worked example
A float travels 10 m in 25 s. Reasoning: velocity = distance ÷ time = 10 ÷ 25 = 0.4 m/s. Repeat three times and average to improve reliability. If one reading is 0.9 m/s, note it as an anomaly and suggest causes: wind, an eddy, or an inconsistent release point. Do not delete it silently.
Traps that cost marks
- Writing 'human error' as a limitation without saying which step and how it affected results.
- Confusing reliability with accuracy.
- Drawing a line graph for categories such as rock type.
- Giving an unexplained anomaly or ignoring it.