[gdal-dev] GDAL 3.0.0 RC1 available

2019-05-02 Thread Even Rouault
Hi, I've issued a release candidate for GDAL 3.0.0. The changes sinces 2.5.0RC1 are: * TileDB: set row-major reads and removed adviseread (fixes #1479) * TileDB: Added support for raster band metadata * TileDB: recreated test array for band re-order (fixes #1490) * gdal_contour: remove explicit

Re: [gdal-dev] Fwd: ogr2ogr

2019-05-02 Thread Jeff McKenna
Hi Mncedi, Welcome to GDAL ! Here is how I recommend working through that (using a working example) : Step 1: ogrinfo Always always start with an ogrinfo command, to see the available layer names: ogrinfo WFS:https://demo.gatewaygeomatics.com/cgi-bin/wfs_gateway

Re: [gdal-dev] Fwd: ogr2ogr

2019-05-02 Thread jratike80
Mncedi Dlayiya wrote > Hello everyone, > > I am new in GDAL so I'm struggling to convert a wfs to shapefile using > ogr2ogr. > > my command is as follows: > > C:\>ogr2ogr -f "ESRI SHAPEFILE" ec_pensioners WFS:" > http://localhost:8080/geoserver/osw?; pensioners Hi, And my command that works

Re: [gdal-dev] Fwd: ogr2ogr

2019-05-02 Thread Even Rouault
On jeudi 2 mai 2019 15:11:03 CEST Mncedi Dlayiya wrote: > Hello everyone, > > I am new in GDAL so I'm struggling to convert a wfs to shapefile using > ogr2ogr. From the error message, it seems there's an extra space between WFS: ad http:// . Try to quote the whole WFS connection string

[gdal-dev] Fwd: ogr2ogr

2019-05-02 Thread Mncedi Dlayiya
Hello everyone, I am new in GDAL so I'm struggling to convert a wfs to shapefile using ogr2ogr. my command is as follows: C:\>ogr2ogr -f "ESRI SHAPEFILE" ec_pensioners WFS:" http://localhost:8080/geoserver/osw?; pensioners - ec_pensioners is the name of the wfs layer - pensioners is the

Re: [gdal-dev] Motion: Promote GDAL 2.5.0 rc1 for release

2019-05-02 Thread Even Rouault
On mercredi 1 mai 2019 16:56:03 CEST Even Rouault wrote: > Hi, > > Motion: GDAL/OGR 2.5.0 rc1 is promoted to be the official 2.5.0 final > release. > Due to the discussion about adopting 3.0 as version number instead, I change my vote to -1 and withdraw this motion. I'll prepare a 3.0.0RC1

Re: [gdal-dev] Should the next version (previously 2.5) be called GDAL 3.0 ?

2019-05-02 Thread Even Rouault
> Is there any other api breaking changes planned if the version does > get bumped to 3.0? Or is it restricted solely to the projection > related api? Well, I was about *releasing* the version, and don't intend to postpone it significantly, so no there won't be any surprise last-minute changes