Re: [gdal-dev] gdalwarp RCP issues between GDAL 2.1.0 and 2.1.3

On vendredi 21 avril 2017 15:58:11 CEST Deschamps, Benjamin (AAFC/AAC) wrote: > Hi, > > I've run into issues using gdalwarp for an RPC ortho. My input GeoTiff file > contains the required information in the RPC metadata domain, and the > command runs fine under the GDAL 2.1.0 command line utility

Re: [gdal-dev] gdalwarp RCP issues between GDAL 2.1.0 and 2.1.3

A bit more information: PROJ4 is 4.8.0 for GDAL 2.1.0; I think GDAL 2.1.3 might be getting the same version, from the system environment variables. Machine has 32GB RAM. Benjamin From: Even Rouault [mailto:even.roua...@spatialys.com] Sent: April-21-17 12:29 PM To: Deschamps, Benjamin (AAFC/AAC

[gdal-dev] gdalwarp RCP issues between GDAL 2.1.0 and 2.1.3

Hi, I've run into issues using gdalwarp for an RPC ortho. My input GeoTiff file contains the required information in the RPC metadata domain, and the command runs fine under the GDAL 2.1.0 command line utility (windows 7, 64-bit): gdalwarp -multi -tap -et 0.0 -r cubic -srcnodata 0 -rpc -overwri

Re: [gdal-dev] 2.2.0beta1 regression NULL values

> > Not a regression as far as I can now see, just a consequence of the > "backward incompatible changes" that will affect many downstream users of > many drivers, I guess. When this was implemented, I didn't foresee a solution that would have kept a clean API while maintaining backward compati

Re: [gdal-dev] Clarification about ownership of srs passed to GDALDatasetCreateLayer()?

Thanks, Even! On Fri, Apr 21, 2017 at 11:14 AM, Even Rouault wrote: > On vendredi 21 avril 2017 10:57:16 CEST Sean Gillies wrote: > > > Hi all, > > > > > > I've written some C code (in one of Fiona's extension modules) that > > > > > > 1. sets a OGRSpatialReferenceH using OSRSetFromUserInput() >

Re: [gdal-dev] 2.2.0beta1 regression NULL values

Hi Even, On Fri, 21 Apr 2017, Even Rouault wrote: Hi Roger, See https://github.com/edzer/sfr/issues/309 - < 2.2.0 we could write "missing values" in vector drivers and read them back. In 2.2.0beta1, we see REAL "missing values" written out OK, but read back as numeric zero. Did you check th

Re: [gdal-dev] Clarification about ownership of srs passed to GDALDatasetCreateLayer()?

On vendredi 21 avril 2017 10:57:16 CEST Sean Gillies wrote: > Hi all, > > I've written some C code (in one of Fiona's extension modules) that > > 1. sets a OGRSpatialReferenceH using OSRSetFromUserInput() > 2. passes this OGRSpatialReferenceH to GDALDatasetCreateLayer() > 3. frees the OGRSpatialR

[gdal-dev] Clarification about ownership of srs passed to GDALDatasetCreateLayer()?

Hi all, I've written some C code (in one of Fiona's extension modules) that 1. sets a OGRSpatialReferenceH using OSRSetFromUserInput() 2. passes this OGRSpatialReferenceH to GDALDatasetCreateLayer() 3. frees the OGRSpatialReferenceH using OSRDestroySpatialReference() 4. adds feature definitions a

Re: [gdal-dev] 2.2.0beta1 regression NULL values

Hi Roger, > See https://github.com/edzer/sfr/issues/309 - < 2.2.0 we could write > "missing values" in vector drivers and read them back. In 2.2.0beta1, we > see REAL "missing values" written out OK, but read back as numeric zero. Did you check the output with ogrinfo/GDAL 2.2 to verify that they

[gdal-dev] 2.2.0beta1 regression NULL values

See https://github.com/edzer/sfr/issues/309 - < 2.2.0 we could write "missing values" in vector drivers and read them back. In 2.2.0beta1, we see REAL "missing values" written out OK, but read back as numeric zero. We've only checked shapefiles and GPKG so far. Is this RFC 67? Until now, rgdal

Re: [gdal-dev] Google OSS Fuzz

On 21 April 2017 at 02:06, Kurt Schwehr wrote: > The Google security team is interested in having GDAL join the OSS-Fuzz - > Continuous Fuzzing for Open Source Software project: > > https://github.com/google/oss-fuzz > > If folks are interested, I've got a few fuzzers that we can start with that >