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

POI filtering #47

Open
kerryconvery opened this issue Jul 13, 2016 · 4 comments
Open

POI filtering #47

kerryconvery opened this issue Jul 13, 2016 · 4 comments
Assignees

Comments

@kerryconvery
Copy link

kerryconvery commented Jul 13, 2016

Hi

Is it possible to get, from the API, a list of POIs within a given radius, say 1 or 2 meters, from where the user is standing? Or will I just need to download all of the POI locations and then have my own algorithm work this out?

Also does the API give the users orientation, i.e. which way they are facing? as I'd like to select POIs within 180 degrees instead of 360?

@kgeorgiou
Copy link
Contributor

That's an interesting concept. At the moment the API serves all POIs per building or all POIs per floor. However, we could definetely utilize Couchbase's geospatial capabilities to serve all POIs that are positioned within a spexific bounding box.

Regarding the orientation, this is something the Android app has access to through the device's sensors therefore it should be possible to filter POIs based on a given position and angle.

At the moment there are no such functionalities in place since most of our use cases have a number of POIs that can be easily loaded without any filtering.

Approximately how many POIs do you have in your use case - if you don't mind me asking?

For the time being you should handle the filtering at the front-end level until the functionalities you mentioned are built into the server - it's definetely something we will be looking into.

@anyplaceucy
Copy link

This is indeed an easy and timely addition. It's already offered for radio map requests. We should discuss it internally to offer this endpoint as well.

@kerryconvery
Copy link
Author

For our hack day project probably around 20 POIs since we want to keep it small. Depending on the efficiency of the algorithm shouldn't adversely impact performance. At a later date, should we decide to take the project to production level, then we are probably looking several 100 or possibly even a 1000+ POIs but that is a way off and we can review our options then.

@anyplaceucy
Copy link

Dimitri, please kindly include the above endpoint (similar to the new radiomap endpoints) in your next release.

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

4 participants