Description
Compare explicit historical or planning window coordinates without inferring safe access.
Public agreements, monitoring, dialogue, and assistance records use explicit identifiers, time windows, accounting bases, and participation categories. A match or coverage share describes a supplied representation. It does not independently establish the accuracy of a record, the fairness of a process, or conditions on the ground.
Compare explicit historical or planning window coordinates without inferring safe access.
When to use this tool
Use Humanitarian Access Window Gap when you need this local public-record match, participation measure, duration, or accounting check.
How to use the tool and how it works
- Enter firstWindowEnd, nextWindowStart. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read gap, overlap. Inspect overlap before interpreting the associated values.
Return gap=nextWindowStart-firstWindowEnd and overlap=(nextWindowStart<firstWindowEnd).1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstWindowEnd | First Window End | Required. Finite number. |
| nextWindowStart | Next Window Start | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| gap | Signed difference under the formula stated above. | Required. Finite number. |
| overlap | True only when next start is strictly before the first end. | Required. Boolean. |
{
"input": {
"firstWindowEnd": 10,
"nextWindowStart": 15
},
"output": {
"gap": 5,
"overlap": false
}
}Limitations and assumptions
- Only two supplied boundary coordinates are compared; exact touching is not overlap. This does not validate full access windows, current permissions, route conditions, or safe humanitarian movement.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Signed zero is exported as zero.
Alternative or Complementary methods
Verify the underlying public sources, time basis, inclusion policy, and interpretation of the reporting denominator. Substantive agreement analysis or current field conditions require information beyond these supplied tokens or coordinates.
References
Similar or alternative tools
- Agreement Clause Date Offset
Compare supplied public agreement date coordinates without interpreting legal effect.
- Ceasefire Clause Date Span
Measure explicitly supplied public clause day bounds without interpreting obligations or forecasting compliance.