Expose API to public

[RLiNREL]

Allow user to call API endpoints to fetch results directly without UI

[RLiNREL]

Dmitry comment:
open up API capabilities with some rate limiting to avoid spikes in usages; use David's help for rate limiting (existing gateway). initial endpoints: 1) get avg wind speed across years, 2) if power curve and hub height are provided, provide yearly windspeed and yearly energy production.

[RLiNREL]

API v1 specs:

• windspeed: {{baseURL}}/api/{{version}}/{{model}}/windspeed?&lat=45&lng=-105&height=40&period=annual
• production: {{baseURL}}/api/{{version}}/{{model}}/production?lat=45&lng=-105&height=40&powercurve=nrel-reference-100kW[&period=annual]
• powercurves: {{baseURL}}/api/{{version}}/powercurves
• grid points: {{baseURL}}/api/{{version}}/{{model}}/grid-points/?at=45&lng=-105&limit=4
• info: {{baseURL}}/api/{{version}}/{{model}}/info
• timeseries:{{baseURL}}/api/{{version}}/{{model}}/timeseries/?gridIndex=index&source=s3
  • timeseries/batch: POST {{baseURL}}/api/{{version}}/{{model}}/timeseries/batch/?source=s3, note list of gridIndex in payload

params:

• model=era5, wtk, ensemble (convert path era5/wtk to param model)
• time_period -> period=all, annual, monthly, hourly
• selected_powercurve -> powercurve
• download-csv -> timeseries

response:

• windspeed return json type, averaged windspeed by period
• production return json type, averaged production by period
• powercurves return json type, available power curves
• grid points return json type, a list of nearest grid points to the given coords
• info return json type, a summary of meta data, author, ranges, last updated, etc.
• timeseries return a csv file to a given grid point gridIndex
  • timeseries/batch return zipped csv files, all csv files