-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add encoding parameter to read_tmy3 #1737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Co-authored-by: Kevin Anderson <kevin.anderso@gmail.com>
…/pvlib-python into expose_encoding_tmy3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @AdamRJensen for the PR and @andylam598 for the bug report!
@kandersolar Setting
While we shouldn't necessarily be able to handle files that are incorrectly formatted (e.g., missing zeros), it seems more robust to use
It seems that it would make sense to also parse the minute part of the time column, just in case some files have an offset - what do @pvlib/pvlib-core think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…/pvlib-python into expose_encoding_tmy3
…mRJensen/pvlib-python into expose_encoding_tmy3" This reverts commit f9c3953, reversing changes made to 8e1f488.
Revert to f638a4d
docs/sphinx/source/reference
for API changes.docs/sphinx/source/whatsnew
for all changes. Includes link to the GitHub Issue with:issue:`num`
or this Pull Request with:pull:`num`
. Includes contributor name and/or GitHub username (link with:ghuser:`user`
).remote-data
) and Milestone are assigned to the Pull Request and linked Issue.Add optional encoding parameter to the
read_tmy3
function.