RE: [gdal-dev] WFS - OGRLayer GetNextFeature - fails

2012-05-13 Thread Odd Ragnar Lydersen
Yes, the server is accessible to the outside world. But first I must say, that we have modified our server to send the correct gml document. The problem was that the server only got the < text/xml > part specified by the OutputFormat parameter, and not the < subtype=gml/3.1.1 > part, so our serve

Re: [gdal-dev] Re: TiffAppendToStrip errors with uncompressed output [SOLVED]

2012-05-13 Thread Rahkonen Jukka
Even Rouault wrote: >> - In case of uncompressed tiff output, make driver to test beforehand if >> there is enough disk space for the target image > I'm not aware of a portable way of doing that (I haven't searched a lot > though). For the record, I've tried the following trick : seek to the offs

Re: [gdal-dev] WFS - OGRLayer GetNextFeature - fails

2012-05-13 Thread Even Rouault
Le jeudi 10 mai 2012 13:21:10, Odd Ragnar Lydersen a écrit : > When I call myLayer->GetNextFeature(), I get an exception that tells me the > format in request is not supported. Is this a server accessible from the outside so I can give a try ? ___ gdal-d

Re: [gdal-dev] Re: TiffAppendToStrip errors with uncompressed output [SOLVED]

2012-05-13 Thread Even Rouault
Le mercredi 09 mai 2012 12:13:06, Jukka Rahkonen a écrit : > Ahem, > > It seems to be so that compression makes resulting tiff files smaller. In > some cases they can then fit to almost full disk even there is not enough > room for an uncompressed version. > > An explanation for why I did not no

Re: [gdal-dev] writing a subregion with GDALRasterIO

2012-05-13 Thread Even Rouault
Le mardi 08 mai 2012 15:52:11, Joaquim Luis a écrit : > Hi, > > I am having some troubles in writing a sub-region on an array with > GDALRasterIO. > > The story is this. GMT internal grid arrays have a padding of 2 rows and > 2 columns around the 'true data region' that is used for boundary > con

Re: [gdal-dev] Force bounding box test for spatial filter in OGR

2012-05-13 Thread Martin Dobias
Hi Frank On Fri, May 11, 2012 at 10:47 PM, Frank Warmerdam wrote: > It occurs to me it would be a huge win in some cases to > extend that so if none of the segments could possible > intersect the envelope then we can be sure there is > no intersection and return FALSE without any use of > GEOS.