GeoKnow/LinkedGeoData

Is this project actively maintained?

jindrichmynarz opened this issue · 5 comments

jindrichmynarz commented

Is the LinkedGeoData project actively maintained? Many links on http://linkedgeodata.org are currently dead, including the browser (#18), the LinkedGeoData Ontology, or the Triplify links (such as http://linkedgeodata.org/resource/triplify/way27743320).

Aklakan commented

Hi jindrich, yes I am still maintaining it; although time is always short :)

According to OSM, way27743320 was deleted.
For example, this one works: http://linkedgeodata.org/triplify/way5013364 (note that there is no /resource/)

As for http://linkedgeodata.org/ontology this is indeed an issue, because actually the server is running, but it doesn't give a response. I need to investigate.

As for the browser: for quite a while I want to replace it with Facete, but unfortunately the app as a whole does not scale to LGD's size at present. In the apps architecture the use of external indices is forseen, but so far I didn't get around to implement them.

Yet, the SPARQL based map component should be capable of it - this is a old demo of it that does live queries against DBpedia: http://cstadler.aksw.org/jassa-ui/jassa-map-ol-demo

jindrichmynarz commented

Thanks for clarifying! Regarding the SPARQL access, do I understand correctly that the Virtuoso-based endpoint at http://linkedgeodata.org/sparql is not up-to-date, while the Sparqlify one at http://linkedgeodata.org/vsparql is?

Aklakan commented

Hi, yes, the vsparql one is live sync'd: SPARQL query for latest changes

It still has to catch up a bit (it was down during the download release creation), but this will happen in the coming days.

jindrichmynarz commented

Great, thanks for clarification.

talespaiva commented

Hi @Aklakan

is there any plans of updating the Virtuoso-based endpoint? The part that I'm woking with (Grenoble, France) is missing important updates.

While I can get the information I need from the vsparql endpoint, I have experienced that the Virtuoso one (/sparql) is better to query programatically (I'm using the SPARQLWrapper Python package). Despite I can send HTTP posts to /vsparql, the response is error 500 most of time and, when it works, the results are always XML regardless of the output parameter.

Thanks for the great work!