Description
Compare two inclusive possible-date envelopes.
Date labels and intervals depend on origins, endpoint inclusion and calendar versus elapsed-time conventions. Numeric serial periods and local token formats can represent useful bookkeeping without resolving a real instant or official fiscal rule.
Compare two inclusive possible-date envelopes.
When to use this tool
Use Date Comparison Partial Precision Overlap when checking a supplied date-label, duration or interval convention.
How to use the tool and how it works
- Enter firstEarliest, firstLatest, secondEarliest, secondLatest. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read overlap, firstDefinitelyBefore. Inspect overlap, firstDefinitelyBefore before interpreting the associated values.
Compare two inclusive possible-date envelopes. Validate ordered bounds; overlap includes shared endpoints, while firstDefinitelyBefore requires firstLatest < secondEarliest.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| firstEarliest | First Earliest | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| firstLatest | First Latest | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| secondEarliest | Second Earliest | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| secondLatest | Second Latest | Required. Text; maximum UTF-16 length 8192. Real proleptic Gregorian YYYY-MM-DD; four-digit years 0000-9999 accepted. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| overlap | Overlap | Required. Boolean. |
| firstDefinitelyBefore | First Definitely Before | Required. Boolean. |
{
"input": {
"firstEarliest": "2026-01-01",
"firstLatest": "2026-01-31",
"secondEarliest": "2026-01-15",
"secondLatest": "2026-02-01"
},
"output": {
"overlap": true,
"firstDefinitelyBefore": false
}
}Limitations and assumptions
- Envelopes are supplied uncertainty bounds, not derived precision or statistical confidence intervals.
- 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.
Alternative or Complementary methods
Use a complete date/time implementation and the applicable calendar policy for actual scheduling and interval interpretation.
References
Similar or alternative tools
- Date Interval Single Day Closure Label
Count civil days under a supplied endpoint convention.
- Date Range Unbounded End Token
Assemble a bounded or open date interval token.