Overview

This site should use static maps deliberately, not as a fallback after an interactive map fails. A static SVG map is often the clearest way to explain:

• the logic of a layer stack
• the geometry of a screening result
• what belongs in a report figure versus a review tool

Why it matters

Static figures have three advantages:

• they are stable and readable inside narrative pages
• they print cleanly
• they force the author to simplify the cartography to what matters

When to use

Use static SVG maps when:

• the page is teaching a method
• the map is a figure, not a workspace
• annotation and layout matter more than panning
• the data volume is modest

Inputs

Typical inputs:

• prepared GeoJSON layers
• a chosen projection
• a small number of symbology decisions
• optional derived counts or labels

Workflow and method

1. Load prepared GeoJSON with FileAttachment.
2. Decide which layers need polygon, line, or point treatment.
3. Render the figure as SVG with D3 or Plot.
4. Keep the legend and title close to the map.
5. Use a dynamic map elsewhere only if the reader truly needs inspection.

D3-rendered figure

Plot-rendered figure

Observable Plot is useful when the map needs to stay declarative and compact.

Outputs

Strong static-map outputs usually include:

• one stable figure per analytical point
• a concise legend
• explicit layer order
• enough contrast that the figure still reads outside a live demo environment

Limitations

Static figures do not support feature inspection, toggles, or free exploration. They are best when the author already knows what the reader should notice.

Related pages