Re: [gdal-dev] [EXT] Re: [EXT] Re: [Doc] gdal_calc.py extent option

2022-10-19 Thread Idan Miara
Hi Matt, No, we don't suggest they should be reversed. If you look at the union, you could also make the minimal bounding box bigger and it will still include the union, thus we dedine the union to be the smallest of all bounding boxes that contains that blue figure. Likewise, for the intersecti

Re: [gdal-dev] [EXT] Re: [EXT] Re: [Doc] gdal_calc.py extent option

2022-10-19 Thread Matt . Wilkie
The definitions are correct. For the union you want a rectangle (or polygon) that's larger than the input, indeed. But you want the smallest of those rectangles, because there's an infinity of them. The larger ones would cover an arbitrary area of the plane (or the globe, if you want). Same for

Re: [gdal-dev] OGR SQL dialect on FlatGeoBuf manipulating timestamps

2022-10-19 Thread Trygve Aspenes
OK, so this is a version thing. I upgraded the gdal version and the following sqlite3 version 3.39.3 then unixepoch works(using the SQLITE dialect) ogrinfo -dialect SQLITE -sql "select * from li_flatgeobuf_demo where unixepoch(TimeStamp) between unixepoch('2013-06-20T17:00:29Z') and unixepoch('201

[gdal-dev] Fwd: OGR SQL dialect on FlatGeoBuf manipulating timestamps

2022-10-19 Thread Trygve Aspenes
Hi I have some FlatGeoBuf files I have generated with the python fiona library. This is a lat lon point and a timestamp. So I want to filter by timestamp. What I have come up with is to use gdal sql dialect like this: ogrinfo -sql "select * from flatgeobuf_demo where TimeStamp>='2013-06-20T17:00: