Skip to content
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

add example for posting prob fx data #302

Open
wholmgren opened this issue Nov 10, 2020 · 1 comment
Open

add example for posting prob fx data #302

wholmgren opened this issue Nov 10, 2020 · 1 comment

Comments

@wholmgren
Copy link
Member

wholmgren commented Nov 10, 2020

The basic API documentation isn't enough unless you already understand the way the probabilistic forecasts are handled.

I started writing something but not sure where it would live so I'll stop before I waste time...

The key thing is that you submit one forecast file for each percentile or threshold. Because it’s for only a single percentile, the file has the exact same structure as a deterministic forecast. This means that you and I don’t need to agree on the structure of a more complicated csv file – we just have to agree on the API endpoints. This might be more clear if you navigate around the probabilistic forecasts on the dashboard and you note which pages allow you to upload/download.

When using the HTTP API, you’d start by getting the probabilistic forecast group metadata:

https://api.solarforecastarbiter.org/#tag/Probabilistic-Forecasts/paths/~1forecasts~1cdf~1{forecast_id}/get

The metadata will contain a “contant_values” field with links to the endpoints for the individual percentiles/thresholds. Then you can post data to those endpoints:

https://api.solarforecastarbiter.org/#tag/Probabilistic-Forecasts/paths/~1forecasts~1cdf~1single~1{forecast_id}~1values/post

@wholmgren
Copy link
Member Author

Reordering the options within the prob fx menu would also help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant