Disclaimer: All users agree to the following disclaimer by virtue of downloading any City of Lebanon data. The City's infrastructure records, drawings, and other documents have been gathered over many decades, using differing standards for quality control, documentation, and verification. While this product is for informational usage only, it may not be suitable for legal, engineering, or surveying purposes. Prior to making any property purchases or other investments based in full or in part upon the material provided, it is specifically advised that you independently verify the information contained within our records.If misleading or inaccurate information is brought to the City's attention, a reasonable effort will be made to fix or remove it. Such concerns should be addressed by email to gis@ci.lebanon.or.us.

The TIGER/Line shapefiles and related database files (.dbf) are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. The All Roads Shapefile includes all features within the MTDB Super Class "Road/Path Features" distinguished where the MAF/TIGER Feature Classification Code (MTFCC) for the feature in MTDB that begins with "S". This includes all primary, secondary, local neighborhood, and rural roads, city streets, vehicular trails (4wd), ramps, service drives, alleys, parking lot roads, private roads for service vehicles (logging, oil fields, ranches, etc.), bike paths or trails, bridle/horse paths, walkways/pedestrian trails, and stairways.

Disclaimer: All users agree to the following disclaimer by virtue of downloading any City of Lebanon data. The City's infrastructure records, drawings, and other documents have been gathered over many decades, using differing standards for quality control, documentation, and verification. While this product is for informational usage only, it may not be suitable for legal, engineering, or surveying purposes. Prior to making any property purchases or other investments based in full or in part upon the material provided, it is specifically advised that you independently verify the information contained within our records.If misleading or inaccurate information is brought to the City's attention, a reasonable effort will be made to fix or remove it. Such concerns should be addressed by email to gis@ci.lebanon.or.us.

The data contains the following:- RATM raster- Watersheds shapefile

This feature service is available through CT ECO, a partnership between UConn CLEAR and CT DEEP. It is also available as a map service and a tiled map service. This dataset is a statewide service of municipal parcels (properties) including their geometry (polygon shape) and attributes (tabular information about each parcel). In order to preserve the attributes, each municipality is added individually to the service.

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.

This dataset presents a list of Localities in Lebanon for the use of humanitarian actors. Central Administration of Statistics. The official governmental institutions for statistics. Cadastral Boundaries: Represent the geographic divisions of Lebanon as per the government. In total Lebanon holds 1623 Cadastral Boundaries. Each boundary could includes 1 or more villages or municipalities; or 1 or more cadastral boundaries could represent one municipality.

P_code This column illustrates the agreed codes of the villages in Lebanon as per the UNICEF and UNHCR IM joint work. Location_Name_En This column illustrates the agreed names of the villages in Lebanon as per the UNICEF and UNHCR IM joint work. Location_Name_Arabic This column illustrates the name of the location in arabic based on the "Real estate areas , cities and villages in Lebanon guide" in 2005 from the ACS for the most of the location Latitude, Longitude Geographical Coordinates in Decimal Degrees. Geographical Projection WGS 1984. Elevation This column has the elevation of the location GPS coordinates. Google Webservices was used to populate this field using location GPS coordinates
Governorate This column illustrates the Mohafazas (Governorates) as per the Lebanese Government divisions. In total, the no. of Mohafazas is 8. as per decree "522 dated 16/7/2003", in English Governorate_Ar This column illustrates the Mohafazas (Governorates) as per the Lebanese Government divisions. In total, the no. of Mohafazas is 8. as per decree "522 dated 16/7/2003", in Arabic UN_Area Of Operation This column illustrates the Mohafazas (Governorates) in Lebanon as per UNHCR operation areas. Noting that Nabatiyeh and South Lebanon Mohafazas were merged into one Mohafaza that is "South"also for Bekaa and Baalbek-El Hermel Mohafazas were merged into one Mohafaza that is "Bekaa" In total, the no. of Mohafazas as per UNHCR is 5.in English UN_AreaOfOperation_Ar This column illustrates the Mohafazas (Governorates) in Lebanon as per UNHCR divisions. Noting that Nabatiyeh and South Lebanon Mohafazas were merged into one Mohafaza that is "South"also for Bekaa and Baalbek-El Hermel Mohafazas were merged into one Mohafaza that is "Bekaa" In total, the no. of Mohafazas as per UNHCR is 5.in Arabic District This column illustrates the cazas (Districts) in Lebanon as per Lebanese Government divisions. In total, the no. of Cazas amounts for 26.
District_Ar This column illustrates the cazas (Districts) in Lebanon as per Lebanese Government divisions. In total, the no. of Cazas amounts for 26. in Arabic
CAS_CODE* This column illustrates the agreed codes of the cadastral boundaries** in Lebanon as per the Lebanese Government.
CAS_CODE_UN This column illustrates the agreed codes of the cadastral boundaries in Lebanon as per the Lebanese Government. The codes holds in its beginning the Lebanese acronyme LBN for international use. CAS_NAME This column illustrates the names of the cadastral boundaries in Lebanon as per the Lebanese Government in English.
CAS_NAME_Ar This column illustrates the names of the cadastral boundaries in Lebanon as per the Lebanese Government in Arabic.
CAS_MaxElevation This column has the elevation of the highest village in the same cadastral zone
Municipality Name_EN This column illustrates the names of the Municipalities in Lebanon in English. Data Source: UNHCR
Municipality Name_AR This column illustrates the names of the Municipalities in Lebanon in Arabic. Data Source: UNHCR
Municipality Phone This column illustrates the Phone number of the Municipalities in Lebanon. Data Source: MoIM website Municipality Address This column illustrates the Available Address of the Municipalities in Lebanon. Data Source: UNDP/Arabia GIS
UNION_ID This column illustrates the codes given for to the union of Municipalities in Lebanon. Data Source: UNHABITAT
Union_Full This column illustrates the names of the union of Municipalities in Lebanon in English. Data Source: UNHABITAT
UOM_Name This column illustrates the abbreviation name of the union of Municipalities in Lebanon in English. Data Source: UNHABITAT

The published paper geologic map for the Lebanon Quadrangle was converted to geographic information system (GIS) format using ESRI's ArcGIS software. The most recent digital raster U.S. Geological Survey topographic 7.5-minute quadrangle map (1:24,000 scale) was substituted for the older base map. The geologic map layout was exported in portable document file (PDF) format for distribution.A PDF file of this map can be obtained for free by contacting the Tennessee Geological Survey.

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

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.

Geospatial data about Durham County, North Carolina Libraries. Export to CAD, GIS, PDF, CSV and access via API.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

amenity IN ('mobile_money_agent','bureau_de_change','bank','microfinance','atm','sacco','money_transfer','post_office')

Features may have these attributes:

• addr:city
• name
• network
• addr:full
• source
• amenity
• operator

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

highway IS NOT NULL

Features may have these attributes:

• highway
• surface
• name
• smoothness
• lanes
• width
• source
• layer
• oneway
• bridge

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

waterway IS NOT NULL OR water IS NOT NULL OR natural IN ('water','wetland','bay')

Features may have these attributes:

• name
• waterway
• covered
• width
• depth
• layer
• blockage
• tunnel
• natural
• water

This dataset is one of many "/dataset?tags=openstreetmap">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

waterway IS NOT NULL OR water IS NOT NULL OR natural IN ('water','wetland','bay')

Features may have these attributes:

• name
• waterway
• covered
• width
• depth
• layer
• blockage
• tunnel
• natural
• water

This dataset is one of many "/dataset?tags=openstreetmap">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

no abstract provided

Disclaimer: All users agree to the following disclaimer by virtue of downloading any City of Lebanon data. The City's infrastructure records, drawings, and other documents have been gathered over many decades, using differing standards for quality control, documentation, and verification. While this product is for informational usage only, it may not be suitable for legal, engineering, or surveying purposes. Prior to making any property purchases or other investments based in full or in part upon the material provided, it is specifically advised that you independently verify the information contained within our records.If misleading or inaccurate information is brought to the City's attention, a reasonable effort will be made to fix or remove it. Such concerns should be addressed by email to gis@ci.lebanon.or.us.

This dataset contains environmental study data on various tree and shrub species in Lebanon. The research examines multiple environmental factors influencing species distribution and presence. Occurrence points were collected from field surveys under various studies, covering Lebanon. We used all the presence points and consistent environmental variables called predictors to conduct ecological niche modelling and further use the outcomes of the predicted distribution of tree and shrub species to outline Lebanon’s biogeography. The data referred to as predictors for ecological niche modelling are the environmental factors used for the study, retrieved from open sources. These include climatic, topographic, and biogeographic factors and predictors retrieved from remote sensing data such as cloud coverage, normalized difference vegetation index, and land surface temperature. This information is used to delineate suitability maps for each species and understand the factors driving..., The data set is a compilation of presence points of phanerophytes across Lebanon to conduct ecological niche modelling, grouping species into regional and global chorotypes, to further define based on their biographic appartunance. In a second step we used dissimilarity indices to define the limits of biogeographic regions and their transition zones. The indices were applied using R package plug ins into GIS tools. , , # Lebanon biogeography outlined by tree and shrub species distribution pattern

Description of the data files

The dataset consists of structured tabular data across three sheets originating from three articles:

• Stephan et al 2020

• Hammoud and Stephan 2022

• Stephan and Korban 2025

From the list of the predictors used in each of the three publications, we used those listed in the table below:

Table 1. Predictors: Data source and calculation tools

Code Predictor Source Tool

DEM Digital elevation model (m) Contour line(a) Topo to raster

Aspect Aspect (°) DEM Aspect

Slope Slope (%) DEM Slope

DFS Distance from the sea (m) DEM Fishnet - Near

CC Mean Cloud Coverage (May -July) (%) Cloud Raster(b) Mean Calculation

Tmin Mean of Minimal Temperature of the coldest month (°C) Mean of Minimal Temperature of the coldest month (c) Mean Calculation

Tmax Mean of Maximum Temperature of the hottest month (°C) Mean of Maximum Temperature of the hottest month (c)...,

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

amenity IS NOT NULL OR man_made IS NOT NULL OR shop IS NOT NULL OR tourism IS NOT NULL

Features may have these attributes:

• name
• amenity
• man_made
• shop
• tourism
• opening_hours
• beds
• rooms
• addr:full
• addr:housenumber
• addr:street
• addr:city

This dataset is one of many "/dataset?tags=openstreetmap">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

amenity IS NOT NULL OR man_made IS NOT NULL OR shop IS NOT NULL OR tourism IS NOT NULL

Features may have these attributes:

• name
• amenity
• man_made
• shop
• tourism
• opening_hours
• beds
• rooms
• addr:full
• addr:housenumber
• addr:street
• addr:city

This dataset is one of many "/dataset?tags=openstreetmap">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.

OpenStreetMap exports for use in GIS applications.

This theme includes all OpenStreetMap features in this area matching:

building IS NOT NULL

Features may have these attributes:

• building:levels
• addr:housenumber
• source
• name
• addr:street
• office
• addr:full
• building
• addr:city
• building:materials

This dataset is one of many "https://data.humdata.org/organization/hot">OpenStreetMap exports on HDX. See the Humanitarian OpenStreetMap Team website for more information.