Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Geo filter on a global scale #85

Open
coreation opened this issue Apr 12, 2012 · 0 comments
Open

Geo filter on a global scale #85

coreation opened this issue Apr 12, 2012 · 0 comments
Assignees

Comments

@coreation
Copy link
Member

Currently some resources support the usage of a geo filter such as OGDWienJSON and KMLGhent, however it would be nice to have this on a higher level (just like the OSpec filter).

This can be done by adding another Filter, which inherits from AFilter (found in model/filters). The filter() function must be implemented, for examples look at the RESTFilter or the SearchFilter.

The usage of the filter comes in the RController ( GET-function ). Starting from line 109 the filters are 1 by 1 called upon, I suggest the geo filter be placed after the opensearch filter, this will already narrow down the amount of entries in the returned object, because the geo-filter will require some triangulation math (which is imho more intensive than the average OSpec filter) so the less entries, the less work the geo filter will require.

@ghost ghost assigned lievenjanssen Apr 12, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants