Call for implementations of OGC API - Features - Part 4: Create, Replace, Update and Delete

Overview

As you may or may not know, one of the founding principles of the OGC API - Features work is that implementations carry a lot of weight in guiding how the features group of specifications evolve.

Recently the SWG published the first draft of the "OGC API - Features - Part 4: Simple Transactions" extension (see: https://github.com/opengeospatial/ogcapi-features/tree/master/extensions/transactions/simple) and we are now doing an informal survey to see who has or is planning to implement Part 4. If you have or are planning to implement part 4 please add a comment to this issue and let us know of your intentions. As I said, this is very informal, so nothing is binding; we are just trying to get a sense of how many implementations of simple transactions might be in the pipeline.

If you are planning to or have implemented transactions in your server (even if your implementation did not follow Part 4) we want to hear your feedback.

Code sprint

In case any of you might be interested in participating, OGC is conducting a code sprint on Sept. 29-30 that will include Part 4. Here are some details:

The Sprint registration page is at https://portal.ogc.org/public_ogc/register/q3_api.php

The Pre-event webinar of the Sprint will be held on Wednesday 23 September from 10:00am to 11:00am EDT, register for the webinar at https://docs.google.com/forms/d/1ZpIC9Sw1xcZ0jkXXfqUd3KNinX3dHrRtjglCzBnJfMk/viewform.

Read the OGC API - Features Part 4 Simple Transactions extension linked in the issue, then review the existing comments for implementation plans and feedback. Done means reporting an existing or planned implementation, including relevant feedback; the issue does not identify a repository file or test to change.