Keep measurement boundaries explicit
A complete local report should state which claim its measurements support.
Retain the claim behind each number
A missing character question is solved by inspecting the supplied cmap, not by letting the operating system render with a different font. Grid counts need a declared coordinate system and exact boundary policy. Thousands of STL files require complete batch accounting rather than a successful sample of one model.
| Observed evidence | What remains unproved |
|---|---|
| Nonzero cmap glyph | Shaping or complete sequence rendering |
| Complete cell counts sum to input points | Lossless original overprecision or equal area |
| Exact edges paired with opposite direction | Self-intersection-free physical solid |
Make partial failure visible
A malformed STL is an invalid row with null geometry, not a zero-volume valid model. The measured and invalid totals must sum to the complete input count. When the whole batch exceeds its work or output budget, producing a truncated success report would conceal missing work, so the operation fails as a whole.
- Keep original files and full downloads.
- Compare declared units and parsing precision before comparing measurements.
- Use the complete reports; the bounded200-row browser table is a preview.
- Rerun after correcting an input or budget; cancellation is not a completed partial result.
References
- Font coverage user question
Question body read on2026-10-07; task evidence, not a claim of universal format support.
- Rectilinear grid user question
Question body read on2026-10-07; task evidence, not a claim of universal format support.
- Large STL batch user question
Question body read on2026-10-07; task evidence, not a claim of universal format support.
Tools in this category
Expand a tool to see its steps, options and supported formats, then open its workspace.
Font Unicode coverageCheck supplied static fonts for each Unicode code point, without installing fonts or using fallback.
Select static TTF/OTF files and enter required text. Read complete per-font glyph IDs and missing code points. Coverage checks cmap, not shaping or rendered emoji sequences.
Steps
- Choose fonts and enter required text.
- Review per-font coverage and selected cmap metadata.
- Download full JSON/CSV; compare glyph IDs without system fallback.
Capabilities and limits
- 20 files;10 MiB each;80 MiB total. Text1 MiB,10,000 unique code points and100,000 font–code-point pairs. Complete JSON/CSV outputs are limited to20 MiB each.
- Uncompressed static SFNT TTF/OTF only. Validate table checksums/ranges and glyph bounds; reject TTC/WOFF/WOFF2, variable fonts and variation-sequence maps. Select cmap12 before4, Windows before Unicode ties. Glyph0 is missing.
Rectilinear grid point countsCount local planar or WGS84 point coordinates in occupied rectangular cells with explicit half-open boundaries.
Use CSV with x,y headers or a Point FeatureCollection. Declare planar units or WGS84 degrees, grid origin and positive steps. Download every occupied cell and count; no online map or CRS inference is used.
Steps
- Supply points and declare coordinate space/units.
- Set origin and positive x/y steps; lower edges are included, upper edges excluded.
- Download all polygon cells and complete count JSON/CSV.
Available options
- Coordinate space
- Planar input units · WGS84 degrees
- Planar length unit
- m
- Grid origin x
- 0
- Grid origin y
- 0
- Cell width in input units
- 0.1
- Cell height in input units
- 0.1
Capabilities and limits
- One30 MiB file or1 MiB pasted text;100,000 points,10,000 occupied cells. CSV has exactly x,y columns; JSON must contain only2D Point geometries and no CRS field.
- Coordinates/origin have absolute value≤1e12; steps≥1e−9, indexes≤1e9. Inputs first parse as IEEE754 binary64. Canonical String(number) decimals use exact BigInt grid arithmetic; original overprecision is not preserved. Reject degenerate corners or WGS84 cells extending outside longitude/latitude bounds.
Batch STL geometry measurementsMeasure up to3,000 local STL models with complete bounds, dimensions, area and explicitly qualified closed-surface integrals.
Choose many ordinary STL files and declare their length unit. Each file gets a complete measured or invalid row. Open, nonmanifold or inconsistent meshes keep usable area/bounds but have null volume; source files are not changed.
Steps
- Choose the complete STL queue and declare input units.
- Review measured/invalid totals and partial status.
- Download every row, bounds, area and qualified volume.
Available options
- Declared length unit
- mm
Capabilities and limits
- 3,000 files,30 MiB each,80 MiB total;100,000 triangles/file and1,000,000 triangle work overall. Full JSON+CSV together≤20 MiB. File budgets reject the whole batch; malformed individual models become invalid rows; all-invalid fails.
- Binary/ASCII finite STL; coordinates absolute value≤1e12 and no degenerate triangle. Exact parsed-coordinate edges, no epsilon merge. Volume is an absolute oriented closed-surface integral only when every edge occurs twice in opposite directions. Self-intersection and nested-shell solid semantics are not certified; no mass/repair/rescale.