Number of Data Files / Resources 2421
Updated: 29 Nov 2023
This dataset contains comprehensive details about all the citizens ridership in Tram
Request Permission

I acknowledge that I have read and agree to the terms and conditions

Send Request
Your request has been successfully submitted
You will receive a confirmation within 14days time period. If you are
having any query feel free to contact us.
Send Feedback
Updated: 29 Nov 2023 File Size : 2.94 MB
Updated: 29 Nov 2023 File Size : 0.65 MB
Updated: 29 Nov 2023 File Size : 2.95 MB
Updated: 29 Nov 2023 File Size : 1.66 MB
Updated: 28 Nov 2023 File Size : 1.94 MB
Updated: 27 Nov 2023 File Size : 1.78 MB
Field Value
Data Provenance
Dataset Source ITIC
Format CSV
Created 16 Feb 2018
Last updated 29 Nov 2023
Frequency of Update on Source daily
Frequency of Update to SDP
Expected Volume/Ingestion Cycle(Daily if Real-time)
10 -> 100
Language ~~~~~~~
State active
Rights N/A
License notspecified
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
txn_type Transaction type (e.g. Check In, Check Out) Yes 5 NVARCHAR(5) “Check In”, “Check Out” Open
txn_date Date on which the transaction is processed by SP Yes DATE Dates “YYYY-MM-DD” Open
txn_time Time at which the transaction is processed by the device Yes TIME Time “hh:mm:ss“ Open
start_location Entry gate location of the transaction e.g. station name No 200 VARCHAR(200) Values in “STATION_NAME” in “Tram  Stations” Dataset Open
end_location Upload location of the transaction e.g. station name Yes 200 VARCHAR(200) Values in “STATION_NAME” in “Tram  Stations” Dataset Open
line_name Tram Line Name Yes 100 VARCHAR(100) Values in “LINE_NAME” In “Tram Lines” Dataset Open
start_zone Trip start zone No 6 VARCHAR(6) “Zone 0”, “Zone 1” , “Zone 2” , “Zone 3” , “Zone 4” , “Zone 5” , “Zone 6” , “Zone 7” , “Zone 8” , “Zone 9” Open
end_zone Zone Name No 6 VARCHAR(6) “Zone 0”, “Zone 1” , “Zone 2” , “Zone 3” , “Zone 4” , “Zone 5” , “Zone 6” , “Zone 7” , “Zone 8” , “Zone 9” Open

Dubai Pulse Data API

Access resource data via a web API with powerful query support.

The Data API can be accessed via the following actions of the CKAN action API.
  • Query
  • End Users will receive "API Key" and "API Secret" in two separate emails on the first time Grant of a Dataset, first Purchase of a Commercial Dataset, or Purchase of an API Package. This API Key and API Secret combination should be used to generate API token and the token will need to be included in the http headers of every API call made.

    Authentication Service to generate API token: with body 'client_id={API Key}&client_secret={API Secret}

    Read the value of "access_token" from the response of the above service and use it in the header of every API call. The obtained API token is valid for certain duration (for example 30 minutes) after which a fresh token needs to be obtained.

    Header Name : Authorization
    Value : Bearer {access_token}

  • Query Parameters
    API calls can be made for full dataset result (subject to maximum results limit) or to a subset of results. Different filters can be applied on the results. Developers can use the attributes to apply a combination of filters with and/or conditions.
  • Limiting the Response Size
    Developers can limit the number of records returned by an API call passing the "Limit" parameter in the call. The value of the "Limit" must be less than the allowed maximum limit.
  • Limiting the Attributes
    Developers can limit the API response to specific set of attributes by passing the attribute names in the API call. The example below explains how the attributes can be specified in the API call. This feature can be used in conjunction with query parameters.
  • Curl Command Sample:
    curl -X GET --header "Authorization: qMtn6xQapeouAlirfHXD7DWJFabV" ""
  • Query Samples: AND zone_id=2 OR zone_id=2
  • Record Limit Sample:
  • Record Offset Sample:
  • Record Order By Sample:
  • Attribute Limiting Sample: OR zone_id=2 &column=zone_id,line_name,location_id