Skip to content

reliance on "now" as end date in geoglows pull can cause failures #2

@mike-gangl

Description

@mike-gangl

recevied the following message when querying geoglows:

Error in py_call_impl(callable, call_args$unnamed, call_args$named) :Error in py_call_impl(callable, call_args$unnamed, call_args$named) :

  | KeyError: Timestamp('2025-12-15 00:00:00') KeyError: Timestamp('2025-12-15 00:00:00')

which i think comes from this being used:

https://github.com/SWOT-Confluence/LakeFlow_Confluence/blob/main/src/geoglows_aws_pull.py#L10

not 100% sure, but this failed the run after about 2 days of running lakeflow input. we can talk about it further. for now, i've got a workaround to continue processing, but it may not contain complete lakes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions