Number of Data Files / Resources 1
Updated: 27 Feb 2024
This dataset contains comprehensive details about bus stops
Request Permission

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

Cancel
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.
Done
Send Feedback
Updated: 27 Feb 2024 File Size : 49.62 MB
CSV
Field Value
Data Provenance Public Transportation Planning System
Dataset Source SDSC
Format CSV
Created 14 Jul 2020
Last updated 27 Feb 2024
Frequency of Update on Source Others
Frequency of Update to SDP
Weekly
Expected Volume/Ingestion Cycle(Daily if Real-time)
Language English~Mix~English~Mix~Mix~English~English~English~English~English~English~English~English~English
State active
Rights ,Who has rights for attribute
License notspecified
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
report_date Date of Reporting No 10 date No YYYY-MM-DD English Open
stop_name Bus Stop Name No 200 nvarchar No Mix Open
stop_id Bus Stop ID + Stop Position (should be unique identifier with the Stop ID ) Yes 8 numeric No English Open
street_name Name of the street at the Bus Stop No 200 nvarchar No Mix Open
route_name Bus Route Name Yes 200 nvarchar Yes ROUTE NAME: (Values in 'ROUTE_NAME' In 'Bus Routes' Dataset) Mix Open
stop_location_longitude Longitude part of Bus Stop Coordinate No 9 numeric No English Open
stop_location_latitude Latitude part of Bus Stop Coordinate No 9 numeric No English Open
bus_stop_type Type of Bus Stop - Pole, Flag, Covered, AC Shelter No 200 nvarchar No Pole, Flag, Covered, AC Shelter English Open
time_table_panel Yes/No to whether there is a timetable panel available at the stop. No 5 nvarchar No Yes/No English Open
mupi_available Yes/NO to whether there is a timetable with map available at the stop. No 5 nvarchar No Yes/No English Open
rtpi_available Yes/No to wheter there is Real Time Passenger Information Available at the stop. No 5 nvarchar No Yes/No English Open
last_survey_date Date of last survey (to show recency of the information). No 10 date No YYYY-MM-DD English Open
valid_from Stop Validity Start Date No 10 date No YYYY-MM-DD English Open
valid_until Stop Validity End Date No 10 date No YYYY-MM-DD English 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
    https://www.dubaipulse.gov.ae/dataset/406c9b9b-eddf-4513-9d80-aa5de39042cf/resource/5c8c54eb-a549-4ebe-bc22-5bd33af07711/download/bus_stop_details.csv
  • 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: https://api.dubaipulse.gov.ae/oauth/client_credential/accesstoken?grant_type=client_credentials 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" "https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api"
  • Query Samples:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 AND zone_id=2 https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2
  • Record Limit Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?limit=10
  • Record Offset Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=primary_key_attribute&offset=10
  • Record Order By Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?order_by=location_id
  • Attribute Limiting Sample:
    https://api.dubaipulse.gov.ae/shared/rta/rta_tram_stations-open-api?filter=location_id=223 OR zone_id=2 &column=zone_id,line_name,location_id