OpenTopography API
GISBox is a one-stop 3D GIS data editing, conversion and publishing platform that supports editing in multiple GIS formats such as OSGB/GEOTIFF/RVT, converting to 3DTiles/Terrain and publishing.
Introduction
OpenTopography API is a RESTful web service interface for developers, through which developers can access global DEM (digital elevation model) datasets hosted by OpenTopography, such as Copernicus GL30, NASA DEM, SRTM, etc. The API is documented using the OpenAPI specification and can be visualized and tested through Swagger. Users need to register through the OpenTopography portal and obtain an API key to authenticate when accessing the API.
File Structure
The OpenTopography API itself does not directly return structured data files in the form of traditional files, but returns data in JSON format through HTTP responses. However, its data organization logic can be explained by analogy with the file structure, mainly including status identification, data body and meta information:
- Status identification: Contains HTTP status code and custom error description. For example, the status code “0” indicates that the request is successful, and other values may indicate parameter errors, insufficient permissions, request frequency restrictions or service unavailable, etc. The error description will further explain the specific reasons, such as “Invalid App Key” (the provided App Key is invalid), “Rate Limit Exceeded” (the request frequency exceeds the limit) or “Service Unavailable” (the service is temporarily unavailable).
- Data body: Contains actual business data. For example, in the product details API, the data body may contain a list of products, each of which contains detailed information such as title, price, image URL, detailed description, etc. In the OpenTopography API, the data body may contain specific information of terrain data, such as coordinates and elevation values of DEM data.
- Meta information: May contain auxiliary data such as timestamps and paging information. This information helps developers understand the data generation time, processing status, and how to perform paging queries.
Pros
- **Rich data: **Provides a variety of global DEM datasets, including high-resolution terrain data, to meet the needs of different users.
- Easy to integrate: API design follows the RESTful principle and supports easy integration into third-party applications through HTTP requests.
- Visualization and testing: Through Swagger, developers can easily visualize the API interface and conduct tests to improve development efficiency.
- **Free use: **For academic users and non-commercial use, OpenTopography API provides free access (with a limit on the number of calls).
Cons
- **Call limit: **Free API keys have a call limit, which may not be enough for users who need to access data frequently.
- **Learning cost: **Although the API is designed to be relatively user-friendly, developers still need to have certain knowledge of HTTP and RESTful API to use the API effectively.
- Data update: Although OpenTopography continues to collect data, some data sets may not be updated in a timely manner, affecting the timeliness of the data.
Application Scenario
The OpenTopography API is suitable for developers who need to integrate high-resolution terrain data into third-party applications, such as geographic information system (GIS) developers, environmental scientists, urban planners, etc. These users can easily obtain terrain data through the API for applications such as terrain analysis, visualization, and simulation.
Example
- OpenTopography API.

Web Coverage Service (WCS)
Web Feature Service(WFS)
Web Map Tile Service (WMTS)
Tile Map Service (TMS)
References
- https://portal.opentopography.org/apidocs/
- https://x.com/OpenTopography/status/1589664346770374656
- https://github.com/knwin/OpenTopography-DEM-Downloader-qgis-plugin/blob/main/README.md