opengeospatial / opengeospatial/ogcapi-features

Support for POST?

Open
#449 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Part 10: Query (was: Search)
Dominant language
CSS
Stars
386
Forks
92
Avg merge
3d 4h
Merged PRs (30d)
15

Description

Do we need support for POST at /collections/{collectionId}/items?

This could be useful/necessary for filter expressions with large geometries (this could use application/x-www-form-urlencoded with cql-text) or for filter expressions with cql-json (with media type application/json and an object with a property for each parameter).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the /collections/{collectionId}/items endpoint and the existing query parameter handling. Determine whether POST should be supported for large-geometry filter expressions and cql-json, including the proposed application/x-www-form-urlencoded and application/json request formats; done means the required behavior and media types are clearly specified.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.