[Geoserver-devel] [JIRA] (GEOS-11077) Implement Requirement Class "Search" from OGC API - Features Part 5 proposal

GeoServer GeoServer Developer
1

Sebastian Frey created an issue

GeoServer / New FeatureGEOS-11077

Implement Requirement Class “Search” from OGC API - Features Part 5 proposal

Issue Type:

New FeatureNew Feature

Assignee:

Unassigned

Created:

18/Jul/23 8:29 AM

Environment:

Currently the OGC API - Features plugin allows only to query features through HTTP GET via the {{/collections/

{collection}

/items}} resource. Querying features with HTTP GET works fine for simple bounding box querys or small CQL filters. As soon as a client tries to filter by larger geometries like cadastral borders or rivers things go bad. The reason for that is, that the amount of vertices of such filter geometries blows up the max http header size of the underlying servlet container very fast. Sure, increasing the max http header size might be a work around, but it does not scale well. In addition it is also a security risk to increase the max http header size to far.

Because of that, I propose the implementation of the OGC API - Features - Part 5: Requirements Class “Search” in the OGC API - Features plugin. I did also some research regarding the status of the proposal and found the following statement https://github.com/opengeospatial/ogcapi-features/issues/771#issuecomment-1508048697. As stated out in the linked comment the search endpoint of Part 5 seems to be the go-to way for querying features via POST.

So if you are interested in adding this functionality to the plugin, I am willing to provide a PR for it.

Priority:

MediumMedium

Reporter:

Sebastian Frey

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS

This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100232-sha1:4a3b42c)

Atlassian logo