Skip to content

Query: response structure (one vs multiple feature collections) #1055

Description

@cportele

The current draft expects an array of feature collections. The earlier drafts had a single feature collection.

In most cases (that I have to work with) a single feature collection is the better representation and easier to process (with globally unique feature ids, deduplication of features that were selected multiple times, etc.).

At a minimum, both options should be specified - as profiles.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
To do

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions