Hi,
What is the detailed error message you get?
Could you provide some test data to reproduce this problem?
Have you tried with ogr2ogr to convert this data source from shapefile to
postgis?
Best regards,
Tamas
2010/12/27 Edi.Karadumi
>
> Hi everyone,
> im a new user to ogr and i have used
> I'm trying to add support for NGA HRE data to our applications using
> GDAL 1.7.3 NITF driver. Sample files 1-4 at
> http://www.gwg.nga.mil/ntb/baseline/docs/HRE_spec/index.html are
> referenced to UTM zone 11 and appear to be inverted north to south.
> NITF imagery I have that is also reference
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 swig/python and build the buindings from
Oops, wrong conclusion. Seems more complicated than I thought, as there
are some python checks in configure that use python...
Lets change this into a question:
as I have both python2 and python3, with /usr/bin/python linking to
python3 (so python3 is the default), and gdal's python extension
Hi,
some time ago, Arch linux made the rather bold decision to have python3
as system python default, of course with a /usr/bin/python2 alternative
sitting next to it. However, as the /usr/bin/python link is pointing to
/usr/bin/python3, gdal's swig python module's setup.py is being called
wi
