Semantic Description of Transits UrbanDataset from SCP Ontology 2.0

This document provides human-friendly documentation for Transits 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 11:10

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

Transits-2.0

UrbanDataset Identification
Scope	Provides information relating to the transit of people or transport means (possibly classified by age range, gender, origin, type of transport means, etc.), giving them a spatial and temporal location. Transits can be related to a route specified via departure point, arrival point and any further monitoring points or to a single point (in this case it will correspond to the departure point)
Category / Subcategory	Transportation / TrafficManagement
Identifier	Transits-2.0
Name	Transits
URI	https://smartcityplatform.enea.it/specification/semantic/2.0/ontology/scps-ontology-2.0.owl#Transits
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
StartLocationID	Identifier of the departure location in the case of a route, or of monitoring place in the case of a single transit point	yes	string
TransitCount *	Number of detected transits	yes	integer
coordinates	Geographic coordinates of the StartLocationID (starting point of the route or single monitoring point, when transits are monitored in a single point)	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
period	Measurement period of the data reported in the row	yes	Aggregated property
subProperty: end_ts	Timestamp indicating the end of the period	yes	dateTime
subProperty: start_ts	Timestamp indicating the beginning of the period	yes	dateTime
ADRCode	Dangerous goods identification code	no	string ADRCode.gc
AnomalousTransitCount *	Number of anomalous transits detected (e.g. transits in the opposite direction to the direction of travel)	no	integer
CarrierName	The name of the carrier carrying out the transport	no	string
EndLocationID	An identifier for the end location of the monitored route	no	string
EndLocationName	A name for the end location of the monitored route	no	string
EndTimeSlot	End time of a time slot	no
EuroClassCode	A code identifying the EURO class of the vehicle	no	string EuroClassCode.gc
LocationID	An identifier for the monitored location	no	string
LocationName	Location name	no	string
MonitoringPointCode	A code specifying in which points of a route the sensors for detecting transit are present	no	string MonitoringPointCode.gc
PeriodQualifierCode	A qualifier for the period	no	string PeriodValueQualifierCode.gc
PeriodValue	The period expressed as a textual value (e.g. "Tuesday", "Wednesday", "2022", etc.)	no	string
PhysicalUnitCategoryCode	A code indicating the category (people, vehicles) the number of transits indicated in the TransitCount field refers to	no	string PhysicalUnitCategoryCode.gc
SchemeID	Indicates the encoding scheme the identifier provided in the Location fields belong to	no	string
StartLocationName	A name for the starting location of the monitored route	no	string
StartTimeSlot	Start time of a time slot	no
TimeSlotDescription	Time slot expressed as a value. Recommended values "daytime", "nighttime", where, if not specified by "Start time" and "End time", it is assumed that: - daytime: from 07:00 to 18:59 - nighttime: from 19:00 to 06:59	no	string
TotalCountFlag	States whether the indicated number of transits is total (true) or partial (false) for the indicated period	no	boolean
TransportMeansCode	A code indicating the macrocategory which the transport means belongs to	no	string TransportMeansCode.gc
TransportScopeCode	A code specifying the type of cargo of the transport means (people, goods, animals, etc.)	no	string TransportScopeCode.gc
VehicleRegistrationCountryCode	A code specifying the country of vehicle registration	no	string CountryCode.gc
WorkingDayFlag	Indicates if the data contained in the row refers to weekdays or holidays

Semantic Description of Transits 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

Transits-2.0