RDF Surveyor is an easy-to-use exploration tool of semantic datasets. It can be plugged in any CORS-enabled SPARQL 1.1 endpoint without requiring any installation.
These are some of the features of RDF Surveyor:
-
Intuitive user interface that completely hides the RDF/SPARQL syntax
-
It gives an overview of the repository contents, supports class navigation and individual visualization
-
No installation required for exploring any RDF dataset
-
Works with large datasets such as DBpedia
-
Prepared to work with multilingual datasets
-
The UI adapts to mobile devices
-
RESTful design
RDF Surveyor is a web application developed in Javascript. You can easily deploy it in your web server or just try RDF Surveyor on http://tools.sirius-labs.no/rdfsurveyor
To begin the exploration of a repository, you only need to copy the URI of the target SPARQL endpoint (and optionally the URI of the named graph). You can also import the URIs of some well-known repositories such as DBpedia with the "Import configuration" button.
RDF Surveyor is available under an Apache 2 license. Please send us an email to [email protected] if you use or plan to use RDF Surveyor in a project. Drop us also a message if you have comments or suggestions for improvement.
Some screenshots of RDF Surveyor:
You can edit the parameters of the configuration file at etc/data/config.js:
-
pagesize: number of elements per page (default 10) -
hidemax: maximum number of elements to show in a list before including a show more button (default 8) -
hidebegin: element index to begin hiding (default 5) -
repos: preloaded configuration of repositories. Each element should have a name, an endpoint URI, and optionally a named graph URI -
geoenabled: if true, RDF Surveyor will try to find geographic coordinates for individuals and show a map widget provided by Leaflet. -
geooptions: the map widget provided by Leaflet requires your ownaccessToken. The rest of parameters here should not be changed -
gaenabled: if true, RDF Surveyor will log events (requested resource, latency, and number of SPARQL queries) through Google Analytics -
gaproperty: you have to provide your own property in order to log Google Analytics events