One option: if caching is possible? Need an update mechanism (e.g. once a day)? Manual purge option?
Another option: parse the points sooner, not on viewIssue: geopoints loading takes long for complex sparql queries
Possible solutions
1. MediaWiki has a built-in purge mechanism.
Idea: Store the GeoJSON result created by the SPARQL query at the same time the page is renderedCache the results of SPARQL requests in a local database for a day or so. SPARQL should take care of it’s own result caching and does already, so the snapshot and interactive map are always consistent.but it doesn’t
Timebox: 82. Cache the final GeoJSON results in a local database for a day or so.
3. Do the query only on page parsing and not every time the page is opened
- Has the advantage that purging is a solved concept
- Issue: page rendering (also preview) will take a long time
- Page rendering in steps (NA)
- Parser already has a fall back to go for a stale version when loading is too long
- Most pages won't have very complex, slow queries.
- Risk: What if rendering the map fails?
Timebox: 8