BBM-STD-86-COORDINATES_AND_GEOREFERENCING-V0.2 | Office standard | 5 November 2026 | V0.2 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-11-04 | First issue: closes rows,,,,,,,,,,, (CRS content; §1.2 gap 5; §1.3 row "CRS & georeferencing register") + cross-doc pointer pass: register row ED-UAE-CRS cited; grid north, true north and grid convergence separated in R5, §4 and the record form; BEP MOB-03 named as the mobilisation check |
| V0.2 | 2026-11-05 | CRS values settled from primary sources: CRS-DXB required by the Dubai BIM Standard 1.4, no datum transformation for WGS 84 data, legacy grids and heights through DM services; CRS-AUH = EPSG:32640 / EPSG:32639 by zone, vertical Ras Ghumays EPSG:5843; §5 office default control-point tolerance |
1 Purpose ownership and scope#
Every project names its coordinate reference system (CRS), vertical datum and units before the first shared exchange, and every model and IFC export carries them. This standard is the CRS register and procedure. Survey acceptance, control evidence, transforms and civil modelling stay in BBM-STD-63; this standard supplies the CRS defaults, the IFC georeferencing rules, the Revit coordinate procedure and the project record form. The Manual §5 and §11, BEP §2.2 and §8.2, BBM-STD-64, BBM-STD-74, BBM-STD-77 and BBM-STD-81 cite the project record ID from this register instead of restating the CRS.
The survey lead owns the CRS decision with the competent surveyor; the coordinator implements it in the models; an independent checker verifies it (BBM-STD-63 §2). The authority requirement for the plot comes from the jurisdiction test in BBM-STD-85 §2. The authority's own survey or CAD/BIM submission guideline overrides the defaults below; an authority instruction that differs is recorded with its source.
2 CRS register (defaults)#
The edition and source-check record of these defaults is register row ED-UAE-CRS in BBM-STD-51 §3; this section holds the detail.
| Key | Jurisdiction | Horizontal CRS | Vertical datum | Units | Source and status | Checked |
|---|---|---|---|---|---|---|
| CRS-DXB | Dubai | DLTM, EPSG:3997 "WGS 84 / Dubai Local TM": Transverse Mercator, central meridian 55°20' E, scale factor 1, false easting 500000 m. Required for permit IFC by the Dubai BIM Standard 1.4 §4.1.2. Defined on WGS 84 (base CRS EPSG:4326): WGS 84 data needs no datum transformation. Legacy grids (Clarke 1880 / Nahrwan, e.g. EPSG:27040) are converted only through the DM Survey Department service "Request for Coordinates Transformation", never with a generic EPSG operation (EPSG:15953 states 5 m accuracy) | DMD (Dubai Municipality Datum, equal to the Port Rashid datum, 0.0 m); the Dubai BIM Standard calls it the DMD level. No EPSG vertical CRS exists: record the name "DMD (Port Rashid)" in full. GNSS ellipsoidal heights are converted through the DM "orthometric height conversion" service | Metres | Dubai BIM Standard 1.4 §4.1.2, §7.7; EPSG registry; DM Survey Department geodesy services | 2026-11-05 |
| CRS-AUH | Abu Dhabi | WGS 84 (ITRF2000, epoch 2000.0) / UTM: EPSG:32640 (zone 40N) for plots east of 54°E, EPSG:32639 (zone 39N) for plots west of 54°E. The zone is chosen from the plot location; never one emirate-wide code. The plot's ADM/DMT guideline overrides where it states otherwise | Ras Ghumays, vertical CRS EPSG:5843 (datum EPSG:1146), the official Abu Dhabi height reference | Metres | DMT / ITC Unified As-Built GeoSpatial Data Submission Standards §2.1, §3.5; ADM BIM Code of Practice §3.3 (BEP states datum, units, offsets, rotation and shared coordinates) | 2026-11-05 |
| CRS-OTH | Other emirates / outside UAE | The CRS stated by the appointment or the authority survey requirement, with EPSG code | As stated by the survey, with geoid model if used | Metres | Per project | Per project |
Do not assume every UAE site shares one CRS. An EPSG number, DWG insertion point or terrain image alone does not establish datum, axis order or height reference (BBM-STD-63 §1). Model length unit is millimetres; map and survey coordinates are metres; the conversion is stated explicitly (§4).
3 Revit coordinate procedure#
| Step | Action | Evidence |
|---|---|---|
| R1 | Accept the survey and control under BBM-STD-63 §1–§2 before any model is positioned | Survey acceptance ID |
| R2 | Create one shared site / coordination model. Leave the internal origin where it is; keep building geometry close to it, inside the working range of the qualified Revit build (BBM-STD-91) | Site model container ID |
| R3 | Set the Survey Point to a surveyed control point: its CRS easting, northing and height (metres in the CRS, entered in the model's units with the conversion recorded) | Control ID used, values entered |
| R4 | Set the Project Base Point at the agreed building reference (normally a grid intersection at the reference level). Record its shared coordinates and the angle to true north | PBP E/N/H and angle |
| R5 | Set true north (Manage › Location / Rotate True North) to the surveyed angle; project north stays aligned with the main grid. Keep three directions apart: project north (the grid), grid north (the CRS northing axis) and true north (geographic). Their difference at the site, the grid convergence, comes from the surveyor and is recorded; it is never assumed to be zero | Angle value and sign convention; grid convergence and its source |
| R6 | Publish shared coordinates from the site model to each discipline model (or each model acquires them from the site model) once; after that every link is placed "By Shared Coordinates" | Publish/acquire log; link placement setting |
| R7 | Lock the survey point, project base point and shared site. Moving either point is a controlled change (one ChangeID, BBM-STD-63 §6) | Lock state; change record |
| R8 | Export the test IFC (§4) and run the control-point check (§5) before the first shared exchange | Test export ID, check result |
Never move a shared origin or all geometry to hide a bad link. One coincident point does not reveal rotation, scale or mirroring; the §5 check does.
4 IFC georeferencing#
| Schema | Rule |
|---|---|
| IFC4 (4.0.2.1 Reference View, office default) and IFC 4.3 (by approval) | Export writes IfcProjectedCRS and IfcMapConversion. IfcProjectedCRS.Name = the EPSG identifier (e.g. "EPSG:3997"); GeodeticDatum, VerticalDatum, MapProjection, MapZone and MapUnit are filled where the Name does not define them. VerticalDatum carries the vertical datum name (e.g. "DMD (Port Rashid)") because it has no EPSG code. IfcMapConversion carries Eastings, Northings, OrthogonalHeight (the CRS position of the project's local origin), XAxisAbscissa and XAxisOrdinate (the direction of the local x-axis in the map plane, rotation θ = arctan(XAxisOrdinate / XAxisAbscissa)) and Scale |
| IFC2x3 (only where an appointment or authority profile requires it) | IFC2x3 has no IfcMapConversion. Write the same values as the property sets ePSet_MapConversion and ePSet_ProjectedCRS per the buildingSMART User Guide for Geo-referencing in IFC v2.0 (Jan 2020). Guidance and exporters differ on the host entity (IfcProject or IfcSite): use the host the receiver reads, proven by the test export |
| Authority submission | The schema and export setup stated by the authority (BBM-STD-85 §3); its georeferencing values must equal the project CRS record |
Rotation. XAxisAbscissa and XAxisOrdinate give the local x-axis against the CRS grid (easting and northing axes), so the rotation is measured from grid north, not true north. Derive it from the project-north-to-grid-north angle; where Revit holds only an angle to true north, correct it by the recorded grid convergence. The round trip (§5) proves the result.
Scale. Scale converts the project length unit to the map unit; if omitted it is 1.0. Set it so that a millimetre model lands on a metre CRS correctly, and prove it by the round trip: a result 1000 times off fails.
Exporter settings. The coordinate base of the IFC export is the shared coordinates. Where the qualified exporter build provides georeference settings (CRS / EPSG fields), fill them from the project record; where it does not, any post-processing tool is named with its version and the result re-checked. The export setup is a controlled release asset in BBM-STD-65.
Receiver check. Reopen the exported IFC in the named receiver and read back IfcProjectedCRS.Name, the IfcMapConversion values (or the IFC2x3 property sets) and the three control points. The declared EPSG code in the file must equal the project record (BEP mobilisation check MOB-03, before the first shared exchange).
5 Control-point check#
Use at least three well-distributed control points plus elevation and unit probes (re-affirms). The points spread across the site footprint; they are not the points used to fit the transform. For each point record: control ID, surveyed E/N/H and uncertainty, expected model value, value read in the native model, value read in the exported IFC, residual components and the criterion source. The elevation probe checks the vertical datum and height type; the unit probe checks that metres and millimetres are not confused. Office default acceptance: the native and IFC read-back of each control point equals the surveyed E/N/H within 10 mm horizontally and 10 mm vertically, or within the surveyor's stated control accuracy where that is coarser (recorded). A stricter appointment or authority value governs; the DM value for a Dubai plot is checked against the DM Survey Department control-coordinate certificate at project start and recorded in BEP §8.2 (rule-based). Survey evidence and decision tolerances stay in BBM-STD-63 §2. The receiving discipline repeats the check after any source, unit, north, link-placement or coordinate change. A failed point holds federation and every exchange that uses the frame (BBM-STD-64).
6 Per-project record form#
One record per project, ID CRS-<PROJ>-<rev>, held with the BEP §8.2 coordinate register and cited by every model, exchange and survey brief.
| Field | Content |
|---|---|
| Record ID / revision | CRS-<PROJ>-Rnn, change ID, date |
| Jurisdiction and authority source | Register key (CRS-DXB / CRS-AUH / CRS-OTH), authority guideline title/revision/URL, check date |
| Horizontal CRS | Name, EPSG code, projection and zone, axis order |
| Vertical datum | Name, EPSG code if any (Abu Dhabi EPSG:5843; Dubai DMD has none), height type (orthometric / ellipsoidal / local), geoid model if used |
| Transformation | "none: WGS 84 based" (EPSG:3997, EPSG:32639/32640 with WGS 84 data) or the transformation used (DM service reference, EPSG operation code or survey method) and its direction |
| Units | Map unit (m); model unit (mm); conversion factor; IFC Scale value |
| Survey point | Control ID and E/N/H |
| Project base point | Location description, E/N/H, angle to true north (value and sign) |
| North directions | Project-north-to-grid-north angle; grid convergence at the site and its source; true-north check result (tested separately from grid north) |
| Local-to-map transform | Eastings, Northings, OrthogonalHeight, XAxisAbscissa, XAxisOrdinate, Scale |
| Control points | At least three IDs with E/N/H, uncertainty and source authority |
| IFC profile | Schema, export setup ID/hash, IfcMapConversion or IFC2x3 property-set host |
| Check results | Native and IFC residuals per point, elevation/unit probe result, checker, date, decision |
| Sharing | Security classification of the coordinate data (BBM-STD-87) |
References#
- EPSG:3997 WGS 84 / Dubai Local TM: https://epsg.io/3997, checked 2026-11-04.
- DMD vertical datum (DM authors, FIG 2011): https://www.fig.net/pub/fig2011/papers/ts08j/ts08j_gopi_alkhatibi_et_al_5058.pdf, checked 2026-11-04.
- Ras Ghumays vertical datum, EPSG datum 1146: https://epsg.io/1146-datum, checked 2026-11-04; Abu Dhabi geoid context: https://fig.net/resources/proceedings/fig_proceedings/fig2020/ppt/ts03g/TS03G_carme_weyer_et_al_10296_ppt.pdf, checked 2026-11-04.
- Abu Dhabi Emirate Spatial Reference System: DMT / ITC Unified As-Built GeoSpatial Data Submission Standards §2.1, §3.5, https://admobility.gov.ae/services/-/media/As-Built-Data-Submission-Standards.pdf; Ras Ghumays height EPSG:5843, https://epsg.io/5843, checked 2026-11-05.
- Dubai BIM Standard 1.4 §4.1.2 (EPSG:3997) and §7.7 (DMD level): https://api.buildindubai.gov.ae/assets/BIM/Documents/DubaiBIMStandards.zip; DM Survey Department services (coordinate transformation, orthometric height conversion): https://www.dm.gov.ae/survey-department/geodesy; legacy grid EPSG:27040 transformation list: https://epsg.io/27040, checked 2026-11-05.
- Control-point accuracy figure 10 mm + 20 ppm: DIFC Registrar, Directives for the Preparation of Survey Plans §3.4.3, https://assets.difc.com/v1/media/edge/images/dubaiintern0078-difcexperie96c5-production-3253/media/project/difcexperiences/difc/difcwebsite/documents/registrars-and-commissioners/registrar-of-real-property/registrar-of-field-property-directives/directives_for_the_preparation_of_survey_plans_in_difc.pdf, checked 2026-11-05.
- ADM BIM Code of Practice, Oct 2020, §3.3: https://www.dmt.gov.ae/adm/-/media/Project/DMT/ADM/E-Library/0001-Jan-2022-Doc/ADM-BIM-005Code-of-Practice.pdf, checked 2026-11-04.
- ISO 16739-1:2024 (IFC 4.3.2.0): https://www.iso.org/standard/84123.html; IFC 4.3 entity definitions IfcMapConversion and IfcProjectedCRS (buildingSMART development source): https://github.com/buildingSMART/IFC4.3.x-development, checked 2026-11-04.
- buildingSMART User Guide for Geo-referencing in IFC v2.0 (Jan 2020), use-case page: https://ucm.buildingsmart.org/use-case-details/2047/en (download needs registration), checked 2026-11-04.
- Revit IFC exporter releases: https://github.com/Autodesk/revit-ifc/releases, checked 2026-11-04; Autodesk shared coordinates: https://www.autodesk.com/support/technical/article/caas/tsarticles/ts/3yOsIKv9VWhk2SeSUREOEI.html.
- Office: BBM-STD-63, BBM-STD-85, BEP §8.2; settled decisions,,,,.