Site vs situation; threshold, range, sphere
Site is the land built ON -- flat, dry, defensible or a bridging point. Situation is the position RELATIVE to surroundings -- other settlements, routes, resources. A service has three ideas: threshold population (minimum customers to be profitable), range (furthest a customer travels) and sphere of influence (area served). Low-order services sit in nearly every settlement; high-order ones (a hospital) need a large threshold and long range, found only in big settlements.
Up the hierarchy: fewer but bigger
A settlement hierarchy arranges settlements -- hamlet, village, town, city -- by size and importance. Moving UP, four things change together: the NUMBER of settlements falls (many hamlets, few cities); the SIZE rises; the RANGE of services rises (a shop and primary school up to shopping centres and hospitals); and the SPHERE OF INFLUENCE grows. Low settlements offer only low-order everyday goods; high ones support high-order specialist services, drawing customers widely.
Cambridge, UK: site and situation to city
Cambridge, England is a transferable case study. Its site was a fording point on the River Cam, on raised, drier ground above the fenland -- defensible, flood-free, with water. Its situation -- midway between London and regional centres, on converging routes -- brought trade through, growing it into a market town then a city. Today it sits near the top of its local hierarchy, with high-order services (shopping centre, hospital, university) that surrounding villages lack.
Drawn from real examiner reports.
Listing services, not explaining WHY
Asked to explain rural service provision, weaker candidates name what exists ("a shop and a church") instead of the LOCATION logic wanted: the threshold population a service needs, the accessibility of the site to customers, and its profitability given the sphere of influence. Listing services is description, not explanation.
Digest (## 1.5): explaining rural service provision, weaker candidates list the services present rather than explaining WHY they locate there -- threshold population, accessibility, profitability need explicit statement (s23 P11 Q2c).
Threshold population is not shop size
The key definition trap. Threshold population is the MINIMUM NUMBER OF CUSTOMERS needed to make a service viable enough to open. It is not the size of the building, and not simply "fewer people nearby" -- that confuses the cause (a small local population) with the term. State it as customers: a corner shop needs a few hundred, a department store many thousands.
Digest (## 1.5): "threshold population" is often confused with shop size or a vague "fewer people nearby" instead of the minimum customer base needed (w23 P22 Q3a(ii)).
Hierarchy: number changes, and the name
Two linked errors on hierarchy. First, candidates rank settlements small-to-large but forget the NUMBER at each level changes too -- many hamlets, few cities; the pyramid needs size rising AND number falling. Second, "service hierarchy" is written for "settlement hierarchy": one ranks the settlements, the other the services. Use the exact term asked.
Digest (## 1.5): candidates rank settlements by size but rarely reference the relative NUMBER at each level, and some substitute "service hierarchy" for the term (w22 P13 Q2a(iv)).
Site vs situation confused
Site and situation are different scales. Site is the ground a settlement stands ON -- flat, dry, defensible, near water. Situation is its position RELATIVE to everything else -- trade routes, midway between regions. Candidates give a situation point ("near London") when asked for site, or a site point ("flat land") when asked for situation.
Threshold population vs range
These two service terms are easily swapped. Threshold population is the minimum number of CUSTOMERS a service needs to open. Range is the maximum DISTANCE a customer will travel to reach it -- one is about people, the other about distance. A high-order service has BOTH, but they are separate ideas: giving a distance when asked for threshold population loses the mark.
Cities are rarer than villages, not commoner
The hierarchy pyramid has a WIDE BASE and NARROW TOP: hamlets and villages are most numerous, towns fewer, cities fewest. What rises upward is not the number of settlements but their SIZE, RANGE of services and SPHERE OF INFLUENCE. Assuming cities are commoner "because they offer more" is backwards: few places reach the threshold a city's services need.
Digest (## 1.5): candidates rank settlements by size but rarely reference the relative NUMBER at each level (w22 P13 Q2a(iv)) -- the same gap underlies the reversed-pyramid misconception.
Describing a settlement pattern
Name the settlement-pattern type precisely -- dispersed (scattered, no focal point), nucleated (clustered around a point) or linear (along a road or valley) -- with located detail (distances apart, dwelling count, direction). If it changes across the map, describe BOTH parts.
7-marker: site AND situation, then hierarchy
The 7-mark site/situation/hierarchy question rewards located detail and linked reasoning. Name a real settlement (Cambridge: the River Cam crossing, dry ground above the fens), cover BOTH site and situation, LINK each to growth, and place it in the hierarchy.
Comparing settlements: link, do not list
A "compare" question links both settlements with comparative words -- whereas, larger/smaller -- not described in turn. Compare like with like (sphere of influence with sphere, services with services), with figures. Two descriptions in turn is not comparing.
Full notes, flashcards, Q&A and the topic quiz for every premium subject.
Premium plans are US$8.99/month or US$49.99/year — first month free.
Studying with a parent's blessing? Show them this.
