Projects, supply pipeline and housing stock (module supply_stock)
Script: scripts/modules/supply_stock.py. Data through 2026-11-05 (last complete month October 2026).
All inputs are Dubai Land Department (DLD) open data published on data.dubai under the Dubai Open Data Licence:
| DLD dataset | Staging table | Used for |
|---|---|---|
| Real Estate Projects register | projects |
project status, dates, planned buildings / units / villas / plots |
| Registered Real Estate Units | units |
registered units by type, bedrooms and size, per project / building / area |
| Building and Property Project Records | buildings_raw |
villa records (villas are not in the units table) and building records |
| Real Estate Transactions | transactions |
sales activity per project (project_number) |
Nothing here comes from a commercial data provider.
1. Project table (projects)
One row per project. Two kinds of rows:
- Register projects (
in_register = true): every row of the DLD projects register (3,474 projects, snapshot 2026-11-01). - Projects outside the register (
in_register = false,status = NOT_IN_REGISTER): projects that appear in the DLD units register (byproject_id), the buildings dataset (byproject_id) or in transactions (byproject_number) but are not in the register file. In the register snapshot of 2026-11-01 most of them are older projects that are no longer in the register (most of those seen in transactions had their last sale before 2020), plus a few recent launches; the register's highest project number (4,615) is above the highest one used in transactions (4,591). A units-registerproject_idand a transactionsproject_numberare treated as the same project when their English names are identical after removing spaces and punctuation and the name is unique on both sides (133 links). Unlinked ids/numbers stay as separate rows, so a few projects may appear twice.
Columns:
| Column | Definition |
|---|---|
project_id, project_number |
DLD identifiers. Units and buildings use project_id; transactions use project_number. |
project_name_en |
English name taken from the units register, else the buildings dataset, else transactions. The register itself carries only an Arabic name; it is not published (Arabic developer credits such as من / بواسطة or a leading brand cannot be removed reliably, and the site does not use it) and is kept in the restricted copy. Names are location labels; some contain a brand name. |
master_project, area_id, area_name_en |
Master project and DLD area (area names from the DLD area lookup). |
status |
Register status: FINISHED, ACTIVE, NOT_STARTED, PENDING, CONDITIONAL_ACTIVATING, FRIEZED (frozen, spelled as in the source), or NOT_IN_REGISTER. |
flag_cancelled |
True when the project is not finished and has a cancellation_date on or after its project_start_date (see section 2). The register has no "cancelled" status; most cancellation dates belong to projects that were later restarted. |
percent_completed, project_start_date, project_end_date, completion_date, cancellation_date |
As published by DLD. For unfinished projects completion_date is a planned date. |
no_of_buildings, no_of_units, no_of_villas, no_of_lands |
Planned counts from the register. no_of_units = units in buildings (apartments, hotel units, offices, shops); no_of_villas = villas; no_of_lands = plots sold as land (on many plot projects villas are added later). |
zoning_authority |
Planning authority (a government body). |
reg_* |
Counts from the DLD units register for the project: reg_units (all units), reg_apartments, reg_hotel, reg_commercial, reg_other, reg_buildings (distinct buildings), reg_villa_records (villa records in the buildings dataset). |
res_studio ... res_b5plus, res_unknown |
Residential units (apartments, stacked townhouses, villas) by bedrooms. |
sales_all_time |
All DLD sales-group transactions recorded for the project_number. |
sales_12m, sales_12m_offplan, sales_12m_value_aed |
Sales in the last 12 complete months (2025-11-01 to 2026-10-31), excluding developer-level "Development" procedures; off-plan = Oqood registrations. Value uses only rows that pass the price check and is empty when fewer than 5 such rows exist. |
median_aed_sqft_12m, n_sales_psf_12m |
Median price per sq ft of residential apartment/villa/townhouse sales in the same window that pass the price and area checks of the staging layer, and the number of such sales. |
withheld_brand_name |
True when the project's registered or published name carries a developer brand. The sales columns above are then empty: sales of such projects are published only inside community and area totals (00-publication-compliance.md, section 4; owner decision of 7 October 2026). 823 projects in the build of 9 November 2026 (785 before the own-developer brand test was added that day, 737 on 9 October and 652 on 7 October 2026; the brand place-name list was corrected on 9 October). |
Developer, master developer and escrow agent names are not published. A copy with them is kept in
data/restricted/supply_stock/ for internal use only.
2. Supply pipeline (pipeline_*)
Built from register projects only (their planned unit counts and dates).
- Included statuses:
ACTIVE,NOT_STARTED,PENDING,CONDITIONAL_ACTIVATING(all "not yet completed"). - Excluded:
FINISHED(goes to completions),FRIEZED(one frozen project), and projects withflag_cancelled(6 projects whose last cancellation date falls after their latest start date). - Expected completion date:
project_end_date; if missing,completion_date. - Year buckets:
2026...2030,after_2030,overdue_pre2026(expected date before 2026 but the project is still not finished; most of these had 2025 dates and are late or awaiting a status update) andno_date(neither date given; mostly projects started in 2023-2024).2026covers the whole calendar year, including dates already passed in 2026. - Estimated variant (
pipeline_city_by_year_type_estimated): undated projects are placed at start date + the median planned duration of register projects started since 2015 (about 1,050 days ≈ 2.9 years); results before 2026 are moved to 2026. Columnunits_with_estimated_yearshows how much of each bucket is estimated. This is an estimate. - Types:
villa=no_of_villas, plus, for plot projects, the number of plots that already carry a residential villa record in the buildings dataset (capped atno_of_lands). The remaining plots are reported asplotand are not counted as homes.- Units in buildings (
no_of_units) are split intoapartment,hotel,commercialandotherusing the mix of units already registered for that project in the units register. This split is an estimate. If no units are registered yet, the units are reported asbuilding_unit_unclassified.
- Projects outside the register (
pipeline_not_in_register_by_area): projects not in the register with off-plan sales in the last 12 months or units first registered in 2025 or later. They have no status or dates, so they are reported separately with the units already registered for them (apartments, villas, hotel, commercial, other), not placed in a year. Area cells with 1-4 registered units are empty.
Caveats: planned dates are developer schedules filed with DLD and often slip; NOT_STARTED and PENDING projects may
never be built; unit counts are planned counts and change as projects are re-planned.
3. Completions history (completions_*)
Register projects with status FINISHED, by year of completion_date (or project_end_date when the completion date
is missing), split by the same types as the pipeline. Only projects in the off-plan projects register are covered;
buildings completed outside that register (older Deira / Bur Dubai stock, buildings developed without off-plan sales)
are not included. Recent years are understated because statuses are updated with a delay: many projects with planned
completion in 2025-2026 are still ACTIVE in the register.
4. Housing stock (stock_*)
Stock = every unit in the DLD units register (2,388,184 units) plus every villa record in the DLD buildings dataset (225,450). Units are classified as:
| Class | Rule |
|---|---|
apartment |
sub type Flat or Unit, or (no sub type) a room label with a bedroom count, Studio, Penthouse or Duplex |
townhouse |
sub type Stacked Townhouses (grouped with villas in villa_townhouse) |
villa |
villa records in the buildings dataset with a residential or missing room label |
hotel |
sub type Hotel Apartment / Hotel Rooms / Hotel, or room label Hotel / Hotel apartments |
labour_staff |
room labels for labour camp rooms, staff accommodation, portacabin rooms, single rooms |
commercial |
offices, shops, stores, warehouses, workshops, kiosks, showrooms, clinics, gyms and other business labels |
other_unknown |
parking, schools, hospitals and similar, plus units with no type information (about 267,000 units have no type at all) |
residential = apartment + townhouse + villa. Hotel units and labour/staff accommodation are reported separately.
freehold counts units flagged freehold.
Bedrooms are parsed from the DLD room label ("Studio" = 0, "2 B/R" and "2 bed rooms+hall" = 2). Buckets: studio, 1, 2, 3, 4, 5+ and unknown. The source does not separate villas from (non-stacked) townhouses.
Sizes: unit size = actual_area from the units register, kept when between 150 and 30,000 sq ft; villa size = built-up
area from the buildings dataset (or actual area when built-up area is missing or zero), kept when between 500 and
60,000 sq ft. avg columns are arithmetic means; the long table stock_area_type_bedrooms also gives medians, which are
more robust (a few mis-recorded sizes can move an average).
Tables: stock_by_area (per DLD area), stock_by_project (per project), stock_by_building and
stock_area_type_bedrooms. A building is the DLD parent building record of a unit (building_record); units without a
parent building are grouped by plot (plot, area + land number). Villas are not listed one by one; they are counted in
the area and project tables only.
5. Privacy and suppression
- No company names (developers, master developers, escrow agents, management companies) are published. A few DLD project records carry a developer's or owner's name instead of a project name; any project or master-project label that equals a company name in the DLD developer, project or service-charge tables (or contains a long one) is left empty in the public tables and the site file.
- No unit-level rows; the smallest published level is a building or plot, and transactions are never linked to units.
- Any count of 1-4 derived from unit records or transactions is published as empty (null), and any statistic (average
size, median price, sales value) built from fewer than 5 records is empty. This includes the numbers of distinct
buildings and projects holding registered stock in
stock_by_area(buildings_with_units,projects_with_stock); numbers of projects in the pipeline, completion and outside-register tables (projects) are not suppressed, since every project is a row of the project table. Instock_by_building,suppressed_small = truemarks buildings with fewer than 5 units; on those rows every count and size column is empty (an empty category next to zeros would show which category holds the units). Planned counts that come directly from the project register (one record per project, published per project) are not suppressed, nor are pipeline and completion totals built from them. - Because small counts are blanked, summing a suppressed column will slightly undercount.
6. How many projects does DLD know about?
- Projects register (snapshot 2026-11-01): 3,474 projects (1,684 finished, 1,237 active, 314 not started, 227 pending, 11 conditionally activating, 1 frozen).
- Plus 309 project identifiers found only in units, buildings or transactions → about 3,780 distinct projects visible in DLD open data.
- DLD project numbers run up to 4,615 in the register (4,591 in transactions), so DLD has issued roughly 4,600 project numbers since off-plan registration began. The gap to the register is explained by projects that were cancelled or merged and dropped from the register, and by recent launches that a published register snapshot does not yet contain (a few in this build, with numbers below the register's highest, 4,615; no project numbered above it has sales).
Commercial "project trackers" usually show more projects than DLD because they also cover other emirates (for example Abu Dhabi), add projects from planning and building permits and developer announcements before DLD registration, and count phases or buildings as separate projects. DLD only lists projects registered for off-plan sale (escrow) in Dubai; older buildings completed before the register, or built without off-plan sales, are not DLD "projects", although their units are in the units register and therefore in the stock tables.
Outputs
data/out/supply_stock/: projects, pipeline_city_by_year_type, pipeline_city_by_year_type_estimated,
pipeline_city_by_year_status, pipeline_area_by_year_type, pipeline_not_in_register_by_area,
completions_city_by_year_type, completions_area_by_year, stock_by_area, stock_by_project, stock_by_building,
stock_area_type_bedrooms (each as .parquet and .csv). Site payload: site/data/supply_stock.json.