Skip to content

602 update clone from s3 to warn about missing gages#603

Merged
samlamont merged 6 commits intomainfrom
602-update-clone_from_s3-to-warn-about-missing-gages
Jan 7, 2026
Merged

602 update clone from s3 to warn about missing gages#603
samlamont merged 6 commits intomainfrom
602-update-clone_from_s3-to-warn-about-missing-gages

Conversation

@samland1116
Copy link
Contributor

  • adds message when subsetting locations table if a gage specified in the user's subset list is absent from the template
  • adds message when subsetting primary_timeseries table if a gage specified in the user's subset list has no observations

@samland1116 samland1116 added this to the v0.6 Release milestone Dec 11, 2025
@samland1116 samland1116 self-assigned this Dec 11, 2025
@samland1116 samland1116 added the enhancement New feature or request label Dec 11, 2025
@samland1116 samland1116 linked an issue Dec 11, 2025 that may be closed by this pull request
@samland1116 samland1116 reopened this Dec 12, 2025
@samland1116 samland1116 reopened this Dec 12, 2025
sdf_in = sdf_in.filter(
sdf_in.location_id.isin(primary_location_ids)
)
# warn user if no timeseries data exists for a gage
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Kind of a nitpick but it seems like this check is redundant to the first check in the locations table? I think our validation ensures that a location id in the primary table has to be in the locations table.

@samlamont samlamont merged commit 35c8944 into main Jan 7, 2026
@samlamont samlamont deleted the 602-update-clone_from_s3-to-warn-about-missing-gages branch January 7, 2026 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update clone_from_s3 to warn about missing gages

2 participants