Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Craig de Stigter
(Just saw Jonathan's email) That approach to `ids` makes sense to me. Let's try and get the current PR merged and I'll submit that as a followup PR (I have a few other minor changes I want to make too, but have been holding off since the current one is too enormous as-is) On Tue, 11 Dec 2018 at 1

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Craig de Stigter
Thanks for the votes and kind words :) I'd applied Kurt's super-minor wording suggestions but haven't added any new sections (on fiona, extra examples, etc) yet. I'll try and incorporate those changes in the next couple days. Cheers Craig On Tue, 11 Dec 2018 at 11:07 Kurt Schwehr wrote: > To f

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Jonathan Moules
Hi Craig, For my suite I've used pytest_make_parameterize_id to auto-create id's using the first parameterised value as the id name if that parameter is called "_" (just underscore - the Python convention for a throwaway variable). It works really well, although would need some work for backw

Re: [gdal-dev] FlatGeobuf; proposal for a new performance oriented vector file format

2018-12-10 Thread Björn Harrtell
Hi Benjamin, Very interesting to read that you have experimented in similar things and of your positive experiences with flatbuffers. Den mån 10 dec. 2018 kl 18:18 skrev Benjamin Stadin < benjamin.sta...@bridging-it.de>: > Björn, > > Interesting to see there is some progress in this area. We've

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Kurt Schwehr
To follow on to Howard's comment about testing in python... I'm looking forward to the day that GDAL can drop all python 2.x support and testing! And anyone working on C++ testing is welcome to the code here. I'll happily donate it with a license change to GDAL (it's apache 2.0 right now). You

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Even Rouault
On jeudi 6 décembre 2018 11:40:49 CET Craig de Stigter wrote: > Hi > > I appreciate your comments on the pytest proposal and all the support to > help get it this far. Given no actionable improvements have been suggested, > and the feedback thus far seems encouraging... > > I move to adopt RFC 72

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Kurt Schwehr
+1 Kurt Awesome!! It's great to see that my work in https://github.com/schwehr/gdal-autotest2/tree/master/python is obsolete. Some very minor suggestions: - "Support testing under Python 2 & Python 3 (2.7+)" Move the (2.7+) to be with Python 2. - Mention that Fiona and Rasterio also use pytest -

Re: [gdal-dev] FlatGeobuf; proposal for a new performance oriented vector file format

2018-12-10 Thread Björn Harrtell
Thanks Even, answers inlined. Den mån 10 dec. 2018 kl 13:19 skrev Even Rouault : > Björn, > > > In my spare time I've been working on a vector file format called > > FlatGeobuf (tentatively). The main reason, besides curiosity and > learning, > > I'm putting time into it is that I think shapefile

Re: [gdal-dev] Motion: adopt RFC 72: Run tests with pytest

2018-12-10 Thread Howard Butler
+1 I watched the ticket traffic and shuddered :) Thank you. GDAL's testing probably predates five or six Python testing regimes/eras.  I also have the concern about GDAL's testing going through Python, but this RFC will make it much easier for people to contribute and improve the story. Congratu

Re: [gdal-dev] gdalwarp ignoring scale and offset

2018-12-10 Thread Even Rouault
On lundi 10 décembre 2018 20:11:33 CET Erik Heinz wrote: > Hello everyone, > > I like to use geotiff files with UInt16 raster bands and scale/offset > metadata for saving cm-resolution elevation data in an efficient way. > > In principle, this works well with gdal. As of version 2.3.2, however, >

[gdal-dev] gdalwarp ignoring scale and offset

2018-12-10 Thread Erik Heinz
Hello everyone, I like to use geotiff files with UInt16 raster bands and scale/offset metadata for saving cm-resolution elevation data in an efficient way. In principle, this works well with gdal. As of version 2.3.2, however, gdalwarp seems to silently drop the offset and scale values. I'm incl

Re: [gdal-dev] GPKG: int16 with scale

2018-12-10 Thread Idan Miara
Got it, thanks for your quick response! On Mon, 10 Dec 2018 at 16:59, Even Rouault wrote: > On lundi 10 décembre 2018 16:29:09 CET Idan Miara wrote: > > Hi, > > > > I'm trying unsuccessfully to save Int16 dataset with scale != 1.0 in > GPKG. > > > > If I understand correctly the remark about "Ti

Re: [gdal-dev] GPKG: int16 with scale

2018-12-10 Thread Even Rouault
On lundi 10 décembre 2018 16:29:09 CET Idan Miara wrote: > Hi, > > I'm trying unsuccessfully to save Int16 dataset with scale != 1.0 in GPKG. > > If I understand correctly the remark about "Tiled gridded coverage data" > here: > https://www.gdal.org/drv_geopackage_raster.html > I expect offset an

[gdal-dev] GPKG: int16 with scale

2018-12-10 Thread Idan Miara
Hi, I'm trying unsuccessfully to save Int16 dataset with scale != 1.0 in GPKG. If I understand correctly the remark about "Tiled gridded coverage data" here: https://www.gdal.org/drv_geopackage_raster.html I expect offset and scale for Int16 to be supported in gdal. I tried to gdal_translate an

Re: [gdal-dev] FlatGeobuf; proposal for a new performance oriented vector file format

2018-12-10 Thread Even Rouault
Björn, > In my spare time I've been working on a vector file format called > FlatGeobuf (tentatively). The main reason, besides curiosity and learning, > I'm putting time into it is that I think shapefile still rules the > read/query static data performance game, which is kind of sad, and probably