Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::hasChildren($allow_links = true) should either be compatible with RecursiveDirectoryIterator::hasChildren(bool $allowLinks = false): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 61

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::rewind() should either be compatible with FilesystemIterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 39

Deprecated: Return type of Ai1wm_Recursive_Directory_Iterator::next() should either be compatible with DirectoryIterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/iterator/class-ai1wm-recursive-directory-iterator.php on line 46

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 51

Deprecated: Return type of Ai1wm_Recursive_Extension_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-extension-filter.php on line 41

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::getChildren() should either be compatible with RecursiveFilterIterator::getChildren(): ?RecursiveFilterIterator, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 67

Deprecated: Return type of Ai1wm_Recursive_Exclude_Filter::accept() should either be compatible with FilterIterator::accept(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/all-in-one-wp-migration/lib/vendor/servmask/filter/class-ai1wm-recursive-exclude-filter.php on line 43

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 395

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 387

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 381

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/form-tag.php on line 399

Deprecated: Return type of WPCF7_Validation::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/validation.php on line 78

Deprecated: Return type of WPCF7_Validation::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/validation.php on line 72

Deprecated: Return type of WPCF7_Validation::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/validation.php on line 59

Deprecated: Return type of WPCF7_Validation::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/contact-form-7/includes/validation.php on line 82

Warning: session_start(): Session cannot be started after headers have already been sent in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/themes/diar/functions.php on line 2

Deprecated: Optional parameter $id declared before required parameter $field is implicitly treated as a required parameter in /home/diarconsult/public_html/staging.diarconsult.com/wp-content/plugins/acf-gallery/includes/5-7/acf-gallery-field.php on line 304
Mainland Development | Diar Consult

Mainland Development

In May 2002, Abu Dhabi National Hotels Co. approached Diar Consult with a view to master planning a new waterfront development along the Mussafah canal. Diar Consult then collaborated with HHCP USA, which took the initial lead in the development of the concept master plan. Diar Consult prepared the detailed master plan and concept design of the individual components of the project. This was one of the earliest projects assigned through international partnering by Abu Dhabi National Hotels Co.

The master plan comprises a private residential community of 170 units (townhouses and villas), creating secure defined neighbourhoods structured around a cul-de-sac system. All the residents enjoy access to the connected linear parks and recreation areas of the development directly from their lots. A manmade internal water creek was introduced into the development to demarcate clearly the territory of the residential zone, separating it from the commercial and public zones; and to create a dramatic and organic integration of land and water bodies. The separately accessible public domain includes retail, a hypermarket and cineplex, a four-star hotel and boutique offices as well as a country club for the residents and the general public.

The project was cancelled in July 2005 due to a complex legal issue related to land ownership. However, it provided a recognised benchmark and standards for this client to build on for their subsequent projects.

  • Location: Mussafah, Abu Dhabi, UAE
  • Client: Abu Dhabi National Hotels Co.
  • Size: 3,410m2 site area, 27,200m2 BUA
  • Status: Concept design completed in 2003