Differences

This shows you the differences between two versions of the page.

--- reference:system-architecture:addressing-data-model [2025/08/25 18:15] – ↷ Page moved from reference:addressing-data-model to reference:system-architecture:addressing-data-model runarbe
+++ reference:system-architecture:addressing-data-model [2025/08/25 18:21] (current) – [4. Foundational data] runarbe
@@ Line 1: / Line 1: @@
-====== Data model ======
+====== Addressing Data Model ======
 This page provides an overview of the data models underpinning the National Addressing System, including logical, relational, and distribution models. These models define how addressing data is structured, stored, and shared across systems.
@@ Line 7: / Line 7: @@
   * The distribution model specifies how data is synchronized and disseminated to consumers and external systems, supporting both centralized and decentralized implementations through standardized interfaces and APIs.
+===== 1. Logical data model =====
-===== Logical data model =====
+{{  :wiki:reference:data-model:logical.png?direct&800  |Logical data model}}
-{{ :wiki:reference:data-model:logical.png?1600&direct&recache |Logical data model}}
+===== 2. Relational data model =====
+The Production Data Model is primarily composed of a relational data model aimed at the maintenance of addressing features. This segment includes several tables, each serving specific functions. The StrSgmt table manages street segments, detailing the particular sections of streets. The SubAdr table deals with sub-addresses, which are subdivisions within larger address units. The AdrUnit table is used for address units, providing unique identifiers for each addressable entity. The Str table contains street IDs and their attributes, ensuring a comprehensive database of all streets. The Wlyt table represents Wilayat, which are administrative divisions in Oman, and the Gov table deals with the governorates, managing identities and attributes of higher-level divisions.
-===== Relational data model =====
+{{  :wiki:reference:data-model:relational_data_model.png?direct&800  |Relational realisation of logical addressing data model}}
-{{ :wiki:reference:data-model:relational_data_model.png?1600&direct&recache |Relational realisation of logical addressing data model}}
+===== 3. Distribution data model =====
+The Distribution Data Model is designed to provide simplified formats of address data for distribution purposes. It employs specific tables to manage this task: the AdrDist table and AdrDistExt table, which handle basic and extended distribution data respectively, and the StrDist table, which focuses on the distribution of street-related information.
-===== Distribution data model =====
+{{  :view_for_flat_distribution_data_model.svg?800  |Distribution data model}}
-{{ :view_for_flat_distribution_data_model.svg?1366&recache |Distribution data model}}
+===== 4. Foundational data =====
+Foundational data provides vital sources for identifying drivable road surfaces, which are then incorporated into street segments. It utilises several tables: the RoadCenterLine table represents the central lines of roads, important for identifying drivable surfaces. The Parcels table includes land parcel data, while the Master Plans table stores urban planning details. The Towns table is dedicated to the identification and characteristics of towns.
+  * Road center lines and edges (to be supplied by NSDI?)
+  * Parcels (to be supplied by MoHUP GIS)
+  * Buildings (to be supplied by NSDI?)
+  * Towns (to be supplied by MoHUP)
+  * Master Plans
+===== 5. Imagery and basemaps  =====
+Imagery and basemaps play a crucial role in the presentation and editing processes of address data. This section includes various datasets that serve as visual backdrops. The Basemap dataset provides fundamental map layers, while Satellite Imagery offers detailed aerial views. Web Map Providers supply additional digital map layers from external services, enhancing the overall usability and presentation of address data.