Goad map¶
Encode property-scale building construction, occupancy, hazards, water supply, and fire protection in a standardized cartographic record designed for fire-insurance risk comparison.
Core Idea¶
A Goad map is a fire-insurance plan produced within the mapping system developed by Charles E. Goad and his firms, representing urban properties at a scale and with a symbol vocabulary suited to underwriting and conflagration risk. Sheets identify building footprints, construction materials, height or storeys, occupancy, openings, party walls, hazards, waterworks, and firefighting resources as available. The identity joins publisher lineage, standardized encoding, property detail, and insurance-risk purpose; it is not merely a map once owned by an insurer.
Scope of Application¶
The abstraction is literal wherever practitioners can identify the same constitutive roles, apply the same boundary tests, and obtain the same kind of output. The following habitats are uses of Goad map itself, not metaphors based only on resemblance.
- Historical underwriting. Comparing construction, adjacency, occupancy, and fire protection across properties.
- Urban morphology. Reconstructing building footprints and land uses at mapped dates.
- Industrial history. Locating works, storage, hazardous uses, and infrastructural relations.
- Heritage research. Tracing demolished buildings and changes in block fabric.
- History of risk. Studying how insurers standardized and visualized fire exposure.
- Cartographic criticism. Reading legend, selection, authority, and revision as part of the represented claim.
Clarity¶
A clear account of Goad map must preserve the recognition invariant stated in the Core Idea rather than rely on the title alone. Identify publisher, city, sheet, survey or revision date, scale, and legend edition. Interpret color and abbreviations from the applicable key rather than a different company's convention. Separate survey-date evidence from later annotations and present-day conditions. Treat absence as ambiguous unless coverage, survey purpose, and revision practice make it informative.
Manages Complexity¶
Goad map manages complexity by replacing a diffuse field of observations or possible operations with a bounded role structure: surveyed urban area supplies a block, property, or industrial district supplies the spatial frame.; building footprint supplies mapped outlines expose adjacency, separation, and internal divisions.; construction code supplies color and symbols distinguish brick, wood, concrete, glass, and related materials.; use and occupancy supplies labels identify residential, commercial, industrial, educational, and other functions.; vertical and opening detail supplies storeys, doors, windows, and party-wall information affect spread models..
Abstract Reasoning¶
- Locate the sheet within its key plan and confirm the relevant edition. 2. Decode construction, occupancy, height, openings, and protection symbols with the matching legend. 3. Reconstruct adjacency and potential fire-spread relations at the represented date. 4. Distinguish original survey marks from revision patches or later annotation. 5. Compare other editions or sources before inferring change or absence. 6. Account for insurer-driven selection and uneven geographic coverage.
Knowledge Transfer¶
The strict upward abstraction is Representation. Goad map instantiates Representation because it selectively encodes complex urban properties and risk relations in a standardized visual model for comparison and decision. Within fire insurance mapping, the full mechanism transfers literally when the same roles and boundary tests recur. Beyond that domain, only the parent-level skeleton should travel. Reusing the label Goad map after removing its constitutive vocabulary would hide a change of mechanism behind an analogy. The honest transfer rule is therefore two-stage: recognize the domain-specific pattern first, then lift only the parent relation that remains invariant under a substrate change.
Relationships to Other Abstractions¶
Current abstraction Goad map Domain-specific
Parents (1) — more general patterns this builds on
-
Goad map is a kind of Representation Prime
Goad map instantiates Representation because it selectively encodes complex urban properties and risk relations in a standardized visual model for comparison and decision.
Hierarchy path (1) — routes to 1 parentless root
- Goad map → Representation → Abstraction
Neighborhood in Abstraction Space¶
Goad map sits in a sparse region of the domain-specific corpus (92nd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (1565 abstractions)
Nearest neighbors
- Architectural ensemble — 0.80
- Space syntax — 0.79
- Form-Based Code — 0.79
- Critical Reconstruction — 0.78
- Suburb — 0.78
Computed from structural-signature embeddings · 2026-09-08