WFS 2.0.0 don't filter correctly on OGR spatialite #4878

Closed
aperi2007 opened this Issue Mar 4, 2014 · 4 comments

Comments

Projects
None yet
3 participants
@aperi2007

Hi,

Doing a wfs 2.0.0 request with a filter seem don't work correctly with the OGR connector and a spatialite DB.
I apply a filter that hould return 1 record, but instead it retrun 0 record.

Instead if I try the same request with filter on a mapfile using the same settings but with a postgis connection it work and return the right result.

The filtered request I use is like this:

http://url-to-mapserver/...?map=wmstest&service=WFS&version=2.0.0&request=GetFeature&OUTPUTFORMAT=application%2Fgml%2Bxml%3B%20version%3D3.2&typenames=test1&maxFeatures=100&Filter=%3Cfes:Filter%20xmlns:wfs=%22http://www.opengis.net/wfs%22%20xmlns:fes=%22http://www.opengis.net/fes/2.0%22%3E%3Cfes:PropertyIsEqualTo%20xmlns:fes=%22http://www.opengis.net/fes/2.0%22%3E%3Cfes:ValueReference%3Efilestgi%3C/fes:ValueReference%3E%3Cfes:Literal%3Ec0001_1_164_06mag1976%3C/fes:Literal%3E%3C/fes:PropertyIsEqualTo%3E%3C/fes:Filter%3E

Andrea.

@rouault

This comment has been minimized.

Show comment
Hide comment
@rouault

rouault Mar 4, 2014

Contributor

Could you share the mapfile and spatialite DB to reproduce the issue ?

Contributor

rouault commented Mar 4, 2014

Could you share the mapfile and spatialite DB to reproduce the issue ?

@aperi2007

This comment has been minimized.

Show comment
Hide comment
@aperi2007

aperi2007 Mar 4, 2014

The spatialite db is too huge and too many tables.
But I can surely prepare a small subset to reproduce the bug.

The spatialite db is too huge and too many tables.
But I can surely prepare a small subset to reproduce the bug.

rouault added a commit that referenced this issue Mar 5, 2014

WFS SortBy support for OGR layers: include WHERE clause (when availab…
…le) to speed-up queries since OGR SQLite driver does not yet support fast attribute filter on SELECT result layers (#4878)
@rouault

This comment has been minimized.

Show comment
Hide comment
@rouault

rouault Mar 5, 2014

Contributor

Note that there was a mix-up that caused values of fields to be displayed in other fields elements, so you may need to adjust your filter to query the right column.

Contributor

rouault commented Mar 5, 2014

Note that there was a mix-up that caused values of fields to be displayed in other fields elements, so you may need to adjust your filter to query the right column.

@rouault rouault closed this Mar 5, 2014

@tbonfort tbonfort added this to the 7.0 Release milestone Mar 5, 2014

@aperi2007

This comment has been minimized.

Show comment
Hide comment
@aperi2007

aperi2007 Mar 5, 2014

Thx Rouault ,

it work.

Thx Rouault ,

it work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment