The main usage of gdalinfo is manual inspection of the image. It was not
intended for use within other scripts. The output is formatted for human
reading.
On Tue, Mar 5, 2013 at 9:00 PM, Caleb Hanger wrote:
> On Tue, Mar 05, 2013 at 01:31:01PM +0530, Chaitanya kumar CH wrote:
> > On Tue, Mar 5,
On Tue, Mar 05, 2013 at 01:31:01PM +0530, Chaitanya kumar CH wrote:
> On Tue, Mar 5, 2013 at 11:53 AM, Caleb Hanger wrote:
> > What do you mean? The histogram is only precomputed if gdalinfo has been
> > run previously and stored a cache of data (the XML file) for later
> > reference; please corr
Caleb,
On Tue, Mar 5, 2013 at 11:53 AM, Caleb Hanger wrote:
> On Tue, Mar 05, 2013 at 11:19:27AM +0530, Chaitanya kumar CH wrote:
>
> > Caleb,
> >
> > gdalinfo uses the GetDefaultHistogram() method which can do this faster
> by
> > fetching a precomputed histogram.
>
> What do you mean? The hi
On Tue, Mar 05, 2013 at 11:19:27AM +0530, Chaitanya kumar CH wrote:
> Caleb,
>
> gdalinfo uses the GetDefaultHistogram() method which can do this faster by
> fetching a precomputed histogram.
What do you mean? The histogram is only precomputed if gdalinfo has been run
previously and stored a c
Caleb,
gdalinfo uses the GetDefaultHistogram() method which can do this faster by
fetching a precomputed histogram.
gdalinfo is a command line program. Even a default histogram of 256 buckets
is hard to visualize in text mode. A much better way is to use a desktop
GIS like qgis to view the histogr
All,
I am writing a script which is calling gdalinfo to get a histogram of pixel
values in an image file. Apparently the mechanism for obtaining a "default"
histogram enables the "bIncludeOutOfRange" flag to dump not-in-range pixels
(including null pixels, in formats that support it) into whic
