|
|
This use case allows the delivery by the providers of real-time information on the availability of parking spaces.
|
|
|
|
|
|
This use case aims to collect and publish in a centralized and homogeneous way the information in real time related to car parks in Spanish cities. Agents/interested third parties can consume the information by subscribing. It allows suppliers to send information to the DGT 3.0 platform on the availability of parking spaces in real time. Consumers will be able to publish the information in their information systems accessible by the end user, allowing them to better plan their trips and consider the use of public transport.
|
|
|
|
|
|
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. If these certificates have not already been requested, they should be requested from *[soporte@cmobility30.es](mailto:soporte@cmobility30.es)*.
|
|
|
|
|
|
Below are the URLs with which each functionality is accessed:
|
|
|
|
|
|
| Mode | URL | Description |
|
|
|
| ------------ | -------------------------------------- | ------------------------------------------------------ |
|
|
|
| Publication | https://pre.cmobility30.es/use-case-11 | Client integration environment endpoint for publishing |
|
|
|
| Subscription | mqtt://mqtt.pre.cmobility30.es:8883 | Integration environment endpoint for subscription |
|
|
|
| Mode | URL | Description |
|
|
|
| ------------ | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
|
|
|
| Publication | https://pre.cmobility30.es/use-case-11 | Client integration environment endpoint for publishing (certain publishing methods will be accessible for consumption) |
|
|
|
| Subscription | [mqtt://mqtt.pre.cmobility30.es:8883](mqtt://mqtt.pre.cmobility30.es:8883) | Integration environment endpoint for subscription |
|
|
|
|
|
|
The two functionalities are described below.
|
|
|
|
... | ... | @@ -23,11 +25,7 @@ This use case has a REST API for the publication (sending) of the data by the co |
|
|
|
|
|
- Information regarding the event to be sent:
|
|
|
|
|
|
> [Event](publicacion/Event)
|
|
|
|
|
|
- Information regarding the methods of this use case:
|
|
|
|
|
|
> [Methods](publicacion/Methods)
|
|
|
> [Publication methods](publicacion/Methods)
|
|
|
|
|
|
## Subscription
|
|
|
|
... | ... | @@ -62,6 +60,12 @@ In the topic, the events are published in JSON format. Here you can see an examp |
|
|
|
|
|
See more information and a connection example [here](https://gitlab.cs.cmobility30.es/dgt3.0_eng/general/-/wikis/MQTT).
|
|
|
|
|
|
In addition, subscribers will also be able to access the following REST API publication methods to obtain information:
|
|
|
|
|
|
- Information regarding the methods of this use case:
|
|
|
|
|
|
> [Subscription methods](suscripcion/Methods)
|
|
|
|
|
|
## Errors
|
|
|
|
|
|
As stated above, all HTTP responses other than **200 – OK**, can be considered **invalid**. The format of the error response is like the following example:
|
... | ... | |