How Can Documentation Explain a Data Gap?
From the earlier reference collection. Read the current software blog.
Good gap documentation identifies the missing scope, distinguishes missing records from zero values, and explains the limits the gap places on comparisons.
Say exactly what is absent
Describe a gap by field, location, and time range wherever that information is known. “Data may be incomplete” leaves readers unable to tell whether a chart has one missing hour or an entire station’s history. A more useful note could say: “No temperature records are present for station R17 from May 4 through May 6; nearby stations are unaffected.” If the extent is still being investigated, mark it as provisional and say when it was last checked.
Distinguish a gap in the provider’s records from a failure in your own retrieval or display process. A missing observation may mean the instrument did not report; a missing file may mean a download failed; an empty chart may mean the interface filtered out valid records. These have different implications and different remedies. Identify which layer is known to be responsible, and avoid presenting a suspected cause as established fact.
Explain how it affects interpretation
Tell readers what comparisons become unreliable. If a day is missing from a daily average, the value may represent fewer observations than neighboring days. If a region lacks readings, a map may make its conditions appear calmer simply because there is nothing to plot. A gap can also break a trend line, obscure a short event, or make two locations seem comparable when their coverage differs.
Do not silently convert absence to zero. Zero is a measurement with meaning; missing is an absence of evidence. If your display interpolates values, carries forward the last observation, or aggregates partial coverage, disclose the rule and label derived results. For example, state that a daily mean is shown only when at least a specified number of hourly records exist, if that is the actual rule.
Help readers assess and revisit the gap
Provide a practical way to see the affected dates or locations, such as a table, downloadable status list, or a note beside the chart. If the gap is temporary, say whether later backfill is expected, and avoid promising a repair date unless the provider has committed to one. Include the date the gap was observed and update the note when new data arrive or its scope changes.
A concise gap explanation should answer: what is missing, where and when, how was that determined, and which conclusions should be treated cautiously? Consider a comparison of two stations over a week: if one station missed two nights, explain that its weekly minimum may not capture the same period as the other station’s. That practical detail lets readers decide whether to compare, wait for backfill, or seek another source. Keep the gap visible in exported data as well as on screen, so downstream users do not mistake a partial series for a complete one.