Count Tactile Warning Tiles Needed Across Kerb Ramp Widths
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.
1 · crossing approach | dropped kerb width mm | depth rows required
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.
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.
Perspective: 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.
2 · Read the tactile paving strip
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.
Paid layer: tactile paving strip print and history
one-time step · the free reading above stays complete
Free tier
- one complete tactile paving strip run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the tactile paving strip with its row workings
- CSV of tactile tiles needed and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the tactile paving strip, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
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.
- 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.
Mechanism: competence-autonomy-loop
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.