Map–List Choice¶
Method — instantiates Representation Fit Selection
Chooses between spatial representation and ordered enumeration depending on whether location, route, adjacency, sequence, or completeness matters more.
Map–List Choice decides between two fundamentally different modalities for the same set of things: lay them out in space (a map) or lay them out in order (a list). A map preserves location, adjacency, route, and terrain — you can see what is near what — but it hides ranking, exact quantities, and whether anything was left out. A list preserves sequence, completeness, and exact enumeration — you can check that every item is accounted for and in what order — but it flattens geography, so two entries that are neighbors on the ground can sit pages apart. The mechanism's defining question is not perception-versus-precision but does the task turn on where things are, or on having them all in order? That single axis decides the form.
Example¶
A county emergency-management team preparing for wildfire season has to build the artifact that field crews will use when an evacuation is ordered, and two instincts collide. One planner wants a printed checklist: every at-risk address, sorted by zone, with a tick-box so no household is missed — completeness is life-and-death. Another wants a map: burn perimeter, wind direction, road closures, and which neighborhoods are cut off from the one remaining highway. Map–List Choice resolves it by naming the task precisely, and finding there are two tasks. For the door-knock accountability task — confirm every household was contacted — the preserved feature is completeness and identity, and the list wins; a map cannot prove you didn't skip a house. For the routing task — which streets are still passable and which neighborhoods will be trapped if the fire jumps the ridge — the preserved feature is adjacency and route, and the map wins decisively; a list of road segments cannot show that closing one street islands three hundred people. The team ships both, each matched to its task, rather than forcing one modality to do a job it structurally cannot.
How it works¶
The method states the task, then identifies the single relation the representation must preserve and sorts it into the spatial family (location, adjacency, route, terrain, proximity) or the enumerative family (sequence, completeness, identity, exact count). The selection rule is a clean fork: spatial relation → map; enumerative relation → list. Crucially it detects when a task is really two tasks wearing one request, and splits rather than compromises — because the failure of a bad compromise here is total, not gradual (a "map with a list stapled on" often does neither job). Where a default is in play (the team always uses a spreadsheet), the rule requires the spatial candidate to be genuinely considered, not dismissed for being harder to produce.
Tuning parameters¶
- Spatial-relevance weight — how much the task actually depends on where things are; high weight forces the map even when a list is easier to maintain.
- Completeness demand — how catastrophic a missed item is; a high demand pulls hard toward the list's audit-ability.
- Split threshold — how readily a two-task request is broken into a map and a list rather than compromised into one; a low threshold protects fit at the cost of maintaining two artifacts.
- Spatial resolution — how fine the map's geography is rendered; finer shows more adjacency but adds clutter and production cost.
When it helps, and when it misleads¶
Map–List Choice helps whenever a set of located things is about to be jammed into whichever modality is habitual — it forces the where-versus-order question and prevents a spatial task from being answered with an enumeration or vice versa.
Its failure mode is the map's quiet aggregation lie: rendering data by area makes the reader believe the boundaries carry meaning they may not, and the same underlying facts can tell opposite spatial stories depending on how regions are drawn.[1] A list has the mirror failure — perfect completeness that conceals that half the entries are physically unreachable. The classic misuse is choosing a map because it looks compelling for a task (allocation, ranking) that turns on exact quantities the map cannot show. The guarding discipline is to name the preserved relation before choosing the modality, and to split a two-task request rather than force one form to carry both.
How it implements the components¶
task_requirement— it begins by stating what the artifact must let field users do (route, or account for every item), and treats that as the deciding input.preserved_feature— it names the single relation to preserve and classifies it as spatial (adjacency, route) or enumerative (completeness, sequence).representation_selection_rule— the explicit fork "spatial relation → map, enumerative relation → list; split when the request is two tasks."
It never runs a side-by-side rendering of two forms over the same values or audits their numeric distortion — comparison_view, distortion_check, and validation_case belong to Graph–Table Comparison, its nearest method twin, which turns on pattern-versus-precision within a single modality rather than choosing the modality itself.
Related¶
- Instantiates: Representation Fit Selection — a map-or-list pick instantiates the archetype only when the modality follows the task's preserved relation, not habit or ease of production.
- Sibling mechanisms: Dashboard View Design · Diagram Model Choice · Graph–Table Comparison · Mathematical Model Selection · Multi-View Model · Narrative Representation · Prototype Representation · Schema Selection
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Map–List Choice operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it chooses between spatial representation and ordered enumeration depending on whether location, route, adjacency, sequence, or completeness matters more.
Independent corroboration: The frozen evidence defines Map–List Choice as 'Chooses between spatial representation and ordered enumeration depending on whether location, route, adjacency, sequence, or completeness matters more', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Human-Computer Interaction
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Selecting a representation by the user's task and the relations it must preserve is primarily an HCI and information-design practice.
Related originating lineages:
- Data Science & Analytics — Data type and analytical question materially determine whether a spatial encoding is faithful.
- Earth Sciences — Cartography materially supplies the map-specific benefits and aggregation distortions.
- Library & Information Science — Information architecture materially shapes when ordered enumeration better serves completeness and retrieval.
Review resolution: Both independent reviews assign primary provenance to human_computer_interaction. The queued secondary differences (reported_ambiguity, alternate_origin_disagreement) are reconciled by retaining earth_sciences, library_information_science, data_science only as formative or independently established lineage(s), not merely as application domains. origin_mode=cross_disciplinary_synthesis records the provenance relationship, while domain_reach=multi_domain separately records applicability breadth. confidence=medium preserves the more cautious assessment, and encyclopedia_synthesis=true records whether either reviewer identified a corpus-specific synthesis.
Attribution caveat: No single historical discipline owns the map-versus-list fork; the named choice method is an encyclopedia synthesis. The explicit map-versus-list rule is a synthesized representation-fit heuristic.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
References¶
[1] Openshaw, S. The Modifiable Areal Unit Problem. Concepts and Techniques in Modern Geography 38, Geo Books / Geo Abstracts, University of East Anglia (1984). Shows that statistical results from the same spatial data can change materially when observations are aggregated into differently drawn areal units. registry ↩