Currently the loaded data points are retrieved by sending a request with current viewbox limits to the server. The server returns a list of ids for all locations in the requested area.
This list is than compared to what has already been stored and the remaining „new“ ids should trigger a new API request. The problem with this approach is that loading more than hundred ids leads to far too long urls (the ids are all stuffed in the url) and a failed request (414).
The previous solution was to simply slice the list of ids and load only the first 50 ids. This makes no sense at all as the retrieved data lacks several randomly excluded locations.
We need a complete new approach that includes fundamental rethinking of exploring locations.
Currently the loaded data points are retrieved by sending a request with current viewbox limits to the server. The server returns a list of ids for all locations in the requested area.
This list is than compared to what has already been stored and the remaining „new“ ids should trigger a new API request. The problem with this approach is that loading more than hundred ids leads to far too long urls (the ids are all stuffed in the url) and a failed request (414).
The previous solution was to simply slice the list of ids and load only the first 50 ids. This makes no sense at all as the retrieved data lacks several randomly excluded locations.
We need a complete new approach that includes fundamental rethinking of exploring locations.