Hi Claus,

The first time the after a DB start DB.DBA.RDF_GEO_FILL () is called, the error occurs after less than a half a minute.
On consecutive attempts it then only takes a few seconds.

The error occurs independent of whether resources carry the virtuoso specific geo-literals. However, as already mentionend, adding those seems to be a workaround for that issue.



This problem is fixed in the new build.

I will contact you shortly where to get a new binary from.

Patrick


Reply via email to