Lebanon - Subnational Edge-matched Administrative Boundaries

  • COD+
  • 10+ Downloads
  • This dataset updates: Every year

Downloads

Related Showcases

There are no showcases for this dataset.


Export metadata for this dataset: JSON | CSV

Source Council for Development and Reconstruction (CDR) and ITOS
Contributor OCHA Field Information Services Section (FISS)
Time Period of the Dataset [?] June 20, 2017-December 03, 2024 ... More
Modified [?] 18 November 2024
Dataset Added on HDX [?] 18 November 2024 Less
Expected Update Frequency Every year
Location
Visibility
Public
License Creative Commons Attribution for Intergovernmental Organisations
Methodology

Adapted by ITOS from the Lebanon - Subnational Administrative Boundaries to fit the UNGSS international boundary.
Caveats / Comments

The edge-matched layers are subject to the following potential limitations:

Where countries border each other, one or even both boundaries may be less accurate than the original, definitive boundaries. The UN Geospatial Hub boundary is generally of lower quality than the definitive COD-AB layers.

Peripheral polygon feature shapes and the relationship of their areas to those of their internal neighbouring features may be distorted, while internal features are untouched.

Peripheral polygon features may artificially appear to touch different, incorrect features belonging the same country.

One of the administrative level 3 features called "Litige", in this case [54001] in administrative level 2 feature "El Hermel" [LB22], in administrative level 1 feature "Baalbek-El Hermel" [LB8] falls outside the UNGIS boundary used to define the edge-matched borders. Thus there are 1,627 COD-AB features but only 1,626 COD-EM features.

The Lebanon administrative level 1 P-codes are based on the post-2014 structure of eight features, including "Akkar" [LB7] and "Baalbek-Hermel" [LB8] governorates. The administrative level 2 P-codes are based on the previous six-feature structure, thus maintaining a P-code nesting conflict.

Furthermore the administrative level 3 features have purely numeric P-codes which follow the administrative level 1 P-code squence but with different numeric values.
Tags
File Format