CHECKWIND.API SUPPORT

How do I use CHECKWIND.API?

The CHECKWIND.API sandbox contains the list of available design APIs as both GET and POST requests. You must include your Revolutio API key in the request string (for GET requests) or the header (for POST requests) for the request to be successful.

How is CHECKWIND.API licenced?

CHECKWIND.API is licenced via monthly and yearly subscriptions. You pay for a specific number of request credits per month which are used each time to make a request. Only successful requests are counted towards your usage quota.

What elevation data do you source?

The availability of specific, accurate, and portable topographic data is an extremely complex issue. We have to attempted to simplify matters by referencing multiple datasets and also providing users with alternative options to best serve their needs.

When Google API key is not included in the request, CHECKWIND.API samples multiple high resolution topography datasets based on the site coordinates to find the best available data for that location. This is the recommended option for vast majority of users.

  1. Australia: 5 m DEM > 30 m SRTM
  2. New Zealand: 1 m DEM > 8 m DEM > 30 m SRTM
  3. United States: 10 m NED > 30 m SRTM
  4. Canada: 1 m HRDEM > 30 m SRTM
  5. Rest of the World: 30 m SRTM

When a Google API key is included in the request, CHECKWIND.API uses Google’s Elevation API.

What are the requirements for the Google API key?

After creating a Google API key (it’s free), you must enable the Maps Elevation API and Geocoding API within the Google Cloud Console API Library.

You must ensure billing is enabled within your Google Cloud Console account. Each account gets 40,000 free requests per month (that’s a lot). Only users exceeding that will be billed as per Google’s pricing, however a payment method must still be on file to make requests.

How do I know if I have correctly enabled APIs within Google Cloud Console?

Enabled APIs will be listed at the bottom of the Google Cloud Console API Dashboard along with the current request totals. If you do not see the relevant API listed here, then it has not been enabled.

You can check that API key has not been restricted by clicking Credentials > [API Key Name]. If you do wish to restrict the API key, make sure that the Geocoding API and Maps Elevation API are selected.

Why is the terrain/exposure category detection not always totally accurate?

We’re dependent on the quality of Google Maps data for terrain/exposure category detection. Most new structures are built in or near urban areas where map data tends to be more accurate, and for this reason the detection algorithm is catered towards getting the best possible answers for urban sites.

Regional sites may have less refined map data, leading the detection algorithm to provide less accurate results. However, their isolation usually makes determining the terrain/exposure category straightforward by simply reviewing the satellite imagery.

My request is taking too long to complete or is returning an error.

Requests for very tall structures such as towers exceeding 50 m can take over 60 seconds to complete. Please make sure you set the timeout of your request to maximum of 230 seconds so the connection does not close before the request completes.

If you are still having trouble, you can make the request without the height (h) parameter, which will ignore terrain, shielding and exposure detection and focus solely on wind speed and topography. As such a request is independent of height, it should return within 5 seconds.