Hatching Pattern Legend¶
Legend / codebook — instantiates Texture as Signal Encoding
Maps line angle, spacing, crosshatch, stipple, or fill texture to categories in charts, maps, or diagrams.
A Hatching Pattern Legend is the human-readable key that binds each texture to its meaning and teaches the reader the mapping. Its defining act is documentation, not rendering: it displays a swatch of the pattern beside a plain-language label, states what property each pattern stands for, and — where a domain standard exists — anchors those patterns to it. The legend never draws the map or chart itself; it is the codebook a reader consults so that the marks someone else drew become interpretable.
Example¶
A field geologist reads a published geologic quadrangle map. The map body is a patchwork of stipples, brick-like patterns, and dash fields — meaningless until the eye drops to the legend box in the margin. There, laid out in a learnable order, each swatch sits next to its meaning: a dotted stipple beside "sandstone," an interlocking brick pattern beside "limestone," short parallel dashes beside "shale," each drawn in the standardized lithologic pattern the survey uses. The geologist studies the legend once, forms the mapping, then reads the map fluently — and, because the patterns follow the shared standard, brings prior knowledge from every other map that used the same code. A reviewer can audit the map against the legend: is every pattern in the field actually accounted for in the key?
How it works¶
The legend is assembled by first enumerating the property states that must be told apart, then assigning each a pattern — reusing an established standard's symbol wherever one exists rather than inventing a private one. The swatch and its label are displayed side by side, and the entries are grouped and ordered to aid learning (related units near each other, a sensible sequence). The whole artifact is placed where it stays available while reading — a margin box, a facing page — because a legend the reader cannot see is no legend at all.
Tuning parameters¶
- Standard adherence — how strictly patterns follow an external convention versus custom design. Following the standard buys instant transfer from prior maps; deviating buys expressiveness at the cost of relearning.
- Legend placement / persistence — margin box, inset, or separate sheet, and whether it stays visible while scrolling or paging.
- Swatch size — large enough to show the pattern faithfully; too small and the key itself becomes unreadable.
- Grouping and order — alphabetical, by category family, or by a natural sequence (e.g., stratigraphic age), which shapes how quickly the mapping is learned.
When it helps, and when it misleads¶
Its strength is that it makes a conventional, otherwise-private code learnable and auditable — a reviewer can check the drawn marks against the key, and a newcomer can acquire the whole vocabulary in one glance rather than by osmosis. This is why high-stakes texture codes should never rely on designer intuition alone.
Its failure mode is a legend that looks complete but misleads. If the patterns in the key are not the ones the audience's standard actually prescribes — a home-brewed "limestone" pattern where the field expects the surveyed one[n1] — the legend teaches a mapping that collides with prior knowledge. It also fails when it grows too many entries to hold in mind. The guarding discipline is to follow the domain register wherever it exists and to bound the entry count, so the key stays both correct and learnable.
How it implements the components¶
encoded_property_definition— it states, entry by entry, exactly which property value (rock type, land use, category) each pattern stands for.legend_or_learning_path— the swatch-plus-label key is the learning artifact; it is the path by which a reader acquires the mapping.cultural_or_domain_convention_register— it anchors patterns to the established domain standard, so readers reuse conventions learned from other artifacts.
It does not run the rendering-side perceptual_discriminability_check that proves the drawn fills are actually tellable apart at print scale — that is Textured Chart Fill's job — nor the cross-product production_consistency_control of reusable tokens, which belongs to Semantic Texture Palette.
Related¶
- Instantiates: Texture as Signal Encoding — supplies the key that makes a texture code readable and auditable.
- Sibling mechanisms: Textured Chart Fill · Semantic Texture Palette · Texture Sample Card · Data-Quality Texture Overlay · Redundancy Style Guide · Material Finish Code · Haptic Feedback Pattern · Raised Ridge or Bump Marker · Tactile Paving Surface
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Hatching Pattern Legend operates as a non-executable information artifact that externalizes static or prospective structure because it maps line angle, spacing, crosshatch, stipple, or fill texture to categories in charts, maps, or diagrams.
Independent corroboration: The frozen evidence defines Hatching Pattern Legend as 'Maps line angle, spacing, crosshatch, stipple, or fill texture to categories in charts, maps, or diagrams', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Earth Sciences
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Graphic and cartographic design developed patterned fills and legends as noncolor categorical encoding.
Related originating lineages:
- Art & Aesthetics — Graphic and cartographic design independently developed hatching and texture as categorical visual encodings.
- Library & Information Science — Legend and code-key practice contributes the stable mapping between each pattern and its category.
Review resolution: USGS and FGDC standards provide explicit lithologic pattern charts and guidance for selecting stipple, hatch, and fill patterns in geologic maps. That canonical standard makes earth_sciences primary. Graphic design independently developed patterned noncolor encoding, while information organization contributes stable legend-to-category mappings. The mechanism is established and transfers beyond geology without becoming universal.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
- https://ngmdb.usgs.gov/fgdc_gds/geolsymstd/download.php — FGDC/USGS geologic symbols, colors, patterns, and pattern chart.
- https://pubs.usgs.gov/tm/2005/11B01/05tm11b01.html — USGS guidance for selecting colors and patterns on geologic maps.
- https://pubs.usgs.gov/tm/2006/11A02/FGDCgeostdTM11A2web_PatternChart.pdf — FGDC lithologic pattern chart and explanation.
Notes¶
The legend, the palette, and the style guide form a governance triangle worth keeping straight: the Hatching Pattern Legend is the reader-facing key for one artifact, the Semantic Texture Palette is the reusable token library behind many artifacts, and the Redundancy Style Guide is the rulebook for pairing texture with other channels. A legend teaches; a palette supplies; a style guide constrains.
[n1] In the United States the FGDC Digital Cartographic Standard for Geologic Map Symbolization prescribes the lithologic and structural patterns geologic maps use. A legend that follows it lets a reader transfer knowledge across maps; one that quietly departs from it forces relearning and invites error. ↩