The Resource Management component in the CityPulse framework is responsible for managing all Data Wrappers. During runtime an application developer or the CityPulse framework operator can deploy new Data Wrappers to include data from new data streams.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


The Resource Management component is responsible for managing all Data Wrappers. During runtime an application developer or the CityPulse framework operator can deploy new Data Wrappers to include data from new data streams. The folder "wrapper_dev" contains examplary Data Wrappers for traffic and parking data of the city of Aarhus, Denmark as well as weather, air quality and incidents of the city of Brasov, Romania. The Resource Management component can be used for the following types of scenarios:

  • Fetch live stream data via one or more Data wrappers
  • Replay historic data embedded in a Data wrapper


The following Ubuntu packages need to be installed in order to run the Resource management:

  • python-pip
  • libgeos++-dev
  • libgeos-3.4.2
  • python-dev
  • libpq-dev
  • git
  • zip

The Resource management is implemented in the programming language Python. The following Python packages have to be installed before using the component. The packages are available either in the package repository of the Ubuntu operating system or can be installed using PIP.

  • Pika (version 0.9.x)
  • CherryPy
  • Psycopg2
  • NumPy
  • SciPy
  • SKLearn
  • RDFlib
  • Requests (version > 2.8)
  • Requests-oauthlib
  • Chardet

Dependencies to other CityPulse components

For the Resource management in order to run properly it needs to have access to the following CityPulse components: Message Bus; Geospatial Data Infrastructure and the Knowledge Base (Triplestore).


As mentioned before, the CityPulse Resource management requires additional libraries, which can be installed using the following command on an Ubuntu Linux installation. The Resource management is not limited to Ubuntu Linux, but no other Linux distribution has been tested so far.

sudo apt-get install python-pip libgeos++-dev libgeos-3.4.2 python-dev libpq-dev python-scipy git automake bison flex libtool gperf unzip python-matplotlib

In addition, using the following command required python packages will be installed: sudo pip install pika cherrypy shapely psycopg2 numpy sklearn rdflib chardet requests requests-oauthlib

The Resource management uses the Virtuoso triplestore to store annotated observations. As of February 2016, the virtuoso provided with the apt-repository in Ubuntu 14.04 LTS is outdated and lacks required features. Therefore, an installation from the sources is necessary. This can be achieved with the followings commands:

wget --no-check-certificate -q -O
unzip -q
cd virtuoso-opensource
sudo make install

After that start the virtuoso:

sudo /etc/init.d/virtuoso-opensource-7 start

NOTE: the make command may hang after "VAD Sticker vad_dav.xml creation ..." if there is a virtuoso process running. Check with "ps ax|grep virtuoso" and kill if a virtuoso is running.

Afterwards you can download the Resource Management source code from the Github repository:

git clone

The next step is to edit the configuration file with your favourite editor. An example configuration can be found in virtualisation/config.json. For details about the configuration file see Table 1. When running the Resource management in replay mode the python process may require a lot of file descriptors to read the historical data. Users may be required to increase a limit for file descriptors in the operating system. To change the limit on Mac OS X 10.10 and higher run the following command in a terminal:

sudo launchctl limit maxfiles 2560 unlimited

This will set the limit to 2560. On Linux

ulimit -n 2560

should do the trick. Add the line into the .bashrc in your home directory to make it permanent.


The Resource management uses a configuration file to store the connection details to other components of the framework. The configuration is provided as JSON document named “config.json” within the “virtualisation” folder. The configuration consists of a dictionary object, where each inner element holds the connection details to one component of the framework, also as a dictionary. The following table lists all inner dictionary keys (bold) and their content.

driverThe Resource Management supports the use of either Virtuoso or Apache Fuseki as triplestore. The value “sparql” tells the Resource Management to use Virtuoso. “fuseki” for Fuseki.
hostThe hostname/IP of the triplestore as string.
portThe port of the triplestore as integer.
pathThe path to the sparql-endpoint.
base_uriThe base URI is used to create the graph name
hostThe hostname/IP of the message bus as string.
portThe port of the message bus as integer.
The configuration of the HTTP based API interface. The API is realised using the CherryPy framework. The configuration here is directly passed to CherryPy’s ‘quickstart’ method. Therefore all configuration options CherryPy provides are available. For more details see
hostThe hostname/IP of the geo-spatial database as string.
portThe port of the geo-spatial database as integer.
usernameThe username for the database as string.
passwordThe user’s password for the database as string.
databaseThe name of the database to use as string.

Running the component

The Resource management is started via command line terminal. There are a series of command line arguments available to control the behaviour of the Resource management. In the following all command line arguments and their purpose.

replayStart in replay mode. In replay mode historic sensor observations between the time frame START and END are used instead of live data. Also the replay speed can be influenced by the speed argument. Requires that the Resource Management has been started at least once before.
from STARTIn replay mode determines the start date. The format is “%Y-%m-%dT%H:%M:%S“.
to ENDIn replay mode determines the end date. The format is “%Y-%m-%dT%H:%M:%S”.
messagebusEnable the message bus feature. The Resource Management will connect to the message bus and publish new observation as soon as they are made.
triplestoreEnable the triplestore feature.
aggregateUse the aggregation method, as specified in the SensorDescription, to aggregate new observations.
speed SPEEDIn replay mode determines the speed of the artificial clock. The value range is [0-1000]. An artificial second within the replay will take 1000 – SPEED milliseconds.
gdiGeospatioal Database Interface. Newly registered Data wrappers are reported to the Geospatioal Database.
gentleReduces the CPU load in replay mode, but slower.
cleartriplestoreDeletes all graphs in the triplestore (may take up to 300s per wrapper!)
restartRestarts the Resource Management with the same arguments as last time.
eventannotationThe Resource Management will listen on the message bus for new events to semantically annotate them and store them into the triplestore. Last feature requires the triplestore argument.


The code of the Resource Management can be found here:

More details for this component can be found in the CityPulse Deliverable 5.3 "Real-Time IoT Stream Processing and Large-scale Data Analytics for Smart City Applications", April 2016,


The Resource Management was developed as part of the EU project CityPulse. The consortium members University of Surrey and University of Applied Sciences Osnabrück provided the main contributions for this component.

License of historical data

Historical data sets for the Aarhus parking and the Aarhus traffic data wrapper are collected from the Open Data Aarhus portal ODAA. The data is published under the Creative Commons-license CC0 or CC-BY. The format has been changed from JSON to CSV and the data has been sorted by the 'REPORT ID' or the 'GARAGECODE' respectively.