Sorry, but I have to agree with Alberto - there is actually no way
(that I have found) of listing the currently loaded styles (for a UI
dropdown for example), either with the OGRStyleTable or with the
OGRStyleMgr.
You have to maintain this list yourself.
Plus the OGRStyleTable is not at all
Alberto Pérez Cassinelli pisze:
Hi, I'm getting an OGRStyleTable from an OGRDataSource.
My problem is that I need to access all members of this OGRStyleTable (that
is all style definitions and names) to store them in a data structure of
type string vector,
Alberto,
Why you need to access priva
Hi, I'm getting an OGRStyleTable from an OGRDataSource.
My problem is that I need to access all members of this OGRStyleTable (that
is all style definitions and names) to store them in a data structure of
type string vector, but I don't find any method to do it sequentially (I
can't read one by one
Tim,
I got a bit swamped into the polygonize thing, which is at the heart of
what the GRASS people suggested to me. There's now a polygonize method
in GDAL too (thanks to Frank), with which one can create those
pixel-edged polygons of reclassed rasters. I haven't yet looked into the
smoothing
Try rebuilding jasper as:
export CFLAGS="-fPIC"
./configure --prefix=/usr/local
make; make install
unset CFLAGS
Then rebuild gdal as usual.
On our 64-bit systems we also compile gdal and related libraries (geos,
jasper, etc.) with "-m64" in the compiler flags environment variable
(CFLAGS
I've recently compiled and installed proj 4.6.1, geos 3.0.0, and jasper 1.900.1
without any errors.
gdal configure progresses cleanly:
./configure \
--with-libz=internal \
--enable-largefile \
--with-pcraster=internal \
--with-png=internal \
--with-libtiff=internal \
--with-geotiff=internal \
--
