Hi Hoan,
The following amended version of the rdf_geo_fill() function, could be used to
create the geometry indexes on a specific graph:
create procedure rdf_geo_fill_single_onegraph (IN onegraph VARCHAR)
{
declare giid any;
giid := iri_to_id (onegraph);
for select "s", "long", "lat" from
Hi Rob,
You are correct, thanks for pointing that out ...
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter -
Hi Alex
Have you looked at the Star Schema bench mark which creates OLAP queries using
SPARQL ?
http://people.aifb.kit.edu/bka/ssb-benchmark/
Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc. // http://www.openlinksw.com/
Weblog -- http://www.
Asking a query with accept header:
text/plain, application/rdf+xml, application/xml,
application/x-binary-rdf, text/turtle, application/x-turtle,
text/rdf+n3, application/xhtml+xml, text/html, image/svg+xml,
application/x-trig, application/trix, text/x-nquads
Virtuoso answer with
Content-Type
Hi everyone,
This question is related to Virtuoso geometry functions, RDF_GEO_FILL(),
which will create geometry index based on (latitude, longitude) properties.
However, according to the documentation (
http://docs.openlinksw.com/virtuoso/rdfsparqlgeospat.html#rdfsparqlgeospatcrg),
this function
Thank you for your reply.
I am working towards an extension of sparql which would make possible
to make "nice looking" OLAP queries over RDF data. When I first
noticed property functions, they seem to be a nice way to do it.
Unfortunately Jena TDB seem to be performing quite poorly in
comparison t
Hugh
This isn't a bug AFAICT, a naked # is not allowed in a SPARQL prefixed name,
even in 1.1 it needs escaping with a \
See the PL_LOCAL_ESCAPE rule -
http://www.w3.org/TR/sparql11-query/#rPN_LOCAL_ESC
So the Virtuoso parser looks to be correct in treating the # onwards as a
comment which is
