Settlements need map readability
Local labels have to survive pins, dialogue, travel notes, and district naming.
Guide
Settlement Label vs Crown-Scale Label
How to tell whether you are naming the settlement itself or the political layer above it.
Definition
The two labels solve different map layers
A settlement label marks the place people travel to, fight over, or mark on a route. A crown-scale label marks the political or territorial unit above it. The two should relate, but they should not sound like the same object at the same scale.
States carry sovereignty
Crown-scale labels need room for dynastic, territorial, or political weight.
Hierarchy should be audible
Readers should feel the difference between a port city and the crown that rules the region.
Patterns
How to choose the right layer
Use local labels for capitals, ports, and frontier nodes
This is the right branch when the settlement itself is the useful unit on the map.
Use state labels for crowns, realms, and borders
Switch here when the story cares more about sovereignty, dynastic identity, and regional power.
Name the smaller layer with room for the bigger one
A local label should not consume all the ceremony if a state label still needs to exist above it.
Common mistakes
Map-layer mistakes
Making every settlement sound imperial
Ports and checkpoint towns lose believability if they all read like jeweled realms.
Using the realm label for the local stop
That flattens geography and makes local travel language less credible.
Ignoring district follow-through
A city should leave room for gates, markets, and quarters to inherit the same naming root.
Worked example
Seven labels from one river valley hierarchy
Begin with a river root, Caldrin, then assign different forms to settlement, district, state, and people. The derivation keeps hierarchy audible without making every label identical.
Caldrin Ford
Use the root plus a practical crossing noun for the local stop. It reads like a destination characters can enter, trade in, or defend.
The Caldrin Crown
For the state layer, keep the root but add a sovereignty noun. Crown signals rule instead of street-level geography.
East Caldrin
A district can keep the city root and add direction. This feels local and navigable rather than dynastic.
Caldrish
The people-label trims the root and adds a compact ending. It can describe dialect, cloth, or food without repeating Ford.
Crownroad
A road can borrow the political cue while dropping the root. This shows state influence on infrastructure.
Old Fordmarket
A market quarter keeps the settlement function visible. It should sound smaller than the kingdom label.
The Lower Caldrin March
For a border province, add March and a position marker. The label now sits between local and state scale.
Application note
Test the label on a map and in a treaty
A local label should work on a road sign, a market rumor, and a player map. A state label should work in a treaty, a banner, and a border dispute. Put the candidate in those documents before deciding whether the scale is correct.
When a single label seems to work everywhere, it is often too vague. Add a local function for the settlement or a sovereignty signal for the state. The goal is not more grandeur; the goal is language that tells the reader which layer of the world is being discussed.
Workflow checklist
Map hierarchy review
- Ask whether the label is a destination, a state, a district, or a people.
- Reserve the most ceremonial words for political layers.
- Keep local city names short enough for dialogue and travel notes.
- Leave room for demonyms and districts to inherit the root later.
Next step
Pick the map layer before opening a tool
After this guide, the next click should match the object that appears in your scene, map, or political note.
Settlement page, Realm page and Place hub cover settlement labels, crown-scale labels, and the wider place hub when the layer is still unclear.