On 12/30/2010 12:53 PM, Norman Vine wrote:
The Ossim utility ossim-icp has a --res-level option that will extract
an overview level from a file
something similar might be a useful addition to gdal functionality
Norman,
I haven't followed this discussion closely, but I did want to note that
the
On 12/30/2010 12:53 PM, Norman Vine wrote:
On Dec 30, 2010, at 6:18 AM, Vincent Schut wrote:
On 12/30/2010 12:07 PM, Even Rouault wrote:
Le jeudi 30 décembre 2010 11:52:34, Vincent Schut a écrit :
Hi all,
Kind of a corner case, but i was hoping that gdal_translate's -expand
option (to expan
On Dec 30, 2010, at 6:18 AM, Vincent Schut wrote:
> On 12/30/2010 12:07 PM, Even Rouault wrote:
>> Le jeudi 30 décembre 2010 11:52:34, Vincent Schut a écrit :
>>> Hi all,
>>>
>>> Kind of a corner case, but i was hoping that gdal_translate's -expand
>>> option (to expand colorindexed 1-band files
On 12/30/2010 12:07 PM, Even Rouault wrote:
Le jeudi 30 décembre 2010 11:52:34, Vincent Schut a écrit :
Hi all,
Kind of a corner case, but i was hoping that gdal_translate's -expand
option (to expand colorindexed 1-band files into 3-band rgb files) would
also copy and expand the overviews when
Le jeudi 30 décembre 2010 11:52:34, Vincent Schut a écrit :
> Hi all,
>
> Kind of a corner case, but i was hoping that gdal_translate's -expand
> option (to expand colorindexed 1-band files into 3-band rgb files) would
> also copy and expand the overviews when run with the (geotiff specific,
> I k
On 12/30/2010 11:39 AM, Even Rouault wrote:
I guess my question actually boils down to: how can I specify in the
configure phase, which python to use for the bindings? E.g. I have both
2 and 3 on my system, and 3 is the default, but I want gdal to build and
install the bindings for 2. Could I s
Hi all,
Kind of a corner case, but i was hoping that gdal_translate's -expand
option (to expand colorindexed 1-band files into 3-band rgb files) would
also copy and expand the overviews when run with the (geotiff specific,
I know) create option "-co COPY_SRC_OVERVIEWS=YES". It appears to not d
> I guess my question actually boils down to: how can I specify in the
> configure phase, which python to use for the bindings? E.g. I have both
> 2 and 3 on my system, and 3 is the default, but I want gdal to build and
> install the bindings for 2. Could I specify
> --with-python=/usr/bin/python2
On 12/29/2010 06:06 PM, Even Rouault wrote:
Vincent,
you didn't mention which GDAL version you use. Since GDAL 1.7.0, the Python
bindings work with both python 2.X and 3.X. But I see that the autoconf check
for python isn't python3 ready indeed. So you can ignore the configure errors
and just cd
i have resolved the problem. I had a constrain in postgre to check if the
geometry was multipolygon now i added (or polygon) check and the import
works fine.
Best Regards
Edi Karadumi
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/C-Binding-ForceToMultiPolygon-tp5869504
10 matches
Mail list logo
