Open cportele opened 3 years ago
Currently an async execution results in a 202 response. See https://docs.ogc.org/DRAFTS/21-000.html#compute_routes_async.
This should be changed to a 201, because the route resource is created with the request and can be fetched by a client.
201 would be consistent with async support in OGC API - Processes.
201
Currently an async execution results in a 202 response. See https://docs.ogc.org/DRAFTS/21-000.html#compute_routes_async.
This should be changed to a 201, because the route resource is created with the request and can be fetched by a client.