GIS Data
Submission
Guidelines
ACUD – 001 REV 01 00. July 2025
Purpose & Scope
The purpose of this document is to define the standards and procedures for collecting and
submitting GIS as-built data for various types of real estate projects. This includes data related to
basemaps, buildings, infrastructure utilities, and smart services. The collected data will support the
effective management, operation, and facility management of the projects and ensure integration
with the centralized GIS platform.
Note: All general requirements or recommendations mentioned are provided as examples or samples based on
recurring issues observed in different projects, and they do not cover all possible issues or requirements.
GIS General Requirements
1
All master plan components shall be submitted in GIS format with all related
attribute data.
All infrastructure networks with related components and available attribute
data mentioned in as built shall be submitted in GIS format with the correct
2 connectivity roles and geometric network (when building a geometric
network, the contractor should specify the topological relationships
between its features).
3
All GIS layers must be organized in Databases according to the disciplines
and follow the ACUD GIS Data model.
4 Delivered GIS data shall be in the 3D format (vertices include Z values).
GIS General Requirements
Only dataset features need to be filled in; all other data are just
specifications or lookups that you must use to fill in any related data fields.
5 Note: If the used value is not present in the lookups or specifications, you
can fill in the necessary feature fields with it by adding it to the specifications
or lookups with a new ID.
Any feature class ended with “table” in the datasets should be filled with
attribute data only if exist such as:
➢ “status_table” feature class in “base” database which should be filled
6 with the executive status of the project to be delivered every quarter.
➢ “us_telecom_RFI_coordinates_table” feature class in “telecom” database
which should be filled with any update or change between as-built
coordinates and designs or shop drawings.
GIS General Requirements
7
All submitted GIS data must use the Egypt Red Belt 1907 coordinate system
and projection.
8
QA/ QC shall be applied to all GIS Layers as per GIS topology rules for every
geometry type (check attached examples of the topology rules).
9 Data Units must be in Meters.
10 Building footprint must have building height as an attribute value.
11
Necessary attribute data shall be included in the feature class table and not
in separate files or tables (depth, materials, type, land use, etc.).
GIS General Requirements
All surveying data or bathymetry data (images, Points Cloud, DTM, DSM, CAD,
Contours, etc.) should be submitted in GIS format (TIFF, LAS Files, Feature
12 classes) and the images, DTM, DSM, should be mosaiced as one Tile, and in
case the size was huge, it can be divided to few tiles based on ACUD
instructions.
13 The date format must be MM/DD/YYYY for all the date fields in all GIS layers.
Any GIS submission must be aligned with the most updated version of the
14 ACUD GIS data model with the ability to add new (layers, fields, lookups) and
all attribute data which is available in approved submittals.
GIS General Requirements
It’s not acceptable to make any changes to the ACUD-sent GIS data model,
including the names of databases, datasets, feature classes, fields, and
lookups. The data supplier may add feature classes, fields and lookups in the
template file but may not delete any of them. Any added records or changes
15 to the file structures such are feature classes, fields and lookups must be
fully documented and added attribute column change must be supported by
a ACUD Transmittal Form, that fully documents the recorded changes. (If you
have any additional layer, you should request ACUD GIS team before adding
this layer)
16
Field data values should have a well-defined name like , special characters (
_, %, etc.) are not allowed.
GIS General Requirements
17
Any GIS layer must be within a dataset, and it is not acceptable to have GIS layers outside the
datasets they belong to.
18
The “source data” folder must include all the files ( CAD/Civil 3D/ Revit , PDF etc.) that have been
used as a source to generate the GIS layers.
All UUID (Universally Unique Identifier) fields must be generated and correctly populated in the GIS
database for each feature to ensure unique identification and traceability.
19 Reference:
[Link]
similar-to-gl-000011677
Following fields shall be configured in editor tracking to record the creation and editing of the
20 attribute:
created_date - created_user - last_edited_user - last_edited_date
GIS General Requirements
For all utility network features, the fields spoke start (start node) and spoke end (end node) are
mandatory and must be filled to define the connectivity between network elements and support
topological integrity.
21
GIS General Requirements
Any GIS deliverables must include the following;
SI No. Submission Description
1 GIS DB Includes all information (attribute and
geographical data) available in an approved
format (CAD, Revit, Civil3D, etc.) and in line with
the NEOM GIS data model.
22
2 GIS Data Source folder Includes all approved files (CAD, Revit, Civil3D,
etc.) and data used to create the GIS database.
3 GIS Data Submission Form An updated Data Submission Form must be
provided with any GIS submissions.
4 GIS Transmittal Form An updated GIS Transmittal Form must be
provided with any GIS submissions.
Quality Assurance Checklist
It is important to check all data before submission. Below are a series of checks that can be used to
ensure data generated are correct.
Attributes
1
Values once sorted, both
2
ascending and descending,
shall contain no outliers, null
Where a unique ID has 3
values, or non-uniform values,
been provided, it shall be
unless already justified in the 4
validated to be unique Attribute values have
remark field.
and not duplicated. been verified for out of
logical range. There shall be no
records with missing
spatial data.
Quality Assurance Checklist
It is important to check all data before submission. Below are a series of checks that can be used to
ensure data generated are correct.
Attributes
5
6 Values of each variable
mapped are visually
There shall be consistent with the
7
consistency in the spatial distribution
provided attributes, expected.
Attributes have been including spelling and
checked for non-standard case sensitivity.
values containing special
characters such as !-@_#.
Quality Assurance Checklist
It is important to check all data before submission. Below are a series of checks that can be used to
ensure data generated are correct.
Spatial Data
1
The data do not intersect with
any other data features except
2
where it makes sense.
Visually, no pattern of
“holes” exists in the data. 3
Acceptable format (ESRI
Geodatabase format-
Geopackage for open source).
Quality Assurance Checklist
It is important to check all data before submission. Below are a series of checks that can be used to
ensure data generated are correct.
Spatial Data
4
5 The data are in a valid
geographical reference
The data do not intersect system.
6
with itself, except where
it makes sense.
The data does not contain
features that are spatially
out of context.
Examples of spatial Quality Recommendations
GIS Geodatabase Topology Rules
Examples of spatial Quality Recommendations
Examples of spatial Quality Recommendations
Examples of spatial Quality Recommendations