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.
having any query feel free to contact us.
Done
Send Feedback
CSV
Field | Value | |||||||
---|---|---|---|---|---|---|---|---|
Data Provenance | Estimated Times - Airlines, Actual Times - ACT/GOSS, Flight Master - AODB | |||||||
Dataset Source | Source | |||||||
Format | CSV | |||||||
Created | 08 Mar 2020 | |||||||
Last updated | 04 Oct 2023 | |||||||
Frequency of Update on Source | RealTime | |||||||
Frequency of Update to SDP
|
Daily
|
|||||||
Expected Volume/Ingestion Cycle(Daily if Real-time)
|
400 records initial load
|
|||||||
Language | English~English~English~English~English~English~English~English~English~English~English~English~Arabic~Arabic~Arabic~Arabic~English~English~English~English~English~English~English~English~English~English~English~English~English~English~English~English~English~English~English | |||||||
State | active | |||||||
Rights | ||||||||
License | notspecified | |||||||
Show more |
Name | Description | Primary Key | Size | Datatype | Foreign Key | Range of Values | Language | Classification |
---|---|---|---|---|---|---|---|---|
estimatedoffblocktime | Estimated Departure time of a flight from DXB(estimatedOffblockTime) | No | datetime | English | Open | |||
actualtakeofftime | The time when aircraft departed fom the runway | No | datetime | English | Open | |||
actualoffblocktime | The time when the aircraft was pushed back from the stand | No | datetime | English | Open | |||
aircraftparkingposition | The name of the stand the aircraft is parked | No | 5 | varchar2 | English | Open | ||
publicgatenumber | Gate number from where the passenger will board the flight | No | 5 | varchar2 | English | Open | ||
checkinallocationfrom | Check in counter | No | 5 | varchar2 | English | Open | ||
checkinallocationto | Check in counter | No | 5 | varchar2 | English | Open | ||
airlinename | Name of the airline which is the operating the flight | No | 255 | nvarchar | English | Open | ||
vianame | City Name of the Via | No | 255 | nvarchar | English | Open | ||
destinationname | City Name of the destination | No | 255 | nvarchar | English | Open | ||
traffictype | Traffic type description of the flight | No | 255 | nvarchar | English | Open | ||
aircraftterminal | Terminal from which the flight is operating | No | 2 | varchar2 | English | Open | ||
airlinenamea | Name of the airline which is operating the flight in arabic | No | 255 | nvarchar | Arabic | Open | ||
destinationnamea | City Name of the Last destination in arabic | No | 255 | nvarchar | Arabic | Open | ||
vianamea | City Name of the Via in arabic | No | 255 | nvarchar | Arabic | Open | ||
flightstatustexta | Flight status description in Arabic | No | 255 | nvarchar | Arabic | Open | ||
aodbuniquefield | Unique identifier for the flight | Yes | 10 | number | English | Open | ||
flightstatus | Status description of the flight eg : Arrived ,Landed , Boarding ,Final Call etc | No | 32 | varchar2 | English | Open | ||
aircraftregistration | Alphanumeric identifier for the flight eg :A6ALI | No | 200 | varchar2 | English | Open | ||
flightnumber | Alphanumeric Flight number , Airline IATA Code + Number : AA123 | No | 10 | varchar2 | English | Open | ||
traffictypecode | Traffic type code of the flight eg: Passenger /Cargo etc | No | 2 | varchar2 | English | Open | ||
arrivalordeparture | Arrival or Departure Identifier A/D | No | 2 | varchar2 | English | Open | ||
lastchanged | 2019-05-01T06:58:01, Last updated time | No | datetime | English | Open | |||
airlinecode_iata | EK, Two letter code for the Airline which operates the flight | No | 2 | varchar2 | English | Open | ||
airlinecode_icao | UAE, Three letter code for the Airline which operates the flight | No | 3 | varchar2 | English | Open | ||
jointflightnumber | B6 5061 QF 8419, All flight Numbers related to the main flight | No | 110 | varchar2 | English | Open | ||
destination_iata | SYD, , IATA three letter code for the destination airport | No | 3 | varchar2 | English | Open | ||
destination_icao | ICAO four letter code for the destination airport | No | 4 | varchar2 | English | Open | ||
via_iata | IATA three letter code for the via(route) airport | No | 3 | varchar2 | English | Open | ||
via_icao | ICAO three letter code for the via(route) airport | No | 4 | varchar2 | English | Open | ||
aircraft_iata | IATA sub category code of the operating flight | No | 3 | varchar2 | English | Open | ||
aircraft_icao | ICAO main category code of the operating flight | No | 5 | varchar2 | English | Open | ||
flightstatuscode | Flight status code | No | 5 | varchar2 | English | Open | ||
publicscheduleddatetime | The scheduled Departures time of a departing flight that is made public | No | datetime | English | Open | |||
scheduledoffblocktime | Scheduled departure time of a flight from DXB | No | datetime | English | Open | |||
Show more Show less |
Dubai Pulse Data API
Access resource data via a web API with powerful query support.
-
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