[Geoserver-devel] [JIRA] (GEOS-8243) app-schema WFS 2.0 resulttype=hits responses have numberMatched="0"

GeoServer GeoServer Developer
1

Ben Caradoc-Davies created an issue

GeoServer / BugGEOS-8243

app-schema WFS 2.0 resulttype=hits responses have numberMatched=“0”

Issue Type:

BugBug

Affects Versions:

2.10.4, 2.12-beta, 2.11.2

Assignee:

Unassigned

Components:

Application schema

Created:

02/Aug/17 2:42 AM

Priority:

MediumMedium

Reporter:

Ben Caradoc-Davies

http://osgeo-org.1560.x6.nabble.com/WFS-2-0-GetFeature-resultType-quot-hits-quot-on-APP-SCHEMA-store-returns-always-numberMatched-quot-0-td5330133.html

I think this is a limitation in app-schema with WFS 2.0. Note that the full response also contains numberMatched=“unknown”; I suspect the same root cause.

Here is an old discussion about numberMatched=“unknown” in app-schema WFS 2.0 responses. The discussion is from 2012, but I do not think anything has changed:
http://osgeo-org.1560.x6.nabble.com/app-schema-numberMatched-is-unknown-td5014036.html

I do not see why this cannot be fixed because WFS 1.1 is quite happy to return a correct numberOfFeatures for requests with resulttype=hits.

Add Comment

Add Comment

Get JIRA notifications on your phone! Download the JIRA Cloud app here.

This message was sent by Atlassian JIRA (v1000.1154.0#100057-sha1:fec937e)

Atlassian logo