-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Organize iotools
reference page by data provider
#2447
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
base: main
Are you sure you want to change the base?
Conversation
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.
Would there be value in listing the sources in alphabetical order within each category?
Co-authored-by: Echedey Luis <[email protected]>
I suggest organizing by topic (Gridded irradiance data, Ground measurement irradiance data, Weather data) and secondary by public/commercial data sources. More importantly, I think we should add a one-line description for each dataset, e.g., CAMSSatellite-derived irradiance data for Europe, Africa, and Asia, and clear-sky irradiance globally. PVGISMultiple gridded irradiance and weather datasets with global coverage. NSRDBSatellite-derived irradiance and weather data for the Americas. |
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.
This is a great improvement! Nice work @kandersolar
I suggest also adding a link to this on the "Weather data" page in the users guide. E.g., "For an overview of available functions, see [reference to this page]" |
Co-authored-by: Adam R. Jensen <[email protected]>
iotools
reference page needs some organization #2446[ ] Tests added[ ] Updates entries indocs/sphinx/source/reference
for API changes.[ ] Adds description and name entries in the appropriate "what's new" file indocs/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`
).[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.remote-data
) and Milestone are assigned to the Pull Request and linked Issue.See #2446. Docs build link: https://pvlib-python--2447.org.readthedocs.build/en/2447/reference/iotools.html