The `obm_built_area_assessments` table contains built-up area estimations and automatic completeness assessments based on the output of the [obmgapanalysis](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/obmgapanalysis) software. These assessments may come from different source datasets. Currently, the completeness is calculated by comparing the buildings in the [OSM replication database](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/database-osmreplication) with the `GHS_BUILT_LDSMT_GLOBE_R2018A` (`source_id = 1`) dataset. More datasources may be added at a later stage.
The quadkeys to be processed with [obmgapanalysis](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/obmgapanalysis) were defined by running each country with the [quadtreegrid](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/quadtreegrid) package, which makes use of the country boundaries from the [GADM 3.6](https://gadm.org/) dataset. Quadkeys for which the built-up area is zero both in the [GHS_BUILT_LDSMT_GLOBE_R2018A](https://git.gfz-potsdam.de/dynamicexposure/datasources/-/tree/master/GHS_BUILT_LDSMT_GLOBE_R2018A) dataset and the `osm_building_polygons` table of the [OSM replication database](https://git.gfz-potsdam.de/dynamicexposure/openbuildingmap/database-osmreplication) are not stored in `obm_built_area_assessments`.
The `GHS_config.yml` file contains the configuration used to process the quadtiles with the `GHS_BUILT_LDSMT_GLOBE_R2018A`. The most important aspects of it are the usage of all the possible built-up pixel values `[6, 5, 4, 3]`, which means that all construction epochs from GHS are considered together, as well as the integration with the OBM roads database, where all road lines are buffered by 4 meters to each side and then subtracted from the GHS areas.