This repository was archived by the owner on Sep 19, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 19, 2024. It is now read-only.
Add better heuristic to determine optimal request filter #124
Description
Activity
To gain a quick solution for this problem we introduce a (temporary) separate connector which optimizes request filtering via
observedProperty. However, the focused heuristic will integrate both cases later on.- added a commit that references this issue
on Jul 21, 2014
Currently, the hydro connector filters according to
procedureparameter. This however is related to sample SOS instances serving just oneobservablePropertywhich resulted in anExceedsSizeLimitexception duringGetFeatureOfInterest.Switching
observablePropertyfilter andprocedurefilter would not solve the problem optimal as other SOS instances may be modeld the other way.proposed solution:
Add kind of a heuristic that chooses that filter parameter which has less values. If still an
ExceedsSizeLimitexception is returned, a combination ofobservablePropertyandprocedurefilter should be used.