If we support filtering using a filter language, there should be a way to determine the property names that may be used in the filter expressions ("queryables").
This could be a separate path (e.g. /collections/{collectionId}/queryables) and/or it could be included in the feature collection metadata.
The content could be something like { "queryables" : [ "f_code", "subtype", ... ] } or probably better a structure that clarifies which properties are for literal comparisons and which are spatial or temporal.
From email discussions in T-14:
If we support filtering using a filter language, there should be a way to determine the property names that may be used in the filter expressions ("queryables").
This could be a separate path (e.g.
/collections/{collectionId}/queryables) and/or it could be included in the feature collection metadata.The content could be something like
{ "queryables" : [ "f_code", "subtype", ... ] }or probably better a structure that clarifies which properties are for literal comparisons and which are spatial or temporal.