Part 4: Discussions about submitting a list of Features?

[m-mohr]

Were there discussions to allow submitting multiple Features at the same time?

STAC API - Transactions has added that for POST /collections/{collectionId}/items:

When the body is a partial ItemCollection:

• Must only create a new resource.
• Each Item in the ItemCollection must have an id field.
• Must return 409 if an Item exists for any of the same collection and id values.
• Must populate the collection field in each Item from the URI.
• Must return 201 without a Location header.
• May create only some of the Items in the ItemCollection. Implementations are not required to implement all-or-none sematics for this operation. For example, if an ItemCollection contains two Items and one is successfully created and the other fails to be created, the server is not required to then delete the successfully created one. When only some of the Items in the ItemCollection are created, the server should communicate this failure back to the client with an error status code.

[cportele]

Meeting 2024-08-26: The scope of Part 4 will be restricted to mutations of a single resource / feature. Changes involving multiple features in a single request are planned for a future extension. We will move this issue to "future work".