Hi,
I have been experimenting with the GDAL_HTTP_MULTIRANGE config option added
in gdal-2.3. I have noticed that setting this to YES requires fewer curl
requests, but utilizes a more memory compared to SERIAL. From a very simple
test (details below):
1. gdal-2.2.4:
Maximum resident set s
On vendredi 19 avril 2019 15:36:33 CEST Fengting Chen wrote:
> Removing .libs helped and now pytest is working. Thank you!
>
> Instead of using pytest to run all the tests, how to run individual test?
https://docs.pytest.org/en/latest/ for full reference
And
https://github.com/OSGeo/gdal/blob/ma
On 4/19/19 9:31 PM, Jim Klassen wrote:
> Shouldn't they have different .so major versions?
They do:
* PROJ
4.9.3: SOVERSION 12
5.0.0: SOVERSION 13
5.1.0: SOVERSION 14
6.0.0: SOVERSION 15
* libgeotiff
1.4.3: SOVERSION 2
1.5.0: SOVERSION 5
* libgdal
2.4.0: SOVERSION 20
Removing .libs helped and now pytest is working. Thank you!
Instead of using pytest to run all the tests, how to run individual test?
On 4/18/2019 3:00 PM, Even Rouault wrote:
Not sure how you find out I used libtool build. In my configure option,
I did specify "--without-libtool".
/scratch/gd
On vendredi 19 avril 2019 14:31:17 CEST Jim Klassen wrote:
> On 4/19/19 9:52 AM, Even Rouault wrote:
> > On vendredi 19 avril 2019 07:42:31 CEST Simon Eves wrote:
> >> Does this mean there won’t be a 2.4.2?
> >
> > I'll issuing a few extra 2.4.x maintenance bugfix releases this year, but
> > this
On 4/19/19 9:52 AM, Even Rouault wrote:
On vendredi 19 avril 2019 07:42:31 CEST Simon Eves wrote:
Does this mean there won’t be a 2.4.2?
I'll issuing a few extra 2.4.x maintenance bugfix releases this year, but this
is a courtesy that will eventually stop.
People needing longer support, and p
Good to know why this syntax works. It brings back fond memories of using MS
Access 😊
-Original Message-
From: Even Rouault
Sent: Friday, April 19, 2019 10:42 AM
To: gdal-dev@lists.osgeo.org
Cc: Moskovitz, Bob@DOC ; John Baumgartner
Subject: Re: [gdal-dev] OGR SQL on CSV file with fi
On vendredi 19 avril 2019 16:05:14 CEST Moskovitz, Bob@DOC wrote:
> Thanks John, it worked perfectly!
oh, indeed. Turns out SQLite is rather permissive in that area:
https://www.sqlite.org/lang_keywords.html
(that said, OGR SQL only accepts double quotes when identifier quoting is
needed)
--
Sp
Thanks John, it worked perfectly!
From: John Baumgartner
Sent: Thursday, April 18, 2019 9:52 PM
To: Moskovitz, Bob@DOC
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] OGR SQL on CSV file with field name with parentheses?
Try surrounding the field name with square brackets:
ogrinfo -al "Da
On 4/19/19 4:22 PM, Sebastiaan Couwenberg wrote:
> The biggest concerns are cartopy, R sf & lwgeom, SAGA, and VTK. I've
> seen no progress for the R packages, nor anything tangible for VTK
> (although it can be built with its embedded copy of libproj4 3.2).
Thanks - the R packages sf, lwgeom and
On vendredi 19 avril 2019 07:42:31 CEST Simon Eves wrote:
> Does this mean there won’t be a 2.4.2?
I'll issuing a few extra 2.4.x maintenance bugfix releases this year, but this
is a courtesy that will eventually stop.
People needing longer support, and potentially backport of features in the 2.
On 4/19/19 4:40 PM, Greg Troxel wrote:
> I was just trying to point out that the 6-only status
> of 2.5.0 is likely going to lead to quite delayed adoption in packaging
> systems.
Can you share an overview of the PROJ 6 status in NetBSD?
Since NetBSD doesn't have most of the problematic packages
Even Rouault writes:
>> I would expect then that packaging systems will hold off on this,
>> because I don't think we've reached the point that the collateral damage
>> of upgrading proj to 6 is ok.
>
> Packaging systems with an experimental staging area should be able to package
> it hopefully,
Greg,
> I would expect then that packaging systems will hold off on this,
> because I don't think we've reached the point that the collateral damage
> of upgrading proj to 6 is ok.
Packaging systems with an experimental staging area should be able to package
it hopefully, and add it to the other
On 4/19/19 4:08 PM, Greg Troxel wrote:
> Even Rouault writes:
>> GDAL 2.5.0 *requires* PROJ >= 6.0, and if using external libgeotiff,
>
> I would expect then that packaging systems will hold off on this,
> because I don't think we've reached the point that the collateral damage
> of upgrading pr
Even Rouault writes:
> GDAL 2.5.0 *requires* PROJ >= 6.0, and if using external libgeotiff,
I would expect then that packaging systems will hold off on this,
because I don't think we've reached the point that the collateral damage
of upgrading proj to 6 is ok.
With any luck I'm wrong and most
Hi,
I have prepared the GDAL/OGR 2.5.0 Beta 1 release. It will hopefully directly
followed by a RC1 next week if things go well.
GDAL 2.5.0 *requires* PROJ >= 6.0, and if using external libgeotiff,
libgeotiff >= 1.5.0
In case you didn't follow recent developments, a revamp has been done in th
On vendredi 19 avril 2019 14:52:13 CEST John Baumgartner wrote:
> Try surrounding the field name with square brackets:
>
> ogrinfo -al "Data_directory" -dialect sqlite -sql "SELECT [Vs30(m/s)] as
> Vs30 FROM file1"
Brackets won't work with OGR SQL or SQLite. You must use double quotes
On a Bash
18 matches
Mail list logo
