Upgraded to gdal 1.10 and still the same problem when writing JP2 files.
It still fails at
oError = CNCSJP2FileView::Open( (m_OStream) );
in ecwcreatecopy.cpp.
I think the problem comes with the way ERDAS library handles m_OStream.
I commented this block just before trying to open the output
I am having problems with easy_install-2.7 gdal
easy_install gdal
Searching for gdal
Reading http://pypi.python.org/simple/gdal/
Reading http://www.gdal.org
Best match: GDAL 1.9.1
Downloading
http://pypi.python.org/packages/source/G/GDAL/GDAL-1.9.1.tar.gz#md5=60cb0e0b652dfb204e150bcb11190248
Hello list
I'm using gdal on android.
I'm having problems reading data from tiff files larger than 2GB.
Smaller files works ok.
Is there a limit in android, or the android GDAL build? Is there some build
flag to make it work?
Thanks
Yehiyam Livneh
Sent from my mobile
Hi
Just a couple of problems:
frmts/msg/msgcommand.cpp:434: error: 'sprintf' was not declared in this
scope
(needed a #include)
--with-rename-internal-libtiff-symbols=yes and
--with-rename-internal-libgeotiff-symbols=yes
.libs/libgdal.so: undefined reference to `TIFFReadEncodedStrip'
(had
Hello list
I'm using gdal on android.
I'm having problems reading data from tiff files larger than 2GB.
Smaller files works ok.
Is there a limit in android, or the android GDAL build? Is there some build
flag to make it work?
Thanks
Yehiyam Livneh
Sent from my mobile
On 06/06/2013 18:54, Andrew Brooks wrote:
Hi
Just a couple of problems:
frmts/msg/msgcommand.cpp:434: error: 'sprintf' was not declared in
this scope
(needed a #include)
--with-rename-internal-libtiff-symbols=yes and
--with-rename-internal-libgeotiff-symbols=yes
.libs/libgdal.so:
Hi Andrew,
Just a couple of problems:
frmts/msg/msgcommand.cpp:434: error: 'sprintf' was not declared in this
scope
(needed a #include)
Perhaps you can provide the patch ? This driver is most likely not compiled on
a regular basis due to its unusual dependencies.
Hi,
As reported in the GML driver page:
when using the GML_SKIP_RESOLVE_ELEMS HUGE method to resolve the GML.
It will produce firstly a file-system based DBMS.
I don't see this dbms file so probably itis removed fter it use.
I'm interest to see its information. So there is a workaround to
On 22.05.2013, at 10:20, Even Rouault wrote:
Le vendredi 17 mai 2013 09:38:31, Hank Finley a écrit :
Hi Tamas,
thanks for the advice, I would still like to continue with my goal, down
the track I'm going to be using this to fuel my OpenGL graphical map. The
SQL API level was far too slow,
hi,
I'm trying to convert a shapefile layer (EPSG:22523) for the same SRS
in a MapInfo TAB file, but despite I try to do it using:
$ ogr2ogr -f MapInfo File -s_srs EPSG:22523 -t_srs EPSG:22523
-a_srs EPSG:22523 /mapinfo_target_folder/ /shp_source_folder
my_layer_1
And despite an orginfo -so
Le jeudi 06 juin 2013 23:14:35, Joaquim Luis a écrit :
Hi,
I'm having this error when building with poppler. It used to build
before but for the doubts I rebuild poppler (from the git repo) but the
error persists.
C:/programs/compa_libs/poppler_GIT\poppler/SplashOutputDev.h(164) :
error
Poppler is one of those libraries during the GDAL build process where I
have to make changes to the GDAL source for the build to succeed. I
believe I change an include path in /frmts/pdf/pdfobject.h to Splash.h -
your error could be related to this.
-jeff
--
Jeff McKenna
MapServer Consulting
I've just tried on Linux with latest poppler git, and GDAL compiles fine. I can
see that SplashThinLineMode is an enumeration defined in
poppler/splash/SplashTypes.h. Perhaps you should check if that exists in it.
Perhaps an installation problem of poppler headers on Windows... ? I can see
that
On 06-06-2013 22:37, Jeff McKenna wrote:
Poppler is one of those libraries during the GDAL build process where I
have to make changes to the GDAL source for the build to succeed. I
believe I change an include path in /frmts/pdf/pdfobject.h to Splash.h -
your error could be related to this.
Hi everyone!
I have a question about using the method OGRLayer::Layer().
Following i show you a protion of code:
/*** */
// Create geometry from wkt
OGRGeometryFactory::createFromWkt(pwkt, pSpatialRef, pgeometry);
/** Configure geom
pCurrentFeature_-SetGeometry(pgeometry);
if
On Thu, Jun 6, 2013 at 3:34 PM, Mauro Pisano
mauropis...@suremptec.com.arwrote:
Hi everyone!
I have a question about using the method OGRLayer::Layer().
Following i show you a protion of code:
/*** */
// Create geometry from wkt
OGRGeometryFactory::createFromWkt(pwkt, pSpatialRef,
Hi,
I have a shapefile in EPSG:2393 but without .prj file and I am getting a bad
result if I convert it into KML format with command:
ogr2ogr -f KML -s_srs epsg:2393 test_2.kml test_region.shp
ERROR 1: Latitude 6785184.157800 is invalid. Valid range is [-90,90]. This
warning will not be issued
Hi,
I received a shapefile with a non-perfect .prj file which does not advertise
that the coordinate system is Finnish KKJ (EPSG:2393) which needs +towgs84
parameters. I knew that GDAL 1.10 finally comes with correct parameters and
thought that problem could be solved easily by adding parameter
Am 07.06.2013 01:26, schrieb Jukka Rahkonen:
The result is good if I add parameter -t_srs epsg:4326. However, this should
be unnecessary with KML because it is always EPSG:4326 and also the driver
manual page http://www.gdal.org/ogr/drv_kml.html claims the same in the text
and in the examples.
Am 07.06.2013 01:42, schrieb Jukka Rahkonen:
Hi,
I received a shapefile with a non-perfect .prj file which does not advertise
that the coordinate system is Finnish KKJ (EPSG:2393) which needs +towgs84
parameters. I knew that GDAL 1.10 finally comes with correct parameters and
thought that
How well does OGRSpatialReference::GetAuthorityCode perform in the wild
when handed a WKT? In particular, if I have satellite imagery from
someplace in the world that was ortho-rectified in a sane manner to a
national or state projection with an conforming WKT, will this function
return an
Thanks Frank.
I have been able to solve the issue. Using your clue, I am reprojecting all
the input images to common projected coordinate system (of the image which
will be at mosaic'c center) and then mosaicing.
--
View this message in context:
Andre Joost andre+joost at nurfuerspam.de writes:
Am 07.06.2013 01:26, schrieb Jukka Rahkonen:
The result is good if I add parameter -t_srs epsg:4326. However, this should
be unnecessary with KML because it is always EPSG:4326 and also the driver
manual page
23 matches
Mail list logo
