>
> 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
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
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
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
