1. APIs & Documentation
2. Climate
3. The Super-Resolution for Renewable Energy Resource Data with Climate Change Impacts (Sup3rCC)
4. Sup3rCC CONUS EC-Earth3-CC SSP245 r1i1p1f1

Sup3rCC CONUS EC-Earth3-CC SSP245 r1i1p1f1 (/api/climate/ncdb/v2/climate/sup3rcc-conus-ecearth3cc-ssp245-r1i1p1f1-v0-2-2-download)

The Super-Resolution for Renewable Energy Resource Data with Climate Change Impacts (Sup3rCC) data is a collection of 4km hourly wind, solar, temperature, humidity, and pressure fields for the contiguous United States under various climate change scenarios. Learn more about the Sup3rCC dataset at the GitHub repository and in this article.

Sup3rCC is downscaled Global Climate Model (GCM) data. The downscaling process was performed using a generative machine learning approach called sup3r: Super-Resolution for Renewable Energy Resource Data. The data includes both historical and future weather years, although the historical years represent the historical climate, not the actual historical weather that we experienced. You cannot use Sup3rCC data to study historical weather events, although other sup3r datasets may be intended for this.

The Sup3rCC data is intended to help researchers study the impact of climate change on energy systems with high levels of wind and solar capacity. Please note that all climate change data is only a representation of the possible future climate and contains significant uncertainty. Analysis of multiple climate change scenarios and multiple climate models can help quantify this uncertainty.

Access to the entire Sup3rCC dataset as a single bulk download is available at The Registry of Open Data on AWS.

Request URL

GET|POST /api/climate/ncdb/v2/climate/sup3rcc-conus-ecearth3cc-ssp245-r1i1p1f1-v0-2-2-download.format?parameters

Request Parameters

NOTE: when using POST to submit a request the api_key must still be included as a query parameter in the url. All other parameters may be included in a POST request as part of the payload.

Response Fields

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

Data File Format

Generated data files are formatted in accordance with the Standard Time Series Data File Format. This file format has been developed to support SAM and other NLR models and is documented fully in this PDF. More information on SAM file formats available on the SAM weather page.

Examples

Examples may not reflect this specific dataset.

JSON Output Format

{
    "inputs": {
        "body": {},
        "params": {
            "0": ".json"
        },
        "query": {
            "email": "user@company.com",
            "wkt": "POINT(-106.19569217545038 42.53470991129683)",
            "names": "2015",
            "interval": "60"
        }
    },
    "metadata": {
        "version": "2.0.0",
        "resultset": {
            "count": 1
        }
    },
    "status": 200,
    "outputs": {
        "message": "File generation in progress. An email will be sent to user@company.com when the download is ready.",
        "downloadUrl": "https://mapfiles.nrel.gov/data/climate/ba0e4954bd72119e4a5d8726055a3180.zip"
    },
    "errors": []
}

CSV Output Format

Direct streaming of CSV data is supported for single location, single year only. The following response example is truncated after the first few rows of data.

Source,Location ID,City,County,State,Country,Offshore,EEZ,Latitude,Longitude,Time Zone,Elevation,Local Time Zone,GHI Units,DNI Units,DHI Units,Temperature Units,Wind Speed Units,Relative Humidity Units,Wind Direction Units,Version
Sup3rCC,711511,-,Natrona,Wyoming,United States,0,1,42.540253,-106.2,0,2246,-7,W/m2,W/m2,W/m2,Celsius,m/s,Percent,Degrees,0.2.2
Year,Month,Day,Hour,Minute,surface air pressure (Pa),DHI,DNI,GHI,relative humidity at 2m (%),air temperature at 2m (Celsius),wind direction at 10m (degrees),wind direction at 100m (degrees),wind direction at 200m (degrees),wind speed at 10m (m/s),wind speed at 100m (m/s),wind speed at 200m (m/s)
2015,1,1,0,0,766.1,0,0,0,77.08,-9.72,215.35,229.77,239.18,5,11.35,13.83
2015,1,1,1,0,766.1,0,0,0,75.32000000000001,-9.870000000000001,214.35,236.73000000000002,244.85,3.12,9.94,14.9
2015,1,1,2,0,766.2,0,0,0,77.66,-9.81,213.43,238.19,245.19,3.66,12.01,17.98
2015,1,1,3,0,766.2,0,0,0,77.60000000000001,-10.13,245.11,246.79,250.4,2.15,9.370000000000001,13.89
...

POST request example in Python

import requests

url = "http://developer.nrel.gov/api/climate/ncdb/v2/climate/sup3rcc-conus-ecearth3cc-ssp245-r1i1p1f1-v0-2-2-download.json?api_key=yourapikeygoeshere"

payload = "email=user@company.com&wkt=POINT%28-106.19569217545038+42.53470991129683%29&names=2015&interval=60"

headers = {
    'content-type': "application/x-www-form-urlencoded",
    'cache-control': "no-cache"
}

response = requests.request("POST", url, data=payload, headers=headers)

print(response.text)

Rate Limits

Rate limits for this application are significantly less than the standard rate limits for developer.nrel.gov. 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 10,000 a day at a frequency of no more than 1 per second. For all other requests this limit is set at 2000 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.

Contact

For questions about the API or the data models please contact ncdb@nlr.gov

Errors

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