Skip to content

Conversation

@jonbry
Copy link
Member

@jonbry jonbry commented Jan 14, 2026

Issue

Original code read baro time series as America/New_York, which applied the wrong TZ. This caused the baro data to be stored with America/New_York but it was really EST (#30) as well as complications downstream with the downloader app (PWD-MARS/shinyDownloadTools#19)

Resolution

Identified issue and verified in #30 as well as ran test to make sure it was correctly applying the change. Time zone is now being read in as EST, which matches the csv file, then is converted to America/New_York.

I would recommend running a larger test before merging since you will need to delete and reimport baro data from at least when the code was added to the baro file:

5d5b9c0#diff-e6b1cf10e378a1cb72004fddf971df66bc8c7aa71bc7ec632ce2f6e2b887f4e2R165

Closes #30

Time zone is now being read in as EST, which matches the csv file, then is converted to America/New_York

Closes #30
@jonbry jonbry requested a review from monica-water January 14, 2026 19:20
@jonbry jonbry added the bug Something isn't working label Jan 14, 2026
@jonbry jonbry changed the title Updated to read TZ as EST then change New_York Updated to read baro as EST then change to New_York Jan 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Baro Imported with Incorrect Time Zone

3 participants