subject:"\[mapserver\-users\] WFS Client..."

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-06-08 Thread Lars Fricke via mapserver-users

t).
  
  Thanks for looking into this.


  
  SkenData Email Signatur
   
  

Am 28.05.21 um 13:55 schrieb
  Even Rouault:


  
  oops, sorry, didn't notice 😅
  Le 28/05/2021 à 13:52, Lars
Fricke a écrit :
  
  

I put in the
  files as attach. Is that filtered? 

  
  SkenData Email Signatur
   
  

Am 28.05.21 um 13:43
  schrieb Even Rouault:


  
  Please include your mapfile and the
wfs-request-testlayer.xml file to reproduce. I'm
confused by the mapfile you posted yesterday that
uses epsg:25832 and the fact that GDAL through
mapserver would issue a GetFeature in EPSG:3857 as
suggested below. I can't see how that could happen
(given the MapServer/GDAL integration, GDAL should
always request in the native SRS of the layer and
MapServer will do the reprojection to the SRSNAME of
the WFS request)
  
  But as Daniel suggested using the CONNECTION WFS is
probably a better way of doing what you want
  
  Le 28/05/2021 à 13:13,
Lars Fricke via mapserver-users a écrit :
  
  
So here is the working not working setup.
Unfortunately the working OGR WFS client layers are
all private so I can not share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified
manually with QGIS).

This call doesn't work as described before as BBOX
is not transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but
works anyhow)

I hope you can find out what is going wrong. Thanks
so much for looking into this!

Best

Lars

  SkenData Email Signatur
  
  
   
  

Am 27.05.21 um 18:28
  schrieb Rahkonen Jukka (MML):


  
  SkenData Email Signatur
  
Hi,
 
Have you
already tried to use WFS connection instead
of OGR connection?
 
 
-Jukka Rahkonen-
 

  
Lähettäjä:
  mapserver-users 
  Puolesta Lars Fricke
      Lähetetty: torstai 27. toukokuuta
  2021 14.59
  Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS
  Client returns data at random with very
  same call

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-06-08 Thread Even Rouault via mapserver-users

Data is delivered in the correct srs (verified manually with QGIS).

This call doesn't work as described before as BBOX is not 
transmitted to external server:

http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for 
looking into this!


Best

Lars
SkenData Email Signatur


Am 27.05.21 um 18:28 schrieb Rahkonen Jukka (MML):

SkenData Email Signatur

Hi,

Have you already tried to use WFS connection instead of OGR 
connection?


-Jukka Rahkonen-

*Lähettäjä:* mapserver-users 
 *Puolesta *Lars Fricke

*Lähetetty:* torstai 27. toukokuuta 2021 14.59
*Vastaanottaja:* mapserver-users@lists.osgeo.org
*Aihe:* Re: [mapserver-users] WFS Client returns data at random 
with very same call


Dear all,
I apologize for finding and posting bits and pieces not all at 
one time.

I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
"""

HTTP: 
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop 
<http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop>)

"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:...
"""
with BBOX.
No wonder I do not get reliable results if the server is 
calling some 1000 whatsoever result objects and starts 
filtering the bbox after.


Any idea what is happening? Or is this something for a GDAL thread?

Best
Lars




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

--
http://www.spatialys.com
My software is free, but my time generally not.



--
http://www.spatialys.com
My software is free, but my time generally not.



--
http://www.spatialys.com
My software is free, but my time generally not.



--
http://www.spatialys.com
My software is free, but my time generally not.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-06-08 Thread Lars Fricke via mapserver-users

robably a better way of doing what you want
  
  Le 28/05/2021 à 13:13, Lars
Fricke via mapserver-users a écrit :
  
  
So here is the working not working setup. Unfortunately
the working OGR WFS client layers are all private so I
can not share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually
with QGIS).

This call doesn't work as described before as BBOX is
not transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works
anyhow)

I hope you can find out what is going wrong. Thanks so
much for looking into this!

Best

Lars

  SkenData Email Signatur
  
  
   
  

Am 27.05.21 um 18:28
  schrieb Rahkonen Jukka (MML):


  
  SkenData Email Signatur
  
Hi,
 
Have you
already tried to use WFS connection instead of
OGR connection?
 
 
-Jukka Rahkonen-
 

  
Lähettäjä:
  mapserver-users 
          Puolesta Lars Fricke
  Lähetetty: torstai 27. toukokuuta 2021
  14.59
  Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client
  returns data at random with very same call
  

 
Dear all, 
  I apologize for finding and posting bits and
  pieces not all at one time. 
  I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I
  see, that 
  """

  
HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
  """
  So there is no BBOX. On other layers I see
  """
  GDALOpen(/vsicurl_streaming/https:... 
  """
  with BBOX. 
  No wonder I do not get reliable results if the
  server is calling some 1000 whatsoever result
  objects and starts filtering the bbox after. 
  
  Any idea what is happening? Or is this
  something for a GDAL thread?
  
  Best
  Lars
  
  
 
  

  




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

  
  -- 
http://www.spatialys.com
My software is free, but my time generally not.


  
  -- 
http://www.spatialys.com
My software is free, but my time generally not.


  
  -- 
http://www.spatialys.com
My software is free, but my time generally not.


  

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-31 Thread Lars Fricke via mapserver-users

issue a GetFeature in EPSG:3857 as suggested
below. I can't see how that could happen (given the
MapServer/GDAL integration, GDAL should always request
in the native SRS of the layer and MapServer will do the
reprojection to the SRSNAME of the WFS request)
  
  But as Daniel suggested using the CONNECTION WFS is
probably a better way of doing what you want
  
  Le 28/05/2021 à 13:13, Lars
Fricke via mapserver-users a écrit :
  
  
So here is the working not working setup. Unfortunately
the working OGR WFS client layers are all private so I
can not share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually
with QGIS).

This call doesn't work as described before as BBOX is
not transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works
anyhow)

I hope you can find out what is going wrong. Thanks so
much for looking into this!

Best

Lars

  SkenData Email Signatur
  
  
   
  

Am 27.05.21 um 18:28
  schrieb Rahkonen Jukka (MML):


  
  SkenData Email Signatur
  
Hi,
 
            Have you
already tried to use WFS connection instead of
OGR connection?
 
 
-Jukka Rahkonen-
 

  
Lähettäjä:
  mapserver-users 
  Puolesta Lars Fricke
  Lähetetty: torstai 27. toukokuuta 2021
  14.59
  Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client
  returns data at random with very same call
  

 
Dear all, 
  I apologize for finding and posting bits and
  pieces not all at one time. 
  I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I
  see, that 
  """

  
HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
  """
  So there is no BBOX. On other layers I see
  """
  GDALOpen(/vsicurl_streaming/https:... 
  """
  with BBOX. 
  No wonder I do not get reliable results if the
  server is calling some 1000 whatsoever result
  objects and starts filtering the bbox after. 
  
  Any idea what is happening? Or is this
  something for a GDAL thread?
  
  Best
  Lars

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Even Rouault via mapserver-users


Lars,

I believe the service you request doesn't implement WFS 1.1 properly.

Trying this

./mapserv 
QUERY_STRING="map=wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer" 



I see that GDAL does:

VSICURL: Start download for 
http://sg.geodatenzentrum.de/wfs_info?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=500&REQUEST=GetFeature&TYPENAME=info:dop&FILTER=%3CFilter%20xmlns%3D%22http:%2F%2Fwww.opengis.net%2Fogc%22%20xmlns:gml%3D%22http:%2F%2Fwww.opengis.net%2Fgml%22%3E%3CBBOX%3E%3CPropertyName%3Egeom%3C%2FPropertyName%3E%3Cgml:Box%3E%3Cgml:coordinates%3E362792.2015953020309098,5459899.7109905285760760%20363491.4383923375280574,5460477.4964771848171949%3C%2Fgml:coordinates%3E%3C%2Fgml:Box%3E%3C%2FBBOX%3E%3C%2FFilter%3E


So Mapserver has transmitted to GDAL a BBOX filter in epsg:25832 (which 
is the native SRS of the layer) that is the reprojection of your source 
BBOX from EPSG:3857. All things are good up to that point.


But the server returns an empty response.

Tweaking it manually to include a srsName="EPSG:25832" attribute in 
gml:Box returns a response with 2 features


http://sg.geodatenzentrum.de/wfs_info?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=500&REQUEST=GetFeature&TYPENAME=info:dop&FILTER=%3CFilter%20xmlns%3D%22http:%2F%2Fwww.opengis.net%2Fogc%22%20xmlns:gml%3D%22http:%2F%2Fwww.opengis.net%2Fgml%22%3E%3CBBOX%3E%3CPropertyName%3Egeom%3C%2FPropertyName%3E%3Cgml:Box%20srsName=%22EPSG:25832%22%3E%3Cgml:coordinates%3E362792.2015953020309098,5459899.7109905285760760%20363491.4383923375280574,5460477.4964771848171949%3C%2Fgml:coordinates%3E%3C%2Fgml:Box%3E%3C%2FBBOX%3E%3C%2FFilter%3E

But we shouldn't have to do this has a missing srsName should be 
interpretated as the defaultSRS according to my understand of the WFS 
1.1 spec


You can however tweak the  element in wfs-request-dop-bkg-age and 
add "&SRSNAME=EPSG:25832" to it (since it is the defaultSRS of all 
the layers of the service), and then GDAL will forward it.


Even


Le 28/05/2021 à 14:11, Lars Fricke a écrit :
No problem. Unfortunately, testing native WFS did not work because it 
does not properly support cascading wfs with different srs (see my 
other post).


Thanks for looking into this.
SkenData Email Signatur

Am 28.05.21 um 13:55 schrieb Even Rouault:


oops, sorry, didn't notice 😅

Le 28/05/2021 à 13:52, Lars Fricke a écrit :

I put in the files as attach. Is that filtered?
SkenData Email Signatur

Am 28.05.21 um 13:43 schrieb Even Rouault:


Please include your mapfile and the wfs-request-testlayer.xml file 
to reproduce. I'm confused by the mapfile you posted yesterday that 
uses epsg:25832 and the fact that GDAL through mapserver would 
issue a GetFeature in EPSG:3857 as suggested below. I can't see how 
that could happen (given the MapServer/GDAL integration, GDAL 
should always request in the native SRS of the layer and MapServer 
will do the reprojection to the SRSNAME of the WFS request)


But as Daniel suggested using the CONNECTION WFS is probably a 
better way of doing what you want


Le 28/05/2021 à 13:13, Lars Fricke via mapserver-users a écrit :
So here is the working not working setup. Unfortunately the 
working OGR WFS client layers are all private so I can not share them.


This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with QGIS).

This call doesn't work as described before as BBOX is not 
transmitted to external server:

http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for 
looking into this!


Best

Lars
SkenData Email Signatur


Am 27.05.21 um 18:28 schrieb Rahkonen Jukka (MML):

SkenData Email Signatur

Hi,

Have you already tried to use WFS connection instead of OGR 
connection?


-Jukka Rahkonen-

*Lähettäjä:* mapserver-users 
 *Puolesta *Lars Fricke

*Lähetetty:* torstai 27. toukokuuta 2021 14.59
*V

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
No problem. Unfortunately,
  testing native WFS did not work because it does not properly
  support cascading wfs with different srs (see my other post).
  
  Thanks for looking into this.


  
  
  

  

Am 28.05.21 um 13:55 schrieb Even
  Rouault:


  
  oops, sorry, didn't notice 😅
  Le 28/05/2021 à 13:52, Lars Fricke a
écrit :
  
  

I put in the files as
  attach. Is that filtered? 

  
  SkenData Email Signatur
   
  

Am 28.05.21 um 13:43 schrieb Even
  Rouault:


  
  Please include your mapfile and the
wfs-request-testlayer.xml file to reproduce. I'm confused by
the mapfile you posted yesterday that uses epsg:25832 and
the fact that GDAL through mapserver would issue a
GetFeature in EPSG:3857 as suggested below. I can't see how
that could happen (given the MapServer/GDAL integration,
GDAL should always request in the native SRS of the layer
and MapServer will do the reprojection to the SRSNAME of the
WFS request)
  
  But as Daniel suggested using the CONNECTION WFS is
probably a better way of doing what you want
  
  Le 28/05/2021 à 13:13, Lars
Fricke via mapserver-users a écrit :
  
  
So here is the working not working setup. Unfortunately the
working OGR WFS client layers are all private so I can not
share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with
QGIS).

This call doesn't work as described before as BBOX is not
transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works
anyhow)

I hope you can find out what is going wrong. Thanks so much
for looking into this!

Best

Lars

  SkenData Email Signatur
  
  
   
  

Am 27.05.21 um 18:28 schrieb
  Rahkonen Jukka (MML):


  
  SkenData Email Signatur
  
Hi,
 
Have you already
tried to use WFS connection instead of OGR
connection?
 
 
-Jukka Rahkonen-
 

  
Lähettäjä:
  mapserver-users 
  Puolesta Lars Fricke
  Lähetetty: torstai 27. toukokuuta 2021
  14.59
          Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client
  returns data at random with very same call
  

 
Dear all, 
  I apologize for finding and posting bits and pieces
  not all at one time. 
  I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see,
  that 
  """

  
HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
  """
  So there is no BBOX. On other layers I see
  """
  GDALOpen(/vsicurl_streaming/http

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Even Rouault via mapserver-users


oops, sorry, didn't notice 😅

Le 28/05/2021 à 13:52, Lars Fricke a écrit :

I put in the files as attach. Is that filtered?
SkenData Email Signatur

Am 28.05.21 um 13:43 schrieb Even Rouault:


Please include your mapfile and the wfs-request-testlayer.xml file to 
reproduce. I'm confused by the mapfile you posted yesterday that uses 
epsg:25832 and the fact that GDAL through mapserver would issue a 
GetFeature in EPSG:3857 as suggested below. I can't see how that 
could happen (given the MapServer/GDAL integration, GDAL should 
always request in the native SRS of the layer and MapServer will do 
the reprojection to the SRSNAME of the WFS request)


But as Daniel suggested using the CONNECTION WFS is probably a better 
way of doing what you want


Le 28/05/2021 à 13:13, Lars Fricke via mapserver-users a écrit :
So here is the working not working setup. Unfortunately the working 
OGR WFS client layers are all private so I can not share them.


This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with QGIS).

This call doesn't work as described before as BBOX is not 
transmitted to external server:

http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for 
looking into this!


Best

Lars
SkenData Email Signatur


Am 27.05.21 um 18:28 schrieb Rahkonen Jukka (MML):

SkenData Email Signatur

Hi,

Have you already tried to use WFS connection instead of OGR connection?

-Jukka Rahkonen-

*Lähettäjä:* mapserver-users 
 *Puolesta *Lars Fricke

*Lähetetty:* torstai 27. toukokuuta 2021 14.59
*Vastaanottaja:* mapserver-users@lists.osgeo.org
*Aihe:* Re: [mapserver-users] WFS Client returns data at random 
with very same call


Dear all,
I apologize for finding and posting bits and pieces not all at one 
time.

I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
"""

HTTP: 
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop 
<http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop>)

"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:...
"""
with BBOX.
No wonder I do not get reliable results if the server is calling 
some 1000 whatsoever result objects and starts filtering the bbox 
after.


Any idea what is happening? Or is this something for a GDAL thread?

Best
Lars




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

--
http://www.spatialys.com
My software is free, but my time generally not.



--
http://www.spatialys.com
My software is free, but my time generally not.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
I put in the files as
  attach. Is that filtered? 

  
  
  

  

Am 28.05.21 um 13:43 schrieb Even
  Rouault:


  
  Please include your mapfile and the wfs-request-testlayer.xml
file to reproduce. I'm confused by the mapfile you posted
yesterday that uses epsg:25832 and the fact that GDAL through
mapserver would issue a GetFeature in EPSG:3857 as suggested
below. I can't see how that could happen (given the
MapServer/GDAL integration, GDAL should always request in the
native SRS of the layer and MapServer will do the reprojection
to the SRSNAME of the WFS request)
  
  But as Daniel suggested using the CONNECTION WFS is probably a
better way of doing what you want
  
  Le 28/05/2021 à 13:13, Lars Fricke
via mapserver-users a écrit :
  
   So
here is the working not working setup. Unfortunately the working
OGR WFS client layers are all private so I can not share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with
QGIS).

This call doesn't work as described before as BBOX is not
transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for
looking into this!

Best

Lars

  SkenData Email Signatur
  
  
   
  

Am 27.05.21 um 18:28 schrieb
  Rahkonen Jukka (MML):


  
  SkenData Email Signatur
  
Hi,
 
Have you already
tried to use WFS connection instead of OGR connection?
 
 
-Jukka Rahkonen-
 

  
Lähettäjä: mapserver-users 
  Puolesta Lars Fricke
  Lähetetty: torstai 27. toukokuuta 2021 14.59
          Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client returns
  data at random with very same call
  

 
Dear all, 
  I apologize for finding and posting bits and pieces not
  all at one time. 
  I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
  
  """

  
HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
  """
  So there is no BBOX. On other layers I see
  """
  GDALOpen(/vsicurl_streaming/https:... 
  """
  with BBOX. 
  No wonder I do not get reliable results if the server
  is calling some 1000 whatsoever result objects and
  starts filtering the bbox after. 
  
  Any idea what is happening? Or is this something for a
  GDAL thread?
  
  Best
  Lars
  
  
 
  

  




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

  
  -- 
http://www.spatialys.com
My software is free, but my time generally not.


  

<>
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Even Rouault via mapserver-users

Please include your mapfile and the wfs-request-testlayer.xml file to 
reproduce. I'm confused by the mapfile you posted yesterday that uses 
epsg:25832 and the fact that GDAL through mapserver would issue a 
GetFeature in EPSG:3857 as suggested below. I can't see how that could 
happen (given the MapServer/GDAL integration, GDAL should always request 
in the native SRS of the layer and MapServer will do the reprojection to 
the SRSNAME of the WFS request)


But as Daniel suggested using the CONNECTION WFS is probably a better 
way of doing what you want


Le 28/05/2021 à 13:13, Lars Fricke via mapserver-users a écrit :
So here is the working not working setup. Unfortunately the working 
OGR WFS client layers are all private so I can not share them.


This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with QGIS).

This call doesn't work as described before as BBOX is not transmitted 
to external server:

http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for 
looking into this!


Best

Lars
SkenData Email Signatur


Am 27.05.21 um 18:28 schrieb Rahkonen Jukka (MML):

SkenData Email Signatur

Hi,

Have you already tried to use WFS connection instead of OGR connection?

-Jukka Rahkonen-

*Lähettäjä:* mapserver-users 
 *Puolesta *Lars Fricke

*Lähetetty:* torstai 27. toukokuuta 2021 14.59
*Vastaanottaja:* mapserver-users@lists.osgeo.org
*Aihe:* Re: [mapserver-users] WFS Client returns data at random with 
very same call


Dear all,
I apologize for finding and posting bits and pieces not all at one time.
I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
"""

HTTP: 
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop 
<http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop>)

"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:...
"""
with BBOX.
No wonder I do not get reliable results if the server is calling some 
1000 whatsoever result objects and starts filtering the bbox after.


Any idea what is happening? Or is this something for a GDAL thread?

Best
Lars




___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users


--
http://www.spatialys.com
My software is free, but my time generally not.

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
So here is the working not working setup. Unfortunately the working
OGR WFS client layers are all private so I can not share them.

This call delivers objects as expected:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer
This one, too:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetFeature&Maxfeatures=10&TYPENAME=TestLayer

Data is delivered in the correct srs (verified manually with QGIS).

This call doesn't work as described before as BBOX is not
transmitted to external server:
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=TestLayer

While the same direct call works:
http://sg.geodatenzentrum.de/wfs_info?SRSNAME=EPSG:3857&SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&BBOX=791880.72463009,6321925.37255709,792929.6378,6322786.10157277&TYPENAME=info:dop
(funny, epsg 3857 is not in the capabilities but works anyhow)

I hope you can find out what is going wrong. Thanks so much for
looking into this!

Best

Lars

  
  
  
  
  

  

Am 27.05.21 um 18:28 schrieb Rahkonen
  Jukka (MML):


  
  
  SkenData Email Signatur
  
  
Hi,
 
Have you already tried to use WFS connection
instead of OGR connection?
 
 
-Jukka
Rahkonen-
 

  
Lähettäjä: mapserver-users
  
  Puolesta Lars Fricke
  Lähetetty: torstai 27. toukokuuta 2021 14.59
      Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client returns data
  at random with very same call
  

 
Dear all, 
  I apologize for finding and posting bits and pieces not all at
  one time. 
  I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that 
  """

  
HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
  """
  So there is no BBOX. On other layers I see
  """
  GDALOpen(/vsicurl_streaming/https:... 
  """
  with BBOX. 
  No wonder I do not get reliable results if the server is
  calling some 1000 whatsoever result objects and starts
  filtering the bbox after.
  
  
  Any idea what is happening? Or is this something for a
  GDAL thread?
  
  Best
  Lars
  
  
 
  

  


  

<>
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
Ok, I will prepare a test
  set. Unfortunately my other layers are not public but Ill see if I
  still find one I may overlook as of now. 
  
  Best
  
  Lars


  
  
  

  

Am 28.05.21 um 12:00 schrieb Rahkonen
  Jukka (MML):


  
  
  SkenData Email Signatur
  
  
Hi,
 
Documentation
  https://mapserver.gis.umn.edu/es/ogc/wfs_client.html
does not mention option “wfs_srs”. That
  is a WFS server option
  https://www.mapserver.org/ogc/wfs_server.html.
  It looks like there is no way to control what SRS is used
  for accessing the remote server. Perhaps you can’t do what
  you want with WFS connection – cascade and reproject. So
  perhaps it is best to return to OGR connection. Luckily
  the remote service is open so you can  share with us a
  complete working test case that includes the mapfile and
  the xml file that you use in the CONNECTION. You also told
  that you have other same kind of layers which work.
  Include such layer into the test package as well.
 
-Jukka Rahkonen-
 
 
 
 

  
Lähettäjä: mapserver-users
  
  Puolesta Lars Fricke via mapserver-users
  Lähetetty: perjantai 28. toukokuuta 2021 12.17
  Vastaanottaja: mapserver-users@lists.osgeo.org
  Aihe: Re: [mapserver-users] WFS Client returns data
  at random with very same call
  

 
Dear
Daniel and Jukka,

following your advice I changed my setup as follows:
"""
LAYER
    NAME "TestLayer"
    CONNECTION "?"
    EXTENT -47443 5145172 1187852 6158846
    CONNECTIONTYPE WFS
    STATUS ON
    DEBUG 5
    METADATA
  "wfs_typename" "info:dop"
  "wfs_request_method"   "GET"
  "wfs_version"    "1.0.0"
  "wfs_srs" "EPSG:25832"
  "wfs_title"    "dop"
  "wfs_connectiontimeout" "60"
  "wfs_maxfeatures" "500"
  "gml_include_items" "all"
  "gml_featureid" "ID"

    END # METADATA
    PROJECTION
  "init=epsg:25832"
    END # PROJECTION
    TYPE POLYGON
    CLASS
  NAME "aerial_image_footprint"
  STYLE
    OUTLINECOLOR 255 0 0
    WIDTH 0.7
  END # STYLE
    END # CLASS
  END # LAYER

"""
What shall I say, it does not work. The strange things I am
noticing are as follows:
1) If I make a call with a bbox in EPSG: 3857 Mapserver
first sends my map-extent as bbox to the external server as
EPSG:3857, not using the layers extent that is in EPSG:25832
as is the source server. However , it does not send the srs
to the external server:

"""
REQUEST=GetFeature&VERSION=1.0.0&SERVICE=WFS&TYPENAME=info:dop&BBOX=-3161903.14172725,2675231.21277502,4977362.15235668,7973075.36166411&MAXFEATURES=500
"""
2) Besides the wrong srs, since the map extent is used
instead of the bbox in my request, I obviously would end up
by getting some 500 objects back that may or may not be in
my bbox. I verified this by putting the correct srs into the
CONNECTION (I think this is deprecated).

Now I also checked the Mapserver Version is 7.4 and I am
basing on this repo: 
https://github.com/camptocamp/docker-mapserver/tree/7.4
Is this Version too outdated (sorry for not mentioning the
version)? I do not have any issues with my other WFS layers
based on OGR connection ( I need WFS beyond 1.0.0)

Just in case it matters, the external server I am calling is
public so I might as well name it:
"http://sg.geodatenzentrum.de/wfs_info?"
The layer is "info:dop"

Thanks for all your help.

Best
Lars

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-28 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
Dear Daniel and Jukka,
  
  following your advice I changed my setup as follows:
  """
  LAYER
      NAME "TestLayer"
      CONNECTION "?"
      EXTENT -47443 5145172 1187852 6158846
      CONNECTIONTYPE WFS
      STATUS ON
      DEBUG 5
      METADATA
    "wfs_typename" "info:dop"
    "wfs_request_method"   "GET"
    "wfs_version"    "1.0.0"
    "wfs_srs" "EPSG:25832"
    "wfs_title"    "dop"
    "wfs_connectiontimeout" "60"
    "wfs_maxfeatures" "500"
    "gml_include_items" "all"
    "gml_featureid" "ID"
  
      END # METADATA
      PROJECTION
    "init=epsg:25832"
      END # PROJECTION
      TYPE POLYGON
      CLASS
    NAME "aerial_image_footprint"
    STYLE
      OUTLINECOLOR 255 0 0
      WIDTH 0.7
    END # STYLE
      END # CLASS
    END # LAYER
  
  """
  What shall I say, it does not work. The strange things I am
  noticing are as follows:
  1) If I make a call with a bbox in EPSG: 3857 Mapserver first
  sends my map-extent as bbox to the external server as EPSG:3857,
  not using the layers extent that is in EPSG:25832 as is the source
  server. However , it does not send the srs to the external server:
  
  """
REQUEST=GetFeature&VERSION=1.0.0&SERVICE=WFS&TYPENAME=info:dop&BBOX=-3161903.14172725,2675231.21277502,4977362.15235668,7973075.36166411&MAXFEATURES=500
  """
  2) Besides the wrong srs, since the map extent is used instead of
  the bbox in my request, I obviously would end up by getting some
  500 objects back that may or may not be in my bbox. I verified
  this by putting the correct srs into the CONNECTION (I think this
  is deprecated).
  
  Now I also checked the Mapserver Version is 7.4 and I am basing on
  this repo: 
  https://github.com/camptocamp/docker-mapserver/tree/7.4
  Is this Version too outdated (sorry for not mentioning the
  version)? I do not have any issues with my other WFS layers based
  on OGR connection ( I need WFS beyond 1.0.0)
  
  Just in case it matters, the external server I am calling is
  public so I might as well name it:
  "http://sg.geodatenzentrum.de/wfs_info?"
  The layer is "info:dop"
  
  Thanks for all your help.
  
  Best
  Lars


  
  
  
  
  

  

Am 27.05.21 um 21:36 schrieb Daniel
  Morissette:

Since
  you use CONNECTIONTYPE OGR, none of the MapServer WFS Client logic
  takes place.  Is there any reason why you cannot use
  CONNECTIONTYPE WFS as documented here:
  
  
  https://mapserver.org/ogc/wfs_client.html
  
  
  
  
  On 2021-05-27 02:51, Lars Fricke wrote:
  
  Dear All,


as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am
facing.


I am calling on a public WFS server I can query "by hand" fast
and successfully every single time. Now I defined a Mapserver
layer (see below) as an OGR layer in my WFS map-file and it does
- on the same call - return data. But not reliably, more at
random. I played with the connection-timeout and the maxfeatures
and it seemed to have some influence but again, not reliably.
I'll post the relevant parts of my mapfile (all my other layers
with other sources are working fine):

"""

MAP

   NAME "WFS_Test"

   SHAPEPATH "/data"

   STATUS ON

   UNITS METERS

   EXTENT -2851663 2776500 5630523 9970363


   PROJECTION

 "init=epsg:3857"

   END # PROJECTION


   WEB

 FOOTER "TestServer"

 IMAGEPATH "/tmp/"

 TEMPPATH "/tmp/"

 IMAGEURL "/tmp/"

 METADATA

   "wfs_title"  "Test"

   "ows_onlineresource"
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"

   "ows_enable_request"    "*"

   "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"

   "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"

   "wfs_getfeature_formatlist" "jsonp,ogrgml"

   "wfs_encoding" "UTF-8"

   "wfs_connectiontimeout" "20"

   #"wfs_request_method"   "GET"

 END # METADATA

 VALIDATION

     callback ".*"

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
Dear Even,
  
  what do you need from me to further investigate? I'll be happy to
  provide anything I can.
  
  Best
  
  Lars


  
  
  

  

Am 27.05.21 um 22:03 schrieb Even
  Rouault:


  
  It might be a bug in the OGR WFS driver (I see optimizations in
the code to avoid adding a BBOX if we have already fetched the
layer, that could be faulty), but we'd need a full reproducer to
be able to investigate.
  
  Le 27/05/2021 à 13:59, Lars Fricke a
écrit :
  
  

Dear all, 
I apologize for finding and posting bits and pieces not all at
one time. 
I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that 
"""

  
  SkenData Email Signatur
  HTTP: Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:... 
"""
with BBOX. 
No wonder I do not get reliable results if the server is
calling some 1000 whatsoever result objects and starts
filtering the bbox after. 

Any idea what is happening? Or is this something for a GDAL
thread?

Best
Lars
  
   
  

Am 27.05.21 um 09:04 schrieb Jörg
  Thomsen (WhereGroup):


  Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:

  
Dear All,

as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am facing.

I am calling on a public WFS server I can query "by hand" fast and
successfully every single time. Now I defined a Mapserver layer (see
below) as an OGR layer in my WFS map-file and it does - on the same call
- return data. But not reliably, more at random. I played with the
connection-timeout and the maxfeatures and it seemed to have some
influence but again, not reliably. I'll post the relevant parts of my
mapfile (all my other layers with other sources are working fine):
"""
MAP
  NAME "WFS_Test"
  SHAPEPATH "/data"
  STATUS ON
  UNITS METERS
  EXTENT -2851663 2776500 5630523 9970363

  PROJECTION
    "init=epsg:3857"
  END # PROJECTION

  WEB
    FOOTER "TestServer"
    IMAGEPATH "/tmp/"
    TEMPPATH "/tmp/"
    IMAGEURL "/tmp/"
    METADATA
  "wfs_title"  "Test"
  "ows_onlineresource"   
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"
  "ows_enable_request"    "*"
  "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_getfeature_formatlist" "jsonp,ogrgml"
  "wfs_encoding" "UTF-8"
  "wfs_connectiontimeout" "20"
  #"wfs_request_method"   "GET"
    END # METADATA
    VALIDATION
        callback ".*"
    END
  END # WEB

  OUTPUTFORMAT
   NAME "jsonp"
   DRIVER "OGR/GEOJSON"
   MIMETYPE "application/json; subtype=geojson; charset=utf-8"
   FORMATOPTION "STORAGE=stream"
   FORMATOPTION "FORM=SIMPLE"
   FORMATOPTION "LCO:COORDINATE_PRECISION=10"
   FORMATOPTION "JSONP=%callback%"
  END

  OUTPUTFORMAT
   NAME "OGRGML"
   DRIVER "OGR/GML"
   FORMATOPTION "STORAGE=filesystem"
   FORMATOPTION "FORM=multipart"
   FORMATOPTION "FILENAME=result.gml"
  END

  SYMBOL
    NAME "circle_filled"
    TYPE ELLIPSE
    FILLED TRUE
    POINTS
  1 1
    END
  END

  LAYER
    NAME "TestLayer"
    CONNECTION "wfs-request-testlayer.xml"
    EXTENT 84710 5210905 1163008 6125425
    CONNECTIONTYPE OGR
    STATUS ON
    DATA "dop"
    METADATA
  "wfs_version"    "2.0.0"
  "wfs_title"    "TestLayer_WFS"
  "wfs_connectiontimeout" "100"
  "wfs_typename"    "TestLayer_WFS_int"
  "wfs_maxfeatures"   "600"

    END # METADATA
    PROJECTION
  "init=epsg:25832"
    END # PROJECTION
    TYPE POLYGON
    CLASS
  NAME "aerial_image_footprint"
  STYLE
    OUTLINECOLOR 255 0 0
    WIDTH 0.7
  END # STYLE
    END # CLASS
  END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
"""
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
"""
If I replace the Server name with the public server, it works like a
breeze (even it is 3857).
The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
"http://mapserver.gis.umn.edu/mapserver" xmlns:gm

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke via mapserver-users

Title: SkenData Email Signatur

  
  
Dear Jukka and dear Daniel,
  
  Thank you very much for pointing out the native WFS capability. I
  moved away from it in the past because OGR has a broader spectrum
  of WFS versions supported and I sort of adopted this for all of my
  WFS client connections after the native one failed me in the past.
  But I see in the capabilities that on this server it should work
  so I guess I should give it a try. 
  
  Best
  
  Lars


  
  
  
  
  

  

Am 27.05.21 um 21:36 schrieb Daniel
  Morissette:

Since
  you use CONNECTIONTYPE OGR, none of the MapServer WFS Client logic
  takes place.  Is there any reason why you cannot use
  CONNECTIONTYPE WFS as documented here:
  
  
  https://mapserver.org/ogc/wfs_client.html
  
  
  
  
  On 2021-05-27 02:51, Lars Fricke wrote:
  
  Dear All,


as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am
facing.


I am calling on a public WFS server I can query "by hand" fast
and successfully every single time. Now I defined a Mapserver
layer (see below) as an OGR layer in my WFS map-file and it does
- on the same call - return data. But not reliably, more at
random. I played with the connection-timeout and the maxfeatures
and it seemed to have some influence but again, not reliably.
I'll post the relevant parts of my mapfile (all my other layers
with other sources are working fine):

"""

MAP

   NAME "WFS_Test"

   SHAPEPATH "/data"

   STATUS ON

   UNITS METERS

   EXTENT -2851663 2776500 5630523 9970363


   PROJECTION

 "init=epsg:3857"

   END # PROJECTION


   WEB

 FOOTER "TestServer"

 IMAGEPATH "/tmp/"

 TEMPPATH "/tmp/"

 IMAGEURL "/tmp/"

 METADATA

   "wfs_title"  "Test"

   "ows_onlineresource"
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"

   "ows_enable_request"    "*"

   "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"

   "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"

   "wfs_getfeature_formatlist" "jsonp,ogrgml"

   "wfs_encoding" "UTF-8"

   "wfs_connectiontimeout" "20"

   #"wfs_request_method"   "GET"

 END # METADATA

 VALIDATION

     callback ".*"

 END

   END # WEB


   OUTPUTFORMAT

    NAME "jsonp"

    DRIVER "OGR/GEOJSON"

    MIMETYPE "application/json; subtype=geojson; charset=utf-8"

    FORMATOPTION "STORAGE=stream"

    FORMATOPTION "FORM=SIMPLE"

    FORMATOPTION "LCO:COORDINATE_PRECISION=10"

    FORMATOPTION "JSONP=%callback%"

   END


   OUTPUTFORMAT

    NAME "OGRGML"

    DRIVER "OGR/GML"

    FORMATOPTION "STORAGE=filesystem"

    FORMATOPTION "FORM=multipart"

    FORMATOPTION "FILENAME=result.gml"

   END


   SYMBOL

 NAME "circle_filled"

 TYPE ELLIPSE

 FILLED TRUE

 POINTS

   1 1

 END

   END


   LAYER

 NAME "TestLayer"

 CONNECTION "wfs-request-testlayer.xml"

 EXTENT 84710 5210905 1163008 6125425

 CONNECTIONTYPE OGR

 STATUS ON

 DATA "dop"

 METADATA

   "wfs_version"    "2.0.0"

   "wfs_title"    "TestLayer_WFS"

   "wfs_connectiontimeout" "100"

   "wfs_typename"    "TestLayer_WFS_int"

   "wfs_maxfeatures"   "600"


 END # METADATA

 PROJECTION

   "init=epsg:25832"

 END # PROJECTION

 TYPE POLYGON

 CLASS

   NAME "aerial_image_footprint"

   STYLE

 OUTLINECO

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Even Rouault

It might be a bug in the OGR WFS driver (I see optimizations in the code 
to avoid adding a BBOX if we have already fetched the layer, that could 
be faulty), but we'd need a full reproducer to be able to investigate.


Le 27/05/2021 à 13:59, Lars Fricke a écrit :

Dear all,
I apologize for finding and posting bits and pieces not all at one time.
I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
"""
SkenData Email Signatur
HTTP: 
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)

"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:...
"""
with BBOX.
No wonder I do not get reliable results if the server is calling some 
1000 whatsoever result objects and starts filtering the bbox after.


Any idea what is happening? Or is this something for a GDAL thread?

Best
Lars

Am 27.05.21 um 09:04 schrieb Jörg Thomsen (WhereGroup):

Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:

Dear All,

as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am facing.

I am calling on a public WFS server I can query "by hand" fast and
successfully every single time. Now I defined a Mapserver layer (see
below) as an OGR layer in my WFS map-file and it does - on the same call
- return data. But not reliably, more at random. I played with the
connection-timeout and the maxfeatures and it seemed to have some
influence but again, not reliably. I'll post the relevant parts of my
mapfile (all my other layers with other sources are working fine):
"""
MAP
   NAME "WFS_Test"
   SHAPEPATH "/data"
   STATUS ON
   UNITS METERS
   EXTENT -2851663 2776500 5630523 9970363

   PROJECTION
     "init=epsg:3857"
   END # PROJECTION

   WEB
     FOOTER "TestServer"
     IMAGEPATH "/tmp/"
     TEMPPATH "/tmp/"
     IMAGEURL "/tmp/"
     METADATA
   "wfs_title"  "Test"
   "ows_onlineresource"
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map";
   "ows_enable_request"    "*"
   "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
   "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
   "wfs_getfeature_formatlist" "jsonp,ogrgml"
   "wfs_encoding" "UTF-8"
   "wfs_connectiontimeout" "20"
   #"wfs_request_method"   "GET"
     END # METADATA
     VALIDATION
         callback ".*"
     END
   END # WEB

   OUTPUTFORMAT
    NAME "jsonp"
    DRIVER "OGR/GEOJSON"
    MIMETYPE "application/json; subtype=geojson; charset=utf-8"
    FORMATOPTION "STORAGE=stream"
    FORMATOPTION "FORM=SIMPLE"
    FORMATOPTION "LCO:COORDINATE_PRECISION=10"
    FORMATOPTION "JSONP=%callback%"
   END

   OUTPUTFORMAT
    NAME "OGRGML"
    DRIVER "OGR/GML"
    FORMATOPTION "STORAGE=filesystem"
    FORMATOPTION "FORM=multipart"
    FORMATOPTION "FILENAME=result.gml"
   END

   SYMBOL
     NAME "circle_filled"
     TYPE ELLIPSE
     FILLED TRUE
     POINTS
   1 1
     END
   END

   LAYER
     NAME "TestLayer"
     CONNECTION "wfs-request-testlayer.xml"
     EXTENT 84710 5210905 1163008 6125425
     CONNECTIONTYPE OGR
     STATUS ON
     DATA "dop"
     METADATA
   "wfs_version"    "2.0.0"
   "wfs_title"    "TestLayer_WFS"
   "wfs_connectiontimeout" "100"
   "wfs_typename"    "TestLayer_WFS_int"
   "wfs_maxfeatures"   "600"

     END # METADATA
     PROJECTION
   "init=epsg:25832"
     END # PROJECTION
     TYPE POLYGON
     CLASS
   NAME "aerial_image_footprint"
   STYLE
     OUTLINECOLOR 255 0 0
     WIDTH 0.7
   END # STYLE
     END # CLASS
   END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
""" http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&; 
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer 
"""

If I replace the Server name with the public server, it works like a
breeze (even it is 3857).
The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
http://mapserver.gis.umn.edu/mapserver";  xmlns:gml="http://www.opengis.net/gml/3.2";  xmlns:wfs="http://www.opengis.net/wfs/2.0";  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";  xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver 
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2 
http://www.opengis.net/wfs/2.0 
http://schemas.opengis.net/wfs/2.0/wfs.xsd 
http://www.opengis.net/gml/3.2 
http://schemas.opengis.net/gml/3.2.1/gml.xsd";  timeStamp="2021-05-27T06:30:38" numberMatched="0" numberReturned="0"> 

"""
And in the log:
"""
[warn] [pid 26] mod_fcgid: stderr: msQueryByRe

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Daniel Morissette

Since you use CONNECTIONTYPE OGR, none of the MapServer WFS Client logic 
takes place.  Is there any reason why you cannot use CONNECTIONTYPE WFS 
as documented here:


https://mapserver.org/ogc/wfs_client.html



On 2021-05-27 02:51, Lars Fricke wrote:

Dear All,

as this list is a source of much deeper insight than I have into 
Mapserver, I would like to ask about a very strange issue I am facing.


I am calling on a public WFS server I can query "by hand" fast and 
successfully every single time. Now I defined a Mapserver layer (see 
below) as an OGR layer in my WFS map-file and it does - on the same call 
- return data. But not reliably, more at random. I played with the 
connection-timeout and the maxfeatures and it seemed to have some 
influence but again, not reliably. I'll post the relevant parts of my 
mapfile (all my other layers with other sources are working fine):

"""
MAP
   NAME "WFS_Test"
   SHAPEPATH "/data"
   STATUS ON
   UNITS METERS
   EXTENT -2851663 2776500 5630523 9970363

   PROJECTION
     "init=epsg:3857"
   END # PROJECTION

   WEB
     FOOTER "TestServer"
     IMAGEPATH "/tmp/"
     TEMPPATH "/tmp/"
     IMAGEURL "/tmp/"
     METADATA
   "wfs_title"  "Test"
   "ows_onlineresource" 
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map";

   "ows_enable_request"    "*"
   "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
   "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
   "wfs_getfeature_formatlist" "jsonp,ogrgml"
   "wfs_encoding" "UTF-8"
   "wfs_connectiontimeout" "20"
   #"wfs_request_method"   "GET"
     END # METADATA
     VALIDATION
         callback ".*"
     END
   END # WEB

   OUTPUTFORMAT
    NAME "jsonp"
    DRIVER "OGR/GEOJSON"
    MIMETYPE "application/json; subtype=geojson; charset=utf-8"
    FORMATOPTION "STORAGE=stream"
    FORMATOPTION "FORM=SIMPLE"
    FORMATOPTION "LCO:COORDINATE_PRECISION=10"
    FORMATOPTION "JSONP=%callback%"
   END

   OUTPUTFORMAT
    NAME "OGRGML"
    DRIVER "OGR/GML"
    FORMATOPTION "STORAGE=filesystem"
    FORMATOPTION "FORM=multipart"
    FORMATOPTION "FILENAME=result.gml"
   END

   SYMBOL
     NAME "circle_filled"
     TYPE ELLIPSE
     FILLED TRUE
     POINTS
   1 1
     END
   END

   LAYER
     NAME "TestLayer"
     CONNECTION "wfs-request-testlayer.xml"
     EXTENT 84710 5210905 1163008 6125425
     CONNECTIONTYPE OGR
     STATUS ON
     DATA "dop"
     METADATA
   "wfs_version"    "2.0.0"
   "wfs_title"    "TestLayer_WFS"
   "wfs_connectiontimeout" "100"
   "wfs_typename"    "TestLayer_WFS_int"
   "wfs_maxfeatures"   "600"

     END # METADATA
     PROJECTION
   "init=epsg:25832"
     END # PROJECTION
     TYPE POLYGON
     CLASS
   NAME "aerial_image_footprint"
   STYLE
     OUTLINECOLOR 255 0 0
     WIDTH 0.7
   END # STYLE
     END # CLASS
   END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
"""
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&;
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
"""
If I replace the Server name with the public server, it works like a 
breeze (even it is 3857).

The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
http://mapserver.gis.umn.edu/mapserver"xmlns:gml="http://www.opengis.net/gml/3.2"xmlns:wfs="http://www.opengis.net/wfs/2.0"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver 
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2 
http://www.opengis.net/wfs/2.0 
http://schemas.opengis.net/wfs/2.0/wfs.xsd 
http://www.opengis.net/gml/3.2 
http://schemas.opengis.net/gml/3.2.1/gml.xsd"timeStamp="2021-05-27T06:30:38"numberMatched="0"numberReturned="0";>

"""
And in the log:
"""
[warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search returned no 
results. No matching record(s) found.
  [warn] [pid 26] mod_fcgid: stderr: freeLayer(): freeing layer at 
0x131f120.
3169463 - 172.17.0.1 - - [27/May/2021:06:30:35 +] "GET 
/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer 
HTTP/1.1" 200 793 "-" "Mozilla/5.0 (X11; Linux x86_64) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
330 - 172.17.0.1 - - [27/May/2021:06:30:38 +] "GET /favicon.ico 
HTTP/1.1" 200 414 
"http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLay

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Rahkonen Jukka (MML)

Hi,

Have you already tried to use WFS connection instead of OGR connection?


-Jukka Rahkonen-

Lähettäjä: mapserver-users  Puolesta 
Lars Fricke
Lähetetty: torstai 27. toukokuuta 2021 14.59
Vastaanottaja: mapserver-users@lists.osgeo.org
Aihe: Re: [mapserver-users] WFS Client returns data at random with very same 
call

Dear all,
I apologize for finding and posting bits and pieces not all at one time.
I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that
"""
HTTP: 
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:...
"""
with BBOX.
No wonder I do not get reliable results if the server is calling some 1000 
whatsoever result objects and starts filtering the bbox after.

Any idea what is happening? Or is this something for a GDAL thread?

Best
Lars

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
Dear all, 
I apologize for finding and posting bits and pieces not all at one
time. 
I fired up 'CONFIG "CPL_DEBUG" "ON"' and there I see, that 
"""

  
  
  HTTP:
Fetch(http://url-to-external-server?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=1000&REQUEST=GetFeature&TYPENAME=dop)
"""
So there is no BBOX. On other layers I see
"""
GDALOpen(/vsicurl_streaming/https:... 
"""
with BBOX. 
No wonder I do not get reliable results if the server is calling
some 1000 whatsoever result objects and starts filtering the
bbox after. 

Any idea what is happening? Or is this something for a GDAL
thread?

Best
Lars
  
  

  

Am 27.05.21 um 09:04 schrieb Jörg
  Thomsen (WhereGroup):


  Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:

  
Dear All,

as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am facing.

I am calling on a public WFS server I can query "by hand" fast and
successfully every single time. Now I defined a Mapserver layer (see
below) as an OGR layer in my WFS map-file and it does - on the same call
- return data. But not reliably, more at random. I played with the
connection-timeout and the maxfeatures and it seemed to have some
influence but again, not reliably. I'll post the relevant parts of my
mapfile (all my other layers with other sources are working fine):
"""
MAP
  NAME "WFS_Test"
  SHAPEPATH "/data"
  STATUS ON
  UNITS METERS
  EXTENT -2851663 2776500 5630523 9970363

  PROJECTION
    "init=epsg:3857"
  END # PROJECTION

  WEB
    FOOTER "TestServer"
    IMAGEPATH "/tmp/"
    TEMPPATH "/tmp/"
    IMAGEURL "/tmp/"
    METADATA
  "wfs_title"  "Test"
  "ows_onlineresource"   
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"
  "ows_enable_request"    "*"
  "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_getfeature_formatlist" "jsonp,ogrgml"
  "wfs_encoding" "UTF-8"
  "wfs_connectiontimeout" "20"
  #"wfs_request_method"   "GET"
    END # METADATA
    VALIDATION
        callback ".*"
    END
  END # WEB

  OUTPUTFORMAT
   NAME "jsonp"
   DRIVER "OGR/GEOJSON"
   MIMETYPE "application/json; subtype=geojson; charset=utf-8"
   FORMATOPTION "STORAGE=stream"
   FORMATOPTION "FORM=SIMPLE"
   FORMATOPTION "LCO:COORDINATE_PRECISION=10"
   FORMATOPTION "JSONP=%callback%"
  END

  OUTPUTFORMAT
   NAME "OGRGML"
   DRIVER "OGR/GML"
   FORMATOPTION "STORAGE=filesystem"
   FORMATOPTION "FORM=multipart"
   FORMATOPTION "FILENAME=result.gml"
  END

  SYMBOL
    NAME "circle_filled"
    TYPE ELLIPSE
    FILLED TRUE
    POINTS
  1 1
    END
  END

  LAYER
    NAME "TestLayer"
    CONNECTION "wfs-request-testlayer.xml"
    EXTENT 84710 5210905 1163008 6125425
    CONNECTIONTYPE OGR
    STATUS ON
    DATA "dop"
    METADATA
  "wfs_version"    "2.0.0"
  "wfs_title"    "TestLayer_WFS"
  "wfs_connectiontimeout" "100"
  "wfs_typename"    "TestLayer_WFS_int"
  "wfs_maxfeatures"   "600"

    END # METADATA
    PROJECTION
  "init=epsg:25832"
    END # PROJECTION
    TYPE POLYGON
    CLASS
  NAME "aerial_image_footprint"
  STYLE
    OUTLINECOLOR 255 0 0
    WIDTH 0.7
  END # STYLE
    END # CLASS
  END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
"""
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
"""
If I replace the Server name with the public server, it works like a
breeze (even it is 3857).
The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
"http://mapserver.gis.umn.edu/mapserver" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2
http://www.opengis.net/wfs/2.0
http://schemas.opengis.net/wfs/2.0/wfs.xsd
http://www.opengis.net/gml/3.2
http://schemas.opengis.net/gml/3.2.1/gml.xsd" timeStamp="2021-05-27T06:30:38" numberMatched="0" numberReturned="0"> 
"""
And in the log:
"""
[warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search returned no
results. No matching record(s) found.
 [warn] [pid 26] mod_fcgid: stderr: freeLay

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
One more observation: 
If I happen to get a response, I get only one result object where it
should be many (and are many if I call directly). The one result
object I get is indeed located inside the BBOX. 

  
  
  
  
  
  
  

  

Am 27.05.21 um 09:04 schrieb Jörg
  Thomsen (WhereGroup):


  Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:

  
Dear All,

as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am facing.

I am calling on a public WFS server I can query "by hand" fast and
successfully every single time. Now I defined a Mapserver layer (see
below) as an OGR layer in my WFS map-file and it does - on the same call
- return data. But not reliably, more at random. I played with the
connection-timeout and the maxfeatures and it seemed to have some
influence but again, not reliably. I'll post the relevant parts of my
mapfile (all my other layers with other sources are working fine):
"""
MAP
  NAME "WFS_Test"
  SHAPEPATH "/data"
  STATUS ON
  UNITS METERS
  EXTENT -2851663 2776500 5630523 9970363

  PROJECTION
    "init=epsg:3857"
  END # PROJECTION

  WEB
    FOOTER "TestServer"
    IMAGEPATH "/tmp/"
    TEMPPATH "/tmp/"
    IMAGEURL "/tmp/"
    METADATA
  "wfs_title"  "Test"
  "ows_onlineresource"   
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"
  "ows_enable_request"    "*"
  "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_getfeature_formatlist" "jsonp,ogrgml"
  "wfs_encoding" "UTF-8"
  "wfs_connectiontimeout" "20"
  #"wfs_request_method"   "GET"
    END # METADATA
    VALIDATION
        callback ".*"
    END
  END # WEB

  OUTPUTFORMAT
   NAME "jsonp"
   DRIVER "OGR/GEOJSON"
   MIMETYPE "application/json; subtype=geojson; charset=utf-8"
   FORMATOPTION "STORAGE=stream"
   FORMATOPTION "FORM=SIMPLE"
   FORMATOPTION "LCO:COORDINATE_PRECISION=10"
   FORMATOPTION "JSONP=%callback%"
  END

  OUTPUTFORMAT
   NAME "OGRGML"
   DRIVER "OGR/GML"
   FORMATOPTION "STORAGE=filesystem"
   FORMATOPTION "FORM=multipart"
   FORMATOPTION "FILENAME=result.gml"
  END

  SYMBOL
    NAME "circle_filled"
    TYPE ELLIPSE
    FILLED TRUE
    POINTS
  1 1
    END
  END

  LAYER
    NAME "TestLayer"
    CONNECTION "wfs-request-testlayer.xml"
    EXTENT 84710 5210905 1163008 6125425
    CONNECTIONTYPE OGR
    STATUS ON
    DATA "dop"
    METADATA
  "wfs_version"    "2.0.0"
  "wfs_title"    "TestLayer_WFS"
  "wfs_connectiontimeout" "100"
  "wfs_typename"    "TestLayer_WFS_int"
  "wfs_maxfeatures"   "600"

    END # METADATA
    PROJECTION
  "init=epsg:25832"
    END # PROJECTION
    TYPE POLYGON
    CLASS
  NAME "aerial_image_footprint"
  STYLE
    OUTLINECOLOR 255 0 0
    WIDTH 0.7
  END # STYLE
    END # CLASS
  END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
"""
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
"""
If I replace the Server name with the public server, it works like a
breeze (even it is 3857).
The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
"http://mapserver.gis.umn.edu/mapserver" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2
http://www.opengis.net/wfs/2.0
http://schemas.opengis.net/wfs/2.0/wfs.xsd
http://www.opengis.net/gml/3.2
http://schemas.opengis.net/gml/3.2.1/gml.xsd" timeStamp="2021-05-27T06:30:38" numberMatched="0" numberReturned="0"> 
"""
And in the log:
"""
[warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search returned no
results. No matching record(s) found.
 [warn] [pid 26] mod_fcgid: stderr: freeLayer(): freeing layer at 0x131f120.
3169463 - 172.17.0.1 - - [27/May/2021:06:30:35 +] "GET
/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
HTTP/1.1" 200 793 "-" "Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
330 - 172.17.0.1 - - [27/May/2021:06:30:38 +] "GET /favicon.ico
HTTP/1

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
Hello,

I continued testing and I verified that the SRS is set correctly (by
doing getfeature without bbox and only maxfeatures=10 in the call).
I also verified I am getting the correct data by this.
No change with the max-features in the map-file. In the xml file it
seems to be needed.

Best

Lars

  
  
  
  
  

  

Am 27.05.21 um 09:04 schrieb Jörg
  Thomsen (WhereGroup):


  Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:

  
Dear All,

as this list is a source of much deeper insight than I have into
Mapserver, I would like to ask about a very strange issue I am facing.

I am calling on a public WFS server I can query "by hand" fast and
successfully every single time. Now I defined a Mapserver layer (see
below) as an OGR layer in my WFS map-file and it does - on the same call
- return data. But not reliably, more at random. I played with the
connection-timeout and the maxfeatures and it seemed to have some
influence but again, not reliably. I'll post the relevant parts of my
mapfile (all my other layers with other sources are working fine):
"""
MAP
  NAME "WFS_Test"
  SHAPEPATH "/data"
  STATUS ON
  UNITS METERS
  EXTENT -2851663 2776500 5630523 9970363

  PROJECTION
    "init=epsg:3857"
  END # PROJECTION

  WEB
    FOOTER "TestServer"
    IMAGEPATH "/tmp/"
    TEMPPATH "/tmp/"
    IMAGEURL "/tmp/"
    METADATA
  "wfs_title"  "Test"
  "ows_onlineresource"   
"http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"
  "ows_enable_request"    "*"
  "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
  "wfs_getfeature_formatlist" "jsonp,ogrgml"
  "wfs_encoding" "UTF-8"
  "wfs_connectiontimeout" "20"
  #"wfs_request_method"   "GET"
    END # METADATA
    VALIDATION
        callback ".*"
    END
  END # WEB

  OUTPUTFORMAT
   NAME "jsonp"
   DRIVER "OGR/GEOJSON"
   MIMETYPE "application/json; subtype=geojson; charset=utf-8"
   FORMATOPTION "STORAGE=stream"
   FORMATOPTION "FORM=SIMPLE"
   FORMATOPTION "LCO:COORDINATE_PRECISION=10"
   FORMATOPTION "JSONP=%callback%"
  END

  OUTPUTFORMAT
   NAME "OGRGML"
   DRIVER "OGR/GML"
   FORMATOPTION "STORAGE=filesystem"
   FORMATOPTION "FORM=multipart"
   FORMATOPTION "FILENAME=result.gml"
  END

  SYMBOL
    NAME "circle_filled"
    TYPE ELLIPSE
    FILLED TRUE
    POINTS
  1 1
    END
  END

  LAYER
    NAME "TestLayer"
    CONNECTION "wfs-request-testlayer.xml"
    EXTENT 84710 5210905 1163008 6125425
    CONNECTIONTYPE OGR
    STATUS ON
    DATA "dop"
    METADATA
  "wfs_version"    "2.0.0"
  "wfs_title"    "TestLayer_WFS"
  "wfs_connectiontimeout" "100"
  "wfs_typename"    "TestLayer_WFS_int"
  "wfs_maxfeatures"   "600"

    END # METADATA
    PROJECTION
  "init=epsg:25832"
    END # PROJECTION
    TYPE POLYGON
    CLASS
  NAME "aerial_image_footprint"
  STYLE
    OUTLINECOLOR 255 0 0
    WIDTH 0.7
  END # STYLE
    END # CLASS
  END # LAYER
"""
I made the xml-file wit ogrinfo as I did for many other layers that work.
The call is:
"""
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
"""
If I replace the Server name with the public server, it works like a
breeze (even it is 3857).
The public server has:
"""
urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""

I see the following response in the browser:
"""
"http://mapserver.gis.umn.edu/mapserver" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2
http://www.opengis.net/wfs/2.0
http://schemas.opengis.net/wfs/2.0/wfs.xsd
http://www.opengis.net/gml/3.2
http://schemas.opengis.net/gml/3.2.1/gml.xsd" timeStamp="2021-05-27T06:30:38" numberMatched="0" numberReturned="0"> 
"""
And in the log:
"""
[warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search returned no
results. No matching record(s) found.
 [warn] [pid 26] mod_fcgid: stderr: freeLayer(): freeing layer at 0x131f120.
3169463 - 172.17.0.1 - - [27/May/2021:06:30:35 +] "GET
/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
HTTP/1.1" 200 793 "-" "Mozilla/5.0 (X11; Linux x86_64)
AppleWebKit/537.36 (KHTML, like Gecko) Ch

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
Hello Jörg,
  
  I tried turning maxfeatures off. If I do it in the mapfile, there
  is no effect. If I do it in the xml file I get "internal server
  error" after same longer time. I also tried calling 
  """
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&TYPENAME=TestLayer&MaxFeatures=10
  """
  and it does indeed return data correctly. I had to add
  "gml_featureid" "ID" to avoid a complaint about verification
  but that does not change the behavior if I use a BBOX.
  
  Best
  
  Lars


  
  
  


  

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
Hello Jörg, 
  
  thank's for the fast reply. I think I did turn it off once but
  I'll double check.
  
  Best
  
  Lars


  
  
  


  

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client returns data at random with very same call

2021-05-27 Thread WhereGroup

Hello Lars,

maxfeatures was my first guess... have you also turned ist it off (no
maxfeatures)?

Jörg


Am 27.05.21 um 08:51 schrieb Lars Fricke:
> Dear All,
> 
> as this list is a source of much deeper insight than I have into
> Mapserver, I would like to ask about a very strange issue I am facing.
> 
> I am calling on a public WFS server I can query "by hand" fast and
> successfully every single time. Now I defined a Mapserver layer (see
> below) as an OGR layer in my WFS map-file and it does - on the same call
> - return data. But not reliably, more at random. I played with the
> connection-timeout and the maxfeatures and it seemed to have some
> influence but again, not reliably. I'll post the relevant parts of my
> mapfile (all my other layers with other sources are working fine):
> """
> MAP
>   NAME "WFS_Test"
>   SHAPEPATH "/data"
>   STATUS ON
>   UNITS METERS
>   EXTENT -2851663 2776500 5630523 9970363
> 
>   PROJECTION
>     "init=epsg:3857"
>   END # PROJECTION
> 
>   WEB
>     FOOTER "TestServer"
>     IMAGEPATH "/tmp/"
>     TEMPPATH "/tmp/"
>     IMAGEURL "/tmp/"
>     METADATA
>   "wfs_title"  "Test"
>   "ows_onlineresource"   
> "http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map";
>   "ows_enable_request"    "*"
>   "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
>   "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
>   "wfs_getfeature_formatlist" "jsonp,ogrgml"
>   "wfs_encoding" "UTF-8"
>   "wfs_connectiontimeout" "20"
>   #"wfs_request_method"   "GET"
>     END # METADATA
>     VALIDATION
>         callback ".*"
>     END
>   END # WEB
> 
>   OUTPUTFORMAT
>    NAME "jsonp"
>    DRIVER "OGR/GEOJSON"
>    MIMETYPE "application/json; subtype=geojson; charset=utf-8"
>    FORMATOPTION "STORAGE=stream"
>    FORMATOPTION "FORM=SIMPLE"
>    FORMATOPTION "LCO:COORDINATE_PRECISION=10"
>    FORMATOPTION "JSONP=%callback%"
>   END
> 
>   OUTPUTFORMAT
>    NAME "OGRGML"
>    DRIVER "OGR/GML"
>    FORMATOPTION "STORAGE=filesystem"
>    FORMATOPTION "FORM=multipart"
>    FORMATOPTION "FILENAME=result.gml"
>   END
> 
>   SYMBOL
>     NAME "circle_filled"
>     TYPE ELLIPSE
>     FILLED TRUE
>     POINTS
>   1 1
>     END
>   END
> 
>   LAYER
>     NAME "TestLayer"
>     CONNECTION "wfs-request-testlayer.xml"
>     EXTENT 84710 5210905 1163008 6125425
>     CONNECTIONTYPE OGR
>     STATUS ON
>     DATA "dop"
>     METADATA
>   "wfs_version"    "2.0.0"
>   "wfs_title"    "TestLayer_WFS"
>   "wfs_connectiontimeout" "100"
>   "wfs_typename"    "TestLayer_WFS_int"
>   "wfs_maxfeatures"   "600"
> 
>     END # METADATA
>     PROJECTION
>   "init=epsg:25832"
>     END # PROJECTION
>     TYPE POLYGON
>     CLASS
>   NAME "aerial_image_footprint"
>   STYLE
>     OUTLINECOLOR 255 0 0
>     WIDTH 0.7
>   END # STYLE
>     END # CLASS
>   END # LAYER
> """
> I made the xml-file wit ogrinfo as I did for many other layers that work.
> The call is:
> """
> http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&;
> SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
> """
> If I replace the Server name with the public server, it works like a
> breeze (even it is 3857).
> The public server has:
> """
> urn:ogc:def:crs:EPSG:6.9:25832
> urn:ogc:def:crs:EPSG:6.9:4326
> """
> 
> I see the following response in the browser:
> """
> http://mapserver.gis.umn.edu/mapserver" 
> xmlns:gml="http://www.opengis.net/gml/3.2" 
> xmlns:wfs="http://www.opengis.net/wfs/2.0" 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
> xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver
> http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2
> http://www.opengis.net/wfs/2.0
> http://schemas.opengis.net/wfs/2.0/wfs.xsd
> http://www.opengis.net/gml/3.2
> http://schemas.opengis.net/gml/3.2.1/gml.xsd" timeStamp="2021-05-27T06:30:38" 
> numberMatched="0" numberReturned="0"> 
> """
> And in the log:
> """
> [warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search returned no
> results. No matching record(s) found.
>  [warn] [pid 26] mod_fcgid: stderr: freeLayer(): freeing layer at 0x131f120.
> 3169463 - 172.17.0.1 - - [27/May/2021:06:30:35 +] "GET
> /cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
> HTTP/1.1" 200 793 "-" "Mozilla/5.0 (X11; Linux x86_64)
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36"
> 330 - 172.17.0.1 - - [27/May/2021:06:30:38 +] "GET /favicon.ico
> HTTP/1.1" 200 414
> "http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=

[mapserver-users] WFS Client returns data at random with very same call

2021-05-26 Thread Lars Fricke

Title: SkenData Email Signatur

  
  
Dear All,
  
  as this list is a source of much deeper insight than I have into
  Mapserver, I would like to ask about a very strange issue I am
  facing.
  
  I am calling on a public WFS server I can query "by hand" fast and
  successfully every single time. Now I defined a Mapserver layer
  (see below) as an OGR layer in my WFS map-file and it does - on
  the same call - return data. But not reliably, more at random. I
  played with the connection-timeout and the maxfeatures and it
  seemed to have some influence but again, not reliably. I'll post
  the relevant parts of my mapfile (all my other layers with other
  sources are working fine):
  """
  MAP
    NAME "WFS_Test"
    SHAPEPATH "/data"
    STATUS ON
    UNITS METERS
    EXTENT -2851663 2776500 5630523 9970363
  
    PROJECTION
      "init=epsg:3857"
    END # PROJECTION
  
    WEB
      FOOTER "TestServer"
      IMAGEPATH "/tmp/"
      TEMPPATH "/tmp/"
      IMAGEURL "/tmp/"
      METADATA
    "wfs_title"  "Test"
    "ows_onlineresource"   
  "http://my_server.de/cgi-bin/mapserv?map=/var/www/html/wfs.map"
    "ows_enable_request"    "*"
    "ows_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
    "wfs_srs"    "EPSG:3857 EPSG:4326 EPSG:25832"
    "wfs_getfeature_formatlist" "jsonp,ogrgml"
    "wfs_encoding" "UTF-8"
    "wfs_connectiontimeout" "20"
    #"wfs_request_method"   "GET"
      END # METADATA
      VALIDATION
          callback ".*"
      END
    END # WEB
  
    OUTPUTFORMAT
     NAME "jsonp"
     DRIVER "OGR/GEOJSON"
     MIMETYPE "application/json; subtype=geojson; charset=utf-8"
     FORMATOPTION "STORAGE=stream"
     FORMATOPTION "FORM=SIMPLE"
     FORMATOPTION "LCO:COORDINATE_PRECISION=10"
     FORMATOPTION "JSONP=%callback%"
    END
  
    OUTPUTFORMAT
     NAME "OGRGML"
     DRIVER "OGR/GML"
     FORMATOPTION "STORAGE=filesystem"
     FORMATOPTION "FORM=multipart"
     FORMATOPTION "FILENAME=result.gml"
    END
  
    SYMBOL
      NAME "circle_filled"
      TYPE ELLIPSE
      FILLED TRUE
      POINTS
    1 1
      END
    END
  
    LAYER
      NAME "TestLayer"
      CONNECTION "wfs-request-testlayer.xml"
      EXTENT 84710 5210905 1163008 6125425
      CONNECTIONTYPE OGR
      STATUS ON
      DATA "dop"
      METADATA
    "wfs_version"    "2.0.0"
    "wfs_title"    "TestLayer_WFS"
    "wfs_connectiontimeout" "100"
    "wfs_typename"    "TestLayer_WFS_int"
    "wfs_maxfeatures"   "600"
  
      END # METADATA
      PROJECTION
    "init=epsg:25832"
      END # PROJECTION
      TYPE POLYGON
      CLASS
    NAME "aerial_image_footprint"
    STYLE
      OUTLINECOLOR 255 0 0
      WIDTH 0.7
    END # STYLE
      END # CLASS
    END # LAYER
  """
  I made the xml-file wit ogrinfo as I did for many other layers
  that work.
  The call is:
  """
http://localhost:8181/cgi-bin/mapserv?map=/var/www/html/wfs.map&
SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,6822730.62911591,1293128.57472490,6823169.70765144&TYPENAME=TestLayer
  """
  If I replace the Server name with the public server, it works like
  a breeze (even it is 3857). 
  The public server has:
  """
  urn:ogc:def:crs:EPSG:6.9:25832
urn:ogc:def:crs:EPSG:6.9:4326
"""
  
  I see the following response in the browser:
  """
 xmlns:ms="http://mapserver.gis.umn.edu/mapserver" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:wfs="http://www.opengis.net/wfs/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://mapserver.gis.umn.edu/mapserver
http://wfs/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=DescribeFeatureType&TYPENAME=DOP_AGE_DE&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2
http://www.opengis.net/wfs/2.0
http://schemas.opengis.net/wfs/2.0/wfs.xsd
http://www.opengis.net/gml/3.2
http://schemas.opengis.net/gml/3.2.1/gml.xsd" timeStamp="2021-05-27T06:30:38" numberMatched="0" numberReturned="0"> 
  """
  And in the log:
  """
  [warn] [pid 26] mod_fcgid: stderr: msQueryByRect(): Search
  returned no results. No matching record(s) found.
   [warn] [pid 26] mod_fcgid: stderr: freeLayer(): freeing layer at
  0x131f120.
  3169463 - 172.17.0.1 - - [27/May/2021:06:30:35 +] "GET
/cgi-bin/mapserv?map=/var/www/html/wfs.map&SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:3857&BBOX=1292610.86313433,682

Re: [mapserver-users] WFS-Client Version 2.0.0

2019-10-08 Thread WhereGroup

thanks, Even, for the quick answer.

and thanks, Lars, too. I will follow Jeffs instrucions on
http://osgeo-org.1560.x6.nabble.com/CONNECTIONTYPE-OGR-is-not-working-after-upgrade-to-mapserver-7-2-2-from-6-4-1-td5400796.html

Jörg


Am 08.10.19 um 13:42 schrieb Lars Fricke:
> Hi Jörg,
> 
> you need to use
> CONNECTIONTYPE OGR
> 
> and generate an xml file using
> 
> ogrinfo
> 
> with
> CONNECTION "my_generated_definition_file.xml"
> 
> see https://gdal.org/drivers/vector/wfs.html
> 
> Mit freundlichen Grüßen
> Lars Fricke
> Forschung & Entwicklung
> 
> +49(0)39602-183097
> +49(0)39602-183098
> 
> SkenData GmbH
> Mühlendamm 8B
> 18055 Rostock
> www.skendata.de
> 
> 
> Wert14
> 
> 
> www.wert14.de
> 
> Geschäftsführer: Jon Meis und Sven Jantzen
> Amtsgericht Rostock HRB 12937
> 
> Am 08.10.19 um 13:23 schrieb Jörg Thomsen (WhereGroup):
>> Hi everyone,
>>
>> I am trying to setup a WMS which uses a WFS as datasource. The WFS only
>> works in version 2.0.0 and MapServer tells me
>>
>>> msBuildWFSLayerGetURL(): WFS connection error. MapServer supports only WFS 
>>> 1.0.0 or 0.0.14 (please verify the version metadata wfs_version)
>> really? What can I do?
>>
>> Regards, Jörg
>>
> 
> 
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
> 


Viele Grüße,
Jörg Thomsen

-- 

***
Where2B Konferenz 2019
12. Dezember 2019 in Bonn
where2b-conference.com
***

Jörg Thomsen
WhereGroup GmbH
Gillweg 3
14193 Berlin
Germany

Fon: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 5130 278 11

joerg.thom...@wheregroup.com
www.wheregroup.com

Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885

---
Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS-Client Version 2.0.0

2019-10-08 Thread Even Rouault

On mardi 8 octobre 2019 13:23:43 CEST Jörg Thomsen (WhereGroup) wrote:
> Hi everyone,
> 
> I am trying to setup a WMS which uses a WFS as datasource. The WFS only
> works in version 2.0.0 and MapServer tells me
> 
> > msBuildWFSLayerGetURL(): WFS connection error. MapServer supports only WFS
> > 1.0.0 or 0.0.14 (please verify the version metadata wfs_version)
> really? 

Yes, as a client

> What can I do?

You could use the GDAL WFS client, which support WFS 2

https://gdal.org/drivers/vector/wfs.html

See https://mapserver.org/input/vector/ogr.html#ogr for general documentation 
on how to use a OGR datasource

In a nutshell, in your LAYER definition:

  CONNECTIONTYPE OGR
  CONNECTION "WFS:https://bla";
  DATA "layer_name"

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS-Client Version 2.0.0

2019-10-08 Thread Lars Fricke


  
  
Hi Jörg,
  
  you need to use 
  CONNECTIONTYPE OGR
  
  and generate an xml file using 
  
  ogrinfo 
  
  with 
  CONNECTION "my_generated_definition_file.xml"
  
  see https://gdal.org/drivers/vector/wfs.html


   Mit
freundlichen Grüßen
Lars Fricke
Forschung & Entwicklung
  
  
+49(0)39602-183097
+49(0)39602-183098
  
  
SkenData GmbH
Mühlendamm 8B
18055 Rostock
www.skendata.de
  
   

  
   
www.wert14.de
  
   Geschäftsführer: Jon Meis und Sven Jantzen
Amtsgericht Rostock HRB 12937
  

Am 08.10.19 um 13:23 schrieb Jörg
  Thomsen (WhereGroup):


  Hi everyone,

I am trying to setup a WMS which uses a WFS as datasource. The WFS only
works in version 2.0.0 and MapServer tells me


  
msBuildWFSLayerGetURL(): WFS connection error. MapServer supports only WFS 1.0.0 or 0.0.14 (please verify the version metadata wfs_version)

  
  
really? What can I do?

Regards, Jörg




  

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS-Client Version 2.0.0

2019-10-08 Thread WhereGroup

sorry, I'll have to use an OGR-Connection

Jörg
Am 08.10.19 um 13:23 schrieb Jörg Thomsen (WhereGroup):
> Hi everyone,
> 
> I am trying to setup a WMS which uses a WFS as datasource. The WFS only
> works in version 2.0.0 and MapServer tells me
> 
>> msBuildWFSLayerGetURL(): WFS connection error. MapServer supports only WFS 
>> 1.0.0 or 0.0.14 (please verify the version metadata wfs_version)
> 
> really? What can I do?
> 
> Regards, Jörg
> 


Viele Grüße,
Jörg Thomsen

-- 

***
Where2B Konferenz 2019
12. Dezember 2019 in Bonn
where2b-conference.com
***

Jörg Thomsen
WhereGroup GmbH
Gillweg 3
14193 Berlin
Germany

Fon: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 5130 278 11

joerg.thom...@wheregroup.com
www.wheregroup.com

Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885

---
Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS-Client Version 2.0.0

2019-10-08 Thread WhereGroup

Hi everyone,

I am trying to setup a WMS which uses a WFS as datasource. The WFS only
works in version 2.0.0 and MapServer tells me

> msBuildWFSLayerGetURL(): WFS connection error. MapServer supports only WFS 
> 1.0.0 or 0.0.14 (please verify the version metadata wfs_version)

really? What can I do?

Regards, Jörg

-- 

***
Where2B Konferenz 2019
12. Dezember 2019 in Bonn
where2b-conference.com
***

Jörg Thomsen
WhereGroup GmbH
Gillweg 3
14193 Berlin
Germany

Fon: +49 (0)30 / 5130 278 74
Fax: +49 (0)30 / 5130 278 11

joerg.thom...@wheregroup.com
www.wheregroup.com

Geschäftsführer:
Olaf Knopp, Peter Stamm
Amtsgericht Bonn, HRB 9885

---
Folgen Sie der WhereGroup auf twitter: http://twitter.com/WhereGroup_com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Lime, Steve D (MNIT)

Ditto, thanks!

-Original Message-
From: mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] On 
Behalf Of Rahkonen Jukka (MML)
Sent: Thursday, February 18, 2016 4:20 PM
To: Even Rouault ; mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WFS Client...

Even Rouault wrote:

> I've committed
> > https://github.com/mapserver/mapserver/commit/de7ef60c4cd04ea9708a17052c48d8875f067410
> in master to enable POST logging :

That's great.

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Rahkonen Jukka (MML)

Even Rouault wrote:

> I've committed
> > https://github.com/mapserver/mapserver/commit/de7ef60c4cd04ea9708a17052c48d8875f067410
> in master to enable POST logging :

That's great.

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Even Rouault

Le jeudi 18 février 2016 22:01:58, Lime, Steve D (MNIT) a écrit :
> Hi all: Is there any way to log the request URL and POST data associated
> with MapServer WFS layers? That info doesn't seem to be showing up in
> debug logs and it would be helpful to see exactly what is being sent to
> the WFS server.

I've committed 
https://github.com/mapserver/mapserver/commit/de7ef60c4cd04ea9708a17052c48d8875f067410
 
in master to enable POST logging :

$ MS_ERRORFILE=/dev/stderr MS_DEBUGLEVEL=1 mapserv 
QUERY_STRING="map=test.map&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetCapabilities"
[Thu Feb 18 22:31:16 2016].769357 loadParams() QUERY_STRING: 
map=test.map&SERVICE=WFS&VERSION=1.1.0&REQUEST=GetCapabilities
[Thu Feb 18 22:31:16 2016].771312 HTTP: Starting to prepare HTTP requests.
[Thu Feb 18 22:31:16 2016].771387 HTTP request: id=0, 
http://demo.mapserver.org/cgi-bin/wfs?
[Thu Feb 18 22:31:16 2016].771486 HTTP: POST = 
http://www.opengis.net/wfs"; xmlns:ogc="http://www.opengis.net/ogc"; 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.0.0/wfs.xsd"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:gml="http://www.opengis.net/gml";>



Geometry

-67.572500,42.00 -58.927500,48.50





> 
> Steve

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Rahkonen Jukka (MML)

Let’s stop all now and think for a while.

Steve asks, as it appears in the title, about Mapserver as WFS client, so 
finding the requests which Mapserver is sending to outer world. Carlos and I 
have answered about how to log incoming requests for WFS server.

I use Fiddler as a local proxy server and configure Mapserver to use the proxy 
http://mapserver.org/ogc/wfs_client.html. Fiddler records all the traffic and 
it is very useful for debugging. BTW. the wfs client manual page tells that 
POST is the default but it can be changed with wfs_request_method metadata.

-Jukka Rahkonen-

Carlos Ruiz wrote:

OK. If you are doing a request to a WFS layer from an OpenLayers application, 
you can see the request by pressing SHIFT+CTRL+J in FireFox and enable the 
Network toggle button.


You will see the full request when hovering the URL


GET 
http://localhost/cgi-bin/accidentes?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=Estaciones%20Tren%20Ligero%20-%20Tipo&CRS=EPSG%3A4326&STYLES=&WIDTH=2025&HEIGHT=962&BBOX=20.624878406524658%2C-103.43881130218506%2C20.707404613494873%2C-103.26500415802002
 [HTTP/1.1 200 OK 361ms]



From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: Carlos Ruiz mailto:boolean10...@yahoo.com>>; 
"mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:06 PM
Subject: RE: [mapserver-users] WFS Client...

The WFS server is not under my control, so no access log.

From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Thursday, February 18, 2016 3:06 PM
To: Lime, Steve D (MNIT) 
mailto:steve.l...@state.mn.us>>; 
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
Subject: Re: [mapserver-users] WFS Client...

Steve,

You can check the Apache "access.log" file and watch for the HTTP GET requests. 
You will find something like this:

127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412



From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: "mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn’t seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Lime, Steve D (MNIT)

Nope, this is MapServer as a WFS client – a WFS layer 
(http://mapserver.org/ogc/wfs_client.html).

From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Thursday, February 18, 2016 3:16 PM
To: Lime, Steve D (MNIT) ; 
mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WFS Client...

OK. If you are doing a request to a WFS layer from an OpenLayers application, 
you can see the request by pressing SHIFT+CTRL+J in FireFox and enable the 
Network toggle button.

You will see the full request when hovering the URL

GET 
http://localhost/cgi-bin/accidentes?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=Estaciones%20Tren%20Ligero%20-%20Tipo&CRS=EPSG%3A4326&STYLES=&WIDTH=2025&HEIGHT=962&BBOX=20.624878406524658%2C-103.43881130218506%2C20.707404613494873%2C-103.26500415802002
 [HTTP/1.1 200 OK 361ms]

From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: Carlos Ruiz mailto:boolean10...@yahoo.com>>; 
"mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:06 PM
Subject: RE: [mapserver-users] WFS Client...

The WFS server is not under my control, so no access log.

From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Thursday, February 18, 2016 3:06 PM
To: Lime, Steve D (MNIT) 
mailto:steve.l...@state.mn.us>>; 
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
Subject: Re: [mapserver-users] WFS Client...

Steve,

You can check the Apache "access.log" file and watch for the HTTP GET requests. 
You will find something like this:

127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412

From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: "mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn’t seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Carlos Ruiz

OK. If you are doing a request to a WFS layer from an OpenLayers application, 
you can see the request by pressing SHIFT+CTRL+J in FireFox and enable the 
Network toggle button.
You will see the full request when hovering the URL
GET 
http://localhost/cgi-bin/accidentes?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=Estaciones%20Tren%20Ligero%20-%20Tipo&CRS=EPSG%3A4326&STYLES=&WIDTH=2025&HEIGHT=962&BBOX=20.624878406524658%2C-103.43881130218506%2C20.707404613494873%2C-103.26500415802002
 [HTTP/1.1 200 OK 361ms]

  From: "Lime, Steve D (MNIT)" 
 To: Carlos Ruiz ; "mapserver-users@lists.osgeo.org" 

 Sent: Thursday, February 18, 2016 3:06 PM
 Subject: RE: [mapserver-users] WFS Client...

#yiv8480966943 #yiv8480966943 -- _filtered #yiv8480966943 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv8480966943 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv8480966943 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv8480966943 
#yiv8480966943 p.yiv8480966943MsoNormal, #yiv8480966943 
li.yiv8480966943MsoNormal, #yiv8480966943 div.yiv8480966943MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv8480966943 a:link, 
#yiv8480966943 span.yiv8480966943MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv8480966943 a:visited, #yiv8480966943 
span.yiv8480966943MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv8480966943 
p.yiv8480966943msonormal, #yiv8480966943 li.yiv8480966943msonormal, 
#yiv8480966943 div.yiv8480966943msonormal 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv8480966943 
p.yiv8480966943msochpdefault, #yiv8480966943 li.yiv8480966943msochpdefault, 
#yiv8480966943 div.yiv8480966943msochpdefault 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv8480966943 
span.yiv8480966943msohyperlink {}#yiv8480966943 
span.yiv8480966943msohyperlinkfollowed {}#yiv8480966943 
span.yiv8480966943emailstyle17 {}#yiv8480966943 p.yiv8480966943msonormal1, 
#yiv8480966943 li.yiv8480966943msonormal1, #yiv8480966943 
div.yiv8480966943msonormal1 
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;}#yiv8480966943 
span.yiv8480966943msohyperlink1 
{color:#0563C1;text-decoration:underline;}#yiv8480966943 
span.yiv8480966943msohyperlinkfollowed1 
{color:#954F72;text-decoration:underline;}#yiv8480966943 
span.yiv8480966943emailstyle171 {color:windowtext;}#yiv8480966943 
p.yiv8480966943msochpdefault1, #yiv8480966943 li.yiv8480966943msochpdefault1, 
#yiv8480966943 div.yiv8480966943msochpdefault1 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv8480966943 
span.yiv8480966943EmailStyle27 {color:#1F497D;}#yiv8480966943 
.yiv8480966943MsoChpDefault {font-size:10.0pt;} _filtered #yiv8480966943 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv8480966943 div.yiv8480966943WordSection1 
{}#yiv8480966943 The WFS server is not under my control, so no access log.    
From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Thursday, February 18, 2016 3:06 PM
To: Lime, Steve D (MNIT) ; 
mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WFS Client...    Steve,    You can check the 
Apache "access.log" file and watch for the HTTP GET requests. You will find 
something like this:

 127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412       From: "Lime, Steve D (MNIT)" 
To: "mapserver-users@lists.osgeo.org" 
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...    Hi all: Is there any way to log the 
request URL and POST data associated with MapServer WFS layers? That info 
doesn’t seem to be showing up in debug logs and it would be helpful to see 
exactly what is being sent to the WFS server.   Steve 
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users 

  ___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Lime, Steve D (MNIT)

I don’t know if mapserver is issuing POSTs or GETs under the hood, haven’t 
checked the code, but capturing both in the mapserver logs would be helpful.

From: Rahkonen Jukka (MML) [mailto:jukka.rahko...@maanmittauslaitos.fi]
Sent: Thursday, February 18, 2016 3:15 PM
To: Carlos Ruiz ; Lime, Steve D (MNIT) 
; mapserver-users@lists.osgeo.org
Subject: RE: [mapserver-users] WFS Client...

Hi,

Didn’t he ask about the contents of POST, not GET? That would need some extra 
components, some hints can be found from 
http://stackoverflow.com/questions/989967/best-way-to-log-post-data-in-apache.

Actually it would be very useful to have an option to write the POST requests 
into Mapserver log file.

-Jukka Rahkonen-

Carlos Ruiz wrote:

Steve,

You can check the Apache "access.log" file and watch for the HTTP GET requests. 
You will find something like this:

127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412

From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: "mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn’t seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Rahkonen Jukka (MML)

Hi,

Didn’t he ask about the contents of POST, not GET? That would need some extra 
components, some hints can be found from 
http://stackoverflow.com/questions/989967/best-way-to-log-post-data-in-apache.

Actually it would be very useful to have an option to write the POST requests 
into Mapserver log file.

-Jukka Rahkonen-

Carlos Ruiz wrote:


Steve,

You can check the Apache "access.log" file and watch for the HTTP GET requests. 
You will find something like this:



127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412



From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: "mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn’t seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client...

2016-02-18 Thread Lime, Steve D (MNIT)

The WFS server is not under my control, so no access log.

From: Carlos Ruiz [mailto:boolean10...@yahoo.com]
Sent: Thursday, February 18, 2016 3:06 PM
To: Lime, Steve D (MNIT) ; 
mapserver-users@lists.osgeo.org
Subject: Re: [mapserver-users] WFS Client...

Steve,

You can check the Apache "access.log" file and watch for the HTTP GET requests. 
You will find something like this:

127.0.0.1 - - [16/Dec/2015:16:59:31 -0600] "GET 
/cgi-bin/landsat8?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image%2Fpng&TRANSPARENT=true&LAYERS=2014&WIDTH=256&HEIGHT=256&CRS=EPSG%3A4326&STYLES=&BBOX=22.5%2C-101.25%2C33.75%2C-90
 HTTP/1.1" 200 412

From: "Lime, Steve D (MNIT)" 
mailto:steve.l...@state.mn.us>>
To: "mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>" 
mailto:mapserver-users@lists.osgeo.org>>
Sent: Thursday, February 18, 2016 3:01 PM
Subject: [mapserver-users] WFS Client...

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn’t seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org<mailto:mapserver-users@lists.osgeo.org>
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS Client...

2016-02-18 Thread Lime, Steve D (MNIT)

Hi all: Is there any way to log the request URL and POST data associated with 
MapServer WFS layers? That info doesn't seem to be showing up in debug logs and 
it would be helpful to see exactly what is being sent to the WFS server.

Steve
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [WFS-client] geometry name

2012-09-20 Thread Rahkonen Jukka

Hi,

That's very limiting. I think that none of the more than 80 feature types on my 
server is using name "Geometry".  suggest you to file a ticket about making 
this configurable.

-Jukka Rahkonen-

Yves Jacolin wrote:

Hello,

Ok I find the answer: Geometry column name is hardcoded in 
https://github.com/mapserver/mapserver/blob/master/mapwfslayer.c#L242

Y.
2012/9/19 Yves Jacolin 
mailto:yves.jaco...@camptocamp.com>>
Hello,

There is not possiblity? Documentation tell nothing about the possibility to 
tell to MapServer the geometry column name to the WFS service used for my layer 
and I can't change the geometry name server side.

Nobody already fall in this issue?

Thanks,

Y.

2012/9/19 Yves Jacolin 
mailto:yves.jaco...@camptocamp.com>>
Hello,

Does it possible to tell MapServer the geometry name to use for a layer in the 
case of WFS CONNECTIONTYPE?

By default, Mapserver use "Geometry", for example:


  Geometry
  2.022184,48.116468
3.923033,49.118807


Thanks,

Y.
--
Responsable Formation et Support
Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac, Cedex
Tel (France) : +33 4 79 26 57 98
Mob. : +33 6 18 75 42 21
Fax : 04 79 70 15 81
Mail : yves.jaco...@camptocamp.com
http://www.camptocamp.com



--

Responsable Formation et Support

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac, Cedex

Tel (France) : +33 4 79 26 57 98

Mob. : +33 6 18 75 42 21

Fax : 04 79 70 15 81

Mail : yves.jaco...@camptocamp.com

http://www.camptocamp.com




--

Responsable Formation et Support

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac, Cedex

Tel (France) : +33 4 79 26 57 98

Mob. : +33 6 18 75 42 21

Fax : 04 79 70 15 81

Mail : yves.jaco...@camptocamp.com

http://www.camptocamp.com

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [WFS-client] geometry name

2012-09-20 Thread Yves Jacolin

Hello,

Ok I find the answer: Geometry column name is hardcoded in
https://github.com/mapserver/mapserver/blob/master/mapwfslayer.c#L242

Y.

2012/9/19 Yves Jacolin 

> Hello,
>
> There is not possiblity? Documentation tell nothing about the possibility
> to tell to MapServer the geometry column name to the WFS service used for
> my layer and I can't change the geometry name server side.
>
> Nobody already fall in this issue?
>
> Thanks,
>
> Y.
>
>
> 2012/9/19 Yves Jacolin 
>
>> Hello,
>>
>> Does it possible to tell MapServer the geometry name to use for a layer
>> in the case of WFS CONNECTIONTYPE?
>>
>> By default, Mapserver use "Geometry", for example:
>>
>> 
>>   Geometry
>>   2.**022184,48.116468
>> 3.923033,49.118807
>> 
>>
>> Thanks,
>>
>> Y.
>> --
>> Responsable Formation et Support
>> Camptocamp France SAS
>> Savoie Technolac, BP 352
>> 73377 Le Bourget du Lac, Cedex
>> Tel (France) : +33 4 79 26 57 98
>> Mob. : +33 6 18 75 42 21
>> Fax : 04 79 70 15 81
>> Mail : yves.jaco...@camptocamp.com
>> http://www.camptocamp.com
>>
>
>
>
> --
>
> Responsable Formation et Support
>
> Camptocamp France SAS
>
> Savoie Technolac, BP 352
>
> 73377 Le Bourget du Lac, Cedex
>
> Tel (France) : +33 4 79 26 57 98
>
> Mob. : +33 6 18 75 42 21
>
> Fax : 04 79 70 15 81
>
> Mail : yves.jaco...@camptocamp.com
>
> http://www.camptocamp.com
> 
>



-- 

Responsable Formation et Support

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac, Cedex

Tel (France) : +33 4 79 26 57 98

Mob. : +33 6 18 75 42 21

Fax : 04 79 70 15 81

Mail : yves.jaco...@camptocamp.com

http://www.camptocamp.com

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [WFS-client] geometry name

2012-09-19 Thread Yves Jacolin

Hello,

There is not possiblity? Documentation tell nothing about the possibility
to tell to MapServer the geometry column name to the WFS service used for
my layer and I can't change the geometry name server side.

Nobody already fall in this issue?

Thanks,

Y.

2012/9/19 Yves Jacolin 

> Hello,
>
> Does it possible to tell MapServer the geometry name to use for a layer in
> the case of WFS CONNECTIONTYPE?
>
> By default, Mapserver use "Geometry", for example:
>
> 
>   Geometry
>   2.**022184,48.116468
> 3.923033,49.118807
> 
>
> Thanks,
>
> Y.
> --
> Responsable Formation et Support
> Camptocamp France SAS
> Savoie Technolac, BP 352
> 73377 Le Bourget du Lac, Cedex
> Tel (France) : +33 4 79 26 57 98
> Mob. : +33 6 18 75 42 21
> Fax : 04 79 70 15 81
> Mail : yves.jaco...@camptocamp.com
> http://www.camptocamp.com
>



-- 

Responsable Formation et Support

Camptocamp France SAS

Savoie Technolac, BP 352

73377 Le Bourget du Lac, Cedex

Tel (France) : +33 4 79 26 57 98

Mob. : +33 6 18 75 42 21

Fax : 04 79 70 15 81

Mail : yves.jaco...@camptocamp.com

http://www.camptocamp.com

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] [WFS-client] geometry name

2012-09-19 Thread Yves Jacolin


Hello,

Does it possible to tell MapServer the geometry name to use for a layer 
in the case of WFS CONNECTIONTYPE?


By default, Mapserver use "Geometry", for example:


  Geometry
  2.022184,48.116468
3.923033,49.118807


Thanks,

Y.
--
Responsable Formation et Support
Camptocamp France SAS
Savoie Technolac, BP 352
73377 Le Bourget du Lac, Cedex
Tel (France) : +33 4 79 26 57 98
Mob. : +33 6 18 75 42 21
Fax : 04 79 70 15 81
Mail : yves.jaco...@camptocamp.com
http://www.camptocamp.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS Client through Proxy and HTTP Authentication

2011-08-09 Thread Daniel Morissette


The error message says:

"Couldn't resolve host 'reg.bom.gov.au'"

Make sure this hostname does resolve on the machine running MapServer, 
that is has proper DNS config, etc.


You could also try using the actual IP address instead of the hostname 
in the CONNECTION string to confirm that this is indeed the problem.


Daniel

On 11-08-09 09:10 PM, bte...@gmail.com wrote:

Hi,

I have MapServer 5.6.0 running on RHEL5.5 (FGS9.5 MapServer package)

I'm behind a proxy (NTLM), and I want to access a WFS source outside that
requires HTTP Authentication.  I'm using a WFS Client setup in my Map file,
and I'm accessing my MapServer using WFS too - eg. a WFS Client... all up a
sort of WFS Relay.

I can do it fine with WMS, however, I can't get it to work with WFS - is it
actually supposed to work?  (not documented in the manual.)  I tried using
"ows_" prefixed METADATA which works fine with WMS (to the same service.)

Here's my map file extract:
LAYER
   NAME "TempDryBulb"
   TYPE RASTER
   STATUS ON
   DEBUG ON
   CONNECTIONTYPE WMS
   CONNECTION "http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?";
   METADATA
 # Source Data
 "wfs_connectiontimeout" "30"
 "wfs_maxfeatures" "10"
 "wfs_typename" "IDY03103_dryblb"
 "wfs_version" "1.0.0"
 "wfs_srs" "EPSG:4283"

 # Source Auth
 "ows_auth_username" "mybomuser"
 "ows_auth_password" "{secrethere}"
 "ows_auth_type" "basic"

 # EDN Proxy Auth
 "ows_proxy_auth_type" "ntlm"
 "ows_proxy_host" "httpgw.mycompany.com.au"
 "ows_proxy_port" "8080"
 "ows_proxy_type" "http"
 "ows_proxy_username" "myuser"
 "ows_proxy_password" "{secrethere}"

 # Layer Outgoing Metadata
 "wfs_title" "TempDryBulbWFS"
   END # METADATA
...

Here's my errors:
[Tue Aug  9 14:01:18 2011].368922 HTTP: Starting to prepare HTTP requests.
[Tue Aug  9 14:01:18 2011].369001 Using
CURL_CA_BUNDLE=/home/maptools/fgs/share/curl/cacert.pem
[Tue Aug  9 14:01:18 2011].369101 HTTP request: id=0,
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?
[Tue Aug  9 14:01:18 2011].369260 HTTP: Before download loop
[Tue Aug  9 14:01:18 2011].373358 HTTP: After download loop
[Tue Aug  9 14:01:18 2011].373370 msHTTPExecuteRequests() timing summary per
layer (connect_time + time_to_first_packet + download_time = total_time in
seconds)
[Tue Aug  9 14:01:18 2011].373378 HTTP: request failed with curl error code
6 (Couldn't resolve host 'reg.bom.gov.au') for
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?[Tue Aug  9
14:01:18 2011].373387 msHTTPExecuteRequests(): HTTP request error. HTTP:
request failed with curl error code 6 (Couldn't resolve host
'reg.bom.gov.au') for
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?
[Tue Aug  9 14:01:18 2011].373414 Layer 0: 0.000 + 0.000 + 0.000 = 0.000s
[Tue Aug  9 14:01:18 2011].373584 msWFSLayerWhichShapes(): WFS connection
error. Got HTTP status -6 downloading WFS layer TempDryBulbWFS
[Tue Aug  9 14:01:18 2011].374109 msWFSLayerWhichShapes(): WFS connection
error. Got HTTP status -6 downloading WFS layer TempDryBulbWFS
[Tue Aug  9 14:01:18 2011].374124 msWFSGetFeature(): WFS server error.
ms_error->code not found

Note: I used msencrypt for the passwords, and these did work fine for WMS.

Note2: using wget or curl from the command line on the server works fine
(with the proxy credentials specified.)

Thanks in advance!
Regards, Bill Teluk

-
Regards, Bill Teluk
--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/WFS-Client-through-Proxy-and-HTTP-Authentication-tp6670451p6670451.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users



--
Daniel Morissette
http://www.mapgears.com/
Provider of Professional MapServer Support since 2000

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS Client through Proxy and HTTP Authentication

2011-08-09 Thread bte...@gmail.com

Hi, 

I have MapServer 5.6.0 running on RHEL5.5 (FGS9.5 MapServer package) 

I'm behind a proxy (NTLM), and I want to access a WFS source outside that
requires HTTP Authentication.  I'm using a WFS Client setup in my Map file,
and I'm accessing my MapServer using WFS too - eg. a WFS Client... all up a
sort of WFS Relay. 

I can do it fine with WMS, however, I can't get it to work with WFS - is it
actually supposed to work?  (not documented in the manual.)  I tried using
"ows_" prefixed METADATA which works fine with WMS (to the same service.)

Here's my map file extract: 
LAYER 
  NAME "TempDryBulb" 
  TYPE RASTER 
  STATUS ON 
  DEBUG ON 
  CONNECTIONTYPE WMS 
  CONNECTION "http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?"; 
  METADATA 
# Source Data 
"wfs_connectiontimeout" "30" 
"wfs_maxfeatures" "10" 
"wfs_typename" "IDY03103_dryblb" 
"wfs_version" "1.0.0" 
"wfs_srs" "EPSG:4283" 

# Source Auth 
"ows_auth_username" "mybomuser" 
"ows_auth_password" "{secrethere}" 
"ows_auth_type" "basic" 

# EDN Proxy Auth 
"ows_proxy_auth_type" "ntlm" 
"ows_proxy_host" "httpgw.mycompany.com.au" 
"ows_proxy_port" "8080" 
"ows_proxy_type" "http" 
"ows_proxy_username" "myuser" 
"ows_proxy_password" "{secrethere}" 

# Layer Outgoing Metadata 
"wfs_title" "TempDryBulbWFS" 
  END # METADATA 
... 

Here's my errors: 
[Tue Aug  9 14:01:18 2011].368922 HTTP: Starting to prepare HTTP requests. 
[Tue Aug  9 14:01:18 2011].369001 Using
CURL_CA_BUNDLE=/home/maptools/fgs/share/curl/cacert.pem 
[Tue Aug  9 14:01:18 2011].369101 HTTP request: id=0,
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs? 
[Tue Aug  9 14:01:18 2011].369260 HTTP: Before download loop 
[Tue Aug  9 14:01:18 2011].373358 HTTP: After download loop 
[Tue Aug  9 14:01:18 2011].373370 msHTTPExecuteRequests() timing summary per
layer (connect_time + time_to_first_packet + download_time = total_time in
seconds) 
[Tue Aug  9 14:01:18 2011].373378 HTTP: request failed with curl error code
6 (Couldn't resolve host 'reg.bom.gov.au') for
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs?[Tue Aug  9
14:01:18 2011].373387 msHTTPExecuteRequests(): HTTP request error. HTTP:
request failed with curl error code 6 (Couldn't resolve host
'reg.bom.gov.au') for
http://reg.bom.gov.au/cgi-bin/reg/ws/gis/users/bomg0022/wxs? 
[Tue Aug  9 14:01:18 2011].373414 Layer 0: 0.000 + 0.000 + 0.000 = 0.000s 
[Tue Aug  9 14:01:18 2011].373584 msWFSLayerWhichShapes(): WFS connection
error. Got HTTP status -6 downloading WFS layer TempDryBulbWFS 
[Tue Aug  9 14:01:18 2011].374109 msWFSLayerWhichShapes(): WFS connection
error. Got HTTP status -6 downloading WFS layer TempDryBulbWFS 
[Tue Aug  9 14:01:18 2011].374124 msWFSGetFeature(): WFS server error.
ms_error->code not found 

Note: I used msencrypt for the passwords, and these did work fine for WMS. 

Note2: using wget or curl from the command line on the server works fine
(with the proxy credentials specified.)

Thanks in advance! 
Regards, Bill Teluk

-
Regards, Bill Teluk
--
View this message in context: 
http://osgeo-org.1803224.n2.nabble.com/WFS-Client-through-Proxy-and-HTTP-Authentication-tp6670451p6670451.html
Sent from the Mapserver - User mailing list archive at Nabble.com.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] wfs client question

2008-12-08 Thread Knut Behrends

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Thanks guys, the on-the-fly transforms
seem to work now. Indeed,
the PROJECTION entries in the MAP and in the LAYER sections must be
specified exactly as Bart said.
And I'll also get a copy of the proj4js Library, it might come in handy
someday.
- --


Knut Behrends Phone: +49 (0) 331 288 1688
Potsdam 14473 KeyID: 0xF22CACEF (PGP Public Key)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk9LOUACgkQcfWHNfIsrO8rYQCfRfE06clsp5Qegb2F3O3++tI8
oq4An12rMjedfkV2/mguzmdYOeE8PJRI
=sgwF
-END PGP SIGNATURE-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] wfs client question

2008-12-08 Thread bartvde

Hi Knut,

Mapserver should be able to do this for you.

Just use wfs_srs "EPSG:31468" on your CONNECTIONTYPE WFS layer, and maybe
add a PROJECTION block as well on the LAYER:

  PROJECTION
"init=epsg:31468"
  END

On your MAP object you can use:

  PROJECTION
"init=epsg:4326"
  END

Mapserver should reproject the coordinates before doing the WFS request.

If you want to do this in javascript instead I would recommend using proj4js:

http://proj4js.org/

Best regards,
Bart

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I want to query a public wfs server for some data.
> Internally, in my DHTML frontend, all lat/lon coordinates are handled in
> geographic coordinates EPSG:4326.
> However, the WFS server only accepts lat/lon values given with
> particular BBOX parameters specified in EPSG:31468, presumably.
>
> Hence, I think that before the making the request for the external WFS
> data, I need to convert the geographic EPSG:4326 coordinates to
> EPSG:31468 on the fly.
>
> What is the best way to do this?
>
> - - in javascript, on the frontend side?
>   -- using ajax requests?
>   -- or is there a recommended JS library for coordinate transforms?
>
> - - or on the the wfs client side, i.e. where my mapserver cgi is hosted ?
> Manipulating the cgi parameters somehow, before the request is sent out
> to the WFS server?
>
>
> Or am I did I get something wrong about the WFS specification?
> This is the first time I interact with a WFS, so please help me out
> someone...
>
>
> Knut
>
> - --
> 
>
> Knut Behrends Phone: +49 (0) 331 288 1688
> Potsdam 14473 KeyID: 0xF22CACEF (PGP Public Key)
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkk9CWQACgkQcfWHNfIsrO/HGACgn6RrH3kRgRSHt0G2UsiB/pEH
> c8wAn1KzH6ACLag6JTaY3ffOejXgqEqD
> =L5Fx
> -END PGP SIGNATURE-
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] wfs client question

2008-12-08 Thread Knut Behrends

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I want to query a public wfs server for some data.
Internally, in my DHTML frontend, all lat/lon coordinates are handled in
geographic coordinates EPSG:4326.
However, the WFS server only accepts lat/lon values given with
particular BBOX parameters specified in EPSG:31468, presumably.

Hence, I think that before the making the request for the external WFS
data, I need to convert the geographic EPSG:4326 coordinates to
EPSG:31468 on the fly.

What is the best way to do this?

- - in javascript, on the frontend side?
  -- using ajax requests?
  -- or is there a recommended JS library for coordinate transforms?

- - or on the the wfs client side, i.e. where my mapserver cgi is hosted ?
Manipulating the cgi parameters somehow, before the request is sent out
to the WFS server?


Or am I did I get something wrong about the WFS specification?
This is the first time I interact with a WFS, so please help me out
someone...


Knut

- --


Knut Behrends Phone: +49 (0) 331 288 1688
Potsdam 14473 KeyID: 0xF22CACEF (PGP Public Key)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkk9CWQACgkQcfWHNfIsrO/HGACgn6RrH3kRgRSHt0G2UsiB/pEH
c8wAn1KzH6ACLag6JTaY3ffOejXgqEqD
=L5Fx
-END PGP SIGNATURE-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS client layer not drawn: missing .gfs file?

2008-10-27 Thread Michael Schulz

Hi Frank,

thanks for your comments that made me put ms_debug all thru the code ;-)

The problem is on my and/or mapservers side... The wfs getfeature
response I'm consuming has the namespace location for gml also
attached to the first featureMember tag (don't ask me why ... though i
think this is not really an error):
- msWFSLayerWhichShapes in mapwfslayer.c around line 1035 initializes
the char array szHeader[2000] and reads the getfeature response,
- then some tests search thru this array, e.g. checking whether it is
valid gml but no featureMembers,
- because the first featureMember tag has the namespace attribute
(http://www.opengis.net/gml";>) it does
not get caught by the test "strstr(szHeader,"featureMember>") == NULL"
in line 1067 (the ">" is the culprit), and then because there are a
lot of attributes for the featuretype the closing featureMember tag is
not included anymore in the szHeader array and we're done thinking we
have gml but no results ...

Well, not sure what to do, at the moment it works by removing the ">"
from the tests. But what a final solution might look like? Increase
size of szheader?

Cheers and thanks, Michael




2008/10/27 Frank Warmerdam <[EMAIL PROTECTED]>:
> Michael Schulz wrote:
>>
>> Hi,
>>
>> I have a problem with gml reading/writing when used in an umn
>> mapserver environment: I have a mapserver WFS client layer, that is
>> not displayed when the getfeature response of the remote wfs-server
>> has too many featuretype attributes. If I reduce the number of
>> attributes in the featuretype the layer gets drawn correctly.
>> Apparently at a certain amount of attribute fields (>15 non-geometry
>> attributes) the layer is not drawn anymore.
>>
>> The interesting thing is, that when the layer gets drawn, the .tmp.gml
>> and tmp.gfs files are created normally in mapservers tmp dir. When it
>> is not drawn only the .tmp.gml is present. I have tested it with an
>> older gdal/ogr version (1.3.2) but also with the latest (1.5.3) one.
>> When i run "ogr2ogr -f "GML" new.gml
>> umn_wfslayer_lot_of_attributes.tmp.gml " then new.gml and new.xsd are
>> created without problems.
>
> Michael,
>
> I'm quite surprised.  So you are saying that ogr2ogr can read the GML
> file but MapServer cannot?  Are you convinced that the new.gml is
> correct?  Are you sure that your MapServer tests really used 1.3.2 and
> 1.5.3?
>
> I would be interested in testing with a GML file with "too many attributes
> to read" with MapServer though if the commandline tools are working fine
> against it there may be little I can learn.
>
>> Is it normal that the ogr gml reader/writer uses the older .gfs format
>> when used in mapserver environment and the .xsd format when invoked
>> from the command line?
>
> Modern OGR versions create the .xsd when writing GML datasets in
> a simplified GML profile.  But when reading foreign datasets a gfs
> file is used to cache information on the GML schema, feature count,
> and extents.  So, essentially this is normal behavior.
>
> Best regards,
> --
> ---+--
> I set the clouds in motion - turn up   | Frank Warmerdam,
> [EMAIL PROTECTED]
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush| Geospatial Programmer for Rent
>
>



-- 
---
Michael Schulz
[EMAIL PROTECTED]

in medias res
Gesellschaft für Informationstechnologie mbH

In den Weihermatten 66
79108 Freiburg

Tel  +49 (0)761 556959-5
Fax +49 (0)761 556959-6

http://www.webgis.de / http://www.zopecms.de
---
Geschäftsführer: Stefan Giese, Dr. Christof Lindenbeck
Eingetragen im Handelsregister HRB 5930 beim Amtsgericht Freiburg
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] WFS client layer not drawn: missing .gfs file?

2008-10-27 Thread Frank Warmerdam


Michael Schulz wrote:

Hi,

I have a problem with gml reading/writing when used in an umn
mapserver environment: I have a mapserver WFS client layer, that is
not displayed when the getfeature response of the remote wfs-server
has too many featuretype attributes. If I reduce the number of
attributes in the featuretype the layer gets drawn correctly.
Apparently at a certain amount of attribute fields (>15 non-geometry
attributes) the layer is not drawn anymore.

The interesting thing is, that when the layer gets drawn, the .tmp.gml
and tmp.gfs files are created normally in mapservers tmp dir. When it
is not drawn only the .tmp.gml is present. I have tested it with an
older gdal/ogr version (1.3.2) but also with the latest (1.5.3) one.
When i run "ogr2ogr -f "GML" new.gml
umn_wfslayer_lot_of_attributes.tmp.gml " then new.gml and new.xsd are
created without problems.


Michael,

I'm quite surprised.  So you are saying that ogr2ogr can read the GML
file but MapServer cannot?  Are you convinced that the new.gml is
correct?  Are you sure that your MapServer tests really used 1.3.2 and
1.5.3?

I would be interested in testing with a GML file with "too many attributes
to read" with MapServer though if the commandline tools are working fine
against it there may be little I can learn.


Is it normal that the ogr gml reader/writer uses the older .gfs format
when used in mapserver environment and the .xsd format when invoked
from the command line?


Modern OGR versions create the .xsd when writing GML datasets in
a simplified GML profile.  But when reading foreign datasets a gfs
file is used to cache information on the GML schema, feature count,
and extents.  So, essentially this is normal behavior.

Best regards,
--
---+--
I set the clouds in motion - turn up   | Frank Warmerdam, [EMAIL PROTECTED]
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush| Geospatial Programmer for Rent

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS client layer not drawn: missing .gfs file?

2008-10-27 Thread Michael Schulz

Hi,

I have a problem with gml reading/writing when used in an umn
mapserver environment: I have a mapserver WFS client layer, that is
not displayed when the getfeature response of the remote wfs-server
has too many featuretype attributes. If I reduce the number of
attributes in the featuretype the layer gets drawn correctly.
Apparently at a certain amount of attribute fields (>15 non-geometry
attributes) the layer is not drawn anymore.

The interesting thing is, that when the layer gets drawn, the .tmp.gml
and tmp.gfs files are created normally in mapservers tmp dir. When it
is not drawn only the .tmp.gml is present. I have tested it with an
older gdal/ogr version (1.3.2) but also with the latest (1.5.3) one.
When i run "ogr2ogr -f "GML" new.gml
umn_wfslayer_lot_of_attributes.tmp.gml " then new.gml and new.xsd are
created without problems.

Is it normal that the ogr gml reader/writer uses the older .gfs format
when used in mapserver environment and the .xsd format when invoked
from the command line?

TIA, Michael

-- 
---
Michael Schulz
[EMAIL PROTECTED]

in medias res
Gesellschaft für Informationstechnologie mbH

In den Weihermatten 66
79108 Freiburg

Tel  +49 (0)761 556959-5
Fax +49 (0)761 556959-6

http://www.webgis.de / http://www.zopecms.de
---
Geschäftsführer: Stefan Giese, Dr. Christof Lindenbeck
Eingetragen im Handelsregister HRB 5930 beim Amtsgericht Freiburg
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

RE: [mapserver-users] WFS-Client layer without style/legend block inWMS-capabilities

2008-10-27 Thread Kralidis,Tom [Ontario]

 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> Michael Schulz
> Sent: Monday, October 27, 2008 6:11 AM
> To: mapserver-users@lists.osgeo.org
> Subject: [mapserver-users] WFS-Client layer without 
> style/legend block inWMS-capabilities
> 
> Hi,
> 
> I found that when using mapserver 5.2 as wms-server and I 
> want to display a layer that connects to a wfs, the resulting 
> capabilities for that layer do not contain a style/legend 
> block. The getlegendgraphic request works without problems. 
> Just changing the layers connectiontype to sth. else, e.g. 
> postgis, results in a correct style/layer block in the 
> capabilities. Can someone reproduce this behaviour?
> 

I can reproduce this behaviour.  If you can file a ticket, and possibly
include a small testcase, that would be much appreciated.

Thanks

..Tom
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] WFS-Client layer without style/legend block in WMS-capabilities

2008-10-27 Thread Michael Schulz

Hi,

I found that when using mapserver 5.2 as wms-server and I want to
display a layer that connects to a wfs, the resulting capabilities for
that layer do not contain a style/legend block. The getlegendgraphic
request works without problems. Just changing the layers
connectiontype to sth. else, e.g. postgis, results in a correct
style/layer block in the capabilities. Can someone reproduce this
behaviour?

Cheers, Michael

-- 
---
Michael Schulz
[EMAIL PROTECTED]

in medias res
Gesellschaft für Informationstechnologie mbH

In den Weihermatten 66
79108 Freiburg

Tel  +49 (0)761 556959-5
Fax +49 (0)761 556959-6

http://www.webgis.de / http://www.zopecms.de
---
Geschäftsführer: Stefan Giese, Dr. Christof Lindenbeck
Eingetragen im Handelsregister HRB 5930 beim Amtsgericht Freiburg
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

53 matches

Mail list logo