<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <issn pub-type="ppub">1613-0073</issn>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Railway track video Knowledge Base</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kai Herbst</string-name>
          <email>Kai.Herbst@deutschebahn.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rene Krieg</string-name>
          <email>Rene.Krieg@deutschebahn.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dirk Friedenberger</string-name>
          <email>Dirk.Friedenberger@deutschebahn.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Athen'23: The 22nd International Semantic Web Conference</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>DB Systel GmbH</institution>
          ,
          <addr-line>Frankfurt</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A video knowledge graph and a corresponding ontology was created based on railway track videos and infrastructure data. It was shown that the heterogeneous and distributed infrastructure and track data in the railway company, enriched with visualisations such as images and videos, implemented as an RDF/OWL graph, fulfill the required use cases and increases business value. These use cases include tasks such as being able to quickly query the graph for a videos in which specific infrastructure elements occur or being able to search for video sequences that start or end with certain elements.</p>
      </abstract>
      <kwd-group>
        <kwd>knowledge graph</kwd>
        <kwd>railway track videos</kwd>
        <kwd>railway infrastructure</kwd>
        <kwd>RDF graph</kwd>
        <kwd>OWL ontology</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>CEUR
ceur-ws.org</p>
    </sec>
    <sec id="sec-2">
      <title>Motivation</title>
    </sec>
    <sec id="sec-3">
      <title>2. Problem Statement</title>
      <p>Monitoring the railway infrastructure is an important part of maintenance. So far, it has
been possible to use the videos to search for the elements, but it has not been possible to jump
directly to the relevant points in the video. Another requirement is the training of train drivers.
Here it is very helpful to be able to use video sequences of special constellations, e.g. passing
through a station from the entry signal to the exit signal, especially location-related to the
stationing of the train driver. To achieve this, the videos must be linked to the elements of the
infrastructure, but also to the information of the railway tracks. These heterogeneous data
CEUR
Workshop
Proceedings
sources are usually distributed throughout the railway company. A harmonized graph-based
and queryable data view would cover a multitude of use cases beyond those mentioned.</p>
    </sec>
    <sec id="sec-4">
      <title>3. Approach</title>
      <p>Firstly the ontology was designed based on the various data sources, modeling diferent
entities and relationships such as signals and stations. The ontology was developed by the
team itself, instead of using an external ontology, in order to be able to adapt it exactly to the
data. The ontology is built up on the data sources mentioned below. For each train ride, we
receive data from LeiDis 1 (Leitsystem Disposition), a control system that monitors the current
operations on the rail network. That data includes information about the stations visited during
the ride, as well as the date and time at which the train arrived at certain stations. Data about
infrastructure occurring at specific kilometer marks along each railway track is derived from
so called substitute timetables. These timetables include all the necessary information for a
train driver, if he needs to drive a railway track without the modern digital version of these
information. Furthermore we can determine for every second of the video the precise location
of the train on the railway track, in terms of kilometer position. The graph also incorporates
various datasets related to tracks and stations. After converting and harmonizing these data
within the knowledge graph, complex queries can now be formed using SPARQL.</p>
      <p>
        The modelling and creation of the ontology associated with the Knowledge Graph were
implemented using the Protégé software 2 from the Stanford University, which supports the W3C
standards of the RDF format and the OWL Web Ontology Language. After no existing ontology
could be found for the specific domain we were describing, we had to build one ourselves. This
has been accomplished by following the steps described in the ”Ontology Development 101”
Guide [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] from the Stanford University and ideas of the ”Generic Ontology Design Patterns”
paper [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. In order to convert the mentioned data into rdf data, a Python module was developed
to collect, process and convert the video specific data into the rdf format. GraphDB 3, based on
the RDF4J framework, was used as the triple store, providing a SPARQL endpoint and a web
interface for working with RDF triples. The architecture of the knowledge graph itself follows
a classical approach described in the paper ”Towards a Definition of Knowledge Graphs” [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] by
sending rdf data to GraphDB, that holds the ontology and uses it for deriving new knowledge.
To interact with the Knowledge Graph, a REST API and a user interface were created using the
FastAPI Python package4. This additional frontend, in which various use cases are predefined,
also allows non-experts to use the information in Knowledge Graph.
1Leitsystem Disposition
2Protégé
3GraphDB
4FastAPI
      </p>
    </sec>
    <sec id="sec-5">
      <title>4. Results</title>
      <p>The knowledge graph enables us to quickly execute powerful queries based on the
combination of data from the railway track network infrastructure and our videos. For example, a
simple query can list the various infrastructure elements occurring in a specific video. This
allows us to search for specific types of signals and list videos with timestamps containing
those elements. By referring to the timestamp in the video, the corresponding element in the
video can be found and visualised, see figure 1. By querying the knowledge graph for videos of
a particular element and sorting the results based on the video recording dates, we can also
analyze the infrastructure over a specific period. Searching for videos with specific elements
or passages through specific stations is particularly useful, especially for training purposes.
Additionally, since GPS data about infrastructure elements are also included in the graph, it is
possible to search for elements within a certain radius of a position.</p>
    </sec>
    <sec id="sec-6">
      <title>5. Conclusions</title>
      <p>This knowledge graph, developed as part of a bachelor’s thesis, ofers significant potential,
particularly due to the underlying RDF data format and the ease of expanding the graph,
extending far beyond its sole use within our team. The graph allows the aggregation of
diferent data from diferent sources in the rail sector. In addition the corresponding SPARQL
endpoint allows us to easily publish the data for others. A possible future improvement to the
knowledge graph could be not to use the aforementioned substitute timetables to determine
the infrastructure elements in a video, but rather to use AI-based recognition mechanisms to
extract the timestamp and position of these elements from the video itself.</p>
      <p>The corresponding presentation will be focused on how we used semantic technology to solve
a problem, that would have been dificult to implement with traditional tools like a relational
database and how we are now able to easily extend the gathered knowledge with more data.</p>
    </sec>
    <sec id="sec-7">
      <title>A. Online Resources</title>
      <p>• Protégé
• GraphDB
• FastAPI
• LeiDis</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>N. F.</given-names>
            <surname>Noy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. L.</given-names>
            <surname>McGuinness</surname>
          </string-name>
          , et al.,
          <article-title>Ontology development 101: A guide to creating your ifrst ontology</article-title>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>B.</given-names>
            <surname>Krieg-Brückner</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Mossakowski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Codescu</surname>
          </string-name>
          ,
          <article-title>Generic ontology design patterns: Roles and change over time</article-title>
          ,
          <year>2020</year>
          .
          <article-title>a r X i v : 2 0 1 1 . 0 9 3 5 3</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>L.</given-names>
            <surname>Ehrlinger</surname>
          </string-name>
          , W. Wöß,
          <article-title>Towards a definition of knowledge graphs</article-title>
          .,
          <source>SEMANTiCS</source>
          (Posters, Demos, SuCCESS)
          <volume>48</volume>
          (
          <year>2016</year>
          )
          <article-title>2</article-title>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>