Number of Data Files / Resources 1
Updated: 01 Jun 2021
This dataset will provide extended details for the sand shifting service
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: 01 Jun 2021 File Size : 0.69 MB
CSV
Field Value
Data Provenance 1. sand shifting application details are created when applicant creates sand shifting request or NOC request and select building 2. Also when application is resubmitted, details are generated
Dataset Source Relational Database
Format CSV
Created 27 Jan 2021
Last updated 01 Jun 2021
Frequency of Update on Source RealTime
Frequency of Update to SDP
Monthly
Expected Volume/Ingestion Cycle(Daily if Real-time)
5000 records monthly
Language English~English~English~English~English~English~Arabic~English~English~English~Arabic~English~English
State active
Rights
License notspecified
Attribute Name Attribute Description Attribute Datatype Attribute Size Attribute Foreign Key Attribute Range of Values Attribute Language Attribute Classification
sandshift_app_id Unique ID number 22 English Open
application_id Application reference ID number 22 English Open
application_no Application Number varchar2 20 English Open
is_coastal is sand is shifted from coastal area varchar2 20 English Open
is_dm_project If the source location is DM project site with permit varchar2 20 English Open
source_location_type_en The type of location of source i.e. no parcel, DM parcel, other authority plot varchar2 500 English Open
source_location_type_ar The type of location of source i.e. no parcel, DM parcel, other authority plot varchar2 500 Arabic Open
oth_auth_plot_no plot number in case of other authority varchar2 12 English Open
oth_auth_permit_no permit number in case of other authority varchar2 255 English Open
request_type_en Type of request i.e. Sand Transfer or Sand Supply varchar2 500 English Open
request_type_ar Type of request i.e. Sand Transfer or Sand Supply varchar2 500 Arabic Open
total_sand_qty Total sand quanitty to be shifted number 22 English Open
last_update_date Last Update Date date 10 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/059d11a9-cd7b-4557-9753-2645ac27df5c/resource/2262eca8-0243-4b61-94a1-084e2c06353e/download/sand_shifting_application_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?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