- Response Formats
- JSON, Texto
- Limited ratio
API of the Spatial Data Infrastructure of Gipuzkoa to obtain topographic profiles with altimetric data.
|coors||Pair of coordinates for a given route, in order to provide its profile. The maximum number of pairs of coordinates is 20; use the comma as the separator among coordinates.||-||Yes|
|srs||Spatial coordinate reference system (SRS), expressed in the EPSG code. If not specified, the system detects it. Supported SRS are EPSG:4326, EPSG:25830, and EPSG:3857.||No, the system detects it||No|
|precision||Accuracy of the request (from 1 to 5). The higher that value, the less accurate it will be, but the response will be faster.||1||No|
|format||Format of the response. It should be: json, xml or php.||json||No|
- 1. Calculation of the topographic profile taking into account the line drawn between three coordinates, in the spatial reference system EPSG:25830
- 2. Calculation of the topographic profile taking into account the line drawn between eight coordinates, in the spatial reference system EPSG:4326
|info||Information about the API: license, metadata, response time, messages, etc.|
|coordinates||Coordinate request received.|
|srs||Spatial reference system in which the calculation was performed.|
|precision||Detail of the request (from 1 to 5), as explained above.|
|elevationProfile||Data to make the topographic profile.|
|distance||Distance in metres for the route of the topographic profile (starting from zero value).|
|height||Altitude of the route of the topographic profile in metres.|
Warning: If there is no altitude data, the altitude value will be represented with the value -9999. In that case, the value of the statuscode parameter will be "1", and you will see this note: "Warning: there are cases out of our range (Gipuzkoa: https://b5m.gipuzkoa.eus) where no height data exists, and the resulting height value is -9999".
Service limit: A maximum of twenty pairs of coordinates will be calculated.