By creating an interactiv map with a few layers selected from overpass-api, often HTTP error 429 appears. Every size or map move causes a new query from overpass. Even with activated proxy it is not necessary to requery every time, even by zoom-in. Facing this erros, I changed my interactive map to a static map, imported from overpass-turbo-data. The map is much faster, but now I don't get any changes.
How about updating imported data every day, also with an overpass query? For this, you could create a new import dialog for one overpass-query per layer with a requery-time option (daily, weekly). This would reduce performance issues on overpass-Server and also boost the responce-time on UMAP.
Please consider my feature-request.
Hi UMAP-Team, you are doing a really good job!
By creating an interactiv map with a few layers selected from overpass-api, often HTTP error 429 appears. Every size or map move causes a new query from overpass. Even with activated proxy it is not necessary to requery every time, even by zoom-in. Facing this erros, I changed my interactive map to a static map, imported from overpass-turbo-data. The map is much faster, but now I don't get any changes.
How about updating imported data every day, also with an overpass query? For this, you could create a new import dialog for one overpass-query per layer with a requery-time option (daily, weekly). This would reduce performance issues on overpass-Server and also boost the responce-time on UMAP. Please consider my feature-request.