Introduction
WindBorne is a pip installable library built to interact with Data and Forecasts APIs.
WindBorne uses API keys to authenticate API requests. If an API request is not properly authenticated, it will fail. To get an API key, email data@windbornesystems.com.
In order to authenticate with the api, you must set the following environment variables:
- WB_CLIENT_ID
- WB_API_KEY
Need access?
Email data@windbornesystems.comget_point_forecasts
This function gets the forecast at a given point or set of points. This runs WindBorne's custom point forecasting model, making it more accurate than simple interpolation of the gridded output.
It returns a custom points response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
coordinates | string | A list of coordinates. This may be a list of latitude,longitude tuples, eg [(37, -121), (40.3, -100)] , or a string with coordinates separated by semicolons, eg 37,-121;40.3,-100 |
min_forecast_time | string | Optional. An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the minimum forecast time to calculate point forecasts for. |
max_forecast_time | string | Optional. An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the maximum forecast time to calculate point forecasts for. |
min_forecast_hour | integer | Optional. The minimum forecast hour to calculate point forecasts for. |
max_forecast_hour | integer | Optional. The maximum forecast hour to calculate point forecasts for. |
initialization_time | string | Optional. An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time at which the forecast was made. This looks solely at the date and the hour; minutes and seconds are discarded. If nothing is provided, the latest forecast is used. Available initialization times for point forecasts can be found using get_initialization_times. |
output_file | string | Optional. If provided, the response data will be saved to this file. The file extension determines the format: .csv or .json. |
print_response | boolean | Optional. If true, the response data will be printed to stdout. Default is false. |
get_initialization_times
This function retrieves which initialization times are available in the API for generating point forecasts. It accepts no parameters.
It returns the following:
Name | Type | Description |
---|---|---|
available | [string] | An array of ISO8601 timestamps of available initialization times for point forecasts, ordered from newest to oldest. |
latest | string | The ISO8601 timestamp of latest available initialization time for point forecasts. |
get_full
This command allows getting the full gridded output of global forecasts, including data for all variables at all levels. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_temperature_2m
This function allows getting the gridded output of global 2m temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_wind_u_10m
This function allows getting the gridded output of global 10m u-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_wind_v_10m
This function allows getting the gridded output of global 10m v-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_pressure_msl
This function allows getting the gridded output of global mean sea level pressure forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_500hpa_temperature
This function allows getting the gridded output of global 500hPa temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_850hpa_temperature
This function allows getting the gridded output of global 850hPa temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_500hpa_wind_u
This function allows getting the gridded output of global 500hPa u-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
get_500hpa_wind_v
This function allows getting the gridded output of global 500hPa v-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If there is no forecast available within an hour of the requested time, a 404 status code will be displayed.
It returns a python response object with content being the bytes of the netcdf file. While we typically recommend using the output_file
parameter, this can be used for custom handling of the response.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
output_file | string | Path to save the file. |
historical_temperature_2m
This function allows getting the historical output of global 2m temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_wind_u_10m
This function allows getting the historical output of global 10m u-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_wind_v_10m
This function allows getting the historical output of global 10m v-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_pressure_msl
This function allows getting the historical output of global mean sea level pressure forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_500hpa_temperature
This function allows getting the historical output of global 500hPa temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_850hpa_temperature
This function allows getting the historical output of global 850hPa temperature forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_500hpa_wind_u
This function allows getting the historical output of global 500hPa u-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
historical_500hpa_wind_v
This function allows getting the historical output of global 500hPa v-component of wind forecasts. These outputs are saved as a netCDF (.nc) file.
If the requested forecast is not available, a 404 status code will be displayed.
It accepts the following parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time for which to get the forecast. This looks solely at the date and the hour; minutes and seconds are discarded. |
forecast_hour | integer | How many hours after the run time the forecast is valid at. |
output_file | string | Path to save the file. |
Tropical Cyclones
This endpoint allows getting the predicted ground track of active tropical cyclones.
It accepts the following query string parameters:
Name | Type | Description |
---|---|---|
initialization_time | string | Optional. An ISO 8601 date string, supporting formats YYYYMMDDHH, YYYY-MM-DDTHH, and YYYY-MM-DDTHH:mm:ss., representing the time at which the forecast was made. This looks solely at the date and the hour; minutes and seconds are discarded. If nothing is provided, the latest forecast is used. |
basin | string | Optional. A string indicating the tropical cyclones basins to be filtered in the response. If not set, all tropical cyclones will be included. |
output_file | string | Optional. Path to save the response data. If provided, saves the data in .json, .csv, .gpx, .geojson, .kml, .little_r format. |
The basin parameter defines specific geographical regions where tropical cyclones are present:
Name | Type | Description |
---|---|---|
NA | string | North Atlantic Basin spanning from African Coast (20°E) to 140°W and Equator to 90°N. |
EP | string | Eastern Pacific Basin spanning from 140°W to 180°W and Equator to 90°N. |
WP | string | Western Pacific Basin spanning from 100°E to 180°E and Equator to 60°N. |
NI | string | North Indian Ocean Basin spanning from 45°E to 100°E and Equator to 90°N. |
SI | string | South-West Indian Ocean Basin spanning from 20°E to 90°E and 40°S to Equator. |
AU | string | Australian Region Basin spanning from 90°E to 160°E and 36°S to Equator. |
SP | string | South Pacific Basin spanning from 160°E to 120°W and 40°S to Equator. |
It returns an object (dictionary) with keys being tropical cyclone IDs and values being arrays of ground track points. Each ground track point is of the form:
Name | Type | Description |
---|---|---|
latitude | number | The latitude where the tropical cyclone is predicted to be |
longitude | number | The longitude where the tropical cyclone is predicted to be |
time | string | The ISO8601 timestamp of when this forecast point is valid |