Simon Bin

maybe we shouldn't derail this thread, but as a stop-gap solution to your concern, we have implemented a method to manually update the geospatial index, which is currently good enough...

this is fixed now right?

works for me in rpt 1.9.2-rc

Hi @pdmosses thanks for your valuable input The problem here is not the IAL or not the example that you have thought of is not a problem either [^1] The...

you can access the github version if you add this line: ``` markdown: GFM ``` to your _config.yml -- it will use https://github.com/github/jekyll-commonmark-ghpages

yes you are right, in many cases kramdown (and IALs) is indispensable for nice markdown-based authoring the patch would also _simplify_ the required IAL (`{:start=41}` instead of `{:style="counter-reset:step-counter 41"}`) but...

afaik the problem with tsv is multiline literals (?) cannot just add . to the end of each line...

I just tried it on a simple example and Jena does _not_ output multiline turtle by default, it uses "...\n", so I guess TSV should be fine

(by the way my colleague @Aklakan has built a [tool](https://github.com/SmartDataAnalytics/RdfProcessingToolkit/releases) around Apache Jena which you could use if you want to: `rpt integrate -e tdb2 --loc=yourtdb2 --geoindex --out-format text/plain yourquery.rq`)

Changing the PathEvaluator to Iters would be able to fix queries with one end, like `?class wdt:P279{,13} wd:Q35120` on wikidata (get all classes that have a maximum length path)