WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573

nmtoken · 2015-06-11T14:51:39Z

Originally tested against deegree 3.3.13, but can confirm the issue remains in 3.3.14 and 3.4-pre17 releases.

When using a WFS 2 GetFeature POST request where the ValueReference attempts to evaluate an attribute value (tested specifically with xlink:href, may apply to other attributes), deegree fails to return any results. deegree therefore fails the Filter Encoding Minimum Standard Filter conformance class.

For example using the following service end point:

http://194.66.252.155/m4eu/services?

Looking at ge:MappedFeature (ref: http://194.66.252.155/m4eu/services?service=WFS&request=GetFeature&version=2.0.0&typenames=ge:MappedFeature&count=3&)

If we use a PropertyIsNull operator (tests the specified property to see if it exists in the resource being evaluated. ref: OpenGIS Filter Encoding 2.0 Encoding Standard, section 7.7.3.5) as below we get no results, but we can see that ge:mappingFrame/@xLink:href should evaluate.

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature version="2.0.0" service="WFS" handle="Filter on attribute test with PropertyIsNull deegree" count="100"
    xmlns="http://www.opengis.net/wfs/2.0" 
    xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wfs="http://www.opengis.net/wfs/2.0"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="ge:MappedFeature">
        <Filter xmlns="http://www.opengis.net/fes/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0">
            <PropertyIsNull>
                <ValueReference>ge:mappingFrame/@xlink:href</ValueReference>
            </PropertyIsNull>
        </Filter>
    </Query>
</GetFeature>

As a sanity check we can see that a similar filter query using the PropertyIsNull operator but without the xlink:href attribute returns results:

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature version="2.0.0" service="WFS" handle="Filter on element test with PropertyIsNull deegree" count="100"
    xmlns="http://www.opengis.net/wfs/2.0" 
    xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wfs="http://www.opengis.net/wfs/2.0"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="ge:MappedFeature">
        <Filter xmlns="http://www.opengis.net/fes/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0">
            <PropertyIsNull>
                <ValueReference>ge:mappingFrame</ValueReference>
            </PropertyIsNull>
        </Filter>
    </Query>`
</GetFeature>

It follows too that using a PropertyIsEqualTo operator to evaluate the value of the attribute also fails:

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature version="2.0.0" service="WFS" handle="Filter on attribute test with PropertyIsEqualTo deegree" count="100"
    xmlns="http://www.opengis.net/wfs/2.0" 
    xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wfs="http://www.opengis.net/wfs/2.0"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="ge:MappedFeature">
        <Filter xmlns="http://www.opengis.net/fes/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0">
            <PropertyIsEqualTo>
                <ValueReference>ge:mappingFrame/@xlink:href</ValueReference>
                <Literal>http://inspire.ec.europa.eu/codeList/MappingFrameTerm/topographicSurface</Literal>
            </PropertyIsEqualTo>
        </Filter>
    </Query>
</GetFeature>

Just checking that such a query should be possible, here it is working as expected in a GeoServer service.

end point: http://ogc.bgs.ac.uk/digmap625k_gsml32_insp_gs/wfs?

Looking at gsml:MappedFeature (ref: http://ogc.bgs.ac.uk/digmap625k_gsml32_insp_gs/wfs?service=WFS&request=GetFeature&version=2.0.0&typenames=gsml:MappedFeature&count=3&)

The null test returns no results

<GetFeature
    version="2.0.2"
    service="WFS"
    handle="Filter on attribute test with PropertyIsNull GeoServer"
    count="10"
    xmlns="http://www.opengis.net/wfs/2.0"
    xmlns:fes="http://www.opengis.net/fes/2.0"
    xmlns:gsml="http://xmlns.geosciml.org/GeoSciML-Core/3.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="gsml:MappedFeature">
        <Filter  
            xmlns="http://www.opengis.net/fes/2.0" 
            xmlns:xlink="http://www.w3.org/1999/xlink" 
            xmlns:gsml="http://xmlns.geosciml.org/GeoSciML-Core/3.2" >
            <PropertyIsNull>
                <ValueReference>gsml:samplingFrame/@xlink:href</ValueReference>
            </PropertyIsNull>
        </Filter>
    </Query>
</GetFeature>

Whilst the PropertyIsEqualTo request for an xlink:href attribute gives us results

<GetFeature
    version="2.0.2"
    service="WFS"
    handle="Filter on attribute test with PropertyIsEqualTo GeoServer"
    count="10"
    xmlns="http://www.opengis.net/wfs/2.0"
    xmlns:fes="http://www.opengis.net/fes/2.0"
    xmlns:gsml="http://xmlns.geosciml.org/GeoSciML-Core/3.2"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="gsml:MappedFeature">
        <Filter  
            xmlns="http://www.opengis.net/fes/2.0" 
            xmlns:xlink="http://www.w3.org/1999/xlink" 
            xmlns:gsml="http://xmlns.geosciml.org/GeoSciML-Core/3.2" >
            <PropertyIsEqualTo>
                <ValueReference>gsml:samplingFrame/@xlink:href</ValueReference>
                <Literal>http://inspire.ec.europa.eu/codelist/MappingFrameValue/topOfBedrock</Literal>
            </PropertyIsEqualTo>
        </Filter>
    </Query>
</GetFeature>

The text was updated successfully, but these errors were encountered:

tfr42 · 2016-08-30T18:37:34Z

@dstenger can you check this against OGC ETS for FE with TEAM engine please?

tfr42 · 2016-11-08T13:35:02Z

Issue was mentioned in https://themes.jrc.ec.europa.eu/discussion/view/108800/examples-of-inspire-view-and-dowload-services-for-lclu

tfr42 · 2017-04-05T17:14:35Z

May apply to SE and deegree layer configuration as well, see #587.

tfr42 · 2017-05-24T06:54:52Z

PR is currently under preparation.

tfr42 · 2017-06-14T11:46:30Z

see the related PR #837 and https://github.com/lat-lon/deegree-cli-utility/pull/1 for deegree-cli-utility

DirkThalheim · 2017-09-18T09:30:00Z

Hi,

I'm having troubles applying filters on xlink:href attributes too. I'm using following workspace: https://github.com/de-bkg/deegree-workspace-dlm250-inspire and the fixed deegree version 3.4-RC3-bayldbvdeegree-1.0.0.

Within the workspace all INSPIRE categories are implemented with a Feature mapping. When I understand this issue right, it should be mapped as Primitive to be able to apply filters for xlink:href attributes. Unfortunately this leads to a totally removal of the xlink:href attribute within the GML output.

For example requesting the hy-n:HydroNode FeatureTypeMapping with following hydroNodeCategory configuration:

    <Complex path="hy-n:hydroNodeCategory">
      <Primitive path="@nilReason" mapping="hydronodecategory_nilreason"/>
      <Primitive path="@xsi:nil" mapping="hydronodecategory_nil"/>
      <Feature path=".">
        <Href mapping="hydronodecategory_href"/>
      </Feature>
    </Complex>

Produces:
<hy-n:hydroNodeCategory xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://inspire.ec.europa.eu/codelist/HydroNodeCategoryValue/flowRegulation"/>

Requesting the same FeatureType with following hydroNodeCategory configuration:

    <Complex path="hy-n:hydroNodeCategory">
      <Primitive path="@xlink:href" mapping="hydronodecategory_href"/>
      <Primitive path="@nilReason" mapping="hydronodecategory_nilreason"/>
      <Primitive path="@xsi:nil" mapping="hydronodecategory_nil"/>
    </Complex>

Produces:
<hy-n:hydroNodeCategory/>

Actually I can't determine the cause for that behaviour.

tfr42 · 2017-11-06T22:53:59Z

Please verify expected behavior against recent release candidate 3.4-RC5 and report your results here.

DirkThalheim · 2017-11-08T08:21:35Z

Just upgraded to deegree 3.4-RC5. Still have the issue: When mapping as primitive, I get an empty hy-n:hydroNodeCategory node.

I just looked into the schema. hy-n:hydroNodeCategory is a gml:ReferencedType. Maybe it's connected to this type. But I'm pretty sure for other FeatureTypes it worked.

tfr42 · 2017-11-13T11:33:15Z

OK, thank you for the feedback. Can you provide or point me to sample test data for the linked workspace?

DirkThalheim · 2017-11-14T06:52:29Z

The complete workspace configuration can be found here: https://github.com/de-bkg/deegree-workspace-dlm250-inspire. From the SQLFeatureStore configuration dlm250 just take the hy-n:HydroNode FeatureTypeMapping. Here you can alter the hy-n:hydroNodeCategory mapping from Feature to Primitive.

Sample data can be imported from this GetFeature Request: http://sg.geodatenzentrum.de/wfs_dlm250_inspire?service=WFS&request=GetFeature&VERSION=2.0.0&TYPENAMES=hy-n:HydroNode&COUNT=10

Let me know if you need more information.

marcusmohr · 2017-12-06T15:10:21Z

I have to confirm Dirk's problem with version 3.4-RC5. Furthermore it seems that it's not possible to use a filter with xlink:href in case of wms layerstyling. Neither a xlink:href filter in a sld nor in a feature layer seems to work. Thematically, this Problem is related to #587

nmtoken · 2017-12-07T18:21:47Z

I can confirm that PropertyIsEqualTo as below fails to return results on a service running 3.4-RC6

<?xml version="1.0" encoding="UTF-8"?>
<GetFeature version="2.0.0" service="WFS" handle="Filter on attribute test with PropertyIsEqualTo deegree" count="5"
    xmlns="http://www.opengis.net/wfs/2.0" 
    xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:wfs="http://www.opengis.net/wfs/2.0"
    xmlns:xlink="http://www.w3.org/1999/xlink"
    xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd">
    <Query typeNames="ge:MappedFeature">
        <Filter xmlns="http://www.opengis.net/fes/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ge="http://inspire.ec.europa.eu/schemas/ge-core/3.0">
            <PropertyIsEqualTo>
                <ValueReference>ge:mappingFrame/@xlink:href</ValueReference>
                <Literal>http://inspire.ec.europa.eu/codeList/MappingFrameTerm/topographicSurface</Literal>
            </PropertyIsEqualTo>
        </Filter>
    </Query>
</GetFeature>

When a GetFeature request shows that the attribute value exists:

http://ogcdev.bgs.ac.uk/test/services?service=WFS&request=GetFeature&version=2.0.0&typenames=ge:MappedFeature&count=3&

lgoltz · 2017-12-08T08:57:27Z

Summary of the problems described in this issue

WFS GetFeature POST request with filter fails to evaluate xlink:href attribute
- The original theme of this issue.
- Should work when the SQLFeatureStore configuration contains a primitive mapping instead of a feature mapping
- Documentation in https://github.com/deegree/deegree3/blob/master/deegree-services/deegree-webservices-handbook/src/main/sphinx/featurestores.rst#mapping-strategies-for-xlinkhref-attributes
WFS GetFeature Response does not contain the @xlink:href attributes configured with primitive mapping
- Described in WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573 (comment)
- New issue created: WFS GetFeature Response does not contain the @xlink:href attributes configured with primitive mapping #875
- Related to nilReason is omitted #866
Filtering on xlink:href in WMS layerstyling or in a feature layer does not work in BLOB mode and relation mode (primitive mapping as well as feature type mapping)
- Described in WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573 (comment)
- Existing issue: Layer with filter using href not working #587

lgoltz · 2017-12-08T09:00:55Z

@nmtoken I assume you are using a SQLFeatureStore with relational mapping? Can you check the configuration of ge:mappingFrame? It is configured as primitive or feature mapping? Differences (concering @xlink:href) are described in https://github.com/deegree/deegree3/blob/master/deegree-services/deegree-webservices-handbook/src/main/sphinx/featurestores.rst#mapping-strategies-for-xlinkhref-attributes

nmtoken · 2017-12-08T19:16:35Z

Yes, the backed is a PostgreSQL/PostGIS relational database, and mappings are done using a SQLFeatureStore.

ge:mappingFrame is part of ge:MappedFeature which has the following mapping:

<!--
=============
MappedFeature
=============
-->
<FeatureTypeMapping name="ge:MappedFeature" table="MineralOccurrence_vw">
	<FIDMapping prefix="M4EU.MAF_">
		<Column name="mineralOccurrenceDbk" type="integer"/>
	</FIDMapping>
	<Complex path="ge:shape">
		<Geometry path="." mapping="geometry"/>
	</Complex>
	<Complex path="ge:mappingFrame">
		<Feature path=".">
			<Href mapping="mappingFrame"/>
		</Feature>
	</Complex>
	<Complex path="ge:specification">
		<Feature path=".">
			<Href mapping="mineralOccurrenceId"/>
		</Feature>
	</Complex>
</FeatureTypeMapping>

The complete mapping for the service and the XML schema is:
m4eu v1.1.2.zip

lgoltz · 2017-12-11T06:06:39Z

@nmtoken Please change your configuration as follows to support filtering on ge: mappingFrame/@xlink:href:

<Complex path="ge:mappingFrame">
  <Primitive path="@xlink:href" mapping="mappingFrame"/>
</Complex>

This is described in the section Mapping strategies for xlink:href attributes in the deegree-webservices Handbook.

nmtoken · 2017-12-11T09:29:16Z

@lgoltz thanks for the feedback.

I didn't create the mapping, just implementing it, so I will pass on this advice; I assume the strategy applies to any attributes I want to query, not just xlink:href?

lgoltz · 2017-12-13T15:37:55Z

I assume the strategy applies to any attributes I want to query, not just xlink:href?

Yes, but usually other attributes than @xlink:href are not configured as feature mapping.

matax87 mentioned this issue Jul 14, 2015

Layer with filter using href not working #587

Closed

tfr42 added the bug error issue and bug (fix) label Aug 21, 2015

tfr42 added this to the 3.4 milestone Nov 17, 2015

tfr42 added contributions welcome asking for contribution (time and money sponsor) funding welcome financial sponsoring wanted (money) easy medium and removed easy labels Nov 8, 2016

tfr42 added in progress and removed contributions welcome asking for contribution (time and money sponsor) funding welcome financial sponsoring wanted (money) labels May 24, 2017

tfr42 mentioned this issue Oct 23, 2017

Improved support for INSPIRE #860

Closed

10 tasks

tfr42 mentioned this issue Nov 6, 2017

Enhance SQLFeatureStoreConfigWriter to differentiate between feature and xlink:href mapping #837

Merged

tfr42 added ready and removed in progress labels Nov 6, 2017

stempler mentioned this issue Nov 23, 2017

compare feature references by uri stempler/deegree3#2

Merged

lgoltz mentioned this issue Dec 8, 2017

WFS GetFeature Response does not contain the @xlink:href attributes configured with primitive mapping #875

Closed

lgoltz added the WFS deegree Web Feature Service label Jan 8, 2018

dstenger mentioned this issue Jan 29, 2018

Fixes several bugs concerning xlink:href attribute #879

Merged

copierrj closed this as completed in #879 Mar 9, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573

WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573

nmtoken commented Jun 11, 2015 •

edited

Loading

tfr42 commented Aug 30, 2016

tfr42 commented Nov 8, 2016

tfr42 commented Apr 5, 2017 •

edited

Loading

tfr42 commented May 24, 2017

tfr42 commented Jun 14, 2017

DirkThalheim commented Sep 18, 2017

tfr42 commented Nov 6, 2017 •

edited

Loading

DirkThalheim commented Nov 8, 2017

tfr42 commented Nov 13, 2017

DirkThalheim commented Nov 14, 2017

marcusmohr commented Dec 6, 2017

nmtoken commented Dec 7, 2017

lgoltz commented Dec 8, 2017

lgoltz commented Dec 8, 2017

nmtoken commented Dec 8, 2017

lgoltz commented Dec 11, 2017

nmtoken commented Dec 11, 2017

lgoltz commented Dec 13, 2017

WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573

WFS GetFeature POST request with filter fails to evaluate xlink:href attribute #573

Comments

nmtoken commented Jun 11, 2015 • edited Loading

tfr42 commented Aug 30, 2016

tfr42 commented Nov 8, 2016

tfr42 commented Apr 5, 2017 • edited Loading

tfr42 commented May 24, 2017

tfr42 commented Jun 14, 2017

DirkThalheim commented Sep 18, 2017

tfr42 commented Nov 6, 2017 • edited Loading

DirkThalheim commented Nov 8, 2017

tfr42 commented Nov 13, 2017

DirkThalheim commented Nov 14, 2017

marcusmohr commented Dec 6, 2017

nmtoken commented Dec 7, 2017

lgoltz commented Dec 8, 2017

Summary of the problems described in this issue

lgoltz commented Dec 8, 2017

nmtoken commented Dec 8, 2017

lgoltz commented Dec 11, 2017

nmtoken commented Dec 11, 2017

lgoltz commented Dec 13, 2017

nmtoken commented Jun 11, 2015 •

edited

Loading

tfr42 commented Apr 5, 2017 •

edited

Loading

tfr42 commented Nov 6, 2017 •

edited

Loading