Gaps, uncertain days, and methodology limits
A presence gap exists when one journey’s destination country is not the next journey’s origin country. Example. You arrive in Thailand, and the next journey starts in Vietnam, with no hop logged between them.
Closed historical gaps
Section titled “Closed historical gaps”TripLedger clips a closed past gap to the active window, removes those dates from the prior country’s contribution, and reports them as unowned uncertain days. It does not guess which country you were in. The same gap block can appear on both endpoint country rows for context. Do not add gap blocks across countries.
A country touched by a gap is marked uncertain regardless of its threshold.
Open gaps to a future journey
Section titled “Open gaps to a future journey”If the current clock sits inside an open gap that leads to a future journey, residency, Schengen, travel summary, and current country all fail until you fix it. A future as-of date also fails when that cutoff sits inside a later gap. The error names both journey ids and countries. Fix the endpoints or log the missing hop, then retry.
Two different gap clocks
Section titled “Two different gap clocks”Uncertain days use country-presence stamps. The Journeys table gap detector uses display bookends (first-leg departure, last-leg arrival). Multi-leg journeys can make those two day counts differ. Both are signals that the ledger is incomplete. Neither invents a location.
Shared limits
Section titled “Shared limits”- Stays never fill gaps or add days.
- Forward results assume you remain in the last logged destination after honoring future journeys already in the ledger.
- Results do not invent movements.
- Crossing dates can count in both countries under any-presence. Schengen zone totals still deduplicate.