On 10/7/21 1:46 PM, Rahkonen Jukka (MML) wrote:
> Hi,
>
> If you are asking the same question in gis.stackexchange please wait some
> minutes if somebody happens to answer you before sending mail to gdal-dev. Or
> vise versa. Crossposting in the long run will not help you to get answers
> faste
Mohammed
Aljezawi
Lähetetty: torstai 7. lokakuuta 2021 13.22
Vastaanottaja: gdal-dev@lists.osgeo.org
Aihe: [gdal-dev] WFS driver
Hi,
I am using gdal to convert from WFS to geopackge, everything is working fine
but I need to change the name of each table before or after converting to
GeoPackage, because
Hi,
I am using gdal to convert from WFS to geopackge, everything is
working fine but I need to change the name of each table before or after
converting to GeoPackage, because the layer name has a special charachart
that in my application it's not working.
Thank you
On mardi 7 mars 2017 09:57:26 CET Rahkonen Jukka (MML) wrote:
> Hi,
>
> What if a WFS server is returning GML that has complex schema, does GDAL
> know to open the response as GML application schema data automatically or
> with some open option? I ask because I can see "succeeds as GML" in the
>
Hi,
What if a WFS server is returning GML that has complex schema, does GDAL know
to open the response as GML application schema data automatically or with some
open option? I ask because I can see "succeeds as GML" in the debug log:
HTTP:
Fetch(https://opaskartta.turku.fi/TeklaOGCWeb/WFS.as
n.roua...@spatialys.com]
Sendt: onsdag 19. oktober 2016 15.55
Til: Odd Ragnar Lydersen
Kopi: gdal-dev@lists.osgeo.org
Emne: Re: SV: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
Le mercredi 19 octobre 2016 15:17:52, Odd Ragnar Lydersen a écrit :
> Now I have come around to test this a bit more.
Le mercredi 19 octobre 2016 15:17:52, Odd Ragnar Lydersen a écrit :
> Now I have come around to test this a bit more.
>
> 1) I tried the same as you did, only for wfs v. 1.1.0
>
> ogrinfo -ro
> "WFS:http://demo.mapserver.org/cgi-bin/wfs?VERSION=1.1.0&MAXFEATURES=1";
> continents -al -spat 0 45
but a
bit awkward and cumbersome.
>Odd-Ragnar<
-Opprinnelig melding-
Fra: Even Rouault [mailto:even.roua...@spatialys.com]
Sendt: torsdag 29. september 2016 11.20
Til: gdal-dev@lists.osgeo.org
Kopi: Odd Ragnar Lydersen
Emne: Re: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
even.roua...@spatialys.com]
Sendt: torsdag 29. september 2016 11.20
Til: gdal-dev@lists.osgeo.org
Kopi: Odd Ragnar Lydersen
Emne: Re: [gdal-dev] WFS driver bug2 - MAXFEATURES not working
Le jeudi 29 septembre 2016 10:06:12, Odd Ragnar Lydersen a écrit :
> So I have tried to dig a bit more into t
Le jeudi 29 septembre 2016 10:06:12, Odd Ragnar Lydersen a écrit :
> So I have tried to dig a bit more into this, and I have noticed a few
> things.
>
>
> 1) I set MAXFEATURES=60 in the url
>
> 2) I select the layer I want to work with, let's call it MyLayer.
>
> 3) I call SetSpa
ng this in the future, but for now we're just
going to disable the use of MAXFEATURES, and just use, SetSpatialFilterRect(),
to restrain the number of features returned from a layer.
>Odd-Ragnar<
Fra: Odd Ragnar Lydersen [mailto:odd-ragnar.lyder...@powel.no]
Sendt: onsdag 28. s
Le mercredi 28 septembre 2016 14:00:36, Odd Ragnar Lydersen a écrit :
> When I'm using the WFS driver for version 1.0.0, or version 1.1.0 then I
> get some error messages back from GDAL, when the service is password
> protected. I have not tested this for version 2.x.
>
> Here is what I have found
When I use the WFS driver (GDAL 2.1.1) for version 1.0.0 or 1.1.0, and add
MAXFEATURES to the url, then I get zero features retuned, from the service.
If I drop MAXFEATURES in the request-url, then I get all the features in my
bounding box returned from the service.
This is a password protected
When I'm using the WFS driver for version 1.0.0, or version 1.1.0 then I get
some error messages back from GDAL, when the service is password protected.
I have not tested this for version 2.x.
Here is what I have found out:
1) Calls to CPLHTTPFetch() from OGRWFSDataSource::HTTPFetch() is se
Hello, I'm experiencing some warnings in GDAL 2.1 and error messages (HTTP 401)
from the server.
In I'm getting some unwanted results.
However I am able to read features from the server, but I wonder why these
errors occur, and if I'm not getting all the information I should have gotten
if this
Le samedi 07 juin 2014 21:36:21, Stefan Ziegler a écrit :
> Hi Even
>
> Using python:
>
> from osgeo import ogr
>
> driver = ogr.GetDriverByName('WFS')
> wfs = driver.Open("WFS:http://www.catais.org/wfs/mopublic?";)
>
> out = "/home/stefan/Projekte/GeoPackage/test5.gpkg"
> outDriver = ogr.GetDr
Hi Even
Using python:
from osgeo import ogr
driver = ogr.GetDriverByName('WFS')
wfs = driver.Open("WFS:http://www.catais.org/wfs/mopublic?";)
out = "/home/stefan/Projekte/GeoPackage/test5.gpkg"
outDriver = ogr.GetDriverByName("GPKG")
outDataSource = outDriver.CreateDataSource(out)
layer = wfs.
Le samedi 07 juin 2014 20:46:51, Stefan Ziegler a écrit :
> Hi
>
> I have a question regarding client/server sided filtering. According to the
> wfs driver website [1] the driver is able to forward spatial and attribute
> filter to the server. If this is not possible it will client-side only
> fil
Hi
I have a question regarding client/server sided filtering. According to the
wfs driver website [1] the driver is able to forward spatial and attribute
filter to the server. If this is not possible it will client-side only
filtering. When does the driver "decide" wether it filters client or serv
Selon xavier lhomme :
> Hi
> I tried to add to the function SetAttributeFirlter the following filter :
> nam = 'MY#FIRST TEST ON' but it doesn't work.
> then I triedHttpUtility.UrlEncode( ) but it doesn't work too.
>
> If I encode my string like this nam = 'MY%23 FIRST+TEST+ON ' it wor
Hi
I tried to add to the function SetAttributeFirlter the following filter :
nam = 'MY#FIRST TEST ON' but it doesn't work.
then I triedHttpUtility.UrlEncode( ) but it doesn't work too.
If I encode my string like this nam = 'MY%23 FIRST+TEST+ON ' it works;
Could you explain a bit more
Even Rouault wrote:
> Note: yesterday after your emails, I've revised substantially how escaping
> was done in the WFS driver, because there were cases where URL-escaping
> would have been needed (for example if you passed '&' or '%'), so now for
> 'ä', you should see 25-43-33-25-41-34 (but that
Selon Jukka Rahkonen :
> I think this is my last question about WFS and URL-encoding this time.
>
> I had a look how the WFS requests look in hexadecimals.
>
> My TinyOWS and Mapserver WFS both accepts two ways to express letter "ä"
> inside
> ogc:Filter with http GET. First of those alternatives
I think this is my last question about WFS and URL-encoding this time.
I had a look how the WFS requests look in hexadecimals.
My TinyOWS and Mapserver WFS both accepts two ways to express letter "ä" inside
ogc:Filter with http GET. First of those alternatives is an UTF-8 letter "ä" in
URL-encode
Even Rouault wrote:
> Looks a bit complicated. Actually, I'm thinking you could avoid those encoding
> problems with using :
> ogrinfo "WFS:http://188.64.1.61/cgi-bin/tinyows"; -sql --optfile sql.txt
> where sql.txt contains (with a UTF-8 text editor, such as Notepad++ correctly
> configured) :
Le mercredi 15 août 2012 23:14:53, Rahkonen Jukka a écrit :
> Even Rouault wrote:
>
> Le mercredi 15 août 2012 21:28:22, Jukka Rahkonen a écrit :
> >> GvSIG is also sending GetFeatures with http GET and filters and it had
> >> same kind of problems with special characters. Now the developers say
>
Even Rouault wrote:
Le mercredi 15 août 2012 21:28:22, Jukka Rahkonen a écrit :
>> GvSIG is also sending GetFeatures with http GET and filters and it had same
>> kind of problems with special characters. Now the developers say that they
>> have fixed URL encoding. I hope that the solution is som
Le mercredi 15 août 2012 21:28:22, Jukka Rahkonen a écrit :
> GvSIG is also sending GetFeatures with http GET and filters and it had same
> kind of problems with special characters. Now the developers say that they
> have fixed URL encoding. I hope that the solution is somehow re-usable
I'm not su
Jukka Rahkonen mmmtike.fi> writes:
>
> Hi,
>
> It looks like it is not possible to use some special characters in filters
> with
> OGR WFS driver.
GvSIG is also sending GetFeatures with http GET and filters and it had same kind
of problems with special characters. Now the developers say that
Hi,
It looks like it is not possible to use some special characters in filters with
OGR WFS driver.
This command works fine:
http://188.64.1.61/cgi-bin/tinyows -sql "select * from municipalities where
kunta_ni1='Helsinki'"
However, the WFS request fails if I use fore example 'Saarijärvi' as an
a
Le mardi 19 juin 2012 21:41:06, xavier lhomme a écrit :
> From specification
>
> When using the HTTP POST method, the content type for XML encoded WFS
> requests must be set to text/xml. When using the HTTP POST method, the
> content type for KVP encoded WFS requests must be set to
> application/
>From specification
When using the HTTP POST method, the content type for XML encoded WFS
requests must be set to text/xml. When using the HTTP POST method, the
content type for KVP encoded WFS requests must be set to
application/x-www-form-urlencoded and the content of the document must be
equiv
Le mardi 19 juin 2012 17:06:17, xavier lhomme a écrit :
> Hi
> I tried to submit a POST request with the KVP form to an ArcGIS Server 10.0
> but in response I've got an XML Parsing error.
>
> Do I need to translate the KVP form of the url into an XML form ?
Yes, the content you send in a POST is
Hi
I tried to submit a POST request with the KVP form to an ArcGIS Server 10.0
but in response I've got an XML Parsing error.
Do I need to translate the KVP form of the url into an XML form ?
xav
2012/6/12 Even Rouault
> Le mardi 12 juin 2012 14:38:05, xavier lhomme a écrit :
> > Hello
> >
>
Le mardi 12 juin 2012 14:38:05, xavier lhomme a écrit :
> Hello
>
> I'm requesting a WFS source with a very long request. The URI generated by
> the WFS driver is very long (more than 2048). In return I' ve got an HTTP
> error code 414.
> OGRWFSDataSource::HTTPFetch function should be protected
Hello
I'm requesting a WFS source with a very long request. The URI generated by
the WFS driver is very long (more than 2048). In return I' ve got an HTTP
error code 414.
OGRWFSDataSource::HTTPFetch function should be protected against very long
URI and switch between a GET request to a POST req
Selon Jukka Rahkonen :
> Hi,
>
> If user wants to read a summary of a certain WFS feature type with a command
> like
>
> ogrinfo -ro -so WFS:http://server.com/wfs ns:typeName
>
> GDAL seems to send then four separate commands:
>
> First:
> SERVICE=WFS&REQUEST=GetCapabilities&ACCEPTVERSIONS=1.1.0,1
Hi,
If user wants to read a summary of a certain WFS feature type with a command
like
ogrinfo -ro -so WFS:http://server.com/wfs ns:typeName
GDAL seems to send then four separate commands:
First:
SERVICE=WFS&REQUEST=GetCapabilities&ACCEPTVERSIONS=1.1.0,1.0.0
Second:
SERVICE=WFS&VERSION=1.1.0&R
38 matches
Mail list logo
