... | ... | @@ -2,16 +2,11 @@ |
|
|
|
|
|
DGT 3.0 Plataform , with the perimeter beaconing service for sporting events, collects and publishes information on the real-time location of all sporting events (cycling competitions, road athletics events, rallies, etc.) that affect circulation and safety road of the users who transit through the roads of the Spanish territory.
|
|
|
|
|
|
In this way, the user better plans their trips, and consider the option of using public transport that allows the reduction of polluting emissions.
|
|
|
V-2 beacons, to track events, and connected cones, that will report the various road closures in the vicinity of the circuit to ensure safety, will be used. In this way, the user better plans their trips, and consider the option of using public transport that allows the reduction of polluting emissions.
|
|
|
|
|
|
The beaconing information of the special vehicles that reaches the end user will depend on the implementation carried out by the agent/third party that consumes the information from the DGT 3.0 platform and publishes it through the vehicle information system, mobile application or other devices.
|
|
|
|
|
|
This use case aims to collect and publish real-time location information of all sporting events (cycling competitions, road athletics events, rallies, etc.) that may affect traffic and road safety of users traveling on the roads of Spanish territory.
|
|
|
|
|
|
The way in which the vehicle information reaches the end user will depend on the implementation carried out by the agent/third party that consumes the information from the DGT 3.0 platform and publishes it to the user through the vehicle information system, mobile application, etc.
|
|
|
|
|
|
The platform has two different functionalities for the **publication (sending)** and for the **subscription (reception)** of information. The first is through a REST API and the second through a real-time MQTT service
|
|
|
The beaconing information of sporting events that reaches the end user will depend on the implementation carried out by the agent/third party that consumes the information from the DGT 3.0 platform and publishes it through the vehicle information system, mobile application or other devices.
|
|
|
|
|
|
The platform has two different functionalities for the **publication (sending)** and for the **subscription (reception)** of information. The first is through a REST API and the second through a real-time MQTT service.
|
|
|
|
|
|
Both the publication and subscription functionality require different access certificates that must be requested and supplied by DGT 3.0. These certificates, if they have not already been requested, must be requested from *[soporte@cmobility30.es](mailto:soporte@cmobility30.es)*.
|
|
|
|
... | ... | @@ -43,7 +38,7 @@ This use case has a REST API for the publication (sending) of the data by the co |
|
|
|
|
|
## Suscription
|
|
|
|
|
|
This use case also has a data subscription (reception) service by companies that so wish through the MQTT protocol. Details of this can be found below:
|
|
|
This use case also has a data subscription (reception) service by companies that so wish through the MQTT protocol. This use case is only for the follow-up services of the sporting events, if you want to subscribe to the information on cone events (road closures) it must be done through the Bandeja de Salida interface that can be found in [Use case 4. Virtual message board](https://gitlab.cs.cmobility30.es/dgt3.0_eng/use-case-4). Details of this can be found below:
|
|
|
|
|
|
**MQTT (MQ Telemetry Transport)** is a messaging protocol used as a simple and lightweight method of transferring data to/from low-power devices.
|
|
|
|
... | ... | @@ -132,13 +127,13 @@ The events are published in the topic in JSON format. Here you can see an exampl |
|
|
}
|
|
|
]
|
|
|
```
|
|
|
Description of the fields for the use case of "Eventos deportivos" through the DGT 3.0 platform. Publish the geometric information of the event along with its roads, pk and passing times:
|
|
|
Description of the fields for the use case of "Eventos deportivos" through the DGT 3.0 platform. It publish the geometric information of the event along with its roads, pk and passing times:
|
|
|
|
|
|
**(*)= Field that may not appear in the posted JSON**
|
|
|
|
|
|
- **type** (string): Feature Identifier.
|
|
|
|
|
|
- **geometry**: Collection of coordinates that represent the result of tracking a sports event. This collection of coordinates will be contained in the collection represented by the _geom_ field of this same JSON document
|
|
|
- **geometry**: Collection of coordinates that represent the result of tracking a sports event. This collection of coordinates will be contained in the collection represented by the _geom_ field of this same JSON document. Of the collection of tracking coordinates that is published, the first in the list corresponds to the location of the trailing car, while the last in the list corresponds to the leading car.
|
|
|
|
|
|
- **type**(string): Geometry type identifier.
|
|
|
|
... | ... | @@ -146,59 +141,59 @@ Description of the fields for the use case of "Eventos deportivos" through the D |
|
|
|
|
|
- **properties**: Schema properties for the publication of sporting events.
|
|
|
|
|
|
- **eventoId** (integer):Sporting event identifier.
|
|
|
- **eventoId** (integer):Sporting event identifier.
|
|
|
|
|
|
- **etapaId** (integer): Identifier of the stage that belongs to a unique sporting event defined by the field _**idEvento**_.
|
|
|
- **etapaId** (integer): Identifier of the stage that belongs to a unique sporting event defined by the field _**idEvento**_.
|
|
|
|
|
|
- **objectid_1** (integer): Identifier of the section that belongs to a single stage defined by the _**etapaId**_ field.
|
|
|
- **objectid_1** (integer): Identifier of the section that belongs to a single stage defined by the _**etapaId**_ field.
|
|
|
|
|
|
- **(*) objectid**(integer): Object identifier according to GIS.
|
|
|
- **(*) objectid**(integer): Object identifier according to GIS.
|
|
|
|
|
|
- **ddtram_cod**(integer): Official identifier of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddtram_cod**(integer): Official identifier of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddcar_codi**(string): Road identifier in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddcar_codi**(string): Road identifier in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddcar_deno**(string): Road name in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddcar_deno**(string): Road name in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddtram_den**(string): Name of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddtram_den**(string): Name of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddtram_tip**(string):Typology of the owner of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddtram_tip**(string):Typology of the owner of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddtram_tit**(string): Name of the owner of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddtram_tit**(string): Name of the owner of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddtram_t_1**(string):Typology of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddtram_t_1**(string):Typology of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **(*) ddtram_lon**(integer):Total length of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **(*) ddtram_lon**(integer):Total length of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **pk_ini**(string): Kilometric starting point of the section and official section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **pk_ini**(string): Kilometer starting point of the section and official section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **pk_fin**(string): Kilometer point of end of the section and official of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **pk_fin**(string): Kilometer point of end of the section and official of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **i(*) dtipovian**(string):Road typology in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **(*) dtipovian**(string):Road typology in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **ddprov_pro**(string): Province of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddprov_pro**(string): Province of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **(*) ddcom_comu**(string): Autonomous community of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **(*) ddcom_comu**(string): Autonomous community of the section in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **(*) color**(string): Road color according to GIS for mapamovilidad.es
|
|
|
- **(*) color**(string): Road color according to GIS for mapamovilidad.es
|
|
|
|
|
|
- **(*) pkinigis**(integer):Starting kilometer point of the section according to the GIS.
|
|
|
- **(*) pkinigis**(integer):Starting kilometer point of the section according to the GIS.
|
|
|
|
|
|
- **(*) pkfingis**(integer): Kilometric point of end of the section according to GIS.
|
|
|
- **(*) pkfingis**(integer): Kilometric point of end of the section according to GIS.
|
|
|
|
|
|
- **(*) shape_leng**(numeric): Length of the shape according to coordinates.
|
|
|
- **(*) shape_leng**(numeric): Length of the shape according to coordinates.
|
|
|
|
|
|
- **ddcar_carr**(string): Official highway nomenclature in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
- **ddcar_carr**(string): Official highway nomenclature in BDC (Base de Datos de Carreteras / Road Database).
|
|
|
|
|
|
- **pk_inicio_tram_etp**(integer): Kilometric starting point of occupation of the stage section.
|
|
|
- **pk_inicio_tram_etp**(integer): Kilometric starting point of occupation of the stage section.
|
|
|
|
|
|
- **pk_fin_tram_etp**(integer): Kilometric point of end of occupation of the stage section.
|
|
|
- **pk_fin_tram_etp**(integer): Kilometric point of end of occupation of the stage section.
|
|
|
|
|
|
- **tipo_vialidad**(string): Description of the road by which the section is affected.
|
|
|
- **tipo_vialidad**(string): Description of the road by which the section is affected.
|
|
|
|
|
|
- **cod_vialidad**(string): Identification code of the road by which the section is affected.
|
|
|
- **cod_vialidad**(string): Identification code of the road by which the section is affected.
|
|
|
|
|
|
- **geom**(string): Collection of coordinates that represent the total route of the segment being tracked.
|
|
|
- **geom**(string): Collection of coordinates that represent the total route of the segment being tracked. From the collection of coordinates that is published, the first in the list corresponds to the location where the event starts, while the last in the list corresponds to the location where the event ends.
|
|
|
|
|
|
- **tsinicio**(ZonedDateTime): Event start date.
|
|
|
|
... | ... | |