Number of Data Files / Resources 1
Updated: 20 Oct 2021
This dataset contains comprehensive details about all free hold units registered in Dubai Land Department , including all available attributes
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: 20 Oct 2021 File Size : 527.91 MB
CSV
Field Value
Data Provenance Units are registered within buildings either for Ijari or ownership registration or freehold.
Dataset Source TABU System
Format CSV
Created 16 Feb 2018
Last updated 20 Oct 2021
Frequency of Update on Source Upon transaction
Frequency of Update to SDP
Daily
Expected Volume/Ingestion Cycle(Daily if Real-time)
1017950
Language English~English~English~English~Arabic~English~English~English~English~English~Arabic~English~English~English~Arabic~English~English~Arabic~English~English~English~English~English~English~English~English~English~English~English~English~English~Arabic~English~Arabic~English~English~Arabic~English~English~English~English~Arabic~English~English~English~English
State active
Rights N/A
License notspecified
Name Description Primary Key Size Datatype Foreign Key Range of Values Language Classification
unit_number UNIT_NUMBER No 100 NVARCHAR2(100) English Open
unit_balcony_area UNIT_BALCONY_AREA No 10 NUMBER(10,2) English Open
unit_parking_number UNIT_PARKING_NUMBER No 1000 NVARCHAR2(1000) English Open
parking_allocation_type PARKING_TYPE_ID No NUMBER English Open
parking_allocation_type_ar PARKING_TYPE_AR No 100 VARCHAR2(100 CHAR) Arabic Open
parking_allocation_type_en PARKING_TYPE_EN No 100 VARCHAR2(100 CHAR) English Open
common_area COMMON_AREA No 20 NUMBER(20,4) English Open
actual_common_area ACTUAL_COMMON_AREA No NUMBER English Open
floor FLOOR No 40 NVARCHAR2(40) English Open
rooms ROOMS No 10 NUMBER(10) English Open
rooms_ar ROOMS_AR No 60 VARCHAR2(60) Arabic Open
rooms_en ROOMS_EN No 60 VARCHAR2(60) English Open
actual_area ACTUAL_AREA No 18 NUMBER(18,2) English Open
property_type_id Number generated through the system No 4 NUMBER(4) English Open
property_type_ar PROPERTY_TYPE_AR No 50 NVARCHAR2(50) Arabic Open
property_type_en PROPERTY_TYPE_EN No 50 NVARCHAR2(50) English Open
property_sub_type_id Number generated through the system No 4 NUMBER(4) English Open
property_sub_type_ar PROPERTY_SUB_TYPE_AR No 50 NVARCHAR2(50) Arabic Open
property_sub_type_en PROPERTY_SUB_TYPE_EN No 50 NVARCHAR2(50) English Open
parent_property_id Number generated through the system No 10 NUMBER(10) Buildings.PROPERTY_ID English Open
grandparent_property_id Number generated through the system No 10 NUMBER(10) Land_Registry.PROPERTY_ID English Open
creation_date CREATION_DATE No 6 TIMESTAMP(6) English Open
munc_zip_code MUNC_ZIP_CODE No 3 VARCHAR2(3) English Open
munc_number MUNC_NUMBER No 10 NVARCHAR2(10) English Open
parcel_id PARCEL_ID No NUMBER English Open
is_free_hold IS_FREE_HOLD No 1 NUMBER(1) English Open
is_lease_hold IS_LEASE_HOLD No 1 NUMBER(1) English Open
is_registered IS_REGISTERED No NUMBER English Open
pre_registration_number PRE_REGISTRATION_NUMBER No 100 NVARCHAR2(100) English Open
master_project_id Number generated through the system No 10 NUMBER(10) English Open
master_project_en MASTER_PROJECT_EN No 250 NVARCHAR2(250) English Open
master_project_ar MASTER_PROJECT_AR No 250 NVARCHAR2(250) Arabic Open
project_id PROJECT_ID No 10 NUMBER(10) English Open
project_name_ar PROJECT_NAME_AR No 200 VARCHAR2(200) Arabic Open
project_name_en PROJECT_NAME_EN No 200 VARCHAR2(200) English Open
land_type_id Number generated through the system No 10 NUMBER(10) English Open
land_type_ar LAND_TYPE_AR No 50 VARCHAR2(50) Arabic Open
land_type_en LAND_TYPE_EN No 50 VARCHAR2(50) English Open
property_id Number generated through the system Yes 10 NUMBER(10) English Open
area_id Number generated through the system No 10 NUMBER(10) English Open
zone_id Number generated through the system No 4 NUMBER(4) English Open
area_name_ar AREA_NAME_AR No 200 NVARCHAR2(200) Arabic Open
area_name_en AREA_NAME_EN No 200 NVARCHAR2(200) English Open
land_number LAND_NUMBER No 100 NVARCHAR2(100) English Open
land_sub_number LAND_SUB_NUMBER No NUMBER English Open
building_number BUILDING_NUMBER No 100 NVARCHAR2(100) 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/85462a5b-08dc-4325-9242-676a0de4afc4/resource/7d4deadf-c9bc-47a4-85de-998d0ce38bf3/download/units.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