Answers interleaved
Le lun. 24 déc. 2018 à 00:27, Bruno P. Kinoshita a
écrit :
> That's great news Jean! That's some fine investigation work you did!
>
> Couple questions
>
> Q1/ is it something that you think could help others doing the same? If so
> we could add it somewhere in the
Oh, and almost forgot
>
>when it should be:
>
> EntityDefinition entDef = new EntityDefinition("uri", "geo");
Feel free to update that page if necessary, either via the link at the top
right corner that says "Improve this Page", or by patching
That's great news Jean! That's some fine investigation work you did!
Couple questions
Q1/ is it something that you think could help others doing the same? If so we
could add it somewhere in the documentation.
Q2/ just to confirm, that's not doable via assembler files, right? Only
I finally got it to work by coding:
https://github.com/jmvanel/semantic_forms/blob/master/scala/forms/src/main/scala/deductions/runtime/jena/lucene/LuceneIndex.scala#L199
A confusing documentation item was this in
Hello, Jean-Marc,
Thank you for investigating this question so carefully! Of course, it should
indeed be possible to build up a "text+spatial" dataset along the lines you've
proposed. But would it do what is needed? I can see how it would feed changes
to both indexes (which, I would note, I
I think it would not be difficult to set Jena for text and spatial, by
adding the indexes in the so-called Context (org.apache.jena.sparql.util
.Context) of the DatasetGraph .
But achieving dynamic update of both indexes when TDB is updated will
require extending the implementation along the line
Thanks Bruno for sharing your trials; alas you're not further than I.
Using gist.github.com is indeed better than the regular git, like I do, for
sharing trials.
I'm getting skeptical about doing spatial + textual as the Jena API stands.
For one thing, nobody stood up and said "I did it" since
I'm still clueless about how to configure Jena for textual AND spatial
indexes.
I tried yet another assembler file:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext3.assembler.ttl
but even less good as
Le lun. 17 déc. 2018 à 13:24, Andy Seaborne a écrit :
> ...
> :spatial_dataset rdf:type spatial:SpatialDataset ;
> rdf:type text:TextDataset ;
> ...
>
> Not sure but I think the system will create this twice.
>
> It would be better to have two declarations, one for spatial, one for
[] ja:loadClass...
Not needed these days. Harmless.
:spatial_dataset rdf:type spatial:SpatialDataset ;
rdf:type text:TextDataset ;
...
Not sure but I think the system will create this twice.
It would be better to have two declarations, one for spatial, one for
text. I'm not
Sorry , I sent a bad link on the list, my assembler file is really this:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext.assembler.ttl
Le dim. 16 déc. 2018 à 13:40, Marco Neumann a
écrit :
> you are missing the text index in the assembler.
>
> On Sun, Dec 16,
you are missing the text index in the assembler.
On Sun, Dec 16, 2018 at 12:08 PM Jean-Marc Vanel
wrote:
> Yes indeed,
> exactly with this assembler file:
>
> https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial.assembler.ttl
>
> And, when the Jena based application is
Yes indeed,
exactly with this assembler file:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial.assembler.ttl
And, when the Jena based application is started with this same assembler
file, the spatial queries work , as said above in this thread.
Le dim. 16 déc. 2018 à
did you create the text index with jena.textindexer
--desc=//config.ttl?
On Sun, Dec 16, 2018 at 8:48 AM Jean-Marc Vanel
wrote:
> I fixed a stupid error in text index URI, resulting from pasting, in new
> file jena.spatial+text.assembler.ttl:
>
>
I fixed a stupid error in text index URI, resulting from pasting, in new
file jena.spatial+text.assembler.ttl:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext.assembler.ttl
Now, it reads:
:spatial_dataset rdf:type spatial:SpatialDataset ;
rdf:type
So I tried a new file jena.spatial+text.assembler.ttl with separate Lucene
indices for spatial and text:
https://github.com/jmvanel/semantic_forms/blob/master/scala/jena.spatial%2Btext.assembler.ttl
It defines a Dataset with both Dataset types and both Lucene indices:
:spatial_dataset rdf:type
> On Dec 15, 2018, at 9:59 AM, Marco Neumann wrote:
>
>> *Question*: does that make sense to have a unique Lucene index for text and
>> space ?
>> It is possible at all? If yes, is it good in terms of disk space and
>> performance?
>> Like this:
>> <#indexLucene> a text:TextIndexLucene ;
>>
yes that is correct Jean-Marc two indexes, one for spatial and another for
text data.
please be advised that the Jena project will introduce a new spatial
indexer in an upcoming release that you might want to consider for your
evaluation since you only start out with spatial queries at this
I began to try using what I sketched in the preceding post:
https://github.com/jmvanel/semantic_forms/blob/master/scala/forms/src/main/scala/deductions/runtime/jena/lucene/LuceneIndex.scala#L88
But it does not work: that is, a spatial query returns nothing.
To create the spatial index by program
19 matches
Mail list logo
