Hi Hugh,

Yes, I have missed this point. But after running DB.DBA.RDF_GEO_FILL my
Virtuoso instance hanged. I couldn't stop it and after rebooting couldn't
start (had to restore from backup). I use High-CPU Medium instance for
storing LinkedGeoData Elements dataset, so may the lack of resources is the
source of this problem (instance was tuned according to documentation).

Regards,
Alexander

2010/5/18 Hugh Williams <[email protected]>

> 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 the most
> likely cause ...
>
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software
> Web: http://www.openlinksw.com
> Support: http://support.openlinksw.com
> Forums: http://boards.openlinksw.com/support
> Twitter: http://twitter.com/OpenLink
>
> On 18 May 2010, at 12:01, Alexander Sidorov wrote:
>
> 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 .}
> 2. endpoint: http://ec2-184-73-209-65.compute-1.amazonaws.com/sparql
>     query: SELECT * FROM <http://linkedgeodata.org/content#> WHERE {<
> http://linkedgeodata.org/triplify/node/163043169#id> ?p ?o .}
>
> "geometry" predicate exists in the first case but doesn't in the second
> one.
>
> P. S. I use Virtuoso Cloud Edition 06.01.3127
>
> Regards,
> Alexander
>
> 2010/5/18 Hugh Williams <[email protected]>
>
>> 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 conductor UI ?
>>
>>  Best Regards
>> Hugh Williams
>> Professional Services
>> OpenLink Software
>> Web: http://www.openlinksw.com
>> Support: http://support.openlinksw.com
>> Forums: http://boards.openlinksw.com/support
>> Twitter: http://twitter.com/OpenLink
>>
>> On 17 May 2010, at 18:04, Alexander Sidorov wrote:
>>
>> Hi Kingsley,
>>
>> Yes, geo capabilities work very well under Virtuoso Cloud Edition (good
>> performance was a great surprise after migrating from lod.openlinksw.comto 
>> custom Amazon EC2 instance). Here I will quote the initial question to
>> point out the problem:
>>
>> "Prevously I executed LGD queries using lod.openlinksw.com endpoint
>> (where full LGD is loaded). Today I have loaded LGD Elements to my custom
>> Virtuoso instance and all LGD queries became broken. As I have found out
>> "geometry" predicate is absent at LGD Elements dataset. Changing "geometry"
>> to combination of "lat" and "long" solved my problem. But please put the
>> note concerning "geometry" predicate at linkedgeodata.org/datasets page
>> to prevent other people to struggle with this problem."
>>
>> Regards,
>> Alexander
>>
>> 2010/5/17 Kingsley Idehen <[email protected]>
>>
>>> Alexander Sidorov wrote:
>>>
>>>> Hi Alex,
>>>>
>>>> You are right, geo-capabilities are included only in commercial Virtuoso
>>>> instances. But it is my case (as I use Virtuoso Cloud Edition). I hope
>>>> OpenLink guys can clarify this behaviour so I have added virtuoso-users to
>>>> cc.
>>>>
>>>
>>> Cloud Edition is the Commercial Edition so you have SPARQL-GEO and
>>> related GeopSpatial index capabilities.
>>>
>>>
>>> Kingsley
>>>
>>>>
>>>> Regards,
>>>> Alexander
>>>>
>>>> 2010/5/17 Alex Tucker <[email protected] <mailto:[email protected]>>
>>>>
>>>>    Hi Alexander,
>>>>
>>>>
>>>>
>>>>>    I followed the link you provided but haven't found any
>>>>>    information concerning "geometry" predicate generation. Could you
>>>>>    please point to it? Also it is strange "geometry" predicate is
>>>>>    generated at lod.openlinksw.com <http://lod.openlinksw.com> but
>>>>>
>>>>>    is not generated at my custom Virtuoso instance.
>>>>>
>>>>
>>>>    My understanding is that the geometry predicate is computed by
>>>>    Virtuoso and is only available in the commercial edition, not the
>>>>    free open source edition.  This explains why you can use it at
>>>>    lod.openlinksw.com <http://lod.openlinksw.com> and potentially at
>>>>
>>>>    the new LGD servers, as I believe OpenLink donated a commercial
>>>>    license to run the LGD servers too.
>>>>
>>>>    Alex.
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>>
>>>>  ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Virtuoso-users mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Kingsley Idehen       President & CEO OpenLink Software     Web:
>>> http://www.openlinksw.com
>>> Weblog: 
>>> http://www.openlinksw.com/blog/~kidehen<http://www.openlinksw.com/blog/%7Ekidehen>
>>> Twitter/Identi.ca: kidehen
>>>
>>>
>>>
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>>
>>
>> _______________________________________________
>> Virtuoso-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>>
>>
>>
>
> ------------------------------------------------------------------------------
>
>
> _______________________________________________
> Virtuoso-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/virtuoso-users
>
>
>

Reply via email to