# Route trace (Notchset): prompt.md (v2.0.0) - id: `route-trace` · version 2.0.0 · component · free - category: Charts - build: one set of files for every shadcn style - install: `npx shadcn@latest add https://notchset.dev/r/route-trace.json` - npm dependencies: none - registry dependencies: utils, https://notchset.dev/r/notchset-foundation.json - docs: https://notchset.dev/components/route-trace - The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand. GPS points projected flat and fitted to the box, drawn in the series hue over a soft halo with a hollow start, a filled finish and a small mark at each whole kilometre. No tiles and no provider key; a buyer adds streets behind the same drawing.. ## Build it - Stack: React 18.3 or 19, TypeScript, Tailwind CSS v4 utility classes on the foundation's roles, a components.json (imports use its aliases). - Packages: none beyond React. - Files: `components/ui/notchset/route-trace.tsx`. - Registry dependencies, installed with it automatically: shadcn `utils` (cn), `notchset-foundation`. - Builds: one set of files, the same for every shadcn style. - Exports to keep: `RouteTrace`, and every exported type. - CSS: the install adds the notchset foundation (its roles, keyframes and motion switch, reading your shadcn tokens for colour) to your global stylesheet once. Nothing to import by hand. - Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules. - Colours: every part reads the foundation's roles (`--ns-canvas`, `--ns-ink`, `--ns-line`, `--ns-signal` …), which read your shadcn tokens (`--background`, `--foreground`, `--border`, `--destructive` …), plus the optional `--success` and `--warning`. Retheme on `:root` or any container; never add Tailwind colour classes inside the component. - This item reads `--ns-canvas`, `--ns-font-mono`, `--ns-ink`, `--ns-ink-2`, `--ns-series`. - Retune it (on any ancestor) with the foundation's roles and hooks: `--ns-bad`, `--ns-bad-ink`, `--ns-band`, `--ns-band-edge`, `--ns-band-grade`, `--ns-band-optimal`, `--ns-beat`, `--ns-bezel`, `--ns-canvas`, `--ns-cat-1`, `--ns-cat-2`, `--ns-cat-3`, `--ns-cat-4`, `--ns-cat-5`, `--ns-cat-6`, `--ns-check`, `--ns-chip`, `--ns-control`, `--ns-control-pad`, `--ns-control-sm`, `--ns-deep`, `--ns-deep-ink`, `--ns-deep-ink-2`, `--ns-deep-line`, `--ns-dialog`, `--ns-dialog-lg`, `--ns-dialog-sm`, `--ns-ease`, `--ns-ease-in`, `--ns-ease-panel`, `--ns-ease-pop`, `--ns-field`, `--ns-flood-arc`, `--ns-flood-aurora`, `--ns-flood-behind-1`, `--ns-flood-behind-2`, `--ns-flood-bloom`, `--ns-flood-deep`, `--ns-flood-dial-bloom`, `--ns-flood-glass`, `--ns-flood-grain`, `--ns-flood-image`, `--ns-flood-ink`, `--ns-flood-ink-low`, `--ns-flood-light`, `--ns-flood-mid`, `--ns-flood-pale`, `--ns-flood-pane`, `--ns-flood-pane-edge`, `--ns-flood-pill-ink`, `--ns-flood-ribbon`, `--ns-flood-ribbon-core`, `--ns-flood-shadow`, `--ns-flood-sheen`, `--ns-flood-wash`, `--ns-font-body`, `--ns-font-display`, `--ns-font-mono`, `--ns-font-script`, `--ns-glass`, `--ns-glass-blur`, `--ns-glass-shadow`, `--ns-glow`, `--ns-grain`, `--ns-gutter`, `--ns-header`, `--ns-heat`, `--ns-hover`, `--ns-ink`, `--ns-ink-2`, `--ns-ink-3`, `--ns-ink-4`, `--ns-leading`, `--ns-lift`, `--ns-light-1`, `--ns-light-2`, `--ns-light-3`, `--ns-light-spread`, `--ns-light-strength`, `--ns-line`, `--ns-line-soft`, `--ns-lit-edge`, `--ns-menu-dy`, `--ns-menu-row`, `--ns-mesh`, `--ns-mesh-frost`, `--ns-ok`, `--ns-ok-ink`, `--ns-orb-body`, `--ns-orb-cool`, `--ns-orb-core`, `--ns-orb-dawn`, `--ns-orb-deep`, `--ns-orb-edge`, `--ns-orb-grain`, `--ns-orb-ground`, `--ns-orb-halo`, `--ns-orb-inner`, `--ns-orb-key`, `--ns-orb-lift`, `--ns-orb-limb`, `--ns-orb-limb-from`, `--ns-orb-rim`, `--ns-orb-skin-hi`, `--ns-orb-skin-lo`, `--ns-orb-skin-mid`, `--ns-orb-warm`, `--ns-panel`, `--ns-panel-w`, `--ns-prism-edge`, `--ns-prism-glint`, `--ns-prism-sheen`, `--ns-prism-tint`, `--ns-pulse`, `--ns-radius`, `--ns-radius-card`, `--ns-radius-full`, `--ns-radius-lg`, `--ns-radius-sm`, `--ns-radius-xl`, `--ns-raised`, `--ns-range`, `--ns-row`, `--ns-row-compact`, `--ns-segment`, `--ns-selected`, `--ns-series`, `--ns-series-core`, `--ns-series-lilac`, `--ns-series-tint`, `--ns-shadow-dialog`, `--ns-shadow-float`, `--ns-shadow-panel`, `--ns-sheet`, `--ns-sheet-bottom`, `--ns-side`, `--ns-signal`, `--ns-sleep-awake`, `--ns-sleep-deep`, `--ns-sleep-light`, `--ns-sleep-rem`, `--ns-space-1`, `--ns-space-2`, `--ns-space-3`, `--ns-space-4`, `--ns-space-5`, `--ns-space-6`, `--ns-space-8`, `--ns-space-section`, `--ns-stack-on`, `--ns-standing-critical`, `--ns-standing-in`, `--ns-standing-out`, `--ns-state-doing`, `--ns-state-done`, `--ns-state-review`, `--ns-state-todo`, `--ns-switch-h`, `--ns-switch-w`, `--ns-text-body`, `--ns-text-control`, `--ns-text-display`, `--ns-text-figure`, `--ns-text-headline`, `--ns-text-hero`, `--ns-text-lede`, `--ns-text-meta`, `--ns-text-page`, `--ns-text-record`, `--ns-text-small`, `--ns-text-strong`, `--ns-text-sub`, `--ns-text-title`, `--ns-tile-shadow`, `--ns-time-born`, `--ns-time-color`, `--ns-time-dialog`, `--ns-time-menu`, `--ns-time-page`, `--ns-time-panel`, `--ns-time-toast`, `--ns-tint`, `--ns-tint-ink`, `--ns-toast-bottom`, `--ns-toast-left`, `--ns-touch`, `--ns-tracking-display`, `--ns-tracking-headline`, `--ns-warn`, `--ns-warn-ink`, `--ns-wash-clay`, `--ns-wash-dusk`, `--ns-wash-graphite`, `--ns-wash-ink`, `--ns-wash-sage`, `--ns-wash-sand`, `--ns-weight-light`, `--ns-weight-medium`, `--ns-weight-regular`, `--ns-weight-strong`, `--ns-well`. - Never add Tailwind colour classes inside the component. ```tsx import { RouteTrace } from "@/components/ui/notchset/route-trace"; ``` ## Parts - A single export that takes props. ## Match the original - Read `components/ui/notchset/route-trace.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour. - If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part. - Keep the accessibility contract, the keyboard map and the motion levels listed below. ## Use it when ### Not when ## Mistakes - Recreating the component instead of installing it ## Usage ```tsx "use client"; import { RouteTrace } from "@/components/ui/notchset/route-trace"; /* a 3 km loop through a park, as a phone's GPS records it */ const loop: [number, number][] = Array.from({ length: 81 }, (_, i) => { const t = (i / 80) * 2 * Math.PI; const r = 1 + 0.2 * Math.sin(2 * t + 1) + 0.09 * Math.sin(3 * t + 2); return [51.5262 + (Math.sin(t) * r * 0.65 * 650) / 111320, -0.1527 + (Math.cos(t) * r * 1.25 * 650) / 69300]; }); export default function RouteTraceDemo() { return (
); } ``` ## Props | Prop | Type | Default | What it does | |---|---|---|---| | `points` | `readonly (readonly [number, number])[]` | | [lat, lng] in the order recorded | | `label` | `string` | | Required. | | `kmMarks` | `boolean` | `true` | mark each whole kilometre | | `height` | `number` | `320` | | Full docs: https://notchset.dev/components/route-trace ## Customising - Colours: every part reads the foundation's roles (`--ns-canvas`, `--ns-ink`, `--ns-line`, `--ns-signal` …), which read your shadcn tokens (`--background`, `--foreground`, `--border`, `--destructive` …), plus the optional `--success` and `--warning`. Retheme on `:root` or any container; never add Tailwind colour classes inside the component. - Dark mode follows the `.dark` class or `data-theme="dark"` on an ancestor (the shadcn and next-themes conventions). - Update later: Commit or stash local changes first (or copy the files), so the update can be undone. Read https://notchset.dev/r/changelog.json for the new versions: a major version, an entry marked breaking or a merge says what to change. Then re-run the install with `--overwrite`, on a branch. It replaces the component's files, the shared helper files they import, and the item's CSS rules in the global stylesheet, so review the whole diff (components, shared files, CSS), re-apply your own edits, and run the app's typecheck, tests and build. ## Accessibility contract (preserve when editing) ## Install ```bash npx shadcn@latest add https://notchset.dev/r/route-trace.json ``` Or add the `@notchset` registry to components.json and run `npx shadcn@latest add @notchset/route-trace`. Every components.json style gets the same files. ## Continue the workflow - [Day timeline](https://notchset.dev/components/day-timeline) - [Ghost trend](https://notchset.dev/components/ghost-trend) - [Glucose day](https://notchset.dev/components/glucose-day) ## Source ### components/ui/notchset/route-trace.tsx ```tsx // Notchset route-trace 2.0.0 · https://notchset.dev/changelog "use client"; import { cn } from "@/lib/utils"; /* * Route trace: a walk or run drawn as a quiet line on the page's own paper, from the GPS points a wearable or phone * supplied. No map tiles and no provider key: the points are projected flat (fine at a park's scale), fitted to the * box and drawn in the series hue over a soft halo, with a hollow dot at the start, a filled one at the finish and a * small mark at each whole kilometre. A buyer who wants streets under it adds tiles behind this same drawing. * * */ type RouteTraceProps = { /** [lat, lng] in the order recorded */ points: readonly (readonly [number, number])[]; label: string; /** mark each whole kilometre */ kmMarks?: boolean | undefined; height?: number | undefined; className?: string | undefined; }; const R = 6371000; const rad = Math.PI / 180; const metres = (a: readonly [number, number], b: readonly [number, number]) => { const x = Math.sin(((b[0] - a[0]) * rad) / 2) ** 2 + Math.cos(a[0] * rad) * Math.cos(b[0] * rad) * Math.sin(((b[1] - a[1]) * rad) / 2) ** 2; return 2 * R * Math.asin(Math.sqrt(x)); }; function RouteTrace({ points, label, kmMarks = true, height = 320, className }: RouteTraceProps) { if (points.length < 2) return null; const lat0 = points.reduce((a, p) => a + p[0], 0) / points.length; const k = Math.cos(lat0 * rad); /* flat metres east (x) and north (y), y flipped for the screen */ const xy = points.map((p) => [p[1] * k * 111320, -p[0] * 111320] as const); const xs = xy.map((p) => p[0]); const ys = xy.map((p) => p[1]); const [x0, x1, y0, y1] = [Math.min(...xs), Math.max(...xs), Math.min(...ys), Math.max(...ys)]; const span = Math.max(x1 - x0, y1 - y0, 1); const pad = span * 0.08; const vb = `${x0 - pad} ${y0 - pad} ${x1 - x0 + 2 * pad} ${y1 - y0 + 2 * pad}`; const d = xy.map((p, i) => `${i ? "L" : "M"}${p[0].toFixed(1)} ${p[1].toFixed(1)}`).join(""); const marks: { at: readonly [number, number]; km: number }[] = []; if (kmMarks) { let run = 0; for (let i = 1; i < points.length; i++) { const before = run; run += metres(points[i - 1]!, points[i]!); const whole = Math.floor(run / 1000); if (whole > Math.floor(before / 1000)) marks.push({ at: xy[i]!, km: whole }); } } const dot = span / 90; return (
{marks.map((m) => ( {`${m.km} km`} ))}
); } export { RouteTrace, type RouteTraceProps }; ``` The foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://notchset.dev/r/notchset-foundation.json.