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
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
The text was updated successfully, but these errors were encountered:
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:
Add spatial filtering between API fetching and data processing:
Another option would be to only download POI that are linked to a trek we fetch, through API
poi/?trek=XXX
route:The text was updated successfully, but these errors were encountered: