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
Yes, good catch. The reason is the way petrimaps works: it first loads all the geometries stored in QLever during startup. Afterwards, only the QLever-internal IDs are transferred to petrimaps, and the corresponding geometry is looked up by petrimaps.
Since the geometry is generated on-the-fly in your query, petrimaps does not have it cached. We are currently experimenting with ways to show the result of arbitrary SQL queries to a PostGIS database in petrimaps. I expect that in the wake of this feature, we will also add the ability to display SPARQL results containing non-cached geometries.
It is impossible to visualize geometries created within the query:
The text was updated successfully, but these errors were encountered: