f | { | f | { |
| "author": "", | | "author": "", |
| "author_email": "", | | "author_email": "", |
| "creator_user_id": "c028eea2-1878-47b8-843b-aa298066c249", | | "creator_user_id": "c028eea2-1878-47b8-843b-aa298066c249", |
| "data_owner": "Tampere", | | "data_owner": "Tampere", |
| "groups": [ | | "groups": [ |
| { | | { |
| "description": "This group collects together data related to the | | "description": "This group collects together data related to the |
| city of Tampere.", | | city of Tampere.", |
| "display_name": "Tampere", | | "display_name": "Tampere", |
| "id": "07adac22-b527-4417-82b9-41c7c24e6f4c", | | "id": "07adac22-b527-4417-82b9-41c7c24e6f4c", |
| "image_display_url": "", | | "image_display_url": "", |
| "name": "tampere", | | "name": "tampere", |
| "title": "Tampere" | | "title": "Tampere" |
| } | | } |
| ], | | ], |
| "id": "c24a59a7-62eb-4807-ae97-e00bf5b698db", | | "id": "c24a59a7-62eb-4807-ae97-e00bf5b698db", |
| "isopen": false, | | "isopen": false, |
| "license_id": "internal", | | "license_id": "internal", |
| "license_title": "For internal research and education use", | | "license_title": "For internal research and education use", |
| "maintainer": "Otto Hylli", | | "maintainer": "Otto Hylli", |
| "maintainer_email": "otto.hylli@tuni.fi", | | "maintainer_email": "otto.hylli@tuni.fi", |
| "metadata_created": "2024-03-25T13:06:08.677152", | | "metadata_created": "2024-03-25T13:06:08.677152", |
n | "metadata_modified": "2024-03-25T15:21:41.570191", | n | "metadata_modified": "2024-03-25T15:24:20.379384", |
| "name": "tampere-bus-passenger-analytics-pilot", | | "name": "tampere-bus-passenger-analytics-pilot", |
| "notes": "Bus passenger analytics data from a small city of Tampere | | "notes": "Bus passenger analytics data from a small city of Tampere |
| pilot project. The\r\ntechnology including the original backend system | | pilot project. The\r\ntechnology including the original backend system |
| was by the Spanish company\r\n[Counterest](https://counterest.net/). | | was by the Spanish company\r\n[Counterest](https://counterest.net/). |
| In the pilot 3D character recognition\r\nsensors were installed to one | | In the pilot 3D character recognition\r\nsensors were installed to one |
t | bus operating on a single line between\r\nPyynikintori and Rauhaniemi. | t | bus operating on a single line. The sensors were\r\nused to count |
| The sensors were\r\nused to count people entering and leaving the bus. | | people entering and leaving the bus. This sensor data together\r\nwith |
| This sensor data together\r\nwith location and bus route information | | location and bus route information was then used to create |
| was then used to create various\r\nanalytics in the system backend. | | various\r\nanalytics in the system backend. These include line level |
| These include line level statistics, stop level\r\nstatistics, | | statistics, stop level\r\nstatistics, statistics for travels between |
| statistics for travels between specific stops on a line | | specific stops on a line and\r\nstatistics showing passenger amounts |
| and\r\nstatistics showing passenger amounts for each hour during | | for each hour during different weekdays.\r\nThe data could be |
| different weekdays.\r\nThe data could be inspected with a web | | inspected with a web dashboard. The data was collected |
| dashboard. The data was collected between\r\nFebruary and April 2019. | | between\r\nFebruary and April 2019. During this period there were some |
| During this period there were some occasional | | |
| technical\r\ndifficulties so not all possible data was collected. A | | occasional technical\r\ndifficulties so not all possible data was |
| subset of this data was\r\ntransfered into the Tampere University | | collected. A subset of this data was\r\ntransfered into the Tampere |
| FIWARE platform and is the only part of\r\nthe data that is currently | | University FIWARE platform and is the only part of\r\nthe data that is |
| available. See | | currently available. See |
| \r\n[CityIoT](https://ckan.energydata.rd.tuni.fi/organization/cityiot) | | \r\n[CityIoT](https://ckan.energydata.rd.tuni.fi/organization/cityiot) |
| project for\r\ngeneral information about how the measurements are | | project for\r\ngeneral information about how the measurements are |
| stored and can be used.\r\n\r\n## Data model\r\n\r\nThe data model is | | stored and can be used.\r\n\r\n## Data model\r\n\r\nThe data model is |
| based on the official FIWARe | | based on the official FIWARe |
| dels.readthedocs.io/en/latest/UrbanMobility/doc/introduction.html)\r\n | | dels.readthedocs.io/en/latest/UrbanMobility/doc/introduction.html)\r\n |
| data model which in turn is based on the [General Transit Feed | | data model which in turn is based on the [General Transit Feed |
| Specification](https://gtfs.org/).\r\nThe General Transit Feed | | Specification](https://gtfs.org/).\r\nThe General Transit Feed |
| Specification (GTFS), also known as GTFS static or\r\nstatic transit, | | Specification (GTFS), also known as GTFS static or\r\nstatic transit, |
| defines a common format for public transportation schedules | | defines a common format for public transportation schedules |
| and\r\nassociated geographic information. GTFS \"feeds\" let public | | and\r\nassociated geographic information. GTFS \"feeds\" let public |
| transit agencies\r\npublish their transit data and developers write | | transit agencies\r\npublish their transit data and developers write |
| applications that consume that\r\ndata in an interoperable | | applications that consume that\r\ndata in an interoperable |
| way.\r\n\r\nHowever this data model does not contain schedule | | way.\r\n\r\nHowever this data model does not contain schedule |
| information and thus is not fully compatible with the Urban Transport | | information and thus is not fully compatible with the Urban Transport |
| data model. Attributes for passenger amounts have been added and some | | data model. Attributes for passenger amounts have been added and some |
| mandatory attributes such as arrival and departure times are not used | | mandatory attributes such as arrival and departure times are not used |
| since that information is not available from the original data | | since that information is not available from the original data |
| source.\r\n\r\nThe model consists of the following entity | | source.\r\n\r\nThe model consists of the following entity |
| types:\r\n\r\n- GtfsRoute): Represents a bus route or line that | | types:\r\n\r\n- GtfsRoute): Represents a bus route or line that |
| consists of trips.\r\n- GtfsTrip: Concrete implementations of the | | consists of trips.\r\n- GtfsTrip: Concrete implementations of the |
| route with for example two trips representing the route to both | | route with for example two trips representing the route to both |
| directions.\r\n- GtfsShape: GtfsShapes describe the physical path that | | directions.\r\n- GtfsShape: GtfsShapes describe the physical path that |
| a vehicle takes. Shapes are associated with individual trips.\r\n- | | a vehicle takes. Shapes are associated with individual trips.\r\n- |
| GtfsStop: Represents a bus stop i.e a location where buses pick up and | | GtfsStop: Represents a bus stop i.e a location where buses pick up and |
| drop off passengers. \r\n- GtfsStopTime: Represents the bus stopping | | drop off passengers. \r\n- GtfsStopTime: Represents the bus stopping |
| on a stop as a part of a trip. In other words these tell what stops a | | on a stop as a part of a trip. In other words these tell what stops a |
| trip consists of.\r\n\r\nSee the attached documentation for detailed | | trip consists of.\r\n\r\nSee the attached documentation for detailed |
| descriptions of the data model\r\nincluding used attributes.\r\n\r\n## | | descriptions of the data model\r\nincluding used attributes.\r\n\r\n## |
| Notes about the data\r\n\r\nThe data is quite limited. It was | | Notes about the data\r\n\r\nThe data is quite limited. It was |
| collected only from one line (GtfsRoute) and\r\nonly from one vehicle | | collected only from one line (GtfsRoute) and\r\nonly from one vehicle |
| on that route. There were also some technical difficulties\r\nduring | | on that route. There were also some technical difficulties\r\nduring |
| the data collection period so there is some missing data.\r\n\r\n## | | the data collection period so there is some missing data.\r\n\r\n## |
| Accessing the data\r\n\r\nThe data is stored in the Tampere University | | Accessing the data\r\n\r\nThe data is stored in the Tampere University |
| CityIoT platform. The used FIWARR\r\nservice is public_transport and | | CityIoT platform. The used FIWARR\r\nservice is public_transport and |
| all entities there are under the service | | all entities there are under the service |
| path\r\n/Tampere/passenger_analytics.\r\n\r\n### Example | | path\r\n/Tampere/passenger_analytics.\r\n\r\n### Example |
| requests\r\n\r\nA few example curl commands for getting the data. | | requests\r\n\r\nA few example curl commands for getting the data. |
| Replace your_apikey with a api key that has at least read access to | | Replace your_apikey with a api key that has at least read access to |
| public_transport service.\r\n\r\nGet all GtfsTrip entities i.e. | | public_transport service.\r\n\r\nGet all GtfsTrip entities i.e. |
| information about the route for both directions from Orion:\r\n\r\n | | information about the route for both directions from Orion:\r\n\r\n |
| curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: | | curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: |
| /Tampere/passenger_analytics' -H 'apikey: your_apikey' | | /Tampere/passenger_analytics' -H 'apikey: your_apikey' |
| ://tlt-cityiot.rd.tuni.fi/orion/v2/entities?type=GtfsTrip\"\r\n\r\nGet | | ://tlt-cityiot.rd.tuni.fi/orion/v2/entities?type=GtfsTrip\"\r\n\r\nGet |
| daily passenger statistics for the trip from Pyynikintori to | | daily passenger statistics for the trip from Pyynikintori to |
| Rauhaniemi from Quantumleap for the 10 most recent days:\r\n\r\n | | Rauhaniemi from Quantumleap for the 10 most recent days:\r\n\r\n |
| curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: | | curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: |
| /Tampere/passenger_analytics' -H 'apikey: your_apikey' | | /Tampere/passenger_analytics' -H 'apikey: your_apikey' |
| 2/entities/urn:ngsi-ld:GtfsTrip:1:2?lastN=10&attrs=dailyPassengers\"", | | 2/entities/urn:ngsi-ld:GtfsTrip:1:2?lastN=10&attrs=dailyPassengers\"", |
| "num_resources": 1, | | "num_resources": 1, |
| "num_tags": 2, | | "num_tags": 2, |
| "organization": { | | "organization": { |
| "approval_status": "approved", | | "approval_status": "approved", |
| "created": "2022-10-17T09:15:18.177419", | | "created": "2022-10-17T09:15:18.177419", |
| "description": "The [CityIoT project](https://www.cityiot.fi/) | | "description": "The [CityIoT project](https://www.cityiot.fi/) |
| collected smart city related data\r\nin Tampere about street lights, | | collected smart city related data\r\nin Tampere about street lights, |
| electric buses and bus passenger analytics. This\r\ndata is stored in | | electric buses and bus passenger analytics. This\r\ndata is stored in |
| a [FIWARE](https://www.fiware.org/) based platform. FIWARE is\r\na | | a [FIWARE](https://www.fiware.org/) based platform. FIWARE is\r\na |
| collection of standards and components for creating smart solutions. | | collection of standards and components for creating smart solutions. |
| The\r\nplatform is available at the URL | | The\r\nplatform is available at the URL |
| https://tlt-cityiot.rd.tuni.fi/. The data is\r\navailable via the HTTP | | https://tlt-cityiot.rd.tuni.fi/. The data is\r\navailable via the HTTP |
| based APIs offered by the platform. To access any of the\r\ndata sets | | based APIs offered by the platform. To access any of the\r\ndata sets |
| an API key is required. If you are interested in using any of | | an API key is required. If you are interested in using any of |
| the\r\nCityIoT data sets, contact the person marked as the maintainer | | the\r\nCityIoT data sets, contact the person marked as the maintainer |
| of the data set. \r\n\r\nIn order to get the data and make use of it | | of the data set. \r\n\r\nIn order to get the data and make use of it |
| some understanding is required about\r\nthe following 3 aspects of the | | some understanding is required about\r\nthe following 3 aspects of the |
| CityIoT platform:\r\n\r\n1. The [NGSI v2 | | CityIoT platform:\r\n\r\n1. The [NGSI v2 |
| pecification](https://fiware.github.io/specifications/ngsiv2/stable/): | | pecification](https://fiware.github.io/specifications/ngsiv2/stable/): |
| defines the API used by the main FIWARE component\r\nthe Orion context | | defines the API used by the main FIWARE component\r\nthe Orion context |
| broker and also the entity based data model used by all | | broker and also the entity based data model used by all |
| FIWARE\r\ncomponents.\r\n2. The [Orion context | | FIWARE\r\ncomponents.\r\n2. The [Orion context |
| broker](https://fiware-orion.readthedocs.io/en/master/): Has the most | | broker](https://fiware-orion.readthedocs.io/en/master/): Has the most |
| recent version of the data i.e. NGSI v2\r\nentities. This data can be | | recent version of the data i.e. NGSI v2\r\nentities. This data can be |
| queried or subscribed to so that you get notified\r\nwhen the data | | queried or subscribed to so that you get notified\r\nwhen the data |
| changes.\r\n3. | | changes.\r\n3. |
| [QuantumLeap](https://quantumleap.readthedocs.io/en/latest/): Stores | | [QuantumLeap](https://quantumleap.readthedocs.io/en/latest/): Stores |
| NGSI v2 entity data into a timeseries data base. It allows\r\nthen the | | NGSI v2 entity data into a timeseries data base. It allows\r\nthen the |
| querying of this historic data via an HTTP API.\r\n\r\nSo in short, | | querying of this historic data via an HTTP API.\r\n\r\nSo in short, |
| understand the NGSI v2 data model so you know what kind of | | understand the NGSI v2 data model so you know what kind of |
| data\r\nstructures you are dealing with. Use Orion if you want a | | data\r\nstructures you are dealing with. Use Orion if you want a |
| programmatic way to\r\nlist all available data entities, query their | | programmatic way to\r\nlist all available data entities, query their |
| current state or subscribe to\r\nchanges in their state. Use | | current state or subscribe to\r\nchanges in their state. Use |
| QuantumLeap if you want to explore how the entities\r\nhave changed | | QuantumLeap if you want to explore how the entities\r\nhave changed |
| over time.\r\n\r\n## The data model\r\n\r\nIn FIWARe NGSI v2 data is | | over time.\r\n\r\n## The data model\r\n\r\nIn FIWARe NGSI v2 data is |
| modelled as context entities. Entities can represent\r\nlogical of | | modelled as context entities. Entities can represent\r\nlogical of |
| physical things such as a sensor, a person or a weather | | physical things such as a sensor, a person or a weather |
| observation.\r\nEntities have a id and a type indicating what the | | observation.\r\nEntities have a id and a type indicating what the |
| entity represents. Entities\r\nthen can have various attributes | | entity represents. Entities\r\nthen can have various attributes |
| providing information about them. The entity\r\ntype determines what | | providing information about them. The entity\r\ntype determines what |
| attributes an entity should have. This way domain specific\r\ndata | | attributes an entity should have. This way domain specific\r\ndata |
| models can be created by defining the needed entity types and | | models can be created by defining the needed entity types and |
| their\r\nattributes. For example weather observation could have | | their\r\nattributes. For example weather observation could have |
| attributes for\r\ntemperature, humidity and the location for the | | attributes for\r\ntemperature, humidity and the location for the |
| observation. An attribute has a\r\nname and a value including data | | observation. An attribute has a\r\nname and a value including data |
| type for the value. An attribute can also have\r\nmetadata such as | | type for the value. An attribute can also have\r\nmetadata such as |
| timestamp for when the value was acquired or what is | | timestamp for when the value was acquired or what is |
| the\r\nmeasurement accuracy for the value. The documentation for each | | the\r\nmeasurement accuracy for the value. The documentation for each |
| CityIoT data set\r\nexplains what entity types the data consists of | | CityIoT data set\r\nexplains what entity types the data consists of |
| and what attributes the entities have.\r\n\r\nThe entities are | | and what attributes the entities have.\r\n\r\nThe entities are |
| represented as JSON. For example an entity representing an\r\nelectric | | represented as JSON. For example an entity representing an\r\nelectric |
| bus from one of the CityIoT data sets looks like this with only part | | bus from one of the CityIoT data sets looks like this with only part |
| of\r\nthe attributes included:\r\n\r\n {\r\n \"id\": | | of\r\nthe attributes included:\r\n\r\n {\r\n \"id\": |
| \"Vehicle:TKL16\",\r\n \"type\": \"Vehicle\",\r\n | | \"Vehicle:TKL16\",\r\n \"type\": \"Vehicle\",\r\n |
| \"vehicleType\": {\r\n \"value\": \"bus\"\r\n },\r\n | | \"vehicleType\": {\r\n \"value\": \"bus\"\r\n },\r\n |
| \"name\": {\r\n \"value\": \"TKL16\"\r\n },\r\n | | \"name\": {\r\n \"value\": \"TKL16\"\r\n },\r\n |
| \"location\": {\r\n \"type\": \"geo:json\",\r\n | | \"location\": {\r\n \"type\": \"geo:json\",\r\n |
| \"value\": {\r\n \"type\": \"Point\",\r\n | | \"value\": {\r\n \"type\": \"Point\",\r\n |
| \"coordinates\": [23.769203333333333, 61.49531666666667]\r\n | | \"coordinates\": [23.769203333333333, 61.49531666666667]\r\n |
| },\r\n \"metadata\": {\r\n \"timestamp\": | | },\r\n \"metadata\": {\r\n \"timestamp\": |
| {\r\n \"type\": \"DateTime\",\r\n | | {\r\n \"type\": \"DateTime\",\r\n |
| \"value\": \"2019-04-03T14:52:18.192881Z\"\r\n }\r\n | | \"value\": \"2019-04-03T14:52:18.192881Z\"\r\n }\r\n |
| }\r\n },\r\n \"speed\": {\r\n \"value\": | | }\r\n },\r\n \"speed\": {\r\n \"value\": |
| 34.5,\r\n \"metadata\": {\r\n \"timestamp\": | | 34.5,\r\n \"metadata\": {\r\n \"timestamp\": |
| {\r\n \"type\": \"DateTime\",\r\n | | {\r\n \"type\": \"DateTime\",\r\n |
| \"value\": \"2019-04-03T14:52:19.867419Z\"\r\n }\r\n | | \"value\": \"2019-04-03T14:52:19.867419Z\"\r\n }\r\n |
| }\r\n }, \r\n \"power\": {\r\n | | }\r\n }, \r\n \"power\": {\r\n |
| \"value\": 75.70000000000027,\r\n \"metadata\": {\r\n | | \"value\": 75.70000000000027,\r\n \"metadata\": {\r\n |
| \"timestamp\": {\r\n \"type\": \"DateTime\",\r\n | | \"timestamp\": {\r\n \"type\": \"DateTime\",\r\n |
| \"value\": \"2019-04-03T14:52:20.218114Z\"\r\n }\r\n | | \"value\": \"2019-04-03T14:52:20.218114Z\"\r\n }\r\n |
| }\r\n },\r\n \"chargeState\": {\r\n | | }\r\n },\r\n \"chargeState\": {\r\n |
| \"value\": 87,\r\n \"metadata\": {\r\n | | \"value\": 87,\r\n \"metadata\": {\r\n |
| \"timestamp\": {\r\n \"type\": \"DateTime\",\r\n | | \"timestamp\": {\r\n \"type\": \"DateTime\",\r\n |
| \"value\": \"2019-04-03T14:52:16.938936Z\"\r\n }\r\n | | \"value\": \"2019-04-03T14:52:16.938936Z\"\r\n }\r\n |
| }\r\n }\r\n }\r\n\r\n\r\n## The Orion context | | }\r\n }\r\n }\r\n\r\n\r\n## The Orion context |
| broker\r\n\r\nThe Orion context broker stores the latest versions of | | broker\r\n\r\nThe Orion context broker stores the latest versions of |
| all entities. Its API is\r\nused to query information about the | | all entities. Its API is\r\nused to query information about the |
| entities or subscribe to changes in their\r\nattributes. The Tampere | | entities or subscribe to changes in their\r\nattributes. The Tampere |
| CityIoT Orion API is available at the | | CityIoT Orion API is available at the |
| URL\r\nhttps://tlt-cityiot.rd.tuni.fi/orion/\r\n\r\nTo separate the | | URL\r\nhttps://tlt-cityiot.rd.tuni.fi/orion/\r\n\r\nTo separate the |
| entities of the different data sets, Orions multi tenancy\r\nfeature | | entities of the different data sets, Orions multi tenancy\r\nfeature |
| is used. Data is separated into different services and under a | | is used. Data is separated into different services and under a |
| service\r\nhierarchical service paths can be used for more | | service\r\nhierarchical service paths can be used for more |
| fine-grained data organization.\r\nIn API calls the service and | | fine-grained data organization.\r\nIn API calls the service and |
| service path are given in HTTP headers:\r\n`Fiware-Service` for the | | service path are given in HTTP headers:\r\n`Fiware-Service` for the |
| service and `Fiware-ServicePath` for the service path. For\r\naccess | | service and `Fiware-ServicePath` for the service path. For\r\naccess |
| control API keys are used. The API key is given in the `apikey` HTTP | | control API keys are used. The API key is given in the `apikey` HTTP |
| header.\r\nDocumentation for each data set tells what service is used | | header.\r\nDocumentation for each data set tells what service is used |
| and how service paths\r\nare used. You can get an API key by | | and how service paths\r\nare used. You can get an API key by |
| requesting access to a data set from the\r\nmaintainer of the data | | requesting access to a data set from the\r\nmaintainer of the data |
| set. As an example how all this works in practice, the\r\n[Tampere | | set. As an example how all this works in practice, the\r\n[Tampere |
| electric | | electric |
| ckan.energydata.rd.tuni.fi/dataset/tampere-electric-bus-pilot)\r\ndata | | ckan.energydata.rd.tuni.fi/dataset/tampere-electric-bus-pilot)\r\ndata |
| set has entities representing electric buses in service | | set has entities representing electric buses in service |
| public_transport\r\nunder the service path /Tampere/electric_bus. | | public_transport\r\nunder the service path /Tampere/electric_bus. |
| Using the command line HTTP client\r\ncurl, this is how to get all the | | Using the command line HTTP client\r\ncurl, this is how to get all the |
| electric bus entities and their attributes from\r\nOrion:\r\n\r\n | | electric bus entities and their attributes from\r\nOrion:\r\n\r\n |
| curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: | | curl -H 'Fiware-Service: public_transport' -H 'Fiware-ServicePath: |
| /Tampere/electric_bus' -H 'apikey: your_apikey' | | /Tampere/electric_bus' -H 'apikey: your_apikey' |
| \"https://tlt-cityiot.rd.tuni.fi/orion/v2/entities\"\r\n\r\n## | | \"https://tlt-cityiot.rd.tuni.fi/orion/v2/entities\"\r\n\r\n## |
| QuantumLeap\r\n\r\nQuantumLeap stores the change history of the | | QuantumLeap\r\n\r\nQuantumLeap stores the change history of the |
| entities in a timeseries database.\r\nThis can then be queried via its | | entities in a timeseries database.\r\nThis can then be queried via its |
| API. The Tampere CityIoT QuantumLeap is\r\navailable at the URL: | | API. The Tampere CityIoT QuantumLeap is\r\navailable at the URL: |
| https://tlt-cityiot.rd.tuni.fi/quantumleap/\r\n\r\nIt uses the same | | https://tlt-cityiot.rd.tuni.fi/quantumleap/\r\n\r\nIt uses the same |
| service and service path\r\nsystem to organize entities as Orion. The | | service and service path\r\nsystem to organize entities as Orion. The |
| same API key based authentication\r\nsystem is also used. See the | | same API key based authentication\r\nsystem is also used. See the |
| Orion section for more details. For example to Get\r\nall values for | | Orion section for more details. For example to Get\r\nall values for |
| power and speed for electric bus entity TKL15 between 14:01 and 14:02 | | power and speed for electric bus entity TKL15 between 14:01 and 14:02 |
| on\r\n28th of October 2019 with curl the following command would be | | on\r\n28th of October 2019 with curl the following command would be |
| used:\r\n\r\n curl -H 'Fiware-Service: public_transport' -H | | used:\r\n\r\n curl -H 'Fiware-Service: public_transport' -H |
| 'Fiware-ServicePath: /Tampere/electric_bus' -H 'apikey: your_apikey' | | 'Fiware-ServicePath: /Tampere/electric_bus' -H 'apikey: your_apikey' |
| ed,power&&fromDate=2019-10-28T12:01:00&&toDate=2019-10-28T12:02:00\"", | | ed,power&&fromDate=2019-10-28T12:01:00&&toDate=2019-10-28T12:02:00\"", |
| "id": "ede7b870-2dff-4a89-889e-1bb3980ffa6f", | | "id": "ede7b870-2dff-4a89-889e-1bb3980ffa6f", |
| "image_url": "", | | "image_url": "", |
| "is_organization": true, | | "is_organization": true, |
| "name": "cityiot", | | "name": "cityiot", |
| "state": "active", | | "state": "active", |
| "title": "CityIoT", | | "title": "CityIoT", |
| "type": "organization" | | "type": "organization" |
| }, | | }, |
| "owner_org": "ede7b870-2dff-4a89-889e-1bb3980ffa6f", | | "owner_org": "ede7b870-2dff-4a89-889e-1bb3980ffa6f", |
| "private": false, | | "private": false, |
| "relationships_as_object": [], | | "relationships_as_object": [], |
| "relationships_as_subject": [], | | "relationships_as_subject": [], |
| "resources": [ | | "resources": [ |
| { | | { |
| "cache_last_updated": null, | | "cache_last_updated": null, |
| "cache_url": null, | | "cache_url": null, |
| "created": "2024-03-25T13:09:47.207549", | | "created": "2024-03-25T13:09:47.207549", |
| "datastore_active": false, | | "datastore_active": false, |
| "description": "Detailed data model documentation. Includes | | "description": "Detailed data model documentation. Includes |
| documentation for each entity and their attributes.", | | documentation for each entity and their attributes.", |
| "format": "ZIP", | | "format": "ZIP", |
| "hash": "", | | "hash": "", |
| "id": "a4dae937-291a-409e-9e5a-eb329cb2de5b", | | "id": "a4dae937-291a-409e-9e5a-eb329cb2de5b", |
| "last_modified": "2024-03-25T13:09:47.186023", | | "last_modified": "2024-03-25T13:09:47.186023", |
| "metadata_modified": "2024-03-25T13:09:47.645711", | | "metadata_modified": "2024-03-25T13:09:47.645711", |
| "mimetype": "application/zip", | | "mimetype": "application/zip", |
| "mimetype_inner": null, | | "mimetype_inner": null, |
| "name": "data model documentation", | | "name": "data model documentation", |
| "package_id": "c24a59a7-62eb-4807-ae97-e00bf5b698db", | | "package_id": "c24a59a7-62eb-4807-ae97-e00bf5b698db", |
| "position": 0, | | "position": 0, |
| "resource_type": null, | | "resource_type": null, |
| "size": 175429, | | "size": 175429, |
| "state": "active", | | "state": "active", |
| "url": | | "url": |
| 91a-409e-9e5a-eb329cb2de5b/download/passengeranalytics_datamodel.zip", | | 91a-409e-9e5a-eb329cb2de5b/download/passengeranalytics_datamodel.zip", |
| "url_type": "upload" | | "url_type": "upload" |
| } | | } |
| ], | | ], |
| "state": "active", | | "state": "active", |
| "tags": [ | | "tags": [ |
| { | | { |
| "display_name": "public transport", | | "display_name": "public transport", |
| "id": "d10aeaed-4911-4ce7-be2f-dc8858a4c02c", | | "id": "d10aeaed-4911-4ce7-be2f-dc8858a4c02c", |
| "name": "public transport", | | "name": "public transport", |
| "state": "active", | | "state": "active", |
| "vocabulary_id": null | | "vocabulary_id": null |
| }, | | }, |
| { | | { |
| "display_name": "tampere", | | "display_name": "tampere", |
| "id": "c4067e38-120f-428f-8175-6e7196e617b8", | | "id": "c4067e38-120f-428f-8175-6e7196e617b8", |
| "name": "tampere", | | "name": "tampere", |
| "state": "active", | | "state": "active", |
| "vocabulary_id": null | | "vocabulary_id": null |
| } | | } |
| ], | | ], |
| "temporal_end": "2019-04-30", | | "temporal_end": "2019-04-30", |
| "temporal_resolution": "1 day", | | "temporal_resolution": "1 day", |
| "temporal_start": "2019-02-20", | | "temporal_start": "2019-02-20", |
| "title": "Tampere bus passenger analytics pilot", | | "title": "Tampere bus passenger analytics pilot", |
| "type": "dataset", | | "type": "dataset", |
| "url": "", | | "url": "", |
| "version": "" | | "version": "" |
| } | | } |