Semantic Description of IndoorPositioningMonitoring UrbanDataset from SCP Ontology 2.0

This document provides human-friendly documentation for IndoorPositioningMonitoring UrbanDataset having semantic definition in the SCP Ontology 2.0, part of the "Smart City Platform Specifications (SCPS) - Semantic Level" developed as part of the Electricity System Research Project.

File creation date

2025-12-07 17:47

SCPS URL

https://smartcityplatform.enea.it/#/it/index.html

Introduction

This document provides the human-friendly representation of the semantic definition of one or more SCPS ontology´s UrbanDatasets.

Each UrbanDataset is described through a table composed of three main sections:

UrbanDataset Identification: defines the purpose of the UrbanDataset and the parameters (identifier, name and URI) uniquely identifing it in the SCPS scope. It states the information that populates the "Specification" section of UrbanDataset messages.
UrbanDataset Contextualization: defines the context properties (ContextProperty) associated with the UrbanDataset; for each one it specifies name, meaning (description), data type and set of values (code list) to which it is constrained, if any. The UrbanDataset context properties have not units of measurement and are all mandatory unless otherwise indicated in the description. Furthermore, this section provides any indications on the use of context properties within the specific UrbanDataset. It states the properties that populate the "Context" section of UrbanDataset messages.
UrbanDataset Properties: states the properties (UrbanDatasetProperty) uniquely defining the UrbanDataset in the SCPS ontology; for each one it specifies name, meaning (description), if it is required, data type, set of values (code list) to which it is constrained, if any, and the admitted units of measurement. The properties properties marked with an asterisk require to indicate, at instance level, the adopted calculation method (for example, total or average value over the measurement period). It states the properties that populate each row of the "Values" section of UrbanDataset messages.

The normative references concerning the syntactic and semantic compliance of UrbanDatasets with the SCPS are:

depending on the adopted syntax, the schema scps-urbandataset-schema-2.0:
- JSON Schema
- XML Schema
the UrbanDataset semantic definition that can be acquired or through the OWL ontology, or through the UDWebLibrary, or through this documentation.

Furthermore, in the resources section available in the tab of each UrbanDataset in the UDWebLibrary, it is possible to download the message templates in JSON and XML syntax, compliant with the specifications. A template is an example of an UrbanDataset instance having all the properties (mandatory and optional) that make it (for any properties with alternative units of measurement and/or calculation method, the default values are used).

SECTION I: UrbanDataset

IndoorPositioningMonitoring-2.0

UrbanDataset Identification
Scope	Monitoring the positioning of a person inside a building
Category / Subcategory	BuiltEnvironment / SmartHome
Identifier	IndoorPositioningMonitoring-2.0
Name	Indoor Positioning Monitoring
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/ontology/scps-ontology-2.0.owl#IndoorPositioningMonitoring
UrbanDataset Contextualization
	Description	Format/Code list
coordinates	Geographical reference	Aggregated property
subProperty: format	Wgs84 format in which the coordinates are expressed (optional attribute)	string FormatCode.gc
subProperty: height	Altitude (optional property)	double
subProperty: latitude	Latitude	double
subProperty: longitude	Longitude	double
language	The language in which the text fields of the instance are expressed	string LanguageCode.gc
timestamp	Timestamp	dateTime
timezone	The time zone to be applied to each timestamp in the instance; it is expressed as an offset, i.e. as + or - the number of hours and minutes respect to UTC time: +/-hh:mm (ISO 8601)	string TimezoneCode.gc
UrbanDataset Properties * properties marked with an asterisk require to indicate, at instance level, the adopted calculation method (e.g. "average", "total", "instantaneous",...)
Name	Description	Mandatory	Format/Code list	Unit of Measure
FloorNumber	An identifier for a floor in a building	yes	integer
PresencePercentage	The percentage of time that at least one person was in a location	yes	double
PresenceScannerCount	Number of tracking devices used by the indoor presence detection system	yes	integer
RoomCode	A code identifying the type of room (e.g. kitchen, bathroom, office) where the sensor is located	yes	string RoomCode.gc
SensorID	A unique identifier of the sensor, e.g. the serial number, the mac address	yes	string
SensorName	Brand or model code of the sensor	yes	string
SensorTypeCode	The type of sensor (e.g. smart plugs, smart switches, presence, ..) that carries out the measurement, expressed as code.	yes	string SensorTypeCode.gc
coordinates	Geographical reference	yes	Aggregated property
subProperty: format	Wgs84 format in which the coordinates are expressed (optional attribute)	no	string FormatCode.gc
subProperty: height	Altitude (optional property)	no	double
subProperty: latitude	Latitude	yes	double
subProperty: longitude	Longitude	yes	double

Semantic Description of IndoorPositioningMonitoring UrbanDataset from SCP Ontology 2.0

Table of content

Introduction

SECTION I: UrbanDataset

SECTION II: Code lists

Introduction

1. How to read this document

2. Artifacts to create an UrbanDataset message

SECTION I: UrbanDataset

IndoorPositioningMonitoring-2.0