@mapmap/maps 0.3.0 → 0.5.0

package/README.md

@@ -304,10 +304,24 @@ const map = new MapMapMap({
 - **`extra.nav`** (Studio's navigation design block) is carried by the theme
   file and ignored by style compilation - see "Using your Studio design"
   below.
-- **Layer ids** (paint order): `background landcover landuse park water
-  waterway aeroway building rail road-path road-minor road-major
-  boundary-minor boundary housenumber road-labels water-name poi-labels
-  mountain-peak-labels aerodrome-labels place-labels`.
+- **Layer ids** (29, paint order): `background landcover landuse park water
+  waterway aeroway building building-outline rail pedestrian-areas road-path
+  road-minor-casing road-major-casing road-minor road-major
+  road-bridge-casing road-bridge boundary-minor boundary road-oneway
+  housenumber road-labels water-name poi-labels
+  mountain-peak-labels aerodrome-labels place-labels country-labels`.
+  `landuse` and `landcover` are class-tinted via a `match` on the feature
+  `class` (hospital, school, cemetery, military, retail, grass, wood, …),
+  blended from existing slots so the palette stays at 17; unknown classes
+  fall through to the plain slot colour. `brunnel: tunnel` roads dim in
+  place and `brunnel: bridge` roads redraw above the flat network as
+  `road-bridge-casing`/`road-bridge`. `road-oneway` draws direction arrows
+  from z16 as a text glyph, so no sprite is required.
+  The `*-casing` and `building-outline` layers take their colour from the
+  `road`/`roadMajor`/`building` slots blended toward `textSecondary` — they
+  are not separate palette slots, so overriding the base slot restyles the
+  casing with it. Both casings paint beneath both road fills so a minor
+  road's casing never crosses a major road at a junction.
 - Per-layer overrides: `visible`, `paint`/`layout` (per-key merge), `filter`
   (replace), `minzoom`/`maxzoom`. `extra_layers` (full MapLibre layers over
   the `territory` source) are inserted above the base map, below labels.
@@ -497,6 +511,35 @@ Voice prompts arrive plain and as SSML; banners carry the maneuver glyph
 and, where OSM has `turn:lanes` data, a lane diagram (sprite icons
 `lane-left`, `lane-straight`, … ship with the map assets).
 
+### Direction icons (`@mapmap/maps/direction-icons`)
+
+A separate entry point (so the core bundle is unaffected) with the platform's
+90-icon manoeuvre set as inline SVG, plus the OSRM maneuver mapping:
+
+```ts
+import {
+  directionIcons,          // { turn_left: "<svg…>", roundabout_right: …, ferry: … }
+  iconNameForStep,         // (step) => DirectionIconName — preferred
+  iconNameForManeuver,     // (type?, modifier?, drivingSide?) => DirectionIconName
+  directionIconSvg,        // shorthand: the SVG for a maneuver
+} from "@mapmap/maps/direction-icons";
+
+el.innerHTML = directionIcons[iconNameForStep(step)];
+```
+
+Icons are 20×20 `viewBox` SVGs. The arrow inherits `currentColor`; secondary
+road furniture (other lanes, the rest of a roundabout ring, ferry water) is
+filled with `var(--mm-icon-secondary, #C9CDD2)` — set that CSS custom
+property to retheme it. Unknown maneuvers degrade to the plain turn family,
+never a missing icon.
+
+Prefer `iconNameForStep(step)`: it reads everything off the OSRM step
+itself — ferry legs from `step.mode`, and the u-turn direction from
+`step.driving_side` (the MapMap gateway emits it on u-turn steps), so
+left-hand-traffic markets render `uturn_right` with no configuration.
+The lower-level `iconNameForManeuver` remains for callers without a step
+object; it defaults to right-hand traffic.
+
 ## Navigation camera
 
 `NavigationCamera` gives the Google-Maps-style chase cam in one call per