Urban Motor Vehicle Traffic Ontology, including control equipment for traffic, traffic measurement devices. traffic sections and incidents.
Traffic refers to the circulation of vehicles that occurs in a certain space and period of time. In order to know how this circulation takes place, or better known as the state of the traffic, a great variety of devices are used to carry out the measurements, for example, turns, artificial vision, etc. These measurements are generally made taking into account different variables, for example: the number of vehicles that pass through an area in a certain period of time, the speed of the vehicle, the type of vehicle, etc. Additionally, it is necessary to consider the incidents that occur on the roads and that influence the circulation of vehicles. These incidents can be planned, as in the case of long-term works or demonstrations, or unplanned, as in the case of accidents.
Having the data on the traffic that occurs in cities is a valuable input for both the Town Halls and the public. On the one hand, thanks to this data, Town and City Councils can have a valuable input for urban planning in different areas such as traffic management, road infrastructure design, forecasts and policies regarding pollution protocols, mobility studies, etc. On the other hand, citizens benefit from the availability of this data to plan the best route to move around, make the decision to use public transport instead of their own vehicle, etc.
In the City Councils, traffic data is published either through visualizations or available files, in some cases in their open data portals, in formats such as: CSV, XLS, XML, KML, JSON, etc. The level of detail and update frequency (which can range from about 5 minutes to several hours) varies between entities, however, it is noted that in general there is traffic status data expressed as traffic intensity, location of points where measurement devices are located, expected incidents on the roads, etc.
Having the semantic representation of traffic status data by means of a consensus model is an opportunity for the development of tools to facilitate access to and exploitation of this data. And in the future, its relationship with other sets of data that can enrich it, for example, data from the street map, districts, neighbourhoods, etc.
dc | <http://purl.org/dc/elements/1.1/> |
dct | <http://purl.org/dc/terms/> |
escjr | <http://vocab.linkeddata.es/datosabiertos/def/urbanismo-infraestructuras/callejero#> |
estraf | <http://vocab.ciudadesabiertas.es/def/transporte/trafico#> |
geo | <http://www.w3.org/2003/01/geo/wgs84_pos#> |
geocore | <https://datos.ign.es/def/geo_core#> |
geosparql | <http://www.opengis.net/ont/geosparql#> |
owl | <http://www.w3.org/2002/07/owl#> |
rdf | <http://www.w3.org/1999/02/22-rdf-syntax-ns#> |
rdfs | <http://www.w3.org/2000/01/rdf-schema#> |
schema | <http://schema.org/> |
sf | <http://www.opengis.net/ont/sf#> |
skos | <http://www.w3.org/2004/02/skos/core#> |
sosa | <http://www.w3.org/ns/sosa/> |
time | <http://www.w3.org/2006/time#> |
vann | <http://purl.org/vocab/vann/> |
xml | <http://www.w3.org/XML/1998/namespace> |
xsd | <http://www.w3.org/2001/XMLSchema> |
This vocabulary represents the traffic information of cities, which includes motor vehicles and excludes other types of vehicles or passers-by.
Therefore the scope of this vocabulary is defined in:
Figure 1 shows the classes and properties of the traffic vocabulary. The main objective of this vocabulary is to allow the representation of traffic equipment as well as incidences.
In order to represent monitoring devices it has been created the concept estraf:EquipoTrafico that must be associated with a estraf:tipoEquipoTrafico that links with the taxonomy estraf-kos:tipo-equipo-trafico. Their properties are a identifier dct:identifier, a description estraf:descripcion, the number of directions it performs estraf#numSentidos, the number of lanes estraf:numCarriles and whether it is urban or not estraf:urbano.
This device monitors estraf:monitorea a section estraf:Tramo which is a created class to describe sections monitored by devices and sections affected by an estraf:Incidencia.
There are two types of traffic equipment, traffic control equipment estraf:EquipoTrafico and traffic measurement devices estraf:DispositivoMedicionTrafico. Both devices and their corresponding subtypes are defined in the above-mentioned taxonomy estraf-kos:tipo-equipo-trafico.
For traffic measurement devices it has been created the class estraf:DispositivoMedicionTrafico which is also a a subclass of sosa:Sensor and it is displayed in the diagram that explains this section of the vocabulary focused on the description of the performance of measurement devices.
The class estraf:DispositivoMedicionTrafico which is a subclass of estraf:EquipoTrafico and sosa:Sensor is monitoring sosa:observes the created class estraf:PropiedadMedicionTrafico which is a subclass of sosa:ObservableProperty where it is especified the unity of measurement of the device with the property estraf:unidadMedida. Moreover, estraf:DispositivoMedicionTrafico it has an attribute that indicates whether or not it is on service estraf:enservicio
The class estraf:PropiedadMedicionTrafico has six instances which are the measurements defined so far: intensity estraf:intensidad, occupation estraf:ocupacion, load estraf:carga, speed estraf:velocidad, occupation level estraf:nivel and composition estraf:composicion.
The properties are the observed properties sosa:observedProperty of the class estraf:ObservacionTrafico, a created class which is a subclass of sosa:Observation with the following attributes: the result time sosa:resultTime, the result itself sosa:hasSimpleResult and the created property "validated" estraf:validada. The time in which the observation has been made is expressed through the property sosa:phenomenonTime which links with the class time:ProperInterval, subclass of time:Interval which has the beginning of an interval time:hasBegining and an end time:hasEnd which both link with the class time:Instant which is also, as time:Interval, a subclass of time:TemporalEntity. Finally, the observation has a feature of interest relation sosa:hasFeatureOfInterest with the section estraf:Tramo it monitors.
The main concept of this section is Incidence estraf:Incidencia which is linked to section estraf:Tramo through the property incidence in section estraf:incidenciaEnTramo.
Due to the fact that is a subclass of geosparql:Feature as well as estraf:Tramo and estraf:EquipoTrafico are, they have the property geosparql:hasGeometry which links with the localisation in a geographic point sf:Point whose attributes are the coordinates in WGS84 with geo:lat and geo:long and in ETRS89 with geo_core:xETRS89 and geo_core:yETRS89.
It also relations with the taxonomy of types of incidence estraf-kos:tipo-incidencia through the property estraf:tipoIncidencia.
estraf:Incidencia has an identifier dct:identifier, a description dct:description, a start date schema:startDate, an end date schema:endDate, the number of directions it affects estraf:numSentidos and the number of lanes estraf:numCarriles.
It has two subclasses, the planned incidence estraf:IncidenciaPlanificada and the unplanned incidences estraf:IncidenciaNoPlanificada for those who are not planned.
As well as for estraf:Incidencia, estraf:EquipoTrafico and estraf:Tramo are also subclasses of geosparql:Feature, so it is repeated the property geosparql:hasGeometry as in estraf:Incidencia.
In order to facilitate the understanding of the use of some classes and properties of this vocabulary, some examples are provided below:
Firstly for the representation of the traffic device it is created the class estraf:EquipoTrafico, or estraf:DispositivoMedicionTrafico if this is a measurement traffic device. In any case the device has an identifier dct:identifier, a description dct:description and if it is a measurement traffic device also the property estraf:enServicio and the frecuency of measurement with estraf:frecuenciaMedicion. It is also possible indicate how many directions a device observes with estraf:numSentidos, how many lanes it observes and whether it is an urban device or not with estraf:urbano.
It is linked throught the property estraf:tipoEquipoTrafico with the corresponding device of the taxaonomy of types of traffic devices estraf-kos:tipo-equipo-trafico. For instance a Pneumatic hose links with estraf-kos:tubo-neumatico.
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/equipotrafico/100> a estraf:DispositivoMedicionTrafico ; dct:identifier "100"^^xsd:string ; dct:description "C. GRAN VIA;San Bernardo-Garcia Molinas;San Bernardo"^^xsd:string ; sosa:observes <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/carga> ; estraf:numSentidos "2"^^xsd:int ; estraf:numCarriles "8"^^xsd:integer ; estraf:urbano "true"^^xsd:boolean ; estraf:enServicio "true"^^xsd:boolean ; estraf:frecuenciaMedicion "5 minutos"^^xsd:string ; geosparql:hasGeometry <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/100> ; estraf:monitorea <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/tramo/100> ; estraf:tipoEquipoTrafico <http://vocab.linkeddata.es/datosabiertos/kos/transporte/trafico/tipo-equipo-trafico/lazo-magnetico> .
Due to the fact that estraf:EquipoTrafico is a subclass of geosparql:Feature, it relates through geosparql:hasGeometry with the localisation of the measurement point sf:Point.
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/100> a sf:Point ; geo:lat "40,42262"^^xsd:float ; geo:long "-3,71224"^^xsd:float ; geo_core:xETRS89 "-2465360,47"^^xsd:float ; geo_core:yETRS89 "5100548,33"^^xsd:float ; geosparql:asWKT "POINT (-3.71224 40,42262)"^^geosparql:wktLiteral .
The instance of estraf:DispositivoMedicionTrafico is associated with instances of the class estraf:PropiedadMedicionTrafico through the property sosa:observes. This instance has the measurement unit of the property in estraf:unidadMedida.
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/carga> a estraf:PropiedadMedicionTrafico ; estraf:unidadMedida "Porcentaje"^^xsd:string .
With instances of this class has also relation the class estraf:ObservacionTrafico through the property sosa:observedProperty. In this class are included as properties the time when the observation was performed in sosa:resultTime and the result itself in sosa:hasSimpleResult, as well as the created property estraf:validada to indicate whether the observation is validated or not. In order to represent the registry interval of observation it is used the property sosa:phenomenonTime which relate with the class time:ProperInterval as it has been explained before.
Observation:
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/observaciontrafico/20200423114500> a estraf:ObservacionTrafico ; dct:identifier "100-20200423114500"^^xsd:string ; sosa:resultTime "2020-04-23T11:45:00+02:00"^^xsd:dateTime ; sosa:hasSimpleResult "60"^^xsd:integer ; estraf:validada "true"^^xsd:boolean ; sosa:madeBySensor <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/equipo-trafico/100> ; sosa:observedProperty <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/carga> ; sosa:hasFeatureOfInterest <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/tramo/100> ; sosa:phenomenonTime <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/properinterval/20200423114500> .
Observation Interval:
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/properinterval/20200423114500> a time:ProperInterval ; time:hasBegining <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/instant/20200423114455> ; time:hasEnd <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/instant/202004231145000> . <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/instant/20200423114455> a time:Instant ; time:inXSDgYearMonth "2020-04-23T11:44:55+02:00"^^xsd:dateTime . <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/instant/20200423114500> a time:Instant ; time:inXSDgYearMonth "2020-04-23T11:45:00+02:00"^^xsd:dateTime .
This observation has a feature of interest sosa:hasFeatureOfInterest which relates the Observation estraf:Observacion with the section estraf:Tramo it monitors.
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/tramo/100> a estraf:Tramo ; geosparql:hasGeometry <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/100> ; estraf:inicioTramo <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/100> ; estraf:finTramo <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/101> ; estraf:via <http://vocab.linkeddata.es/datosabiertos/urbanismo-infraestructuras/callejero/calle/100> .
In order to represent an estraf:Incidencia the class with the properties listed below has been created: a creation date dct:created; a start date schema:startDate; an end date schema:endDate; a scheduled end date estraf:fechaFinPrevista; the number of directions affected by the incidence estraf:numSentidos; the number of lanes affected by the incidence estraf:numCarriles; the property estraf:esRecurrente sets whether the incidence is recurrent or not; the reason of the recurrence estraf:recurrencia; and finally the URI of a document to find all the information about the incidence rdfs:seeAlso:
<http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/incidenciaplanificada/1000> a estraf:Incidencia ; dct:identifier "1000"^^xsd:string ; dct:description "EXP-2020/22329 Plaza Humilladero-Almendro"^^xsd:string ; schema:startDate "2020-03-12T16:00:00+02:00"^^xsd:dateTime ; schema:endDate "2020-03-13T23:00:00+02:00"^^xsd:dateTime ; estraf:fechaFinPrevista "2028-03-08T23:00:00+02:00"^^xsd:dateTime ; estraf:numSentidos "1"^^xsd:integer ; estraf:numCarriles "3"^^xsd:integer ; estraf:esRecurrente "true"^^xsd:boolean ; estraf:recurrencia "Excursión juvenil" ; estraf:tipoIncidencia <http://vocab.linkeddata.es/datosabiertos/kos/transporte/trafico/tipo-equipo-trafico/evento> ; geosparql:hasGeometry <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/point/1000> ; estraf:incidenciaEnTramo <http://vocab.ciudadesabiertas.es/recurso/transporte/trafico/tramo/1000> .
IRI: http://www.w3.org/2004/02/skos/core#Concept
IRI: http://www.w3.org/2004/02/skos/core#ConceptScheme
IRI: http://www.opengis.net/ont/geosparql#Feature
IRI: http://www.w3.org/ns/sosa/FeatureOfInterest
When measuring the height of a tree, the height is the observed ObservableProperty, 20m may be the Result of the Observation, and the tree is the FeatureOfInterest. A window is a FeatureOfInterest for an automatic window control Actuator.
IRI: http://www.opengis.net/ont/sf#Point
IRI: http://www.opengis.net/ont/geosparql#Geometry
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#Incidencia
IRI: http://www.w3.org/ns/sosa/ObservableProperty
The height of a tree, the depth of a water body, or the temperature of a surface are examples of observable properties, while the value of a classic car is not (directly) observable but asserted.
IRI: http://www.w3.org/ns/sosa/Observation
The activity of estimating the intensity of an Earthquake using the Mercalli intensity scale is an Observation as is measuring the moment magnitude, i.e., the energy released by said earthquake.
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#IncidenciaPlanificada
IRI: http://www.w3.org/2006/time#ProperInterval
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#Tramo
IRI: http://www.w3.org/ns/sosa/Sensor
Accelerometers, gyroscopes, barometers, magnetometers, and so forth are Sensors that are typically mounted on a modern smart phone (which acts as Platform). Other examples of sensors include the human eyes.
IRI: http://www.opengis.net/ont/geosparql#SpatialObject
IRI: http://vocab.linkeddata.es/datosabiertos/def/urbanismo-infraestructuras/callejero#Via
IRI: http://www.w3.org/2006/time#TemporalEntity
IRI: http://www.w3.org/2006/time#Instant
IRI: http://www.w3.org/2006/time#Interval
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#EquipoTrafico
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#PropiedadMedicionTrafico
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#DispositivoMedicionTrafico
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#ObservacionTrafico
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#IncidenciaNoPlanificada
IRI: http://www.w3.org/2006/time#hasBeginning
IRI: http://www.w3.org/2006/time#hasEnd
IRI: http://www.w3.org/ns/sosa/hasFeatureOfInterest
IRI: http://www.w3.org/2006/time#inXSDgYearMonth
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#incidenciaEnTramo
has characteristics: functional
IRI: http://www.w3.org/ns/sosa/phenomenonTime
IRI: http://www.w3.org/2004/02/skos/core#inScheme
IRI: http://www.w3.org/ns/sosa/madeBySensor
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#monitorea
has characteristics: functional
IRI: http://www.w3.org/ns/sosa/observedProperty
IRI: http://www.w3.org/ns/sosa/observes
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#finTramo
has characteristics: functional
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#inicioTramo
has characteristics: functional
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#via
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#tipoIncidencia
has characteristics: functional
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#tipoEquipoTrafico
has characteristics: functional
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#fechaFinPrevista
IRI: http://schema.org/startDate
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#incidenciaAdjunto
IRI: http://purl.org/dc/terms/description
IRI: http://schema.org/endDate
IRI: http://purl.org/dc/terms/identifier
IRI: http://www.w3.org/2003/01/geo/wgs84_pos#lat
IRI: http://www.w3.org/2003/01/geo/wgs84_pos#long
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#frecuenciaMedicion
IRI: http://www.w3.org/ns/sosa/hasSimpleResult
IRI: http://www.w3.org/ns/sosa/resultTime
IRI: http://schema.org/datePosted
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#recurrencia
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#esRecurrente
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#enServicio
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#numSentidos
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#numCarriles
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#unidadMedida
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#urbano
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#validada
IRI: https://datos.ign.es/def/geo_core#xETRS89
IRI: https://datos.ign.es/def/geo_core#yETRS89
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#composicion
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#nivel
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#ocupacion
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#velocidad
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#intensidad
IRI: http://vocab.ciudadesabiertas.es/def/transporte/trafico#carga
IRI: http://vocab.linkeddata.es/datosabiertos/kos/sector-publico/transporte/tipo-incidencia
IRI: http://vocab.linkeddata.es/datosabiertos/kos/sector-publico/transporte/tipo-equipo-trafico
The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.