Functional Weave
Code in TypeScript

charts.scale

Map data values onto screen positions and back: linear, log, time, band and point scales, and nice domains.

1.1.0 · published 2026-10-03 by charlie · Anterra

Pinned by 93 tests, run in TypeScript, Python and Rust.linearScale 14 · invertLinear 8 · niceDomain 12 · logScale 17 · timeScale 15 · bandScale 16 · pointScale 11

What it does

A linear scale maps a data value onto a position: `linearScale([0, 100], [0, 500], 25, false)` is `125`, a quarter of the way along a 500 pixel axis. `invertLinear` goes the other way, from a pointer position back to the value under it, and `niceDomain` widens a data extent such as `[0.13, 9.7]` to `[0, 10]` so the axis starts and ends on a tick.

This is a group: three functions that only make sense together, in one package, each in its own file. Install only what you call with `require charts.scale ^1.0.0 only=linearScale`; `invertLinear` brings `linearScale` with it, because it reuses its arithmetic.

The functions

A group: 7 functions that work together, each in its own file, each pinned by its own tests in TypeScript, Python and Rust. A project can install only the ones it calls.

  1. linearScale (domain: float[], range: float[], value: float, clamp: bool) -> float
  2. invertLinear (domain: float[], range: float[], value: float) -> float
  3. niceDomain (domain: float[], count: int) -> NiceDomain
  4. logScale (domain: float[], range: float[], value: float, clamp: bool) -> float
  5. timeScale (domain: date[], range: float[], value: date, clamp: bool) -> float
  6. bandScale (domain: string[], range: float[], value: string, paddingInner: float, paddingOuter: float, align: float) -> Band
  7. pointScale (domain: string[], range: float[], value: string, padding: float, align: float) -> float

The types it declares, generated into your project

/** A domain widened to round numbers, and the tick step that made them round. */
export interface NiceDomain {
  /** [from, to], in the order given */
  readonly domain: readonly number[];
  /** 1, 2 or 5 times a power of ten */
  readonly step: number;
}

/** Where one category's band sits along the range. */
export interface Band {
  /** the band's lower coordinate */
  readonly start: number;
  /** start + width / 2, where a label or tick goes */
  readonly center: number;
  /** the band's width, the same for every category */
  readonly width: number;
}

Once installed, your code imports each one from the group's module.

linearScale throws on bad input 14 tests

export function linearScale(domain: readonly number[], range: readonly number[], value: number, clamp: boolean): number
domainfloat[]the data extent [from, to]; from and to may be in either order but not equal
rangefloat[]the output extent [from, to], usually pixels; may be reversed for a y axis
valuefloat
clampboolkeep the result inside the range when value is outside the domain
returnsfloatrounded to 6 decimal places

For example

  • linearScale(0, 100, 0, 500, 25, false) → 125 a quarter of the way along a 500 pixel axis
  • linearScale(0, 100, 0, 500, 0, false) → 0 the start of the domain is the start of the range
  • linearScale(0, 100, 0, 500, 100, false) → 500 the end of the domain is the end of the range
import { linearScale } from "#fune/charts.scale@^1";
impl/typescript/linear_scale.ts · 38 lines · open · raw
/**
 * Where `value` lands on the range, as a straight-line map from the domain.
 * Outside the domain the line carries on, unless `clamp` stops it at the
 * range's ends.
 */
export function linearScale(domain: readonly number[], range: readonly number[], value: number, clamp: boolean): number {
  const [d0, d1] = pair(domain, "domain");
  const [r0, r1] = pair(range, "range");
  let t = normalise(d0, d1, value, "domain");
  if (clamp) t = Math.max(0, Math.min(1, t));
  return round6(interpolate(r0, r1, t));
}

// The helpers below are exported for invertLinear, which is the same line
// read the other way; they are not part of the group's contract.

/** The two ends of a domain or range, or an error naming which one is wrong. */
export function pair(values: readonly number[], what: string): [number, number] {
  if (values.length !== 2) throw new Error(`${what} must have exactly 2 values, [from, to]; got ${values.length}`);
  return [values[0], values[1]];
}

/** How far along [from, to] the value is: 0 at from, 1 at to. */
export function normalise(from: number, to: number, value: number, what: string): number {
  // Equal ends would divide by zero and answer NaN or Infinity, which then
  // draws nothing without saying why.
  if (from === to) throw new Error(`${what} has no width: both ends are ${from}`);
  return (value - from) / (to - from);
}

export function interpolate(from: number, to: number, t: number): number {
  return from + t * (to - from);
}

/** Half up to 6 decimal places, the same way in every language. */
export function round6(x: number): number {
  return Math.floor(x * 1e6 + 0.5) / 1e6;
}

invertLinear throws on bad input 8 tests

export function invertLinear(domain: readonly number[], range: readonly number[], value: number): number
domainfloat[]
rangefloat[]
valuefloata position in the range, such as a mouse coordinate
returnsfloatthe data value at that position, rounded to 6 decimal places

For example

  • invertLinear(0, 100, 0, 500, 125) → 25 a pixel back to its value
  • invertLinear(0, 100, 0, 500, 0) → 0 the start of the range is the start of the domain
  • invertLinear(0, 50, 300, 0, 240) → 10 a reversed range
import { invertLinear } from "#fune/charts.scale@^1";
impl/typescript/invert_linear.ts · 12 lines · open · raw

Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.

import { interpolate, normalise, pair, round6 } from "./charts_scale_linear_scale.ts";  ← linearScale, another function of this group · built into the same file, even by a slim install

/**
 * The domain value at a position in the range: linearScale read backwards,
 * for turning a pointer coordinate into the value under it. Never clamped; a
 * position past the end of the axis is a value past the end of the data.
 */
export function invertLinear(domain: readonly number[], range: readonly number[], value: number): number {
  const [d0, d1] = pair(domain, "domain");
  const [r0, r1] = pair(range, "range");
  return round6(interpolate(d0, d1, normalise(r0, r1, value, "range")));
}

niceDomain throws on bad input 12 tests

export function niceDomain(domain: readonly number[], count: number): NiceDomain
domainfloat[]
countintroughly how many ticks the axis will have, at least 1
returnsNiceDomain

For example

  • niceDomain(3, 97, 10) → domain 0, 100, step 10 widens to whole tens
  • niceDomain(0.13, 0.87, 10) → domain 0.1, 0.9, step 0.1 small numbers widen to tenths
  • niceDomain(0.13, 9.7, 5) → domain 0, 10, step 2 a messy extent becomes 0 to 10
import { niceDomain } from "#fune/charts.scale@^1";
impl/typescript/nice_domain.ts · 50 lines · open · raw
import type { NiceDomain } from "./charts_scale_types.ts";

/**
 * Widen a domain to multiples of a round tick step (1, 2 or 5 times a power
 * of ten) chosen for about `count` ticks. Widening can change the best step,
 * so it repeats until the step settles, as d3's nice() does.
 */
export function niceDomain(domain: readonly number[], count: number): NiceDomain {
  if (domain.length !== 2) throw new Error(`domain must have exactly 2 values, [from, to]; got ${domain.length}`);
  if (!Number.isInteger(count) || count < 1) throw new Error(`count must be a whole number of at least 1, got ${count}`);
  const reversed = domain[1] < domain[0];
  let lo = reversed ? domain[1] : domain[0];
  let hi = reversed ? domain[0] : domain[1];
  if (lo === hi) return { domain: [domain[0], domain[1]], step: 0 };

  let step = 0;
  for (let i = 0; i < 10; i++) {
    const next = tickStep(lo, hi, count);
    if (next === step) break;
    step = next;
    if (step >= 1) {
      lo = Math.floor(lo / step) * step;
      hi = Math.ceil(hi / step) * step;
    } else {
      // A fractional step divides badly (0.3 / 0.1 is 2.9999999999999996), so
      // multiply by its whole-number inverse instead.
      const inverse = Math.floor(1 / step + 0.5);
      lo = Math.floor(lo * inverse) / inverse;
      hi = Math.ceil(hi * inverse) / inverse;
    }
  }
  const ends = reversed ? [round6(hi), round6(lo)] : [round6(lo), round6(hi)];
  return { domain: ends, step: round6(step) };
}

function tickStep(lo: number, hi: number, count: number): number {
  const raw = (hi - lo) / count;
  // Powers of ten by repeated multiplication rather than log10, whose last
  // digit is not guaranteed to agree between languages.
  let power = 1;
  while (power * 10 <= raw) power *= 10;
  while (power > raw) power /= 10;
  const error = raw / power;
  const factor = error >= Math.sqrt(50) ? 10 : error >= Math.sqrt(10) ? 5 : error >= Math.sqrt(2) ? 2 : 1;
  return factor * power;
}

function round6(x: number): number {
  return Math.floor(x * 1e6 + 0.5) / 1e6;
}

logScale throws on bad input 17 tests

export function logScale(domain: readonly number[], range: readonly number[], value: number, clamp: boolean): number
domainfloat[][from, to], both greater than zero and not equal
rangefloat[]
valuefloatgreater than zero
clampbool
returnsfloatrounded to 6 decimal places, half away from zero

For example

  • logScale(1, 1,000, 0, 300, 10, false) → 100 a decade is a third of three decades
  • logScale(1, 1,000, 0, 300, 100, false) → 200 two decades
  • logScale(1, 100, 0, 1, 1, false) → 0 the start of the domain
import { logScale } from "#fune/charts.scale@^1";
impl/typescript/log_scale.ts · 23 lines · open · raw

Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.

import { roundFloat } from "./math_round_float.ts";  ← from math.round-float ^1.0.0 · built alongside by fune
import { ln } from "./math_ln.ts";  ← from math.ln ^1.0.0 · built alongside by fune
import { interpolate, pair } from "./charts_scale_linear_scale.ts";  ← linearScale, another function of this group · built into the same file, even by a slim install

/**
 * Where `value` lands on the range when the axis is logarithmic: equal ratios
 * (1 to 10, 10 to 100) take equal lengths. The base of the logarithm cancels
 * out, so there is no base argument; it only matters for ticks.
 *
 * ln comes from math.ln rather than Math.log, whose last bit may differ
 * between platforms, so every language lands on the same double.
 */
export function logScale(domain: readonly number[], range: readonly number[], value: number, clamp: boolean): number {
  const [d0, d1] = pair(domain, "domain");
  const [r0, r1] = pair(range, "range");
  if (!(d0 > 0) || !(d1 > 0)) throw new Error(`log scale domain must be positive; got [${d0}, ${d1}]`);
  if (d0 === d1) throw new Error(`domain has no width: both ends are ${d0}`);
  if (!(value > 0)) throw new Error(`value must be positive for a log scale; got ${value}`);
  const l0 = ln(d0);
  let t = (ln(value) - l0) / (ln(d1) - l0);
  if (clamp) t = Math.max(0, Math.min(1, t));
  return roundFloat(interpolate(r0, r1, t), 6);
}

timeScale throws on bad input 15 tests

export function timeScale(domain: readonly string[], range: readonly number[], value: string, clamp: boolean): number
domaindate[][from, to] ISO dates, not equal; may run backwards
rangefloat[]
valuedatean ISO date; days before or after the domain map outside the range unless clamped
clampbool
returnsfloatrounded to 6 decimal places, half away from zero

For example

  • timeScale(2026-01-01, 2026-01-31, 0, 300, 2026-01-16, false) → 150 the middle of January
  • timeScale(2026-01-01, 2026-01-31, 0, 300, 2026-01-01, false) → 0 the first day is the start of the range
  • timeScale(2026-01-01, 2026-01-31, 0, 300, 2026-01-31, false) → 300 the last day is the end of the range
import { timeScale } from "#fune/charts.scale@^1";
impl/typescript/time_scale.ts · 19 lines · open · raw

Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.

import { roundFloat } from "./math_round_float.ts";  ← from math.round-float ^1.0.0 · built alongside by fune
import { daysBetween } from "./dates_days_between.ts";  ← from dates.days-between ^1.0.0 · built alongside by fune
import { interpolate, pair } from "./charts_scale_linear_scale.ts";  ← linearScale, another function of this group · built into the same file, even by a slim install

/**
 * Where an ISO date lands on the range, linearly by calendar days: 2026-01-16
 * is halfway along a January axis. Dates are counted as whole days with
 * dates.days-between, never through a Date object, so no time zone can move
 * a point by a day.
 */
export function timeScale(domain: readonly string[], range: readonly number[], value: string, clamp: boolean): number {
  if (domain.length !== 2) throw new Error(`domain must have exactly 2 values, [from, to]; got ${domain.length}`);
  const [r0, r1] = pair(range, "range");
  const span = daysBetween(domain[0], domain[1]);
  if (span === 0) throw new Error(`domain has no width: both ends are ${domain[0]}`);
  let t = daysBetween(domain[0], value) / span;
  if (clamp) t = Math.max(0, Math.min(1, t));
  return roundFloat(interpolate(r0, r1, t), 6);
}

bandScale throws on bad input 16 tests

export function bandScale(domain: readonly string[], range: readonly number[], value: string, paddingInner: number, paddingOuter: number, align: number): Band
domainstring[]the categories in order, no repeats
rangefloat[]
valuestringone of the categories
paddingInnerfloat0 to 1: the share of each step left as a gap between bands
paddingOuterfloat0 or more, in steps: space before the first and after the last band
alignfloat0 to 1: where the outer space goes; 0.5 centres the bands
returnsBand

For example

  • bandScale(a, b, c, 0, 300, b, 0, 0, 0.5) → start 100, center 150, width 100 three bands with no padding
  • bandScale(a, b, c, d, 0, 100, a, 0.2, 0.1, 0.5) → start 2.5, center 12.5, width 20 padding: the first band
  • bandScale(a, b, c, d, 0, 100, d, 0.2, 0.1, 0.5) → start 77.5, center 87.5, width 20 padding: the last band
import { bandScale } from "#fune/charts.scale@^1";
impl/typescript/band_scale.ts · 64 lines · open · raw

Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.

import { type Band } from "./charts_scale_types.ts";
import { roundFloat } from "./math_round_float.ts";  ← from math.round-float ^1.0.0 · built alongside by fune
import { pair } from "./charts_scale_linear_scale.ts";  ← linearScale, another function of this group · built into the same file, even by a slim install

/**
 * The band a category occupies, as d3.scaleBand lays it out (without
 * rounding to whole pixels): the range is divided into equal steps, each
 * band is a step less the inner padding, and the outer padding is shared out
 * by `align`. A reversed range reverses the order of the bands, not their
 * direction, so `start` is always the lower coordinate.
 */
export function bandScale(
  domain: readonly string[],
  range: readonly number[],
  value: string,
  paddingInner: number,
  paddingOuter: number,
  align: number,
): Band {
  if (!(paddingInner >= 0 && paddingInner <= 1)) throw new Error(`paddingInner must be between 0 and 1; got ${paddingInner}`);
  checkOuter(paddingOuter, "paddingOuter");
  checkAlign(align);
  const [start, width] = bandPosition(domain, range, value, paddingInner, paddingOuter, align);
  return { start: roundFloat(start, 6), center: roundFloat(start + width / 2, 6), width: roundFloat(width, 6) };
}

// Exported for pointScale, which is a band scale whose bands have no width.

export function checkOuter(padding: number, what: string): void {
  if (!(padding >= 0)) throw new Error(`${what} must be 0 or more; got ${padding}`);
}

export function checkAlign(align: number): void {
  if (!(align >= 0 && align <= 1)) throw new Error(`align must be between 0 and 1; got ${align}`);
}

/** The unrounded lower coordinate of value's band, and the band width. */
export function bandPosition(
  domain: readonly string[],
  range: readonly number[],
  value: string,
  paddingInner: number,
  paddingOuter: number,
  align: number,
): [number, number] {
  const [r0, r1] = pair(range, "range");
  const n = domain.length;
  if (n === 0) throw new Error("domain must not be empty");
  let index = -1;
  for (let i = 0; i < n; i++) {
    for (let j = 0; j < i; j++) {
      if (domain[j] === domain[i]) throw new Error(`domain has a repeated value: "${domain[i]}"`);
    }
    if (domain[i] === value) index = i;
  }
  if (index < 0) throw new Error(`value is not in the domain: "${value}"`);
  const reverse = r1 < r0;
  let start = reverse ? r1 : r0;
  const stop = reverse ? r0 : r1;
  const step = (stop - start) / Math.max(1, n - paddingInner + paddingOuter * 2);
  start += (stop - start - step * (n - paddingInner)) * align;
  const slot = reverse ? n - 1 - index : index;
  return [start + step * slot, step * (1 - paddingInner)];
}

pointScale throws on bad input 11 tests

export function pointScale(domain: readonly string[], range: readonly number[], value: string, padding: number, align: number): number
domainstring[]the categories in order, no repeats
rangefloat[]
valuestringone of the categories
paddingfloat0 or more, in steps: space before the first and after the last point
alignfloat0 to 1; 0.5 centres the points
returnsfloatthe point's position, rounded to 6 decimal places

For example

  • pointScale(a, b, c, 0, 100, b, 0, 0.5) → 50 the middle of three points
  • pointScale(a, b, c, 0, 100, a, 0, 0.5) → 0 the first point sits on the start with no padding
  • pointScale(a, b, c, 0, 100, c, 0, 0.5) → 100 the last point sits on the end with no padding
import { pointScale } from "#fune/charts.scale@^1";
impl/typescript/point_scale.ts · 13 lines · open · raw

Imports name this capability’s declared dependencies, which fune builds next to it in your project; each one links to its page.

import { roundFloat } from "./math_round_float.ts";  ← from math.round-float ^1.0.0 · built alongside by fune
import { bandPosition, checkAlign, checkOuter } from "./charts_scale_band_scale.ts";  ← bandScale, another function of this group · built into the same file, even by a slim install

/**
 * The position of a category on an axis of evenly spaced points, as
 * d3.scalePoint: a band scale whose bands have no width (inner padding 1), so
 * the first and last points sit `padding` steps in from the ends.
 */
export function pointScale(domain: readonly string[], range: readonly number[], value: string, padding: number, align: number): number {
  checkOuter(padding, "padding");
  checkAlign(align);
  return roundFloat(bandPosition(domain, range, value, 1, padding, align)[0], 6);
}

Install

fune build

With that line in your source, in a TypeScript project (language typescript in fune.project), fune build resolves it and its 3 dependencies, pins them in fune.lock, downloads only the TypeScript package of each, and builds the code above into your project’s .fune/build, one readable file per capability with a header linking back here. Or pin a range in fune.project and build in one step:

fune add charts.scale

That builds the whole group. To build only what you call, and whatever it uses inside the group:

fune add charts.scale --only linearScale
Download for TypeScript charts.scale-1.1.0-typescript.fune · 38,932 bytes sha256 f3c8924737737dff236335c022f63ed5b6ff524264e07a1050e2fceb416a3283

The manifest, vectors and README with only the TypeScript implementation. Install it without the registry with fune add ./charts.scale-1.1.0-typescript.fune, or fetch it from a terminal with fune pull charts.scale@1.1.0:typescript.

The whole function, every language, is one file too: charts.scale-1.1.0.fune, 61,533 bytes, sha256 c1ff13b925cdadfa1c52e5ae9c82981d412d1778305d2bec4a47e4e0b15f4ba1. It installs into a project of any language.

Customise it in your app

The seams this capability offers. Put a marker directly above a function of your own and fune build wires it into the built code; the package on the registry is not changed, the built file’s header lists it under CUSTOMISED, and fune hooks lists every hook in the project. How hooks work.

before — your function gets the arguments and returns them, changed or not, or throws to refuse the call.

// fune: before charts.scale.linearScale
// fune: before charts.scale.invertLinear
// fune: before charts.scale.niceDomain
// fune: before charts.scale.logScale
// fune: before charts.scale.timeScale
// fune: before charts.scale.bandScale
// fune: before charts.scale.pointScale

after — your function gets the result and the arguments, and returns the final result.

// fune: after charts.scale.linearScale
// fune: after charts.scale.invertLinear
// fune: after charts.scale.niceDomain
// fune: after charts.scale.logScale
// fune: after charts.scale.timeScale
// fune: after charts.scale.bandScale
// fune: after charts.scale.pointScale

replace — inside this capability’s code only, calls to a dependency go to your function, with the same signature. Other capabilities that use it are unaffected; write in * to replace it everywhere.

// fune: replace dates.days-between in charts.scale
// fune: replace math.ln in charts.scale
// fune: replace math.round-float in charts.scale

step — your function runs at a numbered point inside a function’s body, receives the in-scope values it names as parameters, and may return replacements. List the points with fune show charts.scale --steps.

// fune: step charts.scale.<fn> after <n|label>

Tests

A version published now needs at least 8 tests for every function, and one that expects the error for each function that throws; the registry refuses it otherwise. fune verify --all runs each case in TypeScript, Python and Rust, and a project runs them again with fune verify. This page lists the cases; it does not run them. The exact JSON is vectors.json.

linearScale 14 tests

CaseArgumentsExpected
a quarter of the way along a 500 pixel axis 0, 100, 0, 500, 25, false → 125
the start of the domain is the start of the range 0, 100, 0, 500, 0, false → 0
the end of the domain is the end of the range 0, 100, 0, 500, 100, false → 500
a reversed range, as a y axis drawn downwards 0, 50, 300, 0, 10, false → 240
a reversed domain 100, 0, 0, 1, 75, false → 0.25
negative values -20, 40, 0, 600, -5, false → 150
past the end runs on without clamp 0, 10, 0, 100, 15, false → 150
past the end stops at the range with clamp 0, 10, 0, 100, 15, true → 100
before the start stops at the range with clamp 0, 10, 100, 200, -3, true → 100
clamp changes nothing inside the domain 0, 10, 0, 100, 2.5, true → 25
Show the other 4 tests
CaseArgumentsExpected
a third is rounded to 6 decimal places 0, 3, 0, 1, 1, false → 0.333
fractional domain 0.1, 0.3, 0, 10, 0.2, false → 5
a domain with no width is an error 5, 5, 0, 100, 5, false → error: domain has no width
a domain needs two ends 0, 1, 2, 0, 100, 1, false → error: domain must have exactly 2 values, [from, to]

invertLinear 8 tests

CaseArgumentsExpected
a pixel back to its value 0, 100, 0, 500, 125 → 25
the start of the range is the start of the domain 0, 100, 0, 500, 0 → 0
a reversed range 0, 50, 300, 0, 240 → 10
past the end of the axis is past the end of the data 0, 10, 0, 100, 150 → 15
a third is rounded to 6 decimal places 0, 1, 0, 3, 1 → 0.333
negative domain -20, 40, 0, 600, 150 → -5
a range with no width is an error 0, 10, 7, 7, 7 → error: range has no width
a range needs two ends 0, 10, 7, 7 → error: range must have exactly 2 values, [from, to]

niceDomain 12 tests

CaseArgumentsExpected
widens to whole tens 3, 97, 10 → domain 0, 100, step 10
small numbers widen to tenths 0.13, 0.87, 10 → domain 0.1, 0.9, step 0.1
a messy extent becomes 0 to 10 0.13, 9.7, 5 → domain 0, 10, step 2
an already nice domain is unchanged 0, 100, 10 → domain 0, 100, step 10
negative to positive -12.5, 37.2, 5 → domain -20, 40, step 10
a reversed domain stays reversed 97, 3, 10 → domain 100, 0, step 10
large values step in fives of a power of ten 1,234, 98,765, 20 → domain 0, 100,000, step 5,000
one tick 2, 9, 1 → domain 0, 10, step 10
a fractional step that divides badly 0.3, 0.9, 6 → domain 0.3, 0.9, step 0.1
equal ends are returned as they are 4, 4, 10 → domain 4, 4, step 0
Show the other 2 tests
CaseArgumentsExpected
count must be at least 1 0, 10, 0 → error: count must be a whole number of at least 1
a domain needs two ends 1, 5 → error: domain must have exactly 2 values, [from, to]

logScale 17 tests

CaseArgumentsExpected
a decade is a third of three decades 1, 1,000, 0, 300, 10, false → 100
two decades 1, 1,000, 0, 300, 100, false → 200
the start of the domain 1, 100, 0, 1, 1, false → 0
the end of the domain 1, 100, 0, 1, 100, false → 1
a reversed range, as a y axis 10, 1,000, 500, 0, 100, false → 250
2 sits at log10(2) of a decade, not a ninth of it as a linear scale would put it 1, 10, 0, 100, 2, false → 30.103
past the end runs on without clamp 1, 10, 0, 100, 100, false → 200
past the end stops at the range with clamp 1, 10, 0, 100, 100, true → 100
before the start runs on without clamp 1, 10, 0, 100, 0.1, false → -100
before the start stops with clamp 1, 10, 0, 100, 0.1, true → 0
Show the other 7 tests
CaseArgumentsExpected
a reversed domain 1,000, 1, 0, 300, 10, false → 200
a domain below one 0.01, 1, 0, 200, 0.1, false → 100
a domain end of zero is an error 0, 10, 0, 100, 1, false → error: log scale domain must be positive
a negative domain end is an error -1, 10, 0, 100, 1, false → error: log scale domain must be positive
a value of zero is an error 1, 10, 0, 100, 0, false → error: value must be positive for a log scale
a domain with no width is an error 5, 5, 0, 100, 5, false → error: domain has no width
a domain needs two ends 1, 10, 100, 0, 100, 5, false → error: domain must have exactly 2 values, [from, to]

timeScale 15 tests

CaseArgumentsExpected
the middle of January 2026-01-01, 2026-01-31, 0, 300, 2026-01-16, false → 150
the first day is the start of the range 2026-01-01, 2026-01-31, 0, 300, 2026-01-01, false → 0
the last day is the end of the range 2026-01-01, 2026-01-31, 0, 300, 2026-01-31, false → 300
a leap February has 29 days 2024-02-01, 2024-03-01, 0, 29, 2024-02-29, false → 28
a clock change is still one day (no time zone involved) 2026-03-28, 2026-03-30, 0, 100, 2026-03-29, false → 50
a reversed range over a year 2026-01-01, 2027-01-01, 365, 0, 2026-07-02, false → 183
a third of a three-day domain is rounded to 6 places 2026-01-01, 2026-01-04, 0, 1, 2026-01-02, false → 0.333
after the end runs on without clamp 2026-01-01, 2026-01-11, 0, 100, 2026-01-21, false → 200
after the end stops with clamp 2026-01-01, 2026-01-11, 0, 100, 2026-01-21, true → 100
before the start runs on without clamp 2026-01-01, 2026-01-11, 0, 100, 2025-12-22, false → -100
Show the other 5 tests
CaseArgumentsExpected
before the start stops with clamp 2026-01-01, 2026-01-11, 0, 100, 2025-12-22, true → 0
a reversed domain 2026-01-11, 2026-01-01, 0, 100, 2026-01-03, false → 80
a domain of one day has no width 2026-01-01, 2026-01-01, 0, 100, 2026-01-01, false → error: domain has no width
an impossible date is an error 2026-01-01, 2026-03-01, 0, 100, 2026-02-30, false → error: is not a real calendar date
a domain needs two ends 2026-01-01, 0, 100, 2026-01-01, false → error: domain must have exactly 2 values, [from, to]

bandScale 16 tests

CaseArgumentsExpected
three bands with no padding a, b, c, 0, 300, b, 0, 0, 0.5 → start 100, center 150, width 100
padding: the first band a, b, c, d, 0, 100, a, 0.2, 0.1, 0.5 → start 2.5, center 12.5, width 20
padding: the last band a, b, c, d, 0, 100, d, 0.2, 0.1, 0.5 → start 77.5, center 87.5, width 20
align 0 puts the outer space at the end a, b, c, d, 0, 100, a, 0.2, 0.1, 0 → start 0, center 10, width 20
align 1 puts the outer space at the start a, b, c, d, 0, 100, d, 0.2, 0.1, 1 → start 80, center 90, width 20
a reversed range reverses the order, not the band a, b, c, d, 100, 0, a, 0.2, 0.1, 0.5 → start 77.5, center 87.5, width 20
one category x, 0, 50, x, 0.5, 0, 0.5 → start 12.5, center 25, width 25
inner padding 1 leaves bands of no width a, b, 0, 10, b, 1, 0, 0.5 → start 10, center 10, width 0
thirds are rounded to 6 places a, b, c, 0, 100, b, 0, 0, 0.5 → start 33.333, center 50, width 33.333
a range through zero a, b, -50, 50, a, 0, 0.5, 0.5 → start -33.333, center -16.667, width 33.333
Show the other 6 tests
CaseArgumentsExpected
a value outside the domain is an error a, b, 0, 10, z, 0, 0, 0.5 → error: value is not in the domain: "z"
a repeated category is an error a, b, a, 0, 10, a, 0, 0, 0.5 → error: domain has a repeated value: "a"
an empty domain is an error , 0, 10, a, 0, 0, 0.5 → error: domain must not be empty
inner padding above 1 is an error a, 0, 10, a, 1.5, 0, 0.5 → error: paddingInner must be between 0 and 1
negative outer padding is an error a, 0, 10, a, 0, -1, 0.5 → error: paddingOuter must be 0 or more
align above 1 is an error a, 0, 10, a, 0, 0, 2 → error: align must be between 0 and 1

pointScale 11 tests

CaseArgumentsExpected
the middle of three points a, b, c, 0, 100, b, 0, 0.5 → 50
the first point sits on the start with no padding a, b, c, 0, 100, a, 0, 0.5 → 0
the last point sits on the end with no padding a, b, c, 0, 100, c, 0, 0.5 → 100
half a step of padding at each end a, b, c, 0, 100, a, 0.5, 0.5 → 16.667
half a step of padding, the last point a, b, c, 0, 100, c, 0.5, 0.5 → 83.333
a single point is centred x, 0, 80, x, 0, 0.5 → 40
a reversed range a, b, c, 100, 0, a, 0, 0.5 → 100
align 0 pushes the padding to the end a, b, 0, 100, b, 1, 0 → 33.333
a value outside the domain is an error a, b, 0, 100, q, 0, 0.5 → error: value is not in the domain: "q"
negative padding is an error a, b, 0, 100, a, -1, 0.5 → error: padding must be 0 or more
Show the other 1 test
CaseArgumentsExpected
align below 0 is an error a, b, 0, 100, a, 0, -0.1 → error: align must be between 0 and 1

More from the author

Scales are geometry, not money, so they work in floating point. Every result is rounded to 6 decimal places inside the function (half up, as `floor(x * 1e6 + 0.5) / 1e6`), which is far below a pixel and makes TypeScript, Python and Rust agree to the digit.

A domain or range is a two-element list, `[from, to]`. Either may run backwards: a y axis usually maps `[0, max]` onto `[height, 0]`. A domain whose two ends are equal has no width to map, and `linearScale` raises rather than divide by zero; `invertLinear` raises for a range with equal ends for the same reason.

Without `clamp`, a value outside the domain maps outside the range, which is what an axis drawing a point past its end wants. With it, the result stops at the range's ends.

`niceDomain` picks a tick step of 1, 2 or 5 times a power of ten, aiming for about `count` ticks across the domain, then moves each end out to a multiple of that step, repeating until the step stops changing. It returns the step with the domain, so the axis can draw ticks on exactly those multiples. A domain whose ends are equal is returned unchanged with a step of 0.

## New in 1.1.0: log, time, band and point scales

The three functions above are unchanged from 1.0.0, rounding included (half up, `floor(x * 1e6 + 0.5)`), so upgrading moves no existing point. The four new ones round to 6 decimal places with `math.round-float` (half away from zero on the exact double), which is what every newer charts capability uses.

**`logScale`** maps equal ratios to equal lengths: on `[1, 1000]` the value 10 is a third of the way along. The base of the logarithm cancels, so there is no base to pass. Both domain ends and the value must be greater than zero. The logarithm is `math.ln`, built from `+ - * /` only, because `Math.log`, `math.log` and `f64::ln` may differ in their last bit, which is enough to split two languages at a rounding boundary.

**`timeScale`** is a linear scale over calendar days: the position of an ISO date is its day count from the domain's first date (by `dates.days-between`) over the domain's length in days. There is no `Date` object and no time zone, so a clock change or a machine in another zone cannot move a point by an hour or a day. Dates only; a scale over times of day is out of scope.

**`bandScale`** is d3.scaleBand without pixel rounding. The range is divided into `n - paddingInner + 2 x paddingOuter` steps; each band is one step less `paddingInner` of it; `align` shares the leftover outer space (0 all at the end, 1 all at the start, 0.5 centred). It returns the band's `start` (always its lower coordinate), `center` and `width`. A reversed range reverses the order of the categories, not the direction of a band. Repeated categories are an error: d3 silently merges them, which draws two bars on top of each other.

**`pointScale`** is d3.scalePoint: a band scale with `paddingInner` 1, so the bands have no width and each category is a point; `padding` is in steps at each end.

Sources: Mike Bostock, d3-scale (github.com/d3/d3-scale), `band.js`, `log.js` and `time.js`, whose layout rules these follow.

Files

PathBytes
README.md3,731
impl/python/band_scale.py2,411
impl/python/invert_linear.py528
impl/python/linear_scale.py1,503
impl/python/log_scale.py1,007
impl/python/nice_domain.py2,218
impl/python/point_scale.py563
impl/python/time_scale.py907
impl/rust/band_scale.rs3,286
impl/rust/invert_linear.rs772
impl/rust/linear_scale.rs1,867
impl/rust/log_scale.rs1,331
impl/rust/nice_domain.rs2,738
impl/rust/point_scale.rs925
impl/rust/time_scale.rs1,285
impl/typescript/band_scale.ts2,538
impl/typescript/invert_linear.ts590
impl/typescript/linear_scale.ts1,639
impl/typescript/log_scale.ts1,167
impl/typescript/nice_domain.ts2,047
impl/typescript/point_scale.ts637
impl/typescript/time_scale.ts990
vectors.json13,419