Hi Paolo,

On Apr 1, 2012, at 1:12 PM, Paolo Castagna wrote:

> Hi Chris
> thanks for letting us know.

Anytime!

> 
> Mattmann, Chris A (388J) wrote:
>> Hi Andy,
>> 
>> Just to follow up on this, I went ahead and filed this issue:
>> 
>> https://issues.apache.org/jira/browse/SIS-42
>> 
>> I'm going to start work on implementing the Geo SPARQL spec in SIS, maybe
>> even integrating with Any23 (and Jena down the road, but Any23, I'm a tad
>> more familiar with at the moment). 
> 
> I am a bit confused here.
> 
> In my head, SIS (which I do not know very well) is a low-level geo indexing
> library which could be used to provide the indexing capability for a GeoSPARQL
> implementation.

Yeah that's what I was thinking too.

> 
> I know that ARQ (i.e. the SPARQL query engine available in Jena) can
> provide you with a SPARQL 1.1 engine and extension points to use other
> custom indexes (such as SIS in this case).
> 
> What exactly do you mean with "integrating with Any23"?
> Do you mean crawling the web and extract lat/long from web pages?

Yep that's what I was thinking -- maybe doing it in Any23, and/or Tika.

> Where will you store those RDF statements?

It looks like Any23 would store to Sesame -- is that the case?

> 
> How can you implement the GeoSPARQL spec without (re)using a SPARQL
> query engine (such as ARQ)?

I need that too :) I just don't understand it as well (and understand the 
Any23/Tika
and SIS part better). I'll have to learn Jena it looks like though, you game to 
help me out?

> 
> IMHO geo location (as well as free text) are two SPARQL extensions which
> are very useful in loads of use cases.

Yep I'm super excited to get this implemented. You interested in helping? I 
think
we can bring together Tika, Any23, Jena and SIS here...

Cheers,
Chris

> 
>> I'm CC'ing the any23-dev and jena-dev user lists (apologies for the SPAM 
>> guys)
>> just to keep them in the loop.
>> 
>> Cheers,
>> Chris
>> 
>> On Jan 31, 2012, at 4:59 AM, Andy Seaborne wrote:
>> 
>>> Hi there,
>>> 
>>> I'm investigating what it would take to implement GeoSPARQL.
>>> There is already an Apache-licensed SPARQL engine in podling Jena.
>>> 
>>> Of the things needed are a persistent storage layer with the right 
>>> license.  Maybe the SIS project has something to use.
>>> 
>>> If I understand it correctly, the qtree implementation is an in-memory 
>>> structure, with the ability to read from a serialized form on disk, and 
>>> to be able to write it to disk in that form.
>>> 
>>> Is there any information on scaling for the qtree?  Memory usage?
>>> 
>>> California_Restaurants.csv is 54K points - is that typical usage size?
>>> 
>>> (yes ... there are other things needed as well such as conversion code 
>>> between coodinate systems, format parsers, polygon code, ... but a start 
>>> would be just for point data in one system :)
>>> 
>>> An open copy of the spec is available at:
>>> 
>>> http://www.w3.org/2011/02/GeoSPARQL.pdf
>>> 
>>>     Andy
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattm...@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattm...@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
Phone: +1 (818) 354-8810
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to