Service charges (owners-association budgets)
Script: scripts/modules/service_charges.py · Public data: data/out/service_charges/ · Site data: site/data/service_charges.json
Source
Dubai Land Department (DLD) service charge index, published on data.dubai under the Dubai Open Data Licence and staged as table
service_charges (169,109 rows, budget years 2017–2026). Each row is one line of an approved owners-association (OA) budget:
budget year × property group × usage × service category → AED per sq ft per year. A property group is the DLD unit the
budget is approved for: usually one building, sometimes a cluster, a shared area or a master-community zone.
Coverage grows sharply over time (property groups with a budget: 9 in 2017, 73 in 2018, about 1,000 in 2019, about 3,000 in 2025–2026). Years before 2017 are not in the open data. Treat 2017–2018 as sparse.
Definitions
Budget record = one property group × usage × budget year. Usage is the DLD usage label (Residential, Retail, Offices, Parking, Mixed, Stores, Hospitality, ...). The two DLD usage codes that are both labelled "Parking" are merged by label (no property group has both in the same year).
Total service charge (AED/sq ft/yr) = sum of the budget's service-category lines, where
- added: Services, Maintenance, Improvement, Hotel Services, Utilities Services, Management Services, Insurance, Master Community, Reserved Fund, Shared Services, Fire Related Provisions, Doubtful Debts, Adjustment (signed as published, usually negative);
- subtracted: Income (OA income such as interest, fines or leasing of common areas offsets costs; DLD publishes it as a positive number, so we subtract it. 4 Income lines are negative in the source and are therefore effectively added);
- excluded as ancillary items billed separately or on another basis: Unit A/C (Charges), Unit A/C (Sq.Ft), Storage Units,
Parking (a per-bay charge, values in the hundreds or thousands of AED) and Meter Installation (a per-meter charge).
Their values are still published in the category columns prefixed
anc_and incategory_lines.
Totals are rounded to 2 decimals (the source precision).
Top categories = the three largest positive added lines, as text.
Budget type (heuristic from the DLD property-group name):
master_community_or_plot: the name contains Permised, Vacant, Under Construction, Undeveloped, Plot(s), Master Community or Infrastructure. These are master-community charges on plots or zones, typically 0.1–3 AED/sq ft of plot area, and are not comparable with building budgets.shared_area: the name contains Shared Area, Shared Service(s), Shared Facilities or Common Area. These are budgets for areas shared by several towers, which owners pay on top of their tower budget.building: everything else.
Quality flag (budget kept in the building tables, excluded from all statistics):
likely_per_bay_rate: Parking usage with a total above 100 AED/sq ft. Such budgets are almost certainly expressed per parking bay, not per sq ft.implausibly_high: any other usage above 100 AED/sq ft.zero_or_negative: total ≤ 0.no_core_lines: the budget has only ancillary lines, so no total can be computed (rule kept as a guard; no budget currently has it).
Year-on-year change (yoy_pct) = total / total of the same property group and usage in the previous budget year − 1.
In building_latest a second basis is allowed when the property group was re-registered under a new id
(yoy_basis = 'name_link'): exactly one budget with the same normalised name, usage and master community exists in both the
latest year and the year before. same_id means the same DLD property group id. When neither applies, YoY is empty.
Keys, unspecified projects and multiple budgets
- The key is always
property_group_id. 36% of lines carryproject_id = -1("UNSPECIFIED PROJECT"); for thoseproject_idandproject_nameare left empty, and the budget is still fully identified by its property group. One project name that is a DLD placeholder ("Project Registration Request ...") is also treated as missing. - The source has no duplicate lines: each budget year × property group × usage × category appears once.
- Names are not unique. A name can map to several property groups in the same year. This happens for genuinely separate
budgets that share a generic name (for example 13–14 towers of a community, each with its own budget, all named
"... Community Residence - Residential"), and for a name re-registered under a new id from one year to the next.
same_name_budgetslists every year × name × usage × community with more than one property group (89 cases, 332 budgets), and the columnsame_name_budgetsin the building tables gives the count. Use the id, not the name, to identify a budget. - Names are cleaned only by collapsing repeated spaces; spelling is DLD's. Master-community labels are grouped case-insensitively, and the most frequent spelling is shown (for example two DLD ids for "Palm Jumeirah" are merged).
- Each budget has exactly one management company in the source (checked). The company name is kept only in the restricted copy.
Outputs (data/out/service_charges/, parquet + csv)
| file | grain | content |
|---|---|---|
building_year_usage |
property group × usage × year | total, previous-year total, YoY %, top categories, budget type, quality flag, one column per category (anc_ = ancillary, not in total) |
category_lines |
one row per DLD budget line | category, AED/sq ft, role in total (added / subtracted / ancillary_excluded) |
building_latest |
property group × usage | latest budget year and total, YoY with basis, first year and its total, number of years |
community_latest |
master community × usage, latest budget year (2026) | number of building budgets, p25 / median / p75 / mean / min / max, median YoY of budgets present in both years |
community_year |
master community × usage × year | same statistics for every year |
city_year |
usage × year | same statistics, all of Dubai |
category_composition_latest |
usage × category, latest year | median and mean AED/sq ft of each category across budgets that have the line |
same_name_budgets |
year × name × usage × community | property groups sharing a name |
coverage |
year | counts of property groups, budgets, budgets without a project, flagged budgets, budgets by type |
Statistics (community, city, composition) use building budgets only (budget_type = 'building'), exclude flagged budgets,
and the "Unspecified" master community is left out of community tables (it stays in city tables). Each budget counts once,
not weighted by size. The open data has no area per budget, so these are medians of buildings, not of square feet.
Privacy and licence rules applied
- No company names (management companies or developers) in public files or site data. Building, project and community names appear only as location labels, as DLD publishes them.
- No unit-level data: the source is building-level, and nothing is joined to units or transactions.
- Suppression: any aggregate built from fewer than 5 budgets has its count shown as
<5and its statistics set to empty (suppressed = true). Median YoY needs at least 5 budget pairs. Building rows are published as they are: each is one official DLD budget figure for a building, not an aggregate of private records.
Caveats
- Values are approved budgets (what owners are charged per sq ft), not actual spending.
- Budget type is a name-based heuristic. A few master-community budgets with ordinary names will be counted as buildings, and the other way round.
- Growth in budgets over time is partly coverage growth. Compare medians across years with care, and prefer per-building YoY for trend.
- A budget can be split by usage (residential, retail, offices, parking ...) within one building. Owners pay the rate of their unit's usage.
- Ancillary charges (chiller/A/C, parking bays, meters) can be material for owners but are excluded from the total because they are billed on another basis.