Developer Network NREL NREL Developer Network

India (/api/wind-toolkit/v2/wind/india-wind-download)

Collect and download, as CSV, a configurable set of data fields from a national collection of wind stations. The India Wind Dataset, developed in part through the India Renewable Integration Study, contains simulated windspeed, direction, temperate and pressure values at 40m, 80m, 100m and 120m heights above the ground where available. The spatial resolution of the data is 3 km and the temporal resolution is 5 minutes.

This API is capable of creating very large downloadable archives. Unlike a typical API, the response to this provides a request acknowledgement. The real work of creating the requested downloadable archive will continue to run on the server side. When complete, and email will be sent to the email address provided in the initial request with a link to a file to download. In addition to this two step workflow, there is also an option for users who wish to download a single CSV file in direct response to an API request. The .csv format may be used to download a CSV directly. This feature is restricted to use with only a single POINT, for a single YEAR at a time.

Request URL

GET /api/wind-toolkit/v2/wind/india-wind-download.format?parameters

Request Parameters

Parameter Required Value Description
api_key Yes
Type: string
Default: None

Your developer API key. See API keys for more information.

wkt Yes
Type: well-known text point string
Default: None
A well-known text (WKT) representation of the geometry for which to extract data. May be a point or polygon geometry.
attributes Yes
Type: comma delimited string array
Default: None
Options: pressure_40m, temperature_100m, temperature_120m, temperature_40m, temperature_80m, winddirection_100m, winddirection_120m, winddirection_40m, winddirection_80m, windspeed_100m, windspeed_120m, windspeed_40m, windspeed_80m, pressure_100m
Each specified attribute will be returned as a column in the resultant CSV download.
names Yes
Type: comma delimited integer array
Default: 2014
Options: 2014
The year(s) for which data should be extracted.
interval No
Type: integer
Default: 60
Options: 15, 60
Desired data timestep resolution in minutes.
utc No
Type: true or false
Default: true
Pass true to retrieve data with timestamps in UTC. Pass false to retrieve data with timestamps converted to local time of data point (without daylight savings time).
leap_day No
Type: true or false
Default: false
Pass true to retrieve data including leap day (where appropriate). Pass false to retrieve data excluding leap day.
full_name No
Type: string
Default: None
The full name of the user requesting data.
email Yes
Type: email string
Default: None
An active email for the user requesting data. This email will be used to deliver the extracted data.
affiliation No
Type: string
Default: None
The organization with which the user requesting the data is affiliated.
reason No
Type: string
Default: None
The reason that the user is requesting the data.

Response Fields

The response is composed of service-related informational fields and the results of the data query.

Field Value Description
Type: string array

A list of error messages

Type: Object Hash
Key: Value pairs representing all input parameters
Type: Object Hash
Upon successful completion a message will be returned informing the user that file generation is in progress and an email will be sent to the address provided in the email input field when the download is ready


GET /api/wind-toolkit/v2/wind/india-wind-download.json?wkt=POINT(75.36621%2024.726874)&attributes=pressure_40m%2Ctemperature_100m%2Ctemperature_120m%2Ctemperature_40m%2Ctemperature_80m%2Cwinddirection_100m%2Cwinddirection_120m%2Cwinddirection_40m%2Cwinddirection_80m%2Cwindspeed_100m%2Cwindspeed_120m%2Cwindspeed_40m%2Cwindspeed_80m%2Cpressure_100m&names=2014&full_name=Data%20Lover&
  "errors": [],
  "inputs": {
    "wkt": "POINT(75.36621 24.72687)",
    "attributes": [
    "names": [
    "site_url": "wind-toolkit/wind/india_wind_download.json",
    "full_name": "Data Lover",
    "email": "",
    "affiliation": "NREL",
    "mailing_list": false,
    "reason": "test",
    "leap_day": true,
    "utc": false,
    "interval": "60"
  "outputs": {
    "message": "File generation in progress. An email will be sent to when the download is ready."
GET /api/wind-toolkit/v2/wind/india-wind-download.csv?wkt=POINT(75.36621%2024.726874)&attributes=pressure_40m%2Ctemperature_100m%2Ctemperature_120m%2Ctemperature_40m%2Ctemperature_80m%2Cwinddirection_100m%2Cwinddirection_120m%2Cwinddirection_40m%2Cwinddirection_80m%2Cwindspeed_100m%2Cwindspeed_120m%2Cwindspeed_40m%2Cwindspeed_80m%2Cpressure_100m&names=2014&full_name=Data%20Lover&
Site Timezone,5.5,Elevation,358,Is Offshore,0,WRF Region,0
Year,Month,Day,Hour,Minute,air pressure at 40m (Pa),temperature at 100m (C),temperature at 120m (C),temperature at 40m (C),temperature at 80m (C),wind direction at 100m (deg),wind direction at 120m (deg),wind direction at 40m (deg),wind direction at 80m (deg),wind speed at 100m (m/s),wind speed at 120m (m/s),wind speed at 40m (m/s),wind speed at 80m (m/s),air pressure at 100m (Pa)

Rate Limits

Rate limits for this application are significantly less than the standard rate limits for This decrease in the limit is required as the data provided through this service is significantly more computationally intensive to generate and provide. These rate limits are carefully calculated to allow all users the maximum throughput that our servers can sustain.

There are several levels of rate limiting for this service. The first limit determines how many requests a given user can make per 24 hour period. For requests utilizing the .csv format this rate limit is set at 5000 a day at a frequency of no more than 1 per second. For all other requests this limit is set at 1000 requests per day at a frequency of no more than 1 every 2 seconds.

Secondly each user is limited to 20 in-flight requests at any given time.

In addition, the service has a fail-safe mechanism to prevent significant performance decreases that can be caused by unexpectedly high usage of the service. This limit will cause the service to stop accepting requests when the queue reaches a point where additional requests will significantly lower server performance. When this limit is hit, the service will error with a message describing that the request queue is full.

For some tips and tricks to maximize data downloads please read the guide here.


For questions about the API or the data models please contact


Standard errors may be returned. In addition, the following service-specific errors may be returned:

HTTP Status Code Description
400 Bad Request: When required parameters are missing.
Help Improve this Content