Lebanon

OpenStreetMap contains roughly 781.2 thousand buildings in this region. Based on AI-mapped estimates, this is approximately 68% of the total buildings.The average age of data for this region is 10 years ( Last edited 17 days ago ) and 28% buildings were added or updated in the last 6 months. Read about what this summary means : indicators , metrics This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['building'] IS NOT NULL Features may have these attributes: name name:en building building:levels building:materials addr:full addr:housenumber addr:street addr:city office source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap contains roughly 47.7 thousand km of roads in this region. Based on AI-mapped estimates, this is approximately 84 % of the total road length in the dataset region. The average age of data for the region is 10 years ( Last edited 17 days ago ) and 12% of roads were added or updated in the last 6 months. Read about what this summary means : indicators , metrics This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['highway'] IS NOT NULL Features may have these attributes: name name:en highway surface smoothness width lanes oneway bridge layer source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['railway'] IN ('rail','station') Features may have these attributes: name name:en railway ele operator:type layer addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['place'] IN ('isolated_dwelling', 'town', 'village', 'hamlet', 'city') OR tags['landuse'] IN ('residential') Features may have these attributes: name name:en place landuse population is_in source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['amenity'] IN ('mobile_money_agent','bureau_de_change','bank','microfinance','atm','sacco','money_transfer','post_office') Features may have these attributes: name name:en amenity operator network addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['healthcare'] IS NOT NULL OR tags['amenity'] IN ('doctors', 'dentist', 'clinic', 'hospital', 'pharmacy') Features may have these attributes: name name:en amenity building healthcare healthcare:speciality operator:type capacity:persons addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['amenity'] IN ('kindergarten', 'school', 'college', 'university') OR tags['building'] IN ('kindergarten', 'school', 'college', 'university') Features may have these attributes: name name:en amenity building operator:type capacity:persons addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['aeroway'] IS NOT NULL OR tags['building'] = 'aerodrome' OR tags['emergency:helipad'] IS NOT NULL OR tags['emergency'] = 'landing_site' Features may have these attributes: name name:en aeroway building emergency emergency:helipad operator:type capacity:persons addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['amenity'] = 'ferry_terminal' OR tags['building'] = 'ferry_terminal' OR tags['port'] IS NOT NULL Features may have these attributes: name name:en amenity building port operator:type addr:full addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['amenity'] IS NOT NULL OR tags['man_made'] IS NOT NULL OR tags['shop'] IS NOT NULL OR tags['tourism'] IS NOT NULL Features may have these attributes: name name:en amenity man_made shop tourism opening_hours beds rooms addr:full addr:housenumber addr:street addr:city source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This theme includes all OpenStreetMap features in this area matching ( Learn what tags means here ) : tags['waterway'] IS NOT NULL OR tags['water'] IS NOT NULL OR tags['natural'] IN ('water','wetland','bay') Features may have these attributes: name name:en waterway covered width depth layer blockage tunnel natural water source name:ar This dataset is one of many OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

This dataset shows the list of operating health facilities. Attributes included: Name,Nature of Facility, Activities, Lat, Long

We use an anonymized snapshot of all active Facebook users and their friendship networks to measure the intensity of connectedness between locations. The Social Connectedness Index (SCI) is a measure of the social connectedness between different geographies. Specifically, it measures the relative probability that two individuals across two locations are friends with each other on Facebook. Details on the underlying data and the construction of the index are provided in the “Facebook Social Connectedness Index - Data Notes.pdf” file. Please also see https://dataforgood.facebook.com/ as well as the associated research paper “Social Connectedness: Measurement, Determinants and Effects,” published in the Journal of Economic Perspectives (https://www.aeaweb.org/articles?id=10.1257/jep.32.3.259). Region identifiers are taken from GADM v2.8 https://gadm.org/download_country_v2.html. Future versions will update IDs to be compatible with the newest GADM version.

Open and free data for assessing the human presence on the planet. The Global Human Settlement Layer (GHSL) project produces global spatial information, evidence-based analytics, and knowledge describing the human presence on the planet. The GHSL relies on the design and implementation of spatial data processing technologies that allow automatic data analytics and information extraction from large amounts of heterogeneous geospatial data including global, fine-scale satellite image data streams, census data, and crowd sourced or volunteered geographic information sources. The JRC, together with the Directorate-General for Regional and Urban Policy (DG REGIO) and Directorate-General for Defence Industry and Space (DG DEFIS) are working towards a regular and operational monitoring of global built-up and population based on the processing of Sentinel Earth Observation data produced by European Copernicus space program. In addition, the EU Agency for the Space Programme (EUSPA) undertakes activities related to user uptake of data, information and services.

Constrained estimates, total number of people per grid-cell. The dataset is available to download in Geotiff format at a resolution of 3 arc (approximately 100m at the equator). The projection is Geographic Coordinate System, WGS84. The units are number of people per pixel. The mapping approach is Random Forest-based dasymetric redistribution.  The difference between constrained and unconstrained you can read on this page: https://www.worldpop.org/methods/top_down_constrained_vs_unconstrained

Constrained estimates of total number of people per grid square broken down by gender and age groupings (including 0-1 and by 5-year up to 90+) for Lebanon, version v1. The dataset is available to download in Geotiff format at a resolution of 3 arc (approximately 100m at the equator). The projection is Geographic Coordinate System, WGS84. The units are estimated number of male, female or both in each age group per grid square.  The difference between constrained and unconstrained you can read on this page: https://www.worldpop.org/methods/top_down_constrained_vs_unconstrained File Descriptions: {iso} {gender} {age group} {year} {type} {resolution}.tif iso Three-letter country code gender m = male, f= female, t = both genders age group 00 = age group 0 to 12 months 01 = age group 1 to 4 years 05 = age group 5 to 9 years 90 = age 90 years and over year Year that the population represents type CN = Constrained , UC= Unconstrained resolution Resolution of the data e.q. 100m = 3 arc (approximately 100m at the equator)

This dataset provides detailed information on road surfaces from OpenStreetMap (OSM) data, distinguishing between **paved** and **unpaved** surfaces across the region. This information is based on road surface prediction derived from hybrid deep learning approach. For more information on Methods, refer to the [paper](http://arxiv.org/abs/2410.19874) Roughly 0.0517 million km of roads are mapped in OSM in this region. Based on AI-mapped estimates the share of paved and unpaved roads is approximately 0.0099 and 0.002 (in million kms), corressponding to 19.1793% and 3.8679% respectively of the total road length in the dataset region. 0.0398 million km or 76.9528% of road surface information is missing in OSM. In order to fill this gap, Mapillary derived road surface dataset provides an additional 0.0001 million km of information (corressponding to 0.2769% of total missing information on road surface) It is intended for use in transportation planning, infrastructure analysis, climate emissions and geographic information system (GIS) applications. This dataset provides comprehensive information on road and urban area features, including location, surface quality, and classification metadata. This dataset includes attributes from OpenStreetMap (OSM) data, AI predictions for road surface, and urban classifications. AI features: pred_class: Model-predicted class for the road surface, with values "paved" or "unpaved." pred_label: Binary label associated with pred_class (0 = paved, 1 = unpaved). osm_surface_class: Classification of the surface type from OSM, categorized as "paved" or "unpaved." combined_surface_osm_priority: Surface classification combining pred_label and surface(OSM) while prioritizing the OSM surface tag, classified as "paved" or "unpaved." combined_surface_DL_priority: Surface classification combining pred_label and surface(OSM) while prioritizing DL prediction pred_label, classified as "paved" or "unpaved." n_of_predictions_used: Number of predictions used for the feature length estimation. predicted_length: Predicted length based on the DL model’s estimations, in meters. DL_mean_timestamp: Mean timestamp of the predictions used, for comparison. OSM features may have these attributes(Learn what tags mean here): name: Name of the feature, if available in OSM. name:en: Name of the feature in English, if available in OSM. name:* (in local language): Name of the feature in the local official language, where available. highway: Road classification based on OSM tags (e.g., residential, motorway, footway). surface: Description of the surface material of the road (e.g., asphalt, gravel, dirt). smoothness: Assessment of surface smoothness (e.g., excellent, good, intermediate, bad). width: Width of the road, where available. lanes: Number of lanes on the road. oneway: Indicates if the road is one-way (yes or no). bridge: Specifies if the feature is a bridge (yes or no). layer: Indicates the layer of the feature in cases where multiple features are stacked (e.g., bridges, tunnels). source: Source of the data, indicating the origin or authority of specific attributes. Urban classification features may have these attributes: continent: The continent where the data point is located (e.g., Europe, Asia). country_iso_a2: The ISO Alpha-2 code representing the country (e.g., "US" for the United States). urban: Binary indicator for urban areas based on the GHSU Urban Layer 2019. (0 = rural, 1 = urban) urban_area: Name of the urban area or city where the data point is located. osm_id: Unique identifier assigned by OpenStreetMap (OSM) to each feature. osm_type: Type of OSM element (e.g., node, way, relation). The data originates from OpenStreetMap (OSM) and is augmented with model predictions using images downloaded from Mapillary in combination with the GHSU Global Human Settlement Urban Layer 2019 and AFRICAPOLIS2020 urban layer. This dataset is one of many HeiGIT exports on HDX. See the HeiGIT website for more information. We are looking forward to hearing about your use-case! Feel free to reach out to us and tell us about your research at communications@heigit.org – we would be happy to amplify your work.

Lebanon administrative level 0-3 edge-matched gazetteer and boundary files. SEE CAVEATS Live edge-matched boundary geoservices for all edge-matched locations are available in this "COD_External_Edgematch" catalogue. COD-EM datasets do not replace the authoritative COD-AB available here; however COD-EM datasets may be preferred for cartographic purposes. See caveats. These layers are suitable for database or GIS linkage to the Lebanon - Subnational Population Statistics tables using the ADM0, ADM1, ADM2, and ADM3_PCODE fields. Vetting and live service provision by Information Technology Outreach Services (ITOS) with funding from USAID.

Lebanon administrative level 4 (Beirut neighborhoods) boundary shapefile and geodatabase

Lebanon administrative level 0-3 boundaries (COD-AB) dataset. These administrative boundaries were established in: 2014 NOTE: Please see caveats pertaining to the P-coding system. This COD-AB was most recently reviewed for accuracy and necessary changes in November 2024. The COD-AB requires improvements. Sourced from Council for Development and Reconstruction (CDR) Live geoservices (provided by Information Technology Outreach Services (ITOS) with funding from USAID) are available for this COD-AB. Please see COD_External. (For any earlier versions please see here, here, and here.) Vetting, configuration, and geoservices provision by Information Technology Outreach Services (ITOS) with funding from USAID. There is no suitable population statistics dataset (COD-PS) for linkage to this COD-AB.. An edge-matched (COD-EM) version of this COD-AB is available on HDX here. Please see the COD Portal. Administrative level 1 contains 8 feature(s). The normal administrative level 1 feature type is ""Governorate (Mouhafaza)"". Administrative level 2 contains 26 feature(s). The normal administrative level 2 feature type is ""District (Kaza)"". Administrative level 3 contains 1,627 feature(s). The normal administrative level 3 feature type is ""Cadaster (Manatek Ikaria)"". Recommended cartographic projection: Asia South Albers Equal Area Conic This metadata was last updated on January 9, 2025.

This dataset contains the following administrative boundaries: ADM0, ADM1, ADM2. Produced and maintained since 2017, the geoBoundaries Global Database of Political Administrative Boundaries Database www.geoboundaries.org is an open license, standardized resource of boundaries (i.e., state, county) for every country in the world.

This dataset contains administrative polygons grouped by country (admin-0) with the following subdivisions according to Who's On First placetypes: - macroregion (admin-1 including region) - region (admin-2 including state, province, department, governorate) - macrocounty (admin-3 including arrondissement) - county (admin-4 including prefecture, sub-prefecture, regency, canton, commune) - localadmin (admin-5 including municipality, local government area, unitary authority, commune, suburb) The dataset also contains human settlement points and polygons for: - localities (city, town, and village) - neighbourhoods (borough, macrohood, neighbourhood, microhood) The dataset covers activities carried out by Who's On First (WOF) since 2015. Global administrative boundaries and human settlements are aggregated and standardized from hundreds of sources and available with an open CC-BY license. Who's On First data is updated on an as-need basis for individual places with annual sprints focused on improving specific countries or placetypes. Please refer to the README.md file for complete data source metadata. Refer to our blog post for explanation of field names. Data corrections can be proposed using Write Field, an web app for making quick data edits. You’ll need a Github.com account to login and propose edits, which are then reviewed by the Who's On First community using the Github pull request process. Approved changes are available for download within 24-hours. Please contact WOF admin about bulk edits.

Lebanon population density for 400m H3 hexagons. Built from Kontur Population: Global Population Density for 400m H3 Hexagons Vector H3 hexagons with population counts at 400m resolution. Fixed up fusion of GHSL, Facebook, Microsoft Buildings, Copernicus Global Land Service Land Cover, Land Information New Zealand, and OpenStreetMap data.

Lebanon administrative division with aggregated population. Built from Kontur Population: Global Population Density for 400m H3 Hexagons on top of OpenStreetMap administrative boundaries data. Enriched with HASC codes for regions taken from Wikidata. Global version of boundaries dataset: Kontur Boundaries: Global administrative division with aggregated population

Beirut port explosion operational zones UPDATED 9 October 2020: Enlarged zones with UN HABITAT socio-economic classification and the 3Km priority of the Flash Appeal priority radius added. Please see the methodology section in the metadata for further information. UPDATED 19 August 2020: 11 operational zones numbered 129 to 139 inclusive added to the Sinn El-Fil cadastre south of the origional set. Zones spreadsheet added. NOTES Users are referred to the compatible Beirut buildings footprints COD. The standard Administrative Boundary Common Operational Dataset (COD-AB) can be found at Lebanon - Subnational Administrative Boundaries.