Count Tactile Warning Tiles Needed Across Kerb Ramp Widths — Free
Tactile blister paving must span the full dropped-kerb width across every depth row. Divide each approach width by your modular tile size, round up per course, and flag crossings whose width requires masonry cuts.
The proof surface
Ramp-slope tools check longitudinal run-to-rise ratios. This calculates modular tactile warning tile quantities across dropped-kerb widths and identifies non-modular widths needing cut tiles.
Why the flat version breaks
Rounding tile counts down on non-modular widths
Leaving a 150 mm gap at the edge of a dropped kerb creates an unguarded hazard for cane users.
Pooling offcuts across rows without checking pattern alignment
Blister domes must align across joints; narrow offcuts often cannot be reused.
Confusing blister warning tiles with corduroy hazard tiles
Crossing approaches and platform edges use distinct tactile profiles under national standards.
How to work the tactile paving strip
Enter the flush kerb width that tactile warning surfaces must cover at each crossing approach.
Enter the number of tile courses deep required by your local streetscape standard (commonly 2 or 3 rows of 400 mm tiles).
Four hundred millimetres is a common blister-tile module; adjust to 300 mm or your specified product width.
A 1,350 mm approach with 400 mm tiles needs 4 tiles per row (8 tiles across 2 rows) and flags 250 mm of cut trim per row so you order cutting blades and spare units.
What the tactile paving strip replaces
| Question | Before | Visible working |
|---|---|---|
| Rounding tile counts down on non-modular widths | Leaving a 150 mm gap at the edge of a dropped kerb creates an unguarded hazard for cane users. | Specify the number of depth rows required |
| Pooling offcuts across rows without checking pattern alignment | Blister domes must align across joints; narrow offcuts often cannot be reused. | Set the modular square tile width |
| Confusing blister warning tiles with corduroy hazard tiles | Crossing approaches and platform edges use distinct tactile profiles under national standards. | Check total tiles and cut-waste flags |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Modular tile-count arithmetic from dimensions you enter. Not highway engineering or accessibility code certification; verify tactile profile, colour contrast and depth layout against local street-design standards.
Data note: Everything runs in this browser tab on the tactile paving strip: your crossing approach | dropped kerb width mm | depth rows required stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a paper ticker strip
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the tactile paving strip reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The tactile paving strip reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the count tactile warning tiles needed across kerb ramp widths companionBoundary
Modular tile-count arithmetic from dimensions you enter. Not highway engineering or accessibility code certification; verify tactile profile, colour contrast and depth layout against local street-design standards.
What this is built on
- Method: Four hundred millimetres is a common blister-tile module; adjust to 300 mm or your specified product width.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: Leaving a 150 mm gap at the edge of a dropped kerb creates an unguarded hazard for cane users. After: the tactile paving strip shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this tactile paving strip, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a tactile paving strip. Return plain rows only: crossing approach | dropped kerb width mm | depth rows required. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: crossing approach | dropped kerb width mm | depth rows required. No AI response is executed as code.