Re: [gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 11:27:54 CET archgnulinux wrote: > Even Rouault-2 wrote > > > You mention Windows, but your nickname is archgnulinux... So assuming the > > later, the GDAL 2.1.2 package in UbuntuGIS unstable for Xenial is built > > against libkml. > > And I also see that the GDAL packa

Re: [gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread archgnulinux
Even Rouault-2 wrote > You mention Windows, but your nickname is archgnulinux... So assuming the > later, the GDAL 2.1.2 package in UbuntuGIS unstable for Xenial is built > against libkml. > And I also see that the GDAL package in OSGEO4W has the libkml dependency. Unfortunately, I have to use Win

Re: [gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 10:08:01 CET archgnulinux wrote: > Even Rouault-2 wrote > > > From a quick try, I'd say that you must use the "old" KML driver. With the > > LIBKML driver, the > > reported geometry is the last one. > > Thanks, I am using the "old" KML driver. > > I tried to compile L

Re: [gdal-dev] Gdal + Kakadu + Python : unable to write JPEG2000 correctly

2017-02-15 Thread CGA
I just confirmed that gdal_translate works fine : The result image is in effectively in JP2KAK format and readable in QGIS. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Gdal-Kakadu-Python-unable-to-write-JPEG2000-correctly-tp5308040p5308078.html Sent from the GDAL - De

Re: [gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread archgnulinux
Even Rouault-2 wrote > From a quick try, I'd say that you must use the "old" KML driver. With the > LIBKML driver, the > reported geometry is the last one. Thanks, I am using the "old" KML driver. I tried to compile LIBKML for Windows awhile back but had quite a bit of trouble. I'll give it ano

Re: [gdal-dev] problem with HDF format

2017-02-15 Thread Even Rouault
Luca, from a quick skim in the code, the GRINGPOINTLATITUDE / GRINGPOINTLONGITUDE metadata are not used by the HDF4 driver to derive the georeferencing it uses, so it is not unexpected that what gdalinfo reports on the MODIS dataset isn't directly correlated with those. There are several code

Re: [gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 16:21:09 CET Kahly, Philip D. wrote: > Hey all, > > I'm attempting to process some KML files from an outside source and > sometimes a will contain two blocks. > > GDAL will not process these placemarks: layer.GetNextFeature() will return > null, and GetLastErrorMsg()

Re: [gdal-dev] Best vector driver?

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 08:27:06 CET Kurt Schwehr wrote: > Even, > > Thanks for the pointers. I will do touchups on the driver tutorial as I go. > > Maybe more specifically, with the initial setup of the driver and the > datasource: > > I only see two drivers that use GDALDriver. > > grep

Re: [gdal-dev] Best vector driver?

2017-02-15 Thread Kurt Schwehr
Even, Thanks for the pointers. I will do touchups on the driver tutorial as I go. Maybe more specifically, with the initial setup of the driver and the datasource: I only see two drivers that use GDALDriver. grep class */*.{cpp,h} | grep GDALDriver db2/ogr_db2.h:class OGRDB2Driver : public GDA

[gdal-dev] Placemark With Two Geometries Is Not Processed

2017-02-15 Thread Kahly, Philip D.
Hey all, I'm attempting to process some KML files from an outside source and sometimes a will contain two blocks. GDAL will not process these placemarks: layer.GetNextFeature() will return null, and GetLastErrorMsg() returns an empty string. I've attached a sample file "broken.kml", along with

Re: [gdal-dev] Best vector driver?

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 07:19:43 CET Kurt Schwehr wrote: > Hey all, > > What are the top couple vector drivers in terms of being up-to-date w.r.t. > API changes? I'm finally trying to start into adding code and I've got a > couple vector drivers I'd like to write. I've started reading RFC 46

[gdal-dev] Best vector driver?

2017-02-15 Thread Kurt Schwehr
Hey all, What are the top couple vector drivers in terms of being up-to-date w.r.t. API changes? I'm finally trying to start into adding code and I've got a couple vector drivers I'd like to write. I've started reading RFC 46 (GDAL/OGR unification), but I'm trying to figure out the cleanest setu

Re: [gdal-dev] Gdal + Kakadu + Python : unable to write JPEG2000 correctly

2017-02-15 Thread Even Rouault
On mercredi 15 février 2017 07:04:06 CET CGA wrote: > Dear all, > > I'm struggling with the Python bindings of GDAL + Kakadu. I'm trying to clip > a small part of an input image in .jp2 and write it inside another .jp2 > file. > > I read that the JP2KAK images can only be created using the Create

[gdal-dev] Gdal + Kakadu + Python : unable to write JPEG2000 correctly

2017-02-15 Thread CGA
Dear all, I'm struggling with the Python bindings of GDAL + Kakadu. I'm trying to clip a small part of an input image in .jp2 and write it inside another .jp2 file. I read that the JP2KAK images can only be created using the CreateCopy() method. Here is my workflow : - Open input dataset - Cl

[gdal-dev] problem with HDF format

2017-02-15 Thread Luca Delucchi
Hi devs, probably we found a problem with GDAL and HDF format, we are trying to merge several MODIS tiles but we got a wrong "Corner Coordinates" These are our input files gdalinfo MOD11A1.A2012340.h29v05.005.2012342062359.hdf GRINGPOINTLATITUDE.1=39.99583, 39.99583, 30.0041

[gdal-dev] Converting indexed transparent PNG to transparent GeoTIFF

2017-02-15 Thread Tomislav Obad
Hi all, I'm not sure I'm writing to a right address, but I have a rather simple problem, at least a first glance. I'm trying to convert an indexed transparent PNG to transparent GeoTIFF I've tried many different things (using gdal_translate): - convert indexed PNG to rgba PNG with external tool (