Jumeirah Village Circle, Dubai

1. Data and licences: open layers, with what each one lacks

Base layers (block a)

Network and safety layers (block c)

Traffic model outputs (block b)

SUMO 1.28 (EPL-2.0) on the OpenStreetMap network (ODbL); calculation ours [19, istochnik, licenziya]. 20 scenario files present; the list with captions is in section 5.1.

Attribution required on screen and in print

© OpenStreetMap contributors (ODbL); © Overture Maps Foundation; RTA GTFS via MobilityDatabase; Dubai Police open data; Copernicus DEM: produced using Copernicus WorldDEM-30 © DLR e.V. 2010-2014 and © Airbus Defence and Space GmbH 2014-2018 provided under COPERNICUS by the European Union and ESA; all rights reserved [20, attribution] [21].

Dubai Pulse open data licence: what it allows and requires

Two caveats

• The licence text was read from an Internet Archive copy of 07.07.2022; the file name contains the word DRAFT and no other edition was found Not verified [4, s. 6]
• The Dubai Police incident dataset card says “License not specified”; we apply the portal licence Not verified [4, s. 6]

Required credits, used on every page: RTA GTFS via Dubai Pulse / MobilityDatabase (https://files.mobilitydatabase.org/mdb-3359/latest.zip); Dubai Police, traffic incidents, via Dubai Pulse (https://www.dubaipulse.gov.ae/dataset/c9263194-5ee3-4340-b7c0-3269b26acb43/resource/c3ece154-3071-4116-8650-e769d8416d88/download/traffic_incidents.csv) [23, metadata.istochnik] [24, metadata.istochnik]. Independent analysis on open data. Not endorsed by or affiliated with Dubai Municipality, RTA, DEWA or Dubai Police. [22]

Dubai Pulse does not open from our address; datasets that live only there (community boundaries, speed limits and radars, incidents after the archived copy) are not used [25, item 2].

2. Dubai standards used, with document and page

Water, sewerage, stormwater and transformer limits are covered by primary documents with page numbers. Trip generation rates, road design and electrical load densities are not published openly; the model uses stated substitutes [26, s. 1, 4].

Water supply, DEWA

Sewerage, Dubai Municipality

Stormwater, Dubai Municipality

Electricity, DEWA

DEWA facts used for calibration

Traffic impact, RTA

Occupancy, Dubai Building Code

Documents that are closed or not found

DM marks the Sewerage and Stormwater guidelines as Open Data without stating reuse terms; DEWA documents carry no licence. Numbers are cited with document and page; the documents themselves are not redistributed (internal research note 04, s. 4). [26, s. 4]

3. Population is a range of 31,371 to 124,953 residents, and the pipeline of new units a range of 13,147 to about 46,210

The 2023 census does not see what was built after it: towers completed in 2024 to 2026 are not in the 31,371 Assumption [4, s. 3]. Whether the OSM polygon matches the boundary of community 681 is not checked Not verified [4, s. 3].

What the model uses

Construction pipeline

The 2029 scenario adds 36 register projects with 13,019 units, placed at district centres (indicative location): a lower bound Calculated [9, proekty_08.niz]. Projects without coordinates are excluded: Capital One (DLD register, 128 units).

4. Assumptions by layer: what we chose where the data stops

Buildings

Heights of 84.35 % of buildings are estimated (2,862 of 3,393, share from the data): floors by building class × floor height (tower 3.2 m, villa 3.5 m, commercial 4 m, other 3.5 m) Assumption [2, height_source, metadata.normy.ETAZH] [4, s. 2]. All facades are procedural by building type; hero-zone detail is typical appearance, not a survey HQ decision [35].

Visual detail

Detail in the hero zones (doors, canopies, AC units, utility cabinets, street furniture) is typical appearance modelled from public reference photos of Dubai, not a survey of specific buildings; no visual detail is presented as data HQ decision [35]. Hero zones: Hessa Street, the central roundabout, the tower block, a villa street.

Hero-zone asset list with licences

Blender material list with licences

Screen textures: three Poly Haven images under CC0 (asphalt, concrete pavers, herringbone pavement); colour retinted on screen, image unchanged [38].

Base layers (block a)

Largest single assumption of the building layer: 178 towers tagged in OSM with 1 to 2 floors are treated as default tagging; the tag is dropped and floors estimated Assumption [4, s. 2].

Traffic (block b)

Demand matrix of block (a), taz.geojson / od.csv (gravity model, see data passport); zone edges are streets inside each zone, external zones at the nearest network edges; routes by duarouter with en-route rerouting Assumption [19, dopushchenie]

Networks and safety layers (block c)

5. Method: how each layer is calculated

5.1 Traffic (SUMO)

Network: OpenStreetMap through Overpass (snapshot 2026-10-08T23:00:01Z), cut to the district outline plus 1,000 m; 3,413 edges, 46 roundabouts, 2 signals [39, kontur, reber, kolec, svetoforov].

Demand: gravity matrix of block (a) → od2trips → duarouter; morning peak 07:00-08:00, mode mikro [19, okno_chasy, rezhim]. Trip rates are substitutes for the closed RTA manual Substitute [26, s. 3.4].

Red threshold: speedRelative < 0.5 red, < 0.75 yellow, else green; peak-hour mean weighted by vehicle-seconds [19, porog].

2029 against today: raw counts with the model noise beside them

Method: SUMO micro runs of the full peak hour, compared scenario against base; the noise column is the spread of the same count between runs of the base that differ only in the random seed [59, s. 2]. The live tower service uses a different method (meso runs with common random numbers) and its counts are not comparable with this table.

Nothing is subtracted: the raw count and the noise of the comparison scenario stand side by side [59, s. 2].

The 2029 projects add queues inside the district, not cars leaving it: outbound demand grows by 2,057 vehicles an hour, vehicles leaving the district within the hour are 4,583 against 4,630 today, and 809 vehicles could not enter the network against 226 today Calculated [7, 2029-niz, baza-m1-t025] [59, s. 2].

How many cars actually leave JVC in the modelled peak hour

Merge capacity calibrated to HCM per-lane capacity and the RTA bridge figure of 3,200 veh/h; before calibration the model let at most 2.8k veh/h leave the district. Calculated [26, s. 3.4] [60] [59, merge capacity]. After calibration the most that leaves the district within the hour in any scenario above is 4,630 vehicles; the rest of the queue stands on the main roads beyond the exits [7, vyezd_iz_rayona.vyehali_za_chas] [59, s. 1].

The model is not calibrated against traffic counts (none are open); "tower" scenarios are shown as before and after on the same model, not as a forecast of flows [61, s. 3.4] [62].

Live “place a tower” service: response time

6 paired meso runs in parallel (libsumo), common random numbers; HTTP on 127.0.0.1; base scenario baza, utro peak; measured 2026-10-09 08:38 on Apple M4 Pro, 14 cores, 48 GB (sysctl), idle: no other SUMO runs; service start 5.8 s Calculated [63].

This table is about response time only; the traffic verdict of one tower is in the floor series below [63].

Experiment: one tower from 10 to 90 floors, and a cluster of 40-floor towers, on one free plot

Plot 25.064408, 55.216359 (square 39 x 39 m, residential); base baza (census level, through-traffic 25 %), morning peak 07-08, SUMO meso. calculated: people and trips by block (a) norms, routes and noise of the SUMO meso model; not counted traffic; an experiment for the passport, not a presentation scene Calculated [64, uchastok, baza, dopushchenie_en].

one tower of 40 floors: within noise; not measurable up to 90 floors; 6 towers of 40 floors nearby: measurable [64, vyvod_en, klaster_en].

steps above 2 standard errors: 70, 80 floors; the threshold needs every higher step above noise too [64, primechanie_en].

Measure and threshold: effect = mean paired change of summed timeLoss (vehicle-hours) on the approaches of the exits that carry at least 20 % of the tower's outbound trips (shortest path at speed limits); standard error over 6 pairs of meso runs with common random numbers (seeds 42-47); above noise = effect > 2 standard errors and > 30 s Assumption [64, mera] [59, tower service].

Where the cluster towers stand: tower 1 on the plot; tower k at the nearest free plot to tower 1 (rings every 5 m, 8 m along the ring, from east counter-clockwise); footprint 39 x 39 m plus 3 m clear of buildings, roads, sidewalks, hero zones and towers already placed; places chosen before the runs Assumption [64, pravilo_klastera] [59, tower service].

Nearest exit by straight line: nearest exit by straight line (v13 Hessa Street) is reported per step: in the service meso the base routes are fixed by duarouter and no base or tower route uses the v13 approach streets, so its effect is 0 by model construction, not by traffic Assumption [64, mera_v13] [59, tower service].

False alarms: v07 (Al Khail Road) can come out beyond noise; with 19 exits at 2 standard errors about one false alarm per request is expected Assumption [64, lozhnaya_trevoga] [59, tower service].

Why one tower differs between bases

One residential tower of 40 floors on the plot of the floor series, answered by the live service on each base. Method: meso service, 6 pairs of runs with common random numbers; effect on the exits that carry at least 20 % of the tower's trips, beyond noise when it exceeds 2 standard errors Calculated [64, mera].

On the census-level base the network has room and one tower stays within noise; on the estimated-occupancy base the network is saturated and the same tower becomes measurable. The tower's own trips also scale with the district multiplier. On screen the change of base is made openly and captioned HQ decision [35].

Rule for every comparison of bases: the caption lists everything that changes between them: residents of the district, residents of the project, through-traffic HQ decision [35].

5.2 Water supply

No DEWA network plan is open. We laid pipes along OSM streets (179.3 km, 2,629 pipes, 1,763 nodes), connected each of 3,393 buildings to the nearest street, and sized diameters from the DEWA series until velocity and pressure met DEWA Table 2 [27, Table 2, p. 6]; hydraulics in WNTR (EPANET 2.2) Calculated [68].

Demand: residents of block (a) × consumption at the middle of the DEWA ranges (apartments 250, villas 300 l/person/day; worker 52.5) [27, Table 1, p. 4]; peak hour [27, Table 2, p. 6]. Sized for scenario baza-m1; inlet pressure 1.5 bar; terrain ignored Assumption [69].

5.3 Sewerage

Gravity tree along the same streets to one assumed outfall; flow 80 % of water [28, p. 18], peak factor 4.25·(P/1000)^(−1/6) [28, p. 21]; red when d/D exceeds the DM limit by diameter [28, Table 3-4, p. 24]; 12 pump stations where the invert is deeper than about 10 m [28, p. 29] Calculated [68, kanal_nasosnyh].

Today's network is sized for today's buildings; red appears with the 2029 projects HQ decision [35].

5.4 Stormwater drainage (complete method)

The network is synthesised by us along OpenStreetMap streets to the Dubai Municipality standard. We do not have DM drainage plans [71, s. 3.4] [72].

Standards applied

DM Table 0-2, Dubai rainfall intensity, mm/h [29, Table 0-2, p. 30]

How the diameters were chosen

The district with a 150 m buffer (1,224.3 ha) is split into 18 catchments of at most 80 ha (largest 79.9 ha), each with an assumed outfall; roofs cover 11.4 % and asphalt 17.5 % Calculated [73]. Each pipe is the smallest diameter whose full-bore capacity carries both the 1-in-5-year design storm and the 1-in-10-year check (DM gives no proportional depth for stormwater; the 10-year check is taken strictly, without surcharge) Assumption [72, sizing]. Slope gives at least 0.75 m/s at full bore and follows the GLO-30 terrain trend where steeper.

1,745 pipes, 113.8 km; maximum depth 7.53 m; longest time of concentration 76.2 min; 77 pipes of 2,000 mm exceed 2.5 m/s, where a box culvert outside the DM pipe series would be needed Calculated [73].

Storms it was checked against

Load = design flow / full-bore capacity; red above 100 %. The 1-in-5 and 1-in-10 storms produce no red by construction. The shape of the 16.04.2024 storm within the day is unknown, so the event is compared by its daily total, not run as a separate storm [72] [71, s. 2].

Low-lying spots: depression filling on Copernicus GLO-30 after a median filter of about 150 m; 49 spots, 9 inside JVC (191 ha); rule: area from 0.5 ha, fill depth from 1 m Assumption [73, niziny]. No drainage plans, lidar or 2024 incident log were used; water depths and durations were not computed; not compared with the April 2024 extent, which is not published as a raster [71, s. 3.3, 3.9].

5.5 Electricity

DEWA publishes no load density per m² or per apartment [26, s. 3.1]. Residential load is calibrated to DEWA 2025 residential use per customer and the city peak-to-average ratio [31] [26, s. 3.1], giving 23.18 W/m² on average and 36.86 W/m² at peak Substitute [70, k_zhilya_vt_m2_sred, k_zhilya_vt_m2_pik]. Non-residential: 300 kWh/m² a year Substitute [74].

289 substations placed by us (271 × 1000 kVA, 36 × 1500 kVA, 325 MVA); red above 800 kW per 1000 kVA and 1200 kW per 1500 kVA [30, cl. 4.7.2, p. 46], amber from 80 %; power flow in pandapower Calculated [70].

5.6 Ambulance and fire response

Travel time along the OSM road graph from the nearest known station to each building; night at the speed limit, peak at the modelled traffic speed of the baseline SUMO run (upper bound); dispatch and turnout not included Calculated [75]. Stations mapped in OSM: الدفاع المدني القوز; Civil Defence - Jebel Ali Fire Station; Al Sufouh Ambulance Service; Global Village Ambulance Station; Al Barsha Fire Station; Al Marsa Fire Station; Dubai Corporation for Ambulance Services; unnamed (way/1127334014) [76, spisok_stanciy].

Ambulance: station list requested from the city. The layer shows time from the nearest known station and is not coloured red while the list is incomplete HQ decision [35].

Scenario 16.04.2024: speeds from the block (b) SUMO scenario 16-04-2024 (rain: speed factor n/a, headway 1.3 s after FHWA); off the SUMO network, peak speed × the class median ratio of 16.04 to peak Assumption [76, skorosti.16_04].

Scenario pik-prioritet (ambulance only): travel time in traffic divided by 1.4, a London figure for blue-light journeys (Poulton et al., arXiv 1812.03181), used as a substitute Substitute [75, pik-prioritet].

5.7 Camera blind spots

No open camera layout exists and OSM maps 0 cameras in JVC. Typical placement: 540 at junctions, 28 at roundabouts, 17 at district exits; a camera sees a street point within 50 m if no building footprint blocks the line Assumption. Coverage 48.2 % of 164.9 km of streets; 85.2 km without a camera; minimum 960 cameras for 95 % (greedy selection) Calculated [77]. Recognition of people's behaviour is not done and not offered [35].

5.8 Construction project cards

For the 37 register projects with unit counts (13,147 units) at occupancy 0.5: water 4,108 m³/day, peak electricity 19 MW, 2,629 car trips in the morning peak Calculated [78]. Traffic impact study thresholds of Resolution 603 [32, Art. 4(b), 6]: 33 projects below the 150-trip threshold; 4 projects at level 1 (150-500) [78, tis_z05].

Where each project's peak trips queue (scenario 2029-niz)

zone-level: block (a) matrix places each 2029 project in the zone of its block centre and mixes its trips with the zone's existing trips, so the queues are those of all peak-hour trips from the zone; time lost on an edge = time on the edge from SUMO exit times minus length at the speed limit; share = lost time on the edge / total travel time of those trips calculated; project positions are block centres, not plots; the 2029 run uses estimated occupancy (district x1, through-traffic 0.25); not counted traffic Calculated [79, metod_en, dopushchenie_en]

Zone-level: a project's trips cannot be separated from its zone in the demand matrix, so each row shows the queues of its zone HQ decision [35] [79, uroven].

5.9 Presentation frames and render method

The scene is built by script from the same data files as the screen: building footprints and heights (a), roads (a), vehicles from the SUMO baseline trajectories (b), networks at calculated depth and diameter (c), hero zones; sun position for 16.10.2026. Renderer: Blender Cycles, OptiX denoising, adaptive sampling. Facades, balconies, fences, street furniture, vehicles and people are typical appearance, not a survey Assumption [80] [35].

Render time on a rented RTX 5090 is estimated, not measured: a test on the Apple M4 Pro at 5 % resolution and 16 samples, scaled linearly by pixels and samples and by the ratio of Blender Open Data medians (16,088.1 for RTX 5090 OptiX against 2,899.8 for M4 Pro, ratio 5.55) [81] [82, open_data, otnoshenie_5090_k_m4pro]. Upper bound 26 h Calculated [82, pereschet_09_10_08_20]. No final frame has been rendered yet.

7. Retrospective check: where the model turns red against where the city spent money

Rule: a city action counts as matched when at least one modelled exit from JVC to that road is red in the baseline morning peak (mean speed below 50 % of the limit) Assumption [83, status].

After calibration the merges out of the district are not saturated: 136–606 vehicles an hour per lane against the HCM range of 1,800–2,200. Queues form on the arterials beyond the exits: Al Khail Road narrowing from 4 to 3 lanes (3,395 vehicles an hour at 42 % of the speed limit), the on-ramp merges onto Sheikh Mohammed Bin Zayed Road (about 2,900 vehicles an hour each), and a slip road narrowing from 4 to 1 lane(s) (OSM way 447602819, 1,793 vehicles an hour). This is where the RTA programme of AED 6 billion with four grade-separated access points is directed; without RTA interchange drawings and counts the model cannot be refined further Calculated [59, s. 6, arterials beyond the district] [86].

Dubai Police incidents (2023-03-09 to 2024-05-12): 603 of 1,661 lie within 50 m of red edges, while red edges are 20.1 % of the network length with data (our arithmetic) [7, proisshestvij_u_krasnyh, dolya_dliny_krasnaya]. This is not taken as evidence: red sits on the main roads, where there are more vehicles and therefore more incidents [59, s. 5].

8. Your standards vs your rain

A drainage network sized to the DM standard carries the design storm and is over full-bore capacity on 98.6 % of its length in the 1-in-100-year storm

We sized a stormwater network for JVC to the DM 1-in-5-year design storm and checked it at 1 in 10 years: 0 and 0 pipes over capacity. In the 1-in-100-year storm (146.4 mm a day by the DM table) 1,632 of 1,745 pipes are over full-bore capacity, 112.13 km of 113.8 km, 98.6 % of the length; median load 201.8 % Calculated [8, periody.t100] [73, periody.t100.trub_red].

The network is synthesised by us along OpenStreetMap streets to the DM standard. We do not have DM drainage plans. It shows what the standard itself allows for; it is not the built network of JVC [71, s. 3.4] [72].

The standard, the storm, and the table it sits in

By daily depth, 142 mm is 3.07 times the residential design storm and 97 % of the 1-in-100-year storm (our arithmetic on the numbers above). Hourly rainfall for Dubai is not published as open data; short bursts (5 to 60 min) of 16.04.2024 were not checked (internal research note 07, s. 2 and 3.1). [71]

Bars: daily depth = 1440-minute intensity of DM Table 0-2 × 24 h [29, Table 0-2, p. 30]. Marked line: 142 mm at DXB [87]. Other windows of the same event: 119 mm, DXB, 16 April only [90]; 164 mm, DXB, whole event [91]; 168 mm, Jumeirah, 24 hours, return period about 125 years by the vendor's estimate Vendor source [92].

The same network, storm by storm

What this page does not show, and why

• The Dubai stormwater network (pipes, manholes, pump stations, outfalls with levels) is not in any open dataset we found. [71, s. 3.4]
• No lidar or 1 m terrain model of Dubai in open access; Copernicus GLO-30 is a 30 m surface model with vertical error up to 4 m, captured 2010 to 2015. [71, s. 3.5]
• No flood log of April 2024 (points, depths, hours). A satellite study maps 23.8 km2 flooded across Dubai, 66 % of it bare land; no raster published. [93, internal research note 07, s. 3.2, 3.3]
• No press source names JVC among flooded places in April 2024. [71, s. 3.2]
• The network built since 2024 under Tasreef (AED 30 billion, to 2033) differs from the 2024 network. [71, s. 3.4]

Return periods in the DM standard [29, Table 0-1, p. 29]

Method

The stormwater method is in section 5.4 [73].

9. What would turn this demonstration into a calculation

Each item below is closed or not published as open data; each one replaces a stated assumption of this passport. Without them the twin shows where the district is tight and why; with them the same models can be checked against Dubai measurements [61, s. 3.4, 5] [71, s. 1 item 8, 3.7].

10. What changed on 9 October and why

Every correction of the calculation is listed here with its date, the old and the new value. Old values are kept with the project history commit they come from; new values are read from the current data files [35].

09.10.2026: Floor area recalculation (block a)

The FIVE Jumeirah Village footprint in OSM is its podium; multiplying it by 61 floors overstated floor area, electricity and residents. Floor area of known towers now comes from CTBUH; other towers of 8 floors and more get a 4-floor podium plus a typical floor of 2,200 m2 per tower (calibrated on FIVE); apartments are counted above the podium only. [94] [95]

09.10.2026: Lost trips in route assignment fixed (block b)

The route builder silently dropped trips whose external destination was an edge unreachable from the network (Al Khail Road north-east, Hessa Street south-east). This affected every run before the fix; sources and destinations are now taken only from the strongly connected core of the network. [98]

09.10.2026: Census multiplier derived from data on every run (block b)

The district multiplier was set once as 0.36 from an earlier block (a) figure. Since the floor-area recalculation it is computed at every run as census residents of community 681 divided by the residents block (a) computes in the same polygon. [100]

09.10.2026: Hessa Street widening of 19.04.2026 checked against the model network

RTA widened Hessa Street to 4 lanes each way on 19.04.2026. The OpenStreetMap snapshot of 08.10.2026 used by the model already carries 4 to 5 lanes there, so no model edit was needed; the widening is now listed in the retrospective check. [84] [100]

09.10.2026: Merge capacity at the district exits calibrated (block b)

Before calibration the model let at most about 2.8 thousand vehicles an hour leave the district, below the 3,200 veh/h design figure of the single RTA bridge. Merges were calibrated to HCM per-lane capacity and the RTA bridge figure. [100] [60] [26]

09.10.2026: Tower test point moved off an existing building (block b)

The tower test point was inside an existing building (a shopping building, OSM way 700403018); it was moved to the nearest free plot, and the result there is within model noise. The service now checks the plot before every run. [100]

Appendix B. Sources

Pending items in this build: none; every block has delivered the files this passport reads. Opened 09.10.2026 during our research unless stated. Internal notes and data files are available on request.

1. [1] Project data file dannye/jvc/granica.geojson, block a. file time 2026-10-09 06:27
2. [2] Project data file dannye/jvc/zdaniya.geojson, block a. file time 2026-10-09 06:27
3. [3] Dubai Statistics Center, population 2023 by community, via citypopulation.de (community 681 Al Barsha South Fourth). https://citypopulation.de/en/uae/dubai/admin/ block (a) data passport, section 3
4. [4] Block (a) data passport, available on request. file time 2026-10-09 06:27
5. [5] Mirror of the DLD project register, datadubai (projects.csv, cut-off 02.10.2026, licence CC BY 4.0 as declared by the repository). https://github.com/datadubai/dubai-real-estate-dld internal research note 08, section A
6. [6] DXB Interact, off-plan projects in Jumeirah Village Circle (aggregator, vendor site) Vendor source. https://dxbinteract.com/dubai-offplan-project-prices/jumeirah-village-circle internal research note 08, section A
7. [7] Project data file dannye/jvc/sumo/svodka.json, block b. file time 2026-10-09 08:56
8. [8] Project data file dannye/jvc/seti/livnevka_svodka.json, block c. file time 2026-10-09 14:47
9. [9] Project data file dannye/jvc/pasport_dannyh.json, block a. file time 2026-10-09 06:27
10. [10] Project data file dannye/jvc/seti/voda_truby.geojson, block c. file time 2026-10-09 14:47
11. [11] Project data file dannye/jvc/seti/kanal_truby.geojson, block c. file time 2026-10-09 14:47
12. [12] Project data file dannye/jvc/seti/livnevka_truby.geojson, block c. file time 2026-10-09 14:47
13. [13] Project data file dannye/jvc/seti/niziny.geojson, block c. file time 2026-10-09 14:47
14. [14] Project data file dannye/jvc/seti/elektro_podstancii.geojson, block c. file time 2026-10-09 14:48
15. [15] Project data file dannye/jvc/seti/stroyki_nagruzka.geojson, block c. file time 2026-10-09 14:48
16. [16] Project data file dannye/jvc/bezopasnost/doezd_zdaniya.geojson, block c. file time 2026-10-09 14:48
17. [17] Project data file dannye/jvc/bezopasnost/kamery_tipovye.geojson, block c. file time 2026-10-09 14:48
18. [18] Project data file dannye/jvc/bezopasnost/stancii.geojson, block c. file time 2026-10-09 14:48
19. [19] Project data file dannye/jvc/ekran/dvizhenie_baza.geojson, block b. file time 2026-10-09 14:50
20. [20] Project data file dannye/jvc/README.md, block a. file time 2026-10-09 06:27
21. [21] Project data file dannye/jvc/relief.LICENZIYA.txt, block a. file time 2026-10-09 06:27
22. [22] Dubai Pulse (Dubai Data Establishment) Open Data Licence, Internet Archive copy of 07.07.2022, as analysed in the block (a) data passport, section 6.
23. [23] Project data file dannye/jvc/ostanovki.geojson, block a. file time 2026-10-09 06:27
24. [24] Project data file dannye/jvc/proisshestviya.geojson, block a. file time 2026-10-09 06:27
25. [25] Block (a) open issues, available on request. file time 2026-10-09 06:28
26. [26] Internal research note 04, Dubai standards in numbers, available on request.
27. [27] DEWA, Water Transmission Planning Guidelines for Development Projects, update 2023 (read via Internet Archive). https://web.archive.org/web/2026id_/https://dewa.gov.ae/-/media/WT-Planning-Guidelines-for-Dev-Proj--Update-2023.ashx internal research note 04, section 3.2
28. [28] Dubai Municipality, Sewerage Design Guidelines v2.0, approved February 2024, marked Open Data by DM. https://dmpmedia.dm.gov.ae/uploads/2025/01/comp-DM_Sewerage-Guidelines-F.24.01.25.pdf internal research note 04, section 3.2
29. [29] Dubai Municipality, Stormwater Design Guidelines v2.0 (DM-WSA-SRPD-SW1), July 2024, marked Open Data by DM. https://dmpmedia.dm.gov.ae/uploads/2025/01/DM_Stormwater-Guidelines-F.24.01.25.pdf internal research note 04, section 3.3
30. [30] DEWA Regulations for Electrical Installations, 2017 edition (read via Internet Archive). https://web.archive.org/web/2026id_/https://dewa.gov.ae/-/media/DEWA_Regulations_for_Electrical_Installations_2017_Edition.ashx internal research note 04, section 3.1
31. [31] DEWA Annual Statistics Booklet 2025 (read via Internet Archive). https://web.archive.org/web/2026id_/https://dewa.gov.ae/-/media/Files/About-DEWA/Annual-Statistics/DEWA_Annual_Statistics_Booklet_2025_EN.ashx internal research note 04, section 3.1
32. [32] Administrative Resolution No. 603 of 2021 (Implementing Bylaw of Law No. 6 of 2006), Dubai Legislation Portal. https://dlp.dubai.gov.ae/Legislation%20Reference/2021/Administrative%20Resolution%20No.%20(603)%20of%202021%20Issuing%20the%20Implementing%20Bylaw%20of%20Law%20No.%20(6)%20of%202006.html internal research note 04, section 3.4
33. [33] Dubai Building Code, 2021 Edition (Decree No. 45 of 2021). https://dmpmedia.dm.gov.ae/uploads/2021/12/Dubai%20Building%20Code_English_2021%20Edition_compressed.pdf internal research note 04, section 3.1, 3.2, 3.5
34. [34] Search results, 2025, without an opened primary source (AGBI 01.2025 returned 403) Not verified. block (a) data passport, section 3
35. [35] Project decisions of 09.10.2026, internal, available on request.
36. [36] Project data file geroi/assety.csv, block e1. file time 2026-10-09 13:11
37. [37] Project data file blender/materialy.csv, block e1. file time 2026-10-09 15:24
38. [38] Project data file ekran/public/teksturi/LICENZII.txt, block d. file time 2026-10-09 05:50
39. [39] Project data file dannye/jvc/sumo/jvc.net.json, block b. file time 2026-10-09 07:37
40. [40] Project data file dannye/jvc/ekran/dvizhenie_baza-m1-t025.geojson, block b. file time 2026-10-09 14:50
41. [41] Project data file dannye/jvc/ekran/dvizhenie_baza-m1.geojson, block b. file time 2026-10-09 14:50
42. [42] Project data file dannye/jvc/ekran/dvizhenie_baza-x2.geojson, block b. file time 2026-10-09 14:50
43. [43] Project data file dannye/jvc/ekran/dvizhenie_baza-vecher.geojson, block b. file time 2026-10-09 14:50
44. [44] Project data file dannye/jvc/ekran/dvizhenie_baza-m1-vecher.geojson, block b. file time 2026-10-09 14:50
45. [45] Project data file dannye/jvc/ekran/dvizhenie_2029-niz-p.geojson, block b. file time 2026-10-09 14:49
46. [46] Project data file dannye/jvc/ekran/dvizhenie_2029-verh-p.geojson, block b. file time 2026-10-09 14:50
47. [47] Project data file dannye/jvc/ekran/dvizhenie_2029-niz.geojson, block b. file time 2026-10-09 14:49
48. [48] Project data file dannye/jvc/ekran/dvizhenie_2029-verh.geojson, block b. file time 2026-10-09 14:50
49. [49] Project data file dannye/jvc/ekran/dvizhenie_16-04-2024.geojson, block b. file time 2026-10-09 14:49
50. [50] Project data file dannye/jvc/ekran/dvizhenie_razvyazki-rta.geojson, block b. file time 2026-10-09 14:50
51. [51] Project data file dannye/jvc/ekran/dvizhenie_2029-niz-p-vecher.geojson, block b. file time 2026-10-09 14:49
52. [52] Project data file dannye/jvc/ekran/dvizhenie_2029-niz-stress-vecher.geojson, block b. file time 2026-10-09 14:50
53. [53] Project data file dannye/jvc/ekran/dvizhenie_2029-niz-stress.geojson, block b. file time 2026-10-09 14:49
54. [54] Project data file dannye/jvc/ekran/dvizhenie_2029-niz-vecher.geojson, block b. file time 2026-10-09 14:50
55. [55] Project data file dannye/jvc/ekran/dvizhenie_2029-verh-stress.geojson, block b. file time 2026-10-09 14:50
56. [56] Project data file dannye/jvc/ekran/dvizhenie_2029-verh-vecher.geojson, block b. file time 2026-10-09 14:50
57. [57] Project data file dannye/jvc/ekran/dvizhenie_baza-m1-t025-vecher.geojson, block b. file time 2026-10-09 14:50
58. [58] Project data file dannye/jvc/ekran/dvizhenie_verh-125k.geojson, block b. file time 2026-10-09 14:50
59. [59] Block (b) traffic model report, available on request. file time 2026-10-09 15:07
60. [60] Dubai Media Office, RTA achieves completion of Al Khail Road improvement project, 21.10.2024. https://mediaoffice.ae/en/news/2024/october/21-10/rta-achieves-completion-of-al-khail-road internal research note 01, section 3.3
61. [61] Internal research note 03, Traffic, available on request.
62. [62] Hickert et al., arXiv 2608.19642: matching aggregate flows does not prove correct behaviour parameters. https://arxiv.org/pdf/2608.19642 internal research note 03, section 3.4
63. [63] Project data file dannye/jvc/sumo/sluzhba/zamer.json, block b. file time 2026-10-09 15:18
64. [64] Project data file dannye/jvc/sumo/sluzhba/ryad_etazhnosti.json, block b. file time 2026-10-09 15:17
65. [65] Project data file dannye/jvc/sumo/scenarii/sluzhba-baza/kesh/bashnya_71824a89ec594e4f.json, block b. file time 2026-10-09 15:03
66. [66] Project data file dannye/jvc/sumo/scenarii/sluzhba-baza-m1-t025/kesh/bashnya_238fc66da52377a0.json, block b. file time 2026-10-09 15:07
67. [67] Project data file dannye/jvc/sumo/scenarii/sluzhba-baza-m1-t025/kesh/bashnya_71824a89ec594e4f.json, block b. file time 2026-10-09 15:04
68. [68] Project data file dannye/jvc/seti/svodka_voda.json, block c. file time 2026-10-09 14:47
69. [69] Project data file dannye/jvc/seti/dopushcheniya_voda.md, block c. file time 2026-10-09 14:47
70. [70] Project data file dannye/jvc/seti/svodka_elektro.json, block c. file time 2026-10-09 14:48
71. [71] Internal research note 07, Water of April 2024, available on request.
72. [72] Project data file dannye/jvc/seti/dopushcheniya_livnevka.md, block c. file time 2026-10-09 14:47
73. [73] Project data file dannye/jvc/seti/svodka_livnevka.json, block c. file time 2026-10-09 14:47
74. [74] Project data file dannye/jvc/seti/dopushcheniya_elektro.md, block c. file time 2026-10-09 14:48
75. [75] Project data file dannye/jvc/bezopasnost/dopushcheniya_doezd.md, block c. file time 2026-10-09 14:48
76. [76] Project data file dannye/jvc/bezopasnost/svodka_doezd.json, block c. file time 2026-10-09 14:48
77. [77] Project data file dannye/jvc/bezopasnost/svodka_kamery.json, block c. file time 2026-10-09 14:48
78. [78] Project data file dannye/jvc/seti/svodka_stroyki.json, block c. file time 2026-10-09 14:48
79. [79] Project data file dannye/jvc/ekran/stroyki_ocheredi.json, block b. file time 2026-10-09 15:18
80. [80] Project data file dannye/jvc/blender/kadry.json, block e1. file time 2026-10-09 15:29
81. [81] Blender Open Data benchmark, Blender 5.2.0, median scores (RTX 5090 OptiX; Apple M4 Pro 20-core GPU Metal), queried 09.10.2026 by block (e1). https://opendata.blender.org/
82. [82] Block (e1) render time estimate, available on request. file time 2026-10-09 08:27
83. [83] Project data file dannye/jvc/ekran/vyezdy_baza.geojson, block b. file time 2026-10-09 14:50
84. [84] Dubai Media Office, RTA, Hessa Street widened to 4 lanes each way between Sheikh Zayed Road and Al Khail Road, 8,000 to 16,000 vehicles per hour, 19.04.2026 (opened 09.10.2026 by block b). https://mediaoffice.ae/en/news/2026/april/19-04/rta block (b) traffic model report, section 5
85. [85] Dubai Media Office, RTA launches traffic enhancements in 40 locations, 08.06.2025. https://www.mediaoffice.ae/en/news/2025/june/08-06/rta-launches-traffic-enhancements-in-40-locations internal research note 01, section 3.3
86. [86] Dubai Media Office, RTA signs AED 6 billion agreement with Dubai Holding, 02.03.2025. https://mediaoffice.ae/en/news/2025/march/02-03/rta-signs-aed6-billion-agreement-with-dubai-holding internal research note 01, section 3.3
87. [87] JBA Risk Management, Looking back at the Dubai floods 2024 (insurance analytics vendor; quotes AP) Vendor source. https://www.jbarisk.com/knowledge-hub/insights/looking-back-at-the-dubai-floods-2024/ internal research note 07, section 3.1
88. [88] Press reports of more than 142 mm in Dubai within 24 hours (bne IntelliNews; CBC). https://www.intellinews.com/dubai-airport-city-and-roads-still-underwater-from-historic-floods-321480/ internal research note 04, section 3.3
89. [89] ECMWF Newsletter 180, Unprecedented rainfall in the United Arab Emirates. https://www.ecmwf.int/en/newsletter/180/news/unprecedented-rainfall-united-arab-emirates internal research note 07, section 3.1
90. [90] NASA Earth Observatory, Deluge in the United Arab Emirates. https://science.nasa.gov/earth/earth-observatory/deluge-in-the-united-arab-emirates-152703/ internal research note 07, section 3.1
91. [91] Wikipedia, 2024 United Arab Emirates floods (cites Khaleej Times). https://en.wikipedia.org/wiki/2024_United_Arab_Emirates_floods internal research note 07, section 3.1
92. [92] JBA Risk Management, Dubai floods April 2024, event response (vendor) Vendor source. https://www.jbarisk.com/knowledge-hub/event-response/dubai-floods-april-2024/ internal research note 07, section 3.1
93. [93] Zayed University (Hong et al.), PlanetScope flood mapping of Dubai, April 2024; ISPRS Archives XLVIII-G-2025/605 (CC BY 4.0). https://zuscholars.zu.ac.ae/works/7863 internal research note 07, section 3.2
94. [94] CTBUH Skyscraper Center, FIVE Jumeirah Village (61 floors, 277 m, gross floor area 151,606 m2), viewed 09.10.2026. https://www.skyscrapercenter.com/building/five-jumeirah-village-dubai/17450 block (a) data passport, section 3a
95. [95] Project history, commit b8cbc1a (09.10.2026): block (a) floor area by CTBUH and the podium rule; block (a) report states the previous FIVE figure.
96. [96] Project history, commit a3e784a (09.10.2026): block (a) data passport before the floor-area recalculation.
97. [97] Project history, commit e94f40e (09.10.2026): block (b) baseline accepted with district multiplier 0.36 = 31,371 / 87,401.
98. [98] Block (b) traffic build log, internal, available on request.
99. [99] Block (b) traffic build log, available on request. file time 2026-10-09 15:18
100. [100] Block (b) traffic model report, internal, available on request.
101. [101] Eclipse SUMO documentation (O/D import, routeSampler, mesoscopic model, edgeData). https://sumo.dlr.de/docs/Tools/Turns.html internal research note 03, section 3.3, 3.4, 6