Hi Alexander,
Did you run the DB.DBA.RDF_GEO_FILL () procedure to create the geometry
data/predicates for the loaded LGD datasets as detailed at:
http://docs.openlinksw.com/virtuoso/rdfsparqlgeospat.html#rdfsparqlgeospatcrg
As if the "geometry" predicates do not exist, this would seem
Hi Hugh,
There wasn't any error. As there isn't "geometry" predicate at my instance,
Virtuoso doesn't find assertions with it and returns empty result set. Just
compare:
1. endpoint: lod.openlinksw.com/sparq
query: SELECT * WHERE {<
http://linkedgeodata.org/triplify/node/163043169#id> ?p ?o .}
Hi Alexander,
Are the LGD queries that worked against the lod.openlinksw.com server giving a
specific error when you attempt to run against your EC2 AMI with the LGD
datasets loaded ? Also what is the exact version of the Virtuoso EC2 AMI, this
will be reported in the left frame of the conducto
Hi Kingsley,
Please check new table for typos. I have launched High-CPU Medium instance
and here is what I have in my Account: "$0.400 per High-CPU Medium
instance-hour (or partial hour) consumed (First 96 Hrs) 6 Hrs 2.40". So
first 96 hours cost not 0.2$ but 0.4$. And probably following hours wil
