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
Hi Tyler,
'ro' and 'rw' mean what they imply.
The '+' symbol tells that the format supports the Create() method. So, we
can use them to create a dataset from scratch and add metadata explicitly.
Without it, we need a 'template' dataset.
The 'v' means that the format driver supports the virtual s
Not sure how to describe it, but when gdal lists available formats, I see a few
different ways that formats are marked as read, write, etc.
The "rw" and "ro" items are easy enough for me to understand, but what about:
"rov"
"rw+v"
"rwv"
"rw+"
?
Does the "v" refer to support in VRTs perhaps?
Do
Hi everyone,
I am getting a problem, I can't identify custom lines in .Dgn file.
As you know, in Microstation 7, we can assign the style value of lines from
0 to 7.
But if lines are customed lines, they always have the style value is 0. How
can we identify them ?
Please find the attached image
