-
-
Notifications
You must be signed in to change notification settings - Fork 4
Description
At the moment, it is possible to do the following:
inputs:
features:
type:
- "File"
- type: array
items: "File"
format:
- "ogc:FeatureCollection"
- "iana:application/geo+json"
$namespaces:
iana: "https://www.iana.org/assignments/media-types/"
ogc: "http://www.opengis.net/def/glossary/term/"However, it is NOT possible to do something like the following:
inputs:
features:
type:
- type: "File"
format: "ogc:FeatureCollection"
- type: array
items:
type: "File"
format: "iana:application/geo+json"
$namespaces:
iana: "https://www.iana.org/assignments/media-types/"
ogc: "http://www.opengis.net/def/glossary/term/"The reasoning of the above is that the application receiving this features input can either receive a single document embedding of a "FeatureCollection" (a specific type of GeoJSON: https://geojson.org/schema/FeatureCollection.json), or an array of "single feature" GeoJSON (eg: https://geojson.org/schema/Feature.json).
The current limitation of format permitted only directly under the input makes it such that some combinations of formats are inconsistent with the desired use. In the first example, a single "Feature" GeoJSON could be submitted, or an array of "FeatureCollection" (resulting in a 2D array of features) could be submitted, both of which are invalid for the application that expect a "list of features".
Allowing to nest format under the specific type would allow to adequately narrow the structure to the valid combinations.