[gdal-dev] Distinguish between no DTED data and actual DTED elevation of 0
Melvin.LEGGE at ca.thalesgroup.com
Wed Jun 26 05:05:36 PDT 2019
So based on your response, a GDalDataSet normally should have valid data all the way to its edges?
From: Even Rouault [mailto:even.rouault at spatialys.com]
Sent: Wednesday, June 26, 2019 7:39 AM
To: gdal-dev at lists.osgeo.org
Cc: LEGGE Melvin
Subject: Re: [gdal-dev] Distinguish between no DTED data and actual DTED elevation of 0
On mardi 25 juin 2019 19:57:11 CEST LEGGE Melvin wrote:
> I am a relative newbie to GIS programming so forgive me if I use the wrong
> terminology or don't state my problem in the most efficient GIS terms.
> Anyway, I have inherited a project written by an actual GIS person who is
> no longer with the company.
> The DTED data consists of 4 GDalDatasets with actual DTED elevation data not
> reaching the boundaries of GDalDatasets - i.e., GDalDatasets are bigger
> than the actual DTED data. Our program reads the elevation data along a
> bearing line from a given point to some requested distance, at regular
> intervals, by repeatedly calling GDALRasterBand->RasterIO for a specified
> distance. What I am seeing is that elevation values of 0 are returned for
> points between the end of the DTED data and the end of the tile.
> Is there any way I can distinguish between the situation above and an actual
> elevation of 0?
No this looks like a "bug" in the data production itself. You could probably
add your own custom logic to detect that situation and fix those 0 on the
edges of the product to nodata (nearblack might be of help for this)
Spatialys - Geospatial professional services
WARNING: This message is intended only for the named recipients. This message may contain information that is confidential. Any dissemination, copying, or use of this message or its contents by anyone other than the named recipient is strictly prohibited. If you are not a named recipient or an employee or agent responsible for delivering this message to a named recipient, please notify the sender immediately, and immediately destroy this message and any copies you may have. WARNING: Email may not be secure unless properly encrypted. It is possible for e-mails to be intercepted or affected by viruses. While we maintain virus checks on all e-mails, we accept no liability for viruses or other material introduced with this message.
More information about the gdal-dev