You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Like the UO SRML network, the NREL network has different instruments at different sites, and sometimes the instruments change.
NREL has a fairly straightforward API for daily data. I don't know if it's useful to try to wrap that in addition to the 1 minute data. It could help determine instrument changes.
Perhaps #605 isn't the PR to do this, but, do we provide the pvlib variable names someplace? We ask users to create a dict mapping MIDC to pvlib names, it would help to point users to the list of available pvlib names.
It might be useful to add a
pvlib.iotools
parser for the NREL MIDC sites, particularly for the 1 minute data from sites that are currently active.I've copied/pasted code similar to this more times than I'd care to admit:
Like the UO SRML network, the NREL network has different instruments at different sites, and sometimes the instruments change.
NREL has a fairly straightforward API for daily data. I don't know if it's useful to try to wrap that in addition to the 1 minute data. It could help determine instrument changes.
There's also a nice site API here: https://midcdmz.nrel.gov/apps/data_api_doc.pl?_idtextlist_
Describe alternatives you've considered
Let users implement their own MIDC parsers as needed.
Additional context
Could be useful for Solar Forecasting 2. cc @cwhanse @lboeman @alorenzo175
The text was updated successfully, but these errors were encountered: