Skip to content

Distinguish the two ways of asking for daily data - #22

Merged
chross22 merged 1 commit into
masterfrom
readme-daily-forms
Aug 7, 2026
Merged

Distinguish the two ways of asking for daily data#22
chross22 merged 1 commit into
masterfrom
readme-daily-forms

Conversation

@chross22

@chross22 chross22 commented Aug 7, 2026

Copy link
Copy Markdown
Owner

The section introduced frequency = "daily" and dates one after the other without saying they answer different questions, so it read as two routes to the same place with dates merely cheaper.

The question that prompted this — whether a date range still returns every day — is the one the section failed to answer. It does, and now says so.

Want Use Gives
Every day in a period frequency = "daily" with years and months a continuous series
Particular days dates only those dates

Each gets a heading. Every day in a period is for a continuous series — a time series at one station, an animation, anything where the gaps between days would matter. Particular days is for matching observations.

Thinning a long record

Documented for the first time. It was implied by "only the days that matter are downloaded" but never shown, and it is the answer for anyone who wants a decade without 4,017 downloads:

# Weekly through a decade: 574 downloads rather than 4,017
accessEnvDat(vars = "SST", bounding_box = bb,
             dates = seq(as.Date("2005-01-01"), as.Date("2015-12-31"), by = "week"))

The counts are checked, not estimated

seq(..., by = "week") over 2005–2015 gives 574 dates against 4,017 days, and parse_dates() takes the Date vector seq() returns unchanged. I had first written 4,018 — an off-by-one on an inclusive date range — and corrected it after running the arithmetic.

Also verified the underlying claim with a live fetch before writing any of this: frequency = "daily" with years = 2015, months = 2 returns all 28 days of February, 1,344 rows, detected as day.

Verification

R CMD checkStatus: OK. Full suite green. All README anchors re-checked including the two new subsections.

🤖 Generated with Claude Code

The section introduced frequency = "daily" and `dates` one after the
other without saying they answer different questions, so it read as two
routes to the same place with `dates` merely cheaper. The question that
prompted this - whether a date range still returns every day - is the
one the section failed to answer.

They are now contrasted up front and given a heading each. Every day of
a period is frequency = "daily" with years and months, for a continuous
series where the gaps between days would matter. Particular days is
`dates`, for matching observations.

Also documents `dates` as the way to thin a long record, which was
implied by "only the days that matter are downloaded" but never shown.
Any sequence works, so a decade weekly is one seq() call.

The counts in that example are checked rather than estimated: weekly
across 2005-2015 is 574 dates against 4,017 days, and parse_dates()
takes the Date vector seq() returns unchanged. I had written 4,018,
which was an off-by-one on an inclusive date range.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@chross22
chross22 merged commit 2ce5cff into master Aug 7, 2026
5 checks passed
@chross22
chross22 deleted the readme-daily-forms branch August 7, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant