Timber Joist Catalogue Comparator
Enter your own traceable ratings and demand criteria. The sample records are invented schema examples, not usable sections.
Enter your own traceable ratings and demand criteria. The sample records are invented schema examples, not usable sections.
Enter your own traceable ratings and demand criteria. The sample records are invented schema examples, not usable sections.
Comparison report
Units and precision
Lengths: m, cm, mm, ft, in; forces: N, kN, lbf; moments: Nm, kNm, lbf·ft; loads: N/m, kN/m, N/m2, kN/m2; mass: kg, lb; pressure: Pa, kPa, MPa, psi; moisture: %, 1; cost: currency:USD or another three-letter currency. Exact decimal rational conversion is used; currencies are never converted. Limits: 100 records, 20 scenarios, 40 criteria per scenario, 160,000 characters per input. Numeric strings are nonnegative plain decimals, with no exponents; span and dimensions must be positive. Repeating a field allows a lower and upper bound.
Source and scope
Each record carries source, edition and providedBy. Optional record scenarios override base values for that named scenario. Supply user-rated values for the same support, span, spacing, load and service conditions. Missing fields reject the record; undeclared requirements remain unverified.
Required schema keys
Steel requires span, moment and shear criteria; timber requires span, spacing, load and support. Add deflection, dimensions, mass, cost, moisture and service criteria as needed. Field identifiers are schema keys and are not translated.
This compares supplied ratings only. It does not establish structural safety, code compliance or approval. Torsion, buckling, lateral restraint, connections, fire, fatigue, vibration and other undeclared checks remain unverified.
Data stays in this browser. JSON keys are fixed technical identifiers. Labels, instructions and reports use the selected page language.
A QUICK WALKTHROUGH
How to use this tool
- Provide catalogue source, edition and person supplying every rating. Use decimal strings to preserve exact values.
- Declare every load scenario and criterion. min means rating ≥ demand; max means value ≤ limit; equal means exact equality. Text values must match exactly.
- Choose a numeric ranking field and ascending or descending order. Review all eligible records, equal ranks and every rejection; editing inputs clears the previous report. ranking requires field, order (asc/desc), and unit.
Units and precision
Lengths: m, cm, mm, ft, in; forces: N, kN, lbf; moments: Nm, kNm, lbf·ft; loads: N/m, kN/m, N/m2, kN/m2; mass: kg, lb; pressure: Pa, kPa, MPa, psi; moisture: %, 1; cost: currency:USD or another three-letter currency. Exact decimal rational conversion is used; currencies are never converted. Limits: 100 records, 20 scenarios, 40 criteria per scenario, 160,000 characters per input. Numeric strings are nonnegative plain decimals, with no exponents; span and dimensions must be positive. Repeating a field allows a lower and upper bound.
Source and scope
Each record carries source, edition and providedBy. Optional record scenarios override base values for that named scenario. Supply user-rated values for the same support, span, spacing, load and service conditions. Missing fields reject the record; undeclared requirements remain unverified.
Unverified engineering requirements
This compares supplied ratings only. It does not establish structural safety, code compliance or approval. Torsion, buckling, lateral restraint, connections, fire, fatigue, vibration and other undeclared checks remain unverified.
Data stays in this browser. JSON keys are fixed technical identifiers. Labels, instructions and reports use the selected page language.
Choose a numeric ranking field and ascending or descending order. Review all eligible records, equal ranks and every rejection; editing inputs clears the previous report. ranking requires field, order (asc/desc), and unit.
GOOD TO KNOW
Common questions
How do I enter a catalogue?
Use records with id, source, edition, providedBy and values. Numeric values have string value and unit; text values have string value only. No licensed tables or default strengths are included.
What must each scenario declare?
Steel requires span, moment and shear criteria; timber requires span, spacing, load and support. Add deflection, dimensions, mass, cost, moisture and service criteria as needed. Field identifiers are schema keys and are not translated.
Is the first eligible result a certified design?
No. Rankings reflect only your selected field. All equal ranks are retained. Region, current licensed normative data and an engineering review are needed for actual structural selection.