Plinth Height Visibility Sightline Angle Optimizer

Choose all declared plinth-height candidates closest to caller preferred signed 2Deye-above-object viewing angle. Actual viewer/object geometry required, no extrapolated optimum,3Docclusion, universal ideal view or accessible/safe plinth certification.

Description

Plinth sightlines relate eye height, object target height and horizontal viewing distance.

Plinth sightlines relate eye height, object target height and horizontal viewing distance.^[1]

Choosing among declared candidate heights differs from optimizing an unrestricted exhibit layout.

When to use Plinth Height Visibility Sightline Angle Optimizer

Use this tool to calculate or review the supplied observations under the stated rules. Establish the object or visitor scope, measurement units and independently applicable conservation, engineering, access or editorial reference.

How to use Plinth Height Visibility Sightline Angle Optimizer and understand its results

Establish the object or visitor scope, measurement units and independently applicable conservation, engineering, access or editorial reference.
Enter callerCandidatePlinthHeightsMeters, observedViewerEyeHeightMeters, observedObjectTargetOffsetAbovePlinthMeters, observedHorizontalViewingDistanceMeters, callerPreferredSignedViewingAngleDegrees, using the field meanings and rules below, then run the tool.
Read result.bestCallerCandidateHeightsMeters, result.candidateSignedViewingAnglesDegrees. Use the units and sign conventions below.
Correct any reported input issue and run again. Before using a successful result, check the stated units, signs, reference scope and observation coverage.

Input field	Meaning	Value type	Requirement
callerCandidatePlinthHeightsMeters	Caller candidate plinth heights meters	list of number	Required
observedViewerEyeHeightMeters	Observed viewer eye height meters	number	Required
observedObjectTargetOffsetAbovePlinthMeters	Observed object target offset above plinth meters	number	Required
observedHorizontalViewingDistanceMeters	Observed horizontal viewing distance meters	number	Required
callerPreferredSignedViewingAngleDegrees	Caller preferred signed viewing angle degrees	number	Required

Require a nonempty nonnegative candidate-height list, nonnegative eye height and target offset, positive horizontal viewing distance and preferred angle −90 to 90 degrees. For each candidate use atan2(eye−candidate−offset,distance) converted to degrees. Minimize absolute difference from the preferred angle among candidates; return all heights with error within 1e-12 of the minimum and all candidate angles. Positive angles mean eye above target under this convention.

angleDegrees_h=(180/pi)×atan2(eyeHeight−h−targetOffset,distance); bestCandidates={h:abs(error_h−minError)≤1e-12}

Use the matching field units and the exact boundary, ordering and reference rules above.

Output field	Meaning	Value type
result	Structured result; its nested fields below contain the actual calculation or selected reference	object
result.bestCallerCandidateHeightsMeters	All supplied candidate heights within 1e-12 of the minimum absolute angle error; duplicates may remain	list
result.candidateSignedViewingAnglesDegrees	Angles in input candidate order; positive when viewer eye is above the object target under the adopted convention	list

json

{
  "input": {
    "callerCandidatePlinthHeightsMeters": [
      0.5,
      1,
      1.5
    ],
    "observedViewerEyeHeightMeters": 1.5,
    "observedObjectTargetOffsetAbovePlinthMeters": 0.5,
    "observedHorizontalViewingDistanceMeters": 2,
    "callerPreferredSignedViewingAngleDegrees": 0
  },
  "output": {
    "result": {
      "bestCallerCandidateHeightsMeters": [
        1
      ],
      "candidateSignedViewingAnglesDegrees": [
        14.036243467926477,
        0,
        -14.036243467926477
      ]
    }
  }
}

Limitations and assumptions

Object condition, observation coverage and applicable references determine applicability. A supplied comparison or record does not certify conservation treatment, engineering, access compliance or insurance eligibility.

Missing required fields, unknown fields, wrong types and violated rules return input issues. Numeric values and outputs must be finite. Lists and matrices must be dense, without missing cells. Numeric lists allow at most 10000 entries; ordinary string lists allow at most 128 strings of 128 UTF-16 units each; numeric matrices allow at most 128 rows and 128 columns, subject to narrower requirements above. Extremely large composite outputs are rejected.

Alternative or Complementary methods

For a related step, use Wheelchair Reach Display Height Compliance Checker: Wheelchair reach depends on the applicable access standard and the actual approach geometry. For a complementary comparison, use Label Reading Distance Character Height Rule Checker: Character angular height relates measured letter height to reading distance.

References

Plinth Height Visibility Sightline Angle Optimizer — tool.io

Similar or alternative tools

Wheelchair Reach Display Height Compliance Checker
Wheelchair reach depends on the applicable access standard and the actual approach geometry.
Label Reading Distance Character Height Rule Checker
Character angular height relates measured letter height to reading distance.