You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This came up as a possible enhancement during the implementation of the WfsSearch#563.
I think it would be very usable to have some methid to determine fields from the DescribeFeatureType response. Sth. like:
fieldsFromDescribeFeatureType(describeFeatureTypeResponse,filterFn){// returns an array of field objects with name, datatype, min and max etc.}
fieldsFromFeatureType(wfsUrl,featureTypeName,filterFn){// returns a promise, and eventually an array of fields// issue the correct DescribeFeatureType Request,// once we have the response call the above method}
If one only want the names, one could provide a fieldFn, which decides how a field should be represented.
We should additionally have some utilitues to only fetch string-like fields which can be used for LIKE searches.
The text was updated successfully, but these errors were encountered:
This came up as a possible enhancement during the implementation of the
WfsSearch
#563.I think it would be very usable to have some methid to determine fields from the DescribeFeatureType response. Sth. like:
If one only want the names, one could provide a fieldFn, which decides how a field should be represented.
We should additionally have some utilitues to only fetch string-like fields which can be used for LIKE searches.
The text was updated successfully, but these errors were encountered: