iotools reference page needs some organization
#2446
Labels
Milestone
Comments
gets my vote |
4 tasks
|
At one point we (or at least I) had the thought that the many iotools functions would no longer be imported into the base iotools namespace and users would need to reference the functions in the specific module. I think modifying the documentation to reflect that would be a good first step. I think given the structure of the subpackage, that's a long way of saying +1 for organizing by data provider. |
|
There was also some talk of separating iotools from pvlib-python. If that happens the iotools documentation would naturally also be restructured. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The page in question: https://pvlib-python.readthedocs.io/en/latest/reference/iotools.html
The main listing has 40-50 functions. Too many! Let's split it up into smaller listings.
The question is, how should it be split? I suggest organizing by data provider, i.e. separate listings for
PVGIS,NSRDB,Solcast, etc.The text was updated successfully, but these errors were encountered: