[gdal-dev] Naive warping question

In other words, they are *not* complete coverage of the area covered in the original tiffs. This is unexpected to me.. Is this expected results? How can I be sure to get complete coverage in the resulting set of re-projected tiffs? thanks -Brian == Brian Hamlin planetwork.net OSGeo California

Re: [gdal-dev] fail gdal autotest rev-17474

On Jul 28, 2009, at 8:44 PM, Frank Warmerdam wrote: Brian Hamlin wrote: its SegFaulting atgcore/mask.py mask_5 http://paste.debian.net/42924/ Brian, I'm not seeing that problem here. This this just happen to you recently after things were working? Are you using an external s

[gdal-dev] fail gdal autotest rev-17474

its SegFaulting atgcore/mask.py mask_5 http://paste.debian.net/42924/ == Brian Hamlin ISDE5 Steering Committee Planetwork.net OSGeo California Chapter ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo

Re: [gdal-dev] SQL "LEFT JOIN"

cess) but, unfortunately, the Jet driver has an 8.3 filename limitation ... so it creates other problems and additional work. OGR2OGR has proved very powerful for many other tasks.  If I can get to also do DBF joins, I can perform all of necessary shapefile operations in one step. Thanks, Kr

Re: [gdal-dev] SQL "LEFT JOIN"

On Jul 12, 2009, at 4:56 PM, Kris R. DeLaney wrote: Re:  GDAL 1.6.0, released 2008/11/26   I have be unable to use OGR2OGR to accomplish an SQL LEFT JOIN of a shapefile with the attributes of a master dbf table.  If my syntax is not correct, I hope someone can show me where it is wrong.   The

Re: [gdal-dev] query on OGR and Database

Sukesh- there are several options for connecting to databases in OGR. Many of these are illustrated in a set of python test scripts. You can browse those test scripts via http://trac.osgeo.org/gdal/browser/trunk/autotest best regards -Brian == OSGeo California Chapter On Jul 2, 200

Re: [gdal-dev] Simple OGR C API call

It seems the source of my trouble was the connection string The Postgres driver is creating layers just fine, just not whole databases.. now wrangling with append options and data format and such I'll post the example once its worked out -Brian On Apr 1, 2009, at 7:25 AM, Brian Hamlin

[gdal-dev] Simple OGR C API call

Suppose a layer is created with the memory driver. How do you write that layer to a Postgres database? (OGR_Dr_CopyDataSource() appears *not* to be the answer - it implicitly creates the new layer, and Postgres driver doesnt support create.. ) thanks -Brian == Brian Hamlin ISDE5 Steering