[mapserver-users] mapserver OGR does not forward BBOX at all
Scott
public at postholer.com
Tue Mar 29 07:05:57 PDT 2022
In your request you have a typeName=tiger:tigerRoads. In your map file
the wfs_typename is GROUND_REFERENCE_VALUES_NI_int
On 3/29/22 01:17, Lars Fricke wrote:
> Hi,
> thank you for the fast reply. Unfortunately, even with the srs given
> with the bbox the "Fetch" command does not forward any bbox at all. So
> mapserver / OGR fetches up to the max number of features given no matter
> where they are located. They are then filtered out by mapserver using
> the original bbox because they do not fit (just the first 500 or so).
>
> Mapfile layer definition (sorry I forgot):
> LAYER
> NAME "GROUND_REFERENCE_VALUES_NI"
> UNITS METERS
> TYPE POLYGON
> DEBUG "5"
> CONNECTION "ground_reference_values_ni.xml"
> CONNECTIONTYPE OGR
> STATUS ON
> DATA "boris:BR_BodenrichtwertZonal"
> METADATA
> "wfs_srs" "EPSG:25832"
> "wfs_version" "1.1.0"
> "wfs_storedquery_id" ""
> "wfs_title" "GROUND_REFERENCE_VALUES_NI"
> "wfs_connectiontimeout" "30"
> "wfs_typename" "GROUND_REFERENCE_VALUES_NI_int"
> "wfs_maxfeatures" "500"
> "gml_include_items" "all"
> "wfs_enable_request" "*"
> "gml_featureid" "gml_id"
>
> END # METADATA
>
> PROJECTION
> "init=epsg:25832"
> END # PROJECTION
> CLASS
> NAME "reference_map"
> STYLE
> OUTLINECOLOR 255 0 0
> WIDTH 0.7
> END # STYLE
> END # CLASS
> END # LAYER
>
> The XML file referenced is in attach.
>
> Best
> Lars
>
> Am 29.03.22 um 10:06 schrieb artclifford at gmail.com:
>>
>> Hi Lars,
>>
>> Might this help?
>>
>> geoserver - WFS and WMS query SRS parameter and BBOX usage -
>> Geographic Information Systems Stack Exchange
>> <https://gis.stackexchange.com/questions/225535/wfs-and-wms-query-srs-parameter-and-bbox-usage>
>>
>> I haven’t done much with the WFS tech but based on the link above, you
>> may need to provide the crs info for the bbox.
>>
>> In their example:
>>
>> http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&srsName=EPSG:3857&bbox=40.7,-74,40.8,-73,urn:ogc:def:crs:EPSG:4326&maxFeatures=1
>> <http://demo.geo-solutions.it/geoserver/tiger/ows?service=WFS&version=1.1.0&request=GetFeature&typeName=tiger:tiger_roads&srsName=EPSG:3857&bbox=40.7,-74,40.8,-73,urn:ogc:def:crs:EPSG:4326&maxFeatures=1>
>>
>> Note the bbox is defined as:
>> bbox=40.7,-74,40.8,-73,urn:ogc:def:crs:EPSG:4326
>>
>>
>> If your bbox is the same as the requested projection:
>> your bbox in the wfs request would be:
>>
>> BBOX=545592,5806696,548144,5810131,urn:ogc:def:crs: EPSG:25832
>>
>> Or the epsg code at the end would be whatever units your bbox is in.
>> Note, the bbox EPSG code can be different than the srsName
>>
>>
>>
>> *From:* MapServer-users <mapserver-users-bounces at lists.osgeo.org> *On
>> Behalf Of *Lars Fricke
>> *Sent:* Tuesday, March 29, 2022 12:31 AM
>> *To:* mapserver-users at lists.osgeo.org
>> *Subject:* [mapserver-users] mapserver OGR does not forward BBOX at all
>>
>> Hi All,
>>
>> First of all, thank you for your support and great work on Mapserver!
>>
>> I have a strange issue using either OGR WFS driver on Mapserver
>> 7.6.4-1 or ogrinfo (GDAL 3.0.4, released 2020/01/28) on Ubuntu 20.
>>
>> When I call on a particular public server, mapserver / gdal / ogr does
>> not seem to forward the bbox. I had a similar issue before (over a
>> year ago) on another server but this was fixed by an update in GDAL it
>> seemed.
>>
>> The Server is
>>
>> `https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022?`
>>
>> The Layer is
>> `boris:BR_BodenrichtwertZonal`
>>
>> A direct call from the browser works:
>>
>> `https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:25832&BBOX=545592,5806696,548144,5810131&TYPENAMES=boris:BR_BodenrichtwertZonal
>> <https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022?SERVICE=WFS&VERSION=2.0.0&REQUEST=GetFeature&SRSNAME=EPSG:25832&BBOX=545592,5806696,548144,5810131&TYPENAMES=boris:BR_BodenrichtwertZonal>`
>>
>> I can see in Mapserver log (CONFIG "CPL_DEBUG" "ON" CONFIG
>> "PROJ_DEBUG" "ON") that the BBOX is missing:
>>
>> `Fetch(https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=500&SRSNAME=EPSG:25832&TRUST_CAPABILITIES_BOUNDS=YES&REQUEST=GetFeature&TYPENAME=boris:BR_BodenrichtwertZonal
>> <https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022?SERVICE=WFS&VERSION=1.1.0&MAXFEATURES=500&SRSNAME=EPSG:25832&TRUST_CAPABILITIES_BOUNDS=YES&REQUEST=GetFeature&TYPENAME=boris:BR_BodenrichtwertZonal>)`
>>
>> By the way, it does not matter if WFS 1.1.0 or 2.0.0 are used.
>>
>> Trying with ogrinfo:
>> ```
>> ogrinfo -ro -spat 545592 5806696 548144 5810131
>> WFS:"https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022"
>> <https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022>
>> "boris:BR_BodenrichtwertZonal"
>>
>> INFO: Open of
>> `WFS:https://www.geobasisdaten.niedersachsen.de/doorman/noauth/WFS_boris_2022'
>> using driver `WFS' successful.
>> Metadata:
>> ABSTRACT=BORIS 2022 WFS by XtraServer
>> PROVIDER_NAME=Landesamt für Geoinformation und Landesvermessung
>> Niedersachsen (LGLN) - Landesbetrieb Landesvermessung und
>> Geobasisinformation
>> TITLE=BORIS 2022 WFS
>> ERROR 1: No schema information loaded
>> Warning 1: NAS: Skipping geometry without feature
>>
>> Layer name: boris:BR_BodenrichtwertZonal
>> Metadata:
>> TITLE=boris_BR_BodenrichtwertZonal
>> Geometry: None
>> Feature Count: 33931
>> ```
>> There should be some 62 Features in that bbox.
>>
>> Any help is much appreciated.
>>
>> Best
>>
>> Lars
>>
>
>
> _______________________________________________
> MapServer-users mailing list
> MapServer-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
More information about the MapServer-users
mailing list