It would be useful to have automatic resolution of coded domains from REST endpoints.
The GeoServices REST Specification exposes a number of endpoints which return attribute values. Some of the rest endpoints supply automatic coded domain resolution (for example the Identify and Find resources); however, others do not. Specifically, the following REST endpoints return coded values (instead of resolved values):
There may be others as well, but these are the endpoints most exercised by typical client applications.
I would like to propose a change to the GeoServices REST Specification to allow an optional parameter on these endpoints (for example, “resolveCodedDomains=true”) which when supplied would instruct the endpoint to return resolved values as opposed to coded values. I believe that this would be a non-breaking change since the default behavior could remain the same. Obviously, if subtypes are used then the coded values should be resolved according to the subtype of the feature returned.
Additionally, there are several REST endpoints which require the use of coded values in their parameters. For example, although the “Find” resource successfully resolves coded domains when returning results, clients of the operation must supply the “searchText” parameter using the coded values (and not the resolved values). Similarly, the layerDefs parameter used by Identify and Export operations of a MapServer require the use of coded values. It would be helpful if we could provide a parameter to a resource which specifies that the supplied parameters contain resolved coded domain values (instead of the coded values).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.