Flexible time zone handling #301
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds time zone conversion capabilities to
L1_normalize.qmd. In other words, we now can process data from sites with catalogers set to different local times, and everything is converted to a single output timezone (by default, "Etc/GMT+5" or EST) in the output.A small data file from a fake site "TZTEST" in a different time zone is included in the
./data_TEST/Raw/to exercise the timestamp-adjustment code in L1_normalize.Raw file:

After L1_normalize processing:

You can see that the TZTEST site's data (in central standard time, per the
L1_metadata_timezones.csvfile) is now in Eastern time.The output time zone information is now written to both the overall README
and site-specific metadata files:
See #298