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

2 - filter POI by portal #2

Open
IdrissaD opened this issue Apr 12, 2022 · 0 comments
Open

2 - filter POI by portal #2

IdrissaD opened this issue Apr 12, 2022 · 0 comments

Comments

@IdrissaD
Copy link
Contributor

IdrissaD commented Apr 12, 2022

Treks can be filtered by portals, but not POI (cf. GeotrekCE/Geotrek-admin#3043). One way to get roughly the same effect would be to spatially filter POI, assuming portals in the source DB have a spatial meaning (organizations that don't cover the same area).

Add possibility to enter a BBOX to filter POI directly in the API:

  • pros: less data fetched, performances improved;
  • cons: BBOX is not accurate

Add spatial filtering between API fetching and data processing:

  • pros: quite accurate spatial query, performances improved in data processing
  • cons: all POI are still downloaded

Another option would be to only download POI that are linked to a trek we fetch, through API poi/?trek=XXX route:

  • pros: filtering can't be more accurate
  • cons: from a performance point of view, this leads to as many API requests as there are treks...which is disastrous
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant