opentopodata: Bounds error for tiled datasets without overlap
With my own server (running the current version 1.4.1 of opentopodata), I see the following problem regarding the EU-DEM dataset:
curl "https://myserver/v1/eudem25m?locations=50.100,8.387"
{
"results": [
{
"elevation": 362.4136962890625,
"location": {
"lat": 50.1,
"lng": 8.387
}
}
],
"status": "OK"
}
curl "https://myserver/v1/eudem25m?locations=50.101,8.387"
{
"error": "Location '50.101,8.387' has latitude outside of raster bounds",
"status": "INVALID_REQUEST"
}
curl "https://myserver/v1/eudem25m?locations=50.102,8.387"
{
"results": [
{
"elevation": 362.61474609375,
"location": {
"lat": 50.102,
"lng": 8.387
}
}
],
"status": "OK"
}
For some reason, the location 50.101,8.387
seems to trigger this bogus error about the latitude being outside of the raster bounds, although it’s clearly inside of the EU-DEM bounds (and for the two neighboring locations everything seems to be fine).
The error occurs every time I query this location on my own server, but interestingly it does not occur with the public server:
curl "https://api.opentopodata.org/v1/eudem25m?locations=50.101,8.387"
{
"results": [
{
"elevation": 360.98956298828125,
"location": {
"lat": 50.101,
"lng": 8.387
}
}
],
"status": "OK"
}
I assume the difference might be due to a slightly different data setup?
And then, independent of this specific problem, I noticed another small issue that occurs when querying two locations at once:
curl "https://myserver/v1/eudem25m?locations=50.101,8.387|50.102,8.387"
{
"error": "Location '50.102,8.387' has latitude outside of raster bounds",
"status": "INVALID_REQUEST"
}
As shown above, the latitude 50.101
is the problematic one, but here the error message mentions the other one (50.102
). This might be an off-by-one issue in the error diagnostics.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- fix the EUDEM instructions to avoid the problems encountered in issue #24 * skip the renaming and instead use a .vrt file * multi-file datasets fail to handle the boundary regions, where the tiles ... — committed to janusw/opentopodata by janusw 4 years ago
- fix the EUDEM instructions to avoid the problems encountered in issue #24 (#25) * skip the renaming and instead use a .vrt file * multi-file datasets fail to handle the boundary regions, where th... — committed to ajnisbet/opentopodata by janusw 4 years ago
Late comment to this thread: By default, the
gdal_merge
script does not handle the NODATA values correctly for the bkg10m dataset. The arguments-n -9999 -a_nodata -9999
are required to achieve this.