... | ... | @@ -43,20 +43,23 @@ In the topic, the events are published in JSON format. Here you can see an examp |
|
|
|
|
|
```json
|
|
|
{
|
|
|
"municipalityIneCode":50297,
|
|
|
"cityIne":50297,
|
|
|
"parkingId":1,
|
|
|
"freeCapacity":4,
|
|
|
"totalCapacity":5
|
|
|
"free":14,
|
|
|
"capacity":158,
|
|
|
"timestamp":"2021-03-15T13:34:00.000Z"
|
|
|
}
|
|
|
```
|
|
|
|
|
|
- municipalityIneCode (integer): identifier of the municipality where the event is generated according to [INE](https://www.ine.es/daco/daco42/codmun/cod_provincia_estandar.htm)
|
|
|
- **cityIne** (integer): identifier of the municipality where the event is generated according to the [INE](https://www.ine.es/daco/daco42/codmun/cod_provincia_estandar.htm)
|
|
|
|
|
|
- parkingId (integer): parking identifier
|
|
|
- **parkingId** (integer): parking identifier.
|
|
|
|
|
|
- freeCapacity (integer): number of free parking spaces
|
|
|
- **free** (integer): number of free parking spaces.
|
|
|
|
|
|
- totalCapacity (integer): total parking capacity
|
|
|
- **capacity** (integer): total parking capacity.
|
|
|
|
|
|
- **timestamp** (date UTC): date and time in UTC format of the moment in which the car park was updated for the last time. It needs to not be a future timestamp with respect to the current UTC time. The date must end with the character 'Z' that marks that it is in UTC.
|
|
|
|
|
|
See more information and a connection example [here](https://gitlab.cs.cmobility30.es/dgt3.0_eng/general/-/wikis/MQTT).
|
|
|
|
... | ... | |