> Likely threads ought to be enabled by default in GDAL unix/linux builds.
Now done in trunk in r20494
>
> Best regards,
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Dane Springmeyer wrote:
In the Mapnik library we open a GDALDataset per thread, for each feature
query, but have been seeing crashes when rendering large geotiffs.
I've assumed that GDALDataset was fairly threadsafe in recent revisions as
per
(http://trac.osgeo.org/gdal/wiki/FAQMiscellaneous#Ist
I would second configuring GDAL with thread support by default if pthread
library is available, and turn it off only when --without-threads is
explicitely passed.
This would be consistant with how proj.4 works for example.
Le lundi 30 août 2010 18:56:26, Dane Springmeyer a écrit :
> In the Mapn
Volker,
Pardon the late reply I was out of town for a few days.
The libkml driver will read properly formatted schema and extendedData,
but if I recall the kml driver does not produce properly formated schema
so this may not be readable without editing.
Feel free to submit a ticket on the libkml
Chaitanya started looking into it, but after contacting Erdas it turned out
somewhere there was already working on GDAL updates for the new SDK. I am
not sure where that stands now, but I do have a client interested in
having it incorporated so it *should* happen fairly soon.
the website /now s
In the Mapnik library we open a GDALDataset per thread, for each feature query,
but have been seeing crashes when rendering large geotiffs.
I've assumed that GDALDataset was fairly threadsafe in recent revisions as per
(http://trac.osgeo.org/gdal/wiki/FAQMiscellaneous#IstheGDALlibrarythread-safe
Matt,
Donno if you are still working on this problem (I've been on vacation) but
here is one possibility.
If the GIO driver uses ArcObjects, it might need to call this new
"LoadVersion" function before making any other ArcObjects calls. I had a
C++/ATL ArcObjects program that worked fine with 9.x
Hi,
is there a way to have gdal (utilities and library interfaces, notably
python) default to band interleaving instead of pixel interleaving when
writing geotiffs? I know this changed some time ago, but I'd rather have
the old behaviour as many of my scripts are based on delivering max
perf
The recently released 4.1 SDK update now supports an alpha channel for ECW.
This is used to get around the speckle problem.
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-ecw-speckling-in-no-data-area-tp5465609p5477914.html
Sent from the GDAL - Dev mailing li
