Sebastian Frey (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2edf9d89-a043-47ec-80ad-02af3d85b5f1
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
) / New Feature (
https://osgeo-org.atlassian.net/browse/GEOS-11077?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
) GEOS-11077 (
https://osgeo-org.atlassian.net/browse/GEOS-11077?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
) Implement Requirement Class "Search" from OGC API - Features Part 5 proposal
(
https://osgeo-org.atlassian.net/browse/GEOS-11077?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
)
Issue Type: New 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" (
https://htmlpreview.github.io/?https://github.com/opengeospatial/ogcapi-features/blob/master/proposals/search/standard/20-096.html#clause-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: Medium Reporter: Sebastian Frey (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A2edf9d89-a043-47ec-80ad-02af3d85b5f1
)
(
https://osgeo-org.atlassian.net/browse/GEOS-11077#add-comment?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
) Add Comment (
https://osgeo-org.atlassian.net/browse/GEOS-11077#add-comment?atlOrigin=eyJpIjoiOTM5MDVmNGVhYTZhNGMwY2FiYjllYzAyNDY2NzllOGUiLCJwIjoiaiJ9
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100232-
sha1:4a3b42c )_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
