World map

type

block

files

2

registry deps

skeleton, @automindz/world-dots

npm deps

none

• ①One path for five thousand dots — a run per row, stamped by a zero-length dash pattern
• ②A marker is one of those dots, snapped onto the lattice; the land dot under it goes
• ③Two flat rings at 2.25 and 3.25 land-dot radii mark it, not its size
• ④Markers draw from --automindz-worldmap-marker, defaulting to your own --primary
• ⑤Labels are opt-in — the marker list underneath is the content either way

Edit lib/automindz/world-dots.ts, not the component, and pass it — config has no default here (<WorldMap config={WORLD_MARKERS} />). Markers are { lat, lng, label?, size?, id? }; arcs address a marker by its id, or by its index if it has none. The stylesheet is not optional: add import "@/styles/automindz-worldmap.css" to your root layout once, or nothing moves. Skipping it is safe, never blank — the dots are a stroke-dasharray presentation attribute on the component's own path, so the land, the markers with their rings and every route are still drawn end to end; that is also the prefers-reduced-motion path. **A marker is one of the map's own dots, lit — never a pin dropped on top of them.** Its latitude and longitude are snapped to the nearest lattice position by snapToLattice, preferring one that already has a land dot so a coastal city does not round into open water, and that dot is punched out of the land path — so the pitch of the field runs unbroken through the marker instead of an extra dot appearing in the gap between four others. The disc is 1.1 land-dot radii and what marks the place is its colour and two flat concentric rings at 2.25 and 3.25 radii, not its size. All grid units, so the ratios hold at every step instead of being fixed radii that only look right at one spacing. The snap never moves a marker more than one cell, so a point with no land dot near it — an island smaller than step, a marker in mid-ocean, one outside the drawn latitude band — lights its own containing cell rather than being dragged to a coast; and two markers that fall in the same cell take neighbouring dots, in declaration order. **The markers are the one thing here that takes your brand colour.** They draw from --automindz-worldmap-marker, which falls back to your own --primary and then to currentColor — so a client whose brand is orange gets orange markers with no code change, and one line moves them anywhere else: className="[--automindz-worldmap-marker:var(--color-emerald-500)]". The land and the routes stay currentColor, so text-primary retints the drawing. Nothing inside the component names a colour. **Labels are off by default** — pass labels to paint the pills. They are decorative: every marker's name is a real list item underneath either way, and that list plus the route list are the accessible content of the item, so pass label to name them (the drawing itself is aria-hidden). Turn labels on and both survival rules come with it: every pill drops to sr-only below 34rem of container width — a literal in the component, not a dial, because a container query condition cannot read a custom property — and two markers closer than a pill's width lose the second pill, in declaration order, so move a marker up the list to win its label. **The box is always a 2:1 equirectangular frame of the whole planet**, whatever south/north you draw dots between, so lat, lng → x, y is two divisions and the empty space above and below the dots is real latitude rather than padding — the default band drops Antarctica. **No route crosses the ±180 seam**: Tokyo to Los Angeles is drawn the long way, because a split arc is two subpaths and a dash pattern restarts at every subpath, so the beam would appear on both halves at once. Routes that cannot be drawn land in resolveWorldMap's skipped array with a reason (unknown-marker, self, duplicate). **The traffic cadence is capped, not documented**: worldCycle() stretches the cycle until every route is crossed at 1.5Hz or slower, so set it with the cycle prop and never by overriding --automindz-worldmap-cycle, which the component writes and the per-route phases are already measured against. Dials: --automindz-worldmap-marker, --automindz-worldmap-glow (the ink in a marker's inner ring; the outer one is a fraction of it), --automindz-worldmap-dot, --automindz-worldmap-land, --automindz-worldmap-rail, --automindz-worldmap-beam.