Technical environment

A set of tools and APIs that support the co-creation and validation of services and applications under real conditions in the prototype of an innovation ecosystem.

The technical environment enables experimenters to develop websites, web services, desktop applications or smartphone applications which interact with OrganiCity through APIs. The tools require developers, so we encourage you to create an experimentation team across disciplines.

Our tools and services are in development. Most of them are on beta version and some will carry development with you, as you experiment. Below you will find those which are currently stable to experiment. In addition, you can find all the tools and services in our documentation for developers.

Documentation for developers


This is the signing point for all interactions. To test any of the tools available in the demonstration version, sign in for a testing account and send an email to with your username to have a demo experimenter access.

Sign up to test

Management tools

Experimenter portal

The entry point to start each experiment. Here you will create and manage your experiments. It will also be your point of reference to navigate the rest of the technical facility. Ensure you register into the accounts and email for access.

Test the portal (beta)

Facility management

As a city authority or service provider, you will be federating data into Organicity. This portal allows the management of your federation. It allows you to isolate your data under different domains or services.

Explore and annotate data

Urban data observatory

Browse, search, download and visualise city data. You will see all OrganiCity and the data created by the experiments depending on the privacy settings of each data asset.
Once you are logged in, you can access the API related to each data point to discover more information.

Test the Urban data observatory

Data annotation service

Embedded in the Urban data Observatory, this service allows users to better describe the data. By using it, both experimenters and cities will enrich their data information making it more accurate and easier to understand.

Experimenter tools


An online portal for citizens to create, discuss and evaluate ideas for how the city of the future might work.

Use Scenarios


A sensing device for temperature and humidity which you can monitor from a purpose built software. There are 15 indoor sensing devices available.

TSmart documentation


A desktop tool to create custom web apps by dragging and dropping blocks. The main use is to display maps of data in the form of apps.

You need experience developing to build new blocks. You can code blocks from datasets in OrganiCity.

Test Tinkerspace


SensiNact aims at helping coders working with data streams from deployed “IoT” devices without the need to complex API configuration.

SensiNact documentation


This tool has been made available in order to provide real-time updates from assets in the OrganiCity platform.

Websockets documentation

Smartphone Experimentation

This guide will help you understand the functionality provided by the Smartphone Experimentation OrganiCity CoCreation tool, its capabilities and all the necessary steps to create, configure, monitor and manage your experiment as well as retrieve the data collected.

Smartphone Experimentation documentation



A collection of interfaces to interact with Organicity from your tools and applications. Whether you are an experimenter or a city which wants to federate data into Organicity, the different APIs will allow you to connect to the technical environment.

APIs documentation

Aarhus data sets

For an accurate list of data sets, query the APIs.

In the Aarhus cluster, we have integrated five data sources from the local open data platform. As the local platform becomes more mature we will make sure to feed additional data sources into OrganiCity thereby growing its asset base organically. In the following, we will describe each of the existing data sources in more detail.

Real-Time traffic data:
Dataset for traffic measurement in Aarhus and live/real-time measurements of traffic in Aarhus. Data is collected from 125 measurement points on selected roads in the city. Each time a car drives past with a mobile phone where the Bluetooth device is turned on, it is registered. By looking at the time it takes for the car to go from one measuring point to the next, the travel time is converted to a map showing the current traffic flow. The system is provided by Blipsystems. Historical data is not collected, because it would require significantly more space on ODAA’s server, and because it is relatively simple to design a service that itself saves the data in the resolution is needed. In this way, each user can even set this up to suit their own purposes and needs.

Origin of data:
Produced by sniffing Bluetooth signals from mobile devices (MAC addresses are hashed and deleted every day).

Data source properties:
Only latest measurement is available
Updated every 5 minutes
125 measuring stations in Aarhus
JSON format

Visitor numbers at DOKK1:
This dataset contains data from the cameras located at the entrances and exits at DOKK1 – the city’s main library – counting visitor numbers. Cameras are placed at the exits and special software installed on them counts the number of people going in and out.

Origin of data:
Video cameras performing video analysis

Data source properties:
Only latest measurement is available
Updated every 5 minutes
7 cameras
JSON format

Events in the City of Aarhus
A list of events taking place in Aarhus in JSON format.

Origin of data:
Different local communities and organisations feed data in manually

Data source properties:
Historical data is available
Updated every hour
Data is available from May 5, 2017
JSON format

Events in the libraries in Aarhus
Dynamic data set updated every day with a list of all the events taking place in the libraries in Aarhus.

Origin of data:
Library workers feed in data manually

Data source properties:
Historical data is available
Updated every day at 8:00, 11:00 and 16:00
Data is available from October 3, 2013
JSON format

Data from Friluftslivaarhus
Static datasets with geo-information in GeoJSON and KML about outdoor activities and – facilities such as dog parks, outdoor fitness areas,  bonfire places, running, horse and mountain bike routes, playing grounds, shelters and so forth.

Origin of data:
Updated manually by municipal workers

Data source properties:
Only updated data is available
Updated once a year
GeoJSON and KML formats

London data sets

For an accurate list of data sets, query the APIs.

Browse the data available at London Datastore and include in your project plan the integration of the data you need or make a request to the London team to integrate the specific data sets you need.

In addition, this is the data which is currently federated in OrganiCity:

London Borough and Neighbourhood Profiles:
Greater London is divided into 33 Boroughs and each Borough is divided into a number of Neighbourhoods. For each Borough and Neighbourhood, we gather aggregate statistics related to mobility, air quality and communities. Some statistics are based on the census that is collected every 10 years, while other statistics are updated more frequently. Example statistics include population density, average income, average house price, fraction of greenspace and an average number of cars per household. The data is gathered from the London Datastore, Public Health England and other sources.

London Traffic Counts:
In October every year, the Department of Transport performs an extensive traffic count throughout thousands of locations in England. The traffic counts are presented as daily averages of different vehicle types (bicycles, motorcycles, cars, vans, trucks, etc.) that pass through a certain point.

Transport (tube stations, bus stations, bike stations, tube lines, bus lines):
Transport for London and Transport API provide API endpoints for getting information about the London public transport network, tube stations, bus stops, city bicycle rental stations, tube lines and bus lines.

London Air Quality Network:
The London Air Quality Network (LAQN) provides pollution measurements that are essential to underpin air quality management and health studies. The majority of London’s 33 boroughs supply measurements to the network and in addition, these data are increasingly being supplemented by measurements from local authorities surrounding London, thereby providing an overall perspective of air pollution in London. The LAQN is operated and managed by the Environmental Research Group (ERG) at King’s College London. QA/QC audits are carried out by the National Physical Laboratory (NPL). Based on the 2014 LAQN report, the air quality observations made are Carbon Monoxide (CO), Nitrogen Dioxide (NO2), Sulphur dioxide (SO2), Ozone (O3), Particles (PM10) and Particles (PM2.5) along with environmental observations like Wind Speed, Temperature, Rainfall, etc. in over 60 monitoring sites.

Environmental sensors – Queen Elizabeth Olympic Park (QEOP):
A number of environmental stations (3 weather stations) have been deployed in QEOP measuring environmental conditions of the park like temperature, rain levels, wind direction and intensity, humidity, barometric pressure and light intensity.

Santander data sets

For an accurate list of data sets, query the APIs.

Based on the challenges identified as part of the co-creation process developed in the Santander cluster, an analysis of the assets available in the city has been carried out. As a result of such analysis, the following data assets have been integrated into the EaaS facility:


  • Traffic cameras. Four traffic cameras in the city provide real-time images about the status of the traffic in different areas of the city.
  • Traffic intensity sensors. Placed at the main entrance of the city, a set of 48 sensors, provides information about the occupancy, the count of vehicles, the median and average speed in the different lanes of these main roads.
  • Traffic congestion information in the city.  Based on the deployment of the inductive loops existing in the city of Santander, real-time information about the traffic congestion in the city is provided. To this end, the streets of the city are represented by different polylines, including information on how congested this particular path is.
  • Real time information of available parking spots within zone 30. A set of 400 ferromagnetic sensors is placed under the asphalt in zone 30 of the Santander city centre, providing real-time information about the status of occupancy of the different parking spots.
  • Indoor parking. Along the city of Santander, 12 indoor public parking facilities managed by private companies can be found. For every parking facility, a singular asset is created, including information about the occupancy of parking spots and also other extra information.
  • 30 zone areas. Within the city, different areas have been limited to a maximum speed of 30km/h. Assets for each zone have been created, defined by the polygon of the particular areas.
  • Load and unload areas within the city of Santander are provided as part of the assets that will be integrated.
  • Bus lines. To provide information about the existing buses lines in the city, a set of 20 assets, one for each bus line have been integrated.
  • Bus routes. For each one of the bus lines, different routes are implemented. These assets provide information related to the routes of a particular line.
  • Bus stops. A set of 415 assets, one per bus stop in the city, have been created. Those assets provide real-time information about next buses reaching the bus stop, including the distance to reach the bus stop as well as the estimated time of arrival for the first and second bus coming.
  • Taxi stops. These assets provide real-time information about taxi availability in each particular stop, based on the information provided by the fleet management systems deployed by the two taxi associations.
  • Bike stops. A set of 16 assets has been created, providing information about the number of available public hire bikes and also the number of places to return such bikes.
  • Bike lanes. A set of assets, including polylines that represent the lanes for bikes in the city of Santander, will be available.

Neighbourhood improvement:

  • Districts and sections. Assets representing the areas of the districts and sections in which the city is divided using polygons.
  • Pace of the city events. PaceoftheCity application allows citizens to report incidents happening of the city. Each event reported by the citizens constitutes one asset in OC belonging to the Santander site.
  • Shopping information. Assets including information about more than 2000 shops belonging to the “ComercioSantander” initiative will be available for experimenters to create better services in the different neighbourhoods.
  • News. Assets based on the Feeds of news in the city of Santander will be created.
  • Cultural agenda. Events of the “Santander Auna” agenda are integrated as singular assets, providing information about when an event will happen, where and other details.  


  • Environmental nodes. Both fixed and mobile nodes measuring environmental parameters in the city will be available as data assets.
  • Beaches.  Data assets will be created based on the information of the beaches in the city. Accessibility or any other information that may result in interest will be included as attributes of such assets.  
  • Parks and gardens. Information about parks and gardens in the city, the irrigation sensors installed on them will be data assets of the OrganiCity facility