Exploring data

Class hierarchy

To explore your data, navigate to Explore -> Class hierarchy. You can see a diagram depicting the hierarchy of the imported RDF classes by the number of instances. The biggest circles are the parent classes and the nested ones are their children.


If your data has no ontology (hierarchy), the RDF classes is visualised as separate circles, instead of nested ones.


Explore your data - different actions

  • To see what classes each parent has, hover over the nested circles.

  • To explore a given class, click its circle. The selected class is highlighted with a dashed line and a side panel with its instances opens for further exploration. For each RDF class you can see its local name, URI and a list of its first 1000 class instances. The class instances are represented by their URIs, which when clicked lead to another view, where you can further explore their metadata.


    The side panel includes the following:

    • Local name;
    • URI (Press Ctrl+C / Cmd+C to copy to clipboard and Enter to close);
    • Domain-Range Graph button;
    • Class instances count;
    • Scrollable list of the first 1000 class instances;
    • View Instances in SPARQL View button. It redirects to the SPARQL view and executes an auto-generated query that lists all class instances without LIMIT.
  • To go to the Domain-Range Graph diagram, double click a class circle or the Domain-Range Graph button from the side panel.

  • To explore an instance, click its URI from the side panel.

  • To adjust the number of classes displayed, drag the slider on the left-hand side of the screen. Classes are sorted by the maximum instance count and the diagram displays only the current slider value.

  • To administer your data view, use the toolbar options on the right-hand side of the screen.

    • To see only the class labels, click the Hide/Show Prefixes. You can still view the prefixes when you hover over the class that interests you.
    • To zoom out of a particular class, click the Focus diagram home icon.
    • To reload the data on the diagram, click the Reload diagram icon. This is recommended when you have updated the data in your repository or you experience some strange behaviour, for example you cannot see a given class.
    • To export the diagram as an .svg image, click the Export Diagram download icon.

Domain-range graph

To see all properties of a given class as well as their domain and range, double click its class circle or the Domain-Range Graph button from the side panel. The RDF Domain-Range Graph view opens, enabling you to further explore the class connectedness by clicking the green nodes (object property class).

  • To administer your graph view, use the toolbar options on the right-hand side of the screen.

    • To go back to your class in the RDF Class hierarchy, click the Back to Class hierarchy diagram button.
    • To export the diagram as an .svg image, click the Export Diagram download icon.

Class relationships

To explore the relationships between the classes, navigate to Explore -> Class relationships. You can see a complicated diagram which by default is showing only the top relationships. Each of them is a bundle of links between the individual instances of two classes. Each link is an RDF statement where the subject is an instance of one class, the object is an instance of another class, and the link is the predicate. Depending on the number of links between the instances of two classes, the bundle can be thicker or thinner and gets the color of the class with more incoming links. These links can be in both directions. Note that contrary to the Class hierarchy, the Class relationships diagram is based on the real statements between classes, not on the Ontology schema.

In the example below, you can see that Person is the class with the biggest number of links. It is very strongly connected to Feature and City and most of the links are from Person. Also, you notice that all classes have many outgoing links to opengis:_Feature.


Left to the diagram you can see a list of all classes ordered by the links they have and an indicator of the direction of the links. Click on it to see the actual classes this class is linked to, again ordered by the number of links with the actual number shown. Also, the direction of the links is displayed.


Use the list of classes to control which classes to see in the diagram with the add/remove icons next to each class. Remove all classes by the rubber icon. The green background of a class indicates that the class is present in the diagram. You see that Person has much more connections to City than Village.


For each two classes in the diagram you can find the top predicates that connect them, again ordered and with the number of statements of this predicate and instances of these classes. Person is linked to City by the birthPlace and deathPlace predicates.


All these statistics are built on top of the whole repository so when you have a lot of data, the building of the diagram may be very slow. Please, be patient in that case.

Viewing and editing resources

View and add a resource

To view a resource in the repository, go to Explore -> View resource and enter the URI of a resource or navigate to it by clicking the SPARQL results links.


Viewing resources provides an easy way to see triples where a given URI is the subject, predicate or object.


Even when the resource is not in the database, you can still add it from the resource view.

_images/resourceFindNew.png _images/resourceNew.png

Here, you can create as many triples as you need for it, using the resource edit. To add a triple, fill in the necessary fields and click the tick, next to the last one.


To view the new statements in TriG, click the View TriG button.

_images/resourceViewTriG-1.png _images/resourceViewTriG-2.png

When ready, save the new resource to the repository.

Edit a resource

Once you open a resource in View resource, you can also edit it. Click the edit icon next to the resource namespace and add, change or delete the properties of this resource.



You cannot change or delete the inferred statements.