37 datasets found
  1. m

    Data from: Data for GIS-based spatial vulnerability analysis in the area of...

    • data.mendeley.com
    Updated Mar 21, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Amirehsan Charlang Bakhtyari (2025). Data for GIS-based spatial vulnerability analysis in the area of Alessandria in Italy in case of road network disruption [Dataset]. http://doi.org/10.17632/sg7267bcs6.2
    Explore at:
    Dataset updated
    Mar 21, 2025
    Authors
    Amirehsan Charlang Bakhtyari
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Alessandria, Italy
    Description

    The input file contains supply data (based on data from geoportal of piedmont and OSM data) and flood map (based on data from geoportal of piedmont) for the Alessandria area in Italy, detailing both basic and disrupted flood scenarios to be analyzed in GIS software. It includes information on closed bridges during flood events. The output file presents the analysis results for both the basic and disrupted scenarios.

  2. A

    ‘Delta Hydrology’ analyzed by Analyst-2

    • analyst-2.ai
    Updated Sep 15, 2020
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com) (2020). ‘Delta Hydrology’ analyzed by Analyst-2 [Dataset]. https://analyst-2.ai/analysis/data-gov-delta-hydrology-ea90/c17d40a4/?iid=006-124&v=presentation
    Explore at:
    Dataset updated
    Sep 15, 2020
    Dataset authored and provided by
    Analyst-2 (analyst-2.ai) / Inspirient GmbH (inspirient.com)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Analysis of ‘Delta Hydrology’ provided by Analyst-2 (analyst-2.ai), based on source dataset retrieved from https://catalog.data.gov/dataset/dc8a4f95-557e-42e4-803f-f0d1246b598f on 27 January 2022.

    --- Dataset description provided by original source is as follows ---

    This point dataset represents the location of gaging stations in the Sacramento-San Joaquin Delta and Suisun Marsh that have historic and statistical hydrologic data, specifically various river stage data. Stages are given in NAVD88, units feet. Specific stages are given for peak stages, 100-year stages produced under 2 separate US Army Corps of Engineers hydrology reports from 1976 and 1992, the year of previous peak stages cited by the 1976 and 1992 reports, and approximate typical tidal values as approximately estimated based on long term data records. The stage data was compiled by Joel Dudas, Senior Engineer in DWR's Division of Engineering, based on a wide variety of sources, including the HYDSTRA database, various historic bulletins, raw data, station histories, and other information provided by DWR's North Central Region Office, USGS, and other misc sources. He also adjusted all data to approximate NAVD88-related stages. Observed data periods of record varied widely by station, but go back as far as 1905. All peak values were derived from start of records until up to May, 2017. The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.1, dated September 11, 2019. DWR makes no warranties or guarantees —either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. The official DWR GIS Steward for this data set is Joel Dudas, who may be contacted at gis@water.ca.gov. Comments, problems, improvements, updates, or suggestions should be forwarded to the official GIS Steward as available and appropriate.

    --- Original source retains full ownership of the source dataset ---

  3. USACE GIS Open Data Portal

    • data.cnra.ca.gov
    Updated Jul 18, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    United States Army Corps of Engineers (2020). USACE GIS Open Data Portal [Dataset]. https://data.cnra.ca.gov/dataset/usace-gis-open-data-portal
    Explore at:
    Dataset updated
    Jul 18, 2020
    Dataset authored and provided by
    United States Army Corps of Engineershttp://www.usace.army.mil/
    Description

    The U.S. Army Corps of Engineers Geospatial Open Data provides shared and trusted USACE geospatial data, services and applications for use by our partner agencies and the public.

  4. Engineering Projects

    • data-bc-er.opendata.arcgis.com
    • hub.arcgis.com
    • +1more
    Updated Aug 30, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    BC_Energy_Regulator (2016). Engineering Projects [Dataset]. https://data-bc-er.opendata.arcgis.com/datasets/81a48eb254e840b0b5c4e79efa6e3646
    Explore at:
    Dataset updated
    Aug 30, 2016
    Dataset provided by
    Oil and Gas Commission
    Authors
    BC_Energy_Regulator
    Area covered
    Description

    BC Energy Regulator Engineering Project approvals may be issued, upon application, under the authority of Section 100 of the Drilling and Production Regulation or Section 97 of the Petroleum and Natural Gas Act, depending on project type. Projects grant the applicant operating latitude, under specific conditions, for the purpose of extracting oil and/or natural gas in the most efficient way that will result in maximization of resource recovery and benefit to the Crown, balanced with surface impact and socio-economic factors. Examples are ?Good Engineering Practice?, allowing increased well density in a poor quality reservoir, or ?Pressure Maintenance Water Flood? to allow injection of water into an oil pool to increase total oil recovery. Spatial data for approved projects are included. Data is updated nightly.

  5. n

    High-Resolution QuickBird Imagery and Related GIS Layers for Barrow, Alaska,...

    • cmr.earthdata.nasa.gov
    • datasets.ai
    • +3more
    not provided
    Updated May 23, 2023
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    (2023). High-Resolution QuickBird Imagery and Related GIS Layers for Barrow, Alaska, USA, Version 1 [Dataset]. https://cmr.earthdata.nasa.gov/search/concepts/C1386246127-NSIDCV0.html
    Explore at:
    not providedAvailable download formats
    Dataset updated
    May 23, 2023
    Time period covered
    Aug 1, 2002 - Aug 2, 2002
    Area covered
    Description

    This data set contains high-resolution QuickBird imagery and geospatial data for the entire Barrow QuickBird image area (156.15° W - 157.07° W, 71.15° N - 71.41° N) and Barrow B4 Quadrangle (156.29° W - 156.89° W, 71.25° N - 71.40° N), for use in Geographic Information Systems (GIS) and remote sensing software. The original QuickBird data sets were acquired by DigitalGlobe from 1 to 2 August 2002, and consist of orthorectified satellite imagery. Federal Geographic Data Committee (FGDC)-compliant metadata for all value-added data sets are provided in text, HTML, and XML formats.

    Accessory layers include: 1:250,000- and 1:63,360-scale USGS Digital Raster Graphic (DRG) mosaic images (GeoTIFF format); 1:250,000- and 1:63,360-scale USGS quadrangle index maps (ESRI Shapefile format); an index map for the 62 QuickBird tiles (ESRI Shapefile format); and a simple polygon layer of the extent of the Barrow QuickBird image area and the Barrow B4 quadrangle area (ESRI Shapefile format).

    Unmodified QuickBird data comprise 62 data tiles in Universal Transverse Mercator (UTM) Zone 4 in GeoTIFF format. Standard release files describing the QuickBird data are included, along with the DigitalGlobe license agreement and product handbooks.

    The baseline geospatial data support education, outreach, and multi-disciplinary research of environmental change in Barrow, which is an area of focused scientific interest. Data are provided on four DVDs. This product is available only to investigators funded specifically from the National Science Foundation (NSF), Office of Polar Programs (OPP), Arctic Sciences Section. An NSF OPP award number must be provided when ordering this data. Contact NSIDC User Services at nsidc@nsidc.org to order the data, and include an NSF OPP award number in the email.

  6. i17 Delta Levees Stationing

    • catalog.data.gov
    • data.cnra.ca.gov
    • +6more
    Updated Jul 24, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Water Resources (2025). i17 Delta Levees Stationing [Dataset]. https://catalog.data.gov/dataset/i17-delta-levees-stationing-02747
    Explore at:
    Dataset updated
    Jul 24, 2025
    Dataset provided by
    California Department of Water Resourceshttp://www.water.ca.gov/
    Description

    Levee stations, usually in feet but in some cases miles, snapped to 2017 Delta levee centerlines (derived from the 2017 Delta LiDAR). Base source for station locations are surveyed field markers on the levees or distance-derived CAD files, in either case as supplied by local maintaining agency's engineers. DWR collected station location data and snapped the stations into the levee centerline file from 2012. After updated levee centerlines were created, the existing points were snapped to the new lines. So there is some small difference between the supplied station locations, previous station locations and these station locations. In some cases, multiple series of stations exist for a district, generally associated with distinct waterways. Also, district levees may be demarked in feet or in miles. The label fields are simply cartographic support, the label data are identical in all cases, but are provided to support fast labeling at more infrequent intervals as needed. Stationing is not as simple as it may seem. In some cases, multiple sets of stationing exist for a district's levees (see Sherman Island for example). What this dataset intends to represent is the current stationing used by District engineers for that District on levee maintenance and improvement projects. As changes are made to the stationing, and the new stationing data become available to the Levee Program, they will be added to this database. Some islands also have separate groups of stations for various parts of the district. This version is current as of 03/24/2020. Source of the original levee stationing is DWR Delta Levees Program, compiled from data provided by internal files, from CSU Chico State, MBK Engineers, KSN Engineers, Siegfried Engineers, Malani & Associates, Green Mountain Engineers, and DCC Engineers. Processing work done by CA DWR, Division of Engineering, Geodetic Branch, Geospatial Data Support Section, specifically by Arina Ushakova (Research Data Analyst I), and initial QC by Joel Dudas (Senior Engineer, Water Resources).

  7. Urban Road Network Data

    • figshare.com
    zip
    Updated May 30, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Urban Road Networks (2023). Urban Road Network Data [Dataset]. http://doi.org/10.6084/m9.figshare.2061897.v1
    Explore at:
    zipAvailable download formats
    Dataset updated
    May 30, 2023
    Dataset provided by
    Figsharehttp://figshare.com/
    Authors
    Urban Road Networks
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    Tool and data set of road networks for 80 of the most populated urban areas in the world. The data consist of a graph edge list for each city and two corresponding GIS shapefiles (i.e., links and nodes).Make your own data with our ArcGIS, QGIS, and python tools available at: http://csun.uic.edu/codes/GISF2E.htmlPlease cite: Karduni,A., Kermanshah, A., and Derrible, S., 2016, "A protocol to convert spatial polyline data to network formats and applications to world urban road networks", Scientific Data, 3:160046, Available at http://www.nature.com/articles/sdata201646

  8. i12 Delta Hydrology

    • data.ca.gov
    • data.cnra.ca.gov
    • +4more
    Updated Jun 19, 2023
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    California Department of Water Resources (2023). i12 Delta Hydrology [Dataset]. https://data.ca.gov/dataset/i12-delta-hydrology
    Explore at:
    arcgis geoservices rest api, zip, csv, kml, html, geojsonAvailable download formats
    Dataset updated
    Jun 19, 2023
    Dataset authored and provided by
    California Department of Water Resourceshttp://www.water.ca.gov/
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This point dataset represents the location of gaging stations in the Sacramento-San Joaquin Delta and Suisun Marsh that have historic and statistical hydrologic data, specifically various river stage data. Stages are given in NAVD88, units feet. Specific stages are given for peak stages, 100-year stages produced under 2 separate US Army Corps of Engineers hydrology reports from 1976 and 1992, the year of previous peak stages cited by the 1976 and 1992 reports, and approximate typical tidal values as approximately estimated based on long term data records. This 2023 version of this datset replaces the prior 2020 version, and should be used as a complete replacement. The underlying analyses did not change, but the USACE peak observed stage field names from the prior version were corrected and supplemental USACE 50- and 100-year stages were added accordingly. In addition, the vertical datum conversion used at specific gages was added. The vertical datum conversion is based on DWR survey and North Central Regional Office information that is maintained for each gage station. The stage data was compiled by Karen Tolentino, engineer with Delta Levees, and by Joel Dudas, Senior Engineer in DWR's Division of Engineering, based on a wide variety of sources, including the HYDSTRA database, various historic bulletins, raw data, station histories, and other information provided by DWR's North Central Region Office, USGS, and other misc sources. They also adjusted all data to approximate NAVD88-related stages. Observed data periods of record varied widely by station, but go back as far as 1905. All peak values were derived from start of records until up to May, 2017.

    The associated data are considered DWR enterprise GIS data, which meet all appropriate requirements of the DWR Spatial Data Standards, specifically the DWR Spatial Data Standard version 3.5, dated April 12, 2023. DWR makes no warranties or guarantees —either expressed or implied — as to the completeness, accuracy, or correctness of the data. DWR neither accepts nor assumes liability arising from or for any incorrect, incomplete, or misleading subject data. Comments, problems, improvements, updates, or suggestions should be forwarded to GIS@water.ca.gov.

  9. d

    Protected Areas Database of the United States (PAD-US)

    • search.dataone.org
    • datadiscoverystudio.org
    • +1more
    Updated Oct 26, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    US Geological Survey (USGS) Gap Analysis Program (GAP) (2017). Protected Areas Database of the United States (PAD-US) [Dataset]. https://search.dataone.org/view/0459986b-9a0e-41d9-9997-cad0fbea9c4e
    Explore at:
    Dataset updated
    Oct 26, 2017
    Dataset provided by
    United States Geological Surveyhttp://www.usgs.gov/
    Authors
    US Geological Survey (USGS) Gap Analysis Program (GAP)
    Time period covered
    Jan 1, 2005 - Jan 1, 2016
    Area covered
    United States,
    Variables measured
    Shape, Access, Des_Nm, Des_Tp, Loc_Ds, Loc_Nm, Agg_Src, GAPCdDt, GAP_Sts, GIS_Src, and 20 more
    Description

    The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public open space and voluntarily provided, private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastral Theme (http://www.fgdc.gov/ngda-reports/NGDA_Datasets.html). PAD-US is an ongoing project with several published versions of a spatial database of areas dedicated to the preservation of biological diversity, and other natural, recreational or cultural uses, managed for these purposes through legal or other effective means. The geodatabase maps and describes public open space and other protected areas. Most areas are public lands owned in fee; however, long-term easements, leases, and agreements or administrative designations documented in agency management plans may be included. The PAD-US database strives to be a complete “best available” inventory of protected areas (lands and waters) including data provided by managing agencies and organizations. The dataset is built in collaboration with several partners and data providers (http://gapanalysis.usgs.gov/padus/stewards/). See Supplemental Information Section of this metadata record for more information on partnerships and links to major partner organizations. As this dataset is a compilation of many data sets; data completeness, accuracy, and scale may vary. Federal and state data are generally complete, while local government and private protected area coverage is about 50% complete, and depends on data management capacity in the state. For completeness estimates by state: http://www.protectedlands.net/partners. As the federal and state data are reasonably complete; focus is shifting to completing the inventory of local gov and voluntarily provided, private protected areas. The PAD-US geodatabase contains over twenty-five attributes and four feature classes to support data management, queries, web mapping services and analyses: Marine Protected Areas (MPA), Fee, Easements and Combined. The data contained in the MPA Feature class are provided directly by the National Oceanic and Atmospheric Administration (NOAA) Marine Protected Areas Center (MPA, http://marineprotectedareas.noaa.gov ) tracking the National Marine Protected Areas System. The Easements feature class contains data provided directly from the National Conservation Easement Database (NCED, http://conservationeasement.us ) The MPA and Easement feature classes contain some attributes unique to the sole source databases tracking them (e.g. Easement Holder Name from NCED, Protection Level from NOAA MPA Inventory). The "Combined" feature class integrates all fee, easement and MPA features as the best available national inventory of protected areas in the standard PAD-US framework. In addition to geographic boundaries, PAD-US describes the protection mechanism category (e.g. fee, easement, designation, other), owner and managing agency, designation type, unit name, area, public access and state name in a suite of standardized fields. An informative set of references (i.e. Aggregator Source, GIS Source, GIS Source Date) and "local" or source data fields provide a transparent link between standardized PAD-US fields and information from authoritative data sources. The areas in PAD-US are also assigned conservation measures that assess management intent to permanently protect biological diversity: the nationally relevant "GAP Status Code" and global "IUCN Category" standard. A wealth of attributes facilitates a wide variety of data analyses and creates a context for data to be used at local, regional, state, national and international scales. More information about specific updates and changes to this PAD-US version can be found in the Data Quality Information section of this metadata record as well as on the PAD-US website, http://gapanalysis.usgs.gov/padus/data/history/.) Due to the completeness and complexity of these data, it is highly recommended to review the Supplemental Information Section of the metadata record as well as the Data Use Constraints, to better understand data partnerships as well as see tips and ideas of appropriate uses of the data and how to parse out the data that you are looking for. For more information regarding the PAD-US dataset please visit, http://gapanalysis.usgs.gov/padus/. To find more data resources as well as view example analysis performed using PAD-US data visit, http://gapanalysis.usgs.gov/padus/resources/. The PAD-US dataset and data standard are compiled and maintained by the USGS Gap Analysis Program, http://gapanalysis.usgs.gov/ . For more information about data standards and how the data are aggregated please review the “Standards and Methods Manual for PAD-US,” http://gapanalysis.usgs.gov/padus/data/standards/ .

  10. N

    OSE Points of Diversion

    • catalog.newmexicowaterdata.org
    csv, html, xlsx, zip
    Updated Jun 24, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    New Mexico Office of the State Engineer & Interstate Stream Commission (2025). OSE Points of Diversion [Dataset]. https://catalog.newmexicowaterdata.org/dataset/ose-points-of-diversion
    Explore at:
    xlsx(84245), zip(30911308), html, csv(150535724)Available download formats
    Dataset updated
    Jun 24, 2025
    Dataset provided by
    New Mexico Office of the State Engineer & Interstate Stream Commission
    License

    Open Database License (ODbL) v1.0https://www.opendatacommons.org/licenses/odbl/1.0/
    License information was derived automatically

    Description

    The NM Office of the State Engineer (OSE) "Point of Diversions" (POD) layer includes well locations, surface declarations, or surface permits updated on a monthly basis. These data were extracted from the OSE W.A.T.E.R.S. (Water Administration Technical Engineering Resource System) database and geo-located (mapped). These data have varying degrees of accuracy and have not been validated. Data included in this dataset only includes PODs that have coordinates located within the State of New Mexico. This message is to alert users of this data to various changes regarding how this POD data is generated and maintained by the NM Office of the State Engineer. In addition, all attribute fields are fully described in the metadata, including descriptions of field codes. Please read the metadata accompanying this GIS data layer for further information. Any questions regarding this GIS data should be directed NM OSE Information Technology Systems Bureau GIS at the contact information given below.

  11. a

    Michigan Forest Land Ownership 2019

    • usfs.hub.arcgis.com
    Updated Jun 14, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    U.S. Forest Service (2021). Michigan Forest Land Ownership 2019 [Dataset]. https://usfs.hub.arcgis.com/maps/f1a15650f89f4da794030f65044f7ef9
    Explore at:
    Dataset updated
    Jun 14, 2021
    Dataset authored and provided by
    U.S. Forest Service
    Area covered
    Description

    This geospatial dataset depicts ownership patterns of forest land across Michigan, circa 2019. The data sources are listed below. The first seven sources of data supersede the final data source. The final data source is modeled from Forest Inventory and Analysis points from 2012-2017 and the most up-to-date publicly available boundaries of federal, state, and tribal lands.1.MI_State_Boundary_Census_Gov_2019.shp (State of MI boundary) clipped from cb_2019_us_state_500k from https://www.census.gov/geographies/mapping-files/time-series/geo/cartographic-boundary.html2.NPS_Land_Resources_Division_MI.shp clipped from NPS_-_Land_Resources_Division_Boundary_and_Tract_Data_Service-shp taken from https://public-nps.opendata.arcgis.com/datasets/nps-land-resources-division-boundary-and-tract-data-service/data?layer=1Published December 12, 2019This service depicts National Park Service tract and boundary data that was created by the Land Resources Division. NPS Director's Order #25 states: "Land status maps will be prepared to identify the ownership of the lands within the authorized boundaries of the park unit. These maps, showing ownership and acreage, are the 'official record' of the acreage of Federal and non-federal lands within the park boundaries. While these maps are the official record of the lands and acreage within the unit's authorized boundaries, they are not of survey quality and not intended to be used for survey purposes." As such this data is intended for use as a tool for GIS analysis. It is in no way intended for engineering or legal purposes. The data accuracy is checked against best available sources which may be dated and vary by location. NPS assumes no liability for use of this data. The boundary polygons represent the current legislated boundary of a given NPS unit. NPS does not necessarily have full fee ownership or hold another interest (easement, right of way, etc...) in all parcels contained within this boundary. Equivalently NPS may own or have an interest in parcels outside the legislated boundary of a given unit. In order to obtain complete information about current NPS interests both inside and outside a unit’s legislated boundary tract level polygons are also created by NPS Land Resources Division and should be used in conjunction with this boundary data. To download this data directly from the NPS go to https://irma.nps.gov/App/Portal/Home Property ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service (NPS) shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data. Terms of UseProperty ownership data is compiled from deeds, plats, surveys, and other source data. These are not engineering quality drawings and should be used for administrative purposes only. The National Park Service shall not be held liable for improper or incorrect use of the data described and/or contained herein. These data and related graphics are not legal documents and are not intended to be used as such. The information contained in these data is dynamic and may change over time. The data are not better than the original sources from which they were derived. It is the responsibility of the data user to use the data appropriately and consistent within the limitations of geospatial data in general and these data in particular. The related graphics are intended to aid the data user in acquiring relevant data; it is not appropriate to use the related graphics as data. The National Park Service gives no warranty, expressed or implied, as to the accuracy, reliability, or completeness of these data. It is strongly recommended that these data are directly acquired from an NPS server and not indirectly through other sources which may have changed the data in some way. Although these data have been processed successfully on a computer system at the National Park Service, no warranty expressed or implied is made regarding the utility of the data on another system or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. This disclaimer applies both to individual use of the data and aggregate use with other data.3.Isle Royale.shp only Isle Royale clipped from MI_State_Boundary_Census_Gov_2019.shp4.FWSInterest_MI.shp (U.S. Fish and Wildlife Service) clipped from FWSInterest from FWSInterest_Apr2020.zipfrom https://www.fws.gov/gis/data/CadastralDB/index_cadastral.html (being moved on 6/26/2020)Use inttype1 = OThis data layer depicts lands and waters administered by the U.S. Fish and Wildlife Service (USFWS) in North America, U.S. Trust Territories and Possessions. It may also include inholdings that are not administered by USFWS. The primary source for this information is the USFWS Realty program.5.surfaceownership_MI.shp (U.S. National Forest Service) clipped from S_USA.SurfaceOwnership.gdb and downloaded fromhttps://data.fs.usda.gov/geodata/edw/datasets.phphttps://data.fs.usda.gov/geodata/edw/datasets.php?xmlKeyword=surfaceownershiprefreshed May 26, 2020Used NFSLandU_4 field and surfaceO_3 and surfaceO_3 to identify NFS parcelsAn area depicting ownership parcels of the surface estate. Each surface ownership parcel is tied to a particular legal transaction. The same individual or organization may currently own many parcels that may or may not have been acquired through the same legal transaction. Therefore, they are captured as separate entities rather than merged together. This is in contrast to Basic Ownership, in which the surface ownership parcels having the same owner are merged together. Basic Ownership provides the general user with the Forest Service versus non-Forest Service view of land ownership within National Forest boundaries. Surface Ownership provides the land status user with a current snapshot of ownership within National Forest boundaries.6.MichiganDNR_02062020.shp (State of Michigan) from the State of MI delivered @ email on 5/14/2020Has State forests, State Wildlife areas, and State parks.7.The previous public ownership layers supersede this Sass et al. (2020) layer.In Sass et al. (2020), the nonforest areas are masked out.Identification_Information:Citation:Citation_Information:Originator: Sass, Emma M.Originator: Butler, Brett J.Originator: Markowski-Lindsay, Marla Publication_Date: 2020Title:Estimated distribution of forest ownership across the conterminous United States – geospatial datasetGeospatial_Data_Presentation_Form: raster digital dataPublication_Information:Publication_Place: Fort Collins, COPublisher: Forest Service Research Data ArchiveEight values of ownership type:1 = Family (Private): Owned by families, individuals, trusts, estates, family partnerships, and other unincorporated groups of individuals that own forest land. FIACode 45.2 = Corporate (Private): Owned by corporations. FIA Code 41.3 = TIMO/REIT (Private): Owned by Timber Investment Management Organizations or Real Estate Investment Trusts. Included in FIA Code 414 = Other Private (Private): Owned by conservation and natural resource organizations, unincorporated partnerships and associations. FIA Codes 42-43.5 = Federal (Public): Owned by the federal government. FIA Codes 11-13, 21-25.6 = State (Public): Owned by a state government. FIA Code 31.7 = Local (Public): Owned by a local government. FIA Code 32.8 = Tribal: Owned by Native American tribes. FIA Code 44.8.FIA inventory units developed by FIA, 2020

  12. a

    Maui 2019 DTM elevation

    • kauai-open-data-kauaigis.hub.arcgis.com
    • opendata.hawaii.gov
    • +1more
    Updated Aug 11, 2021
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Hawaii Statewide GIS Program (2021). Maui 2019 DTM elevation [Dataset]. https://kauai-open-data-kauaigis.hub.arcgis.com/datasets/ad6906de458e46528e0c352321015788
    Explore at:
    Dataset updated
    Aug 11, 2021
    Dataset authored and provided by
    Hawaii Statewide GIS Program
    Area covered
    Description

    Digital Terrain Model (bare earth) of parts of Maui and Molokai. Partial coverage Vexcel, Inc. LIDAR of Maui and Molokai were purchased by County of Maui to assist with three-dimensional modeling of structures in areas of higher development. 1'/px, LIDAR-derived, bare earth DEM/elevation raster of parts of Maui and Molokai – specifically, Central Molokai, Kahului, Kihei, Lahaina and Pukalani. XY units: feet, Z units: meters. Use Limitations: 1.Disclaimer - This dataset is being placed in the public domain. Any use is allowed except for re-sale. Neither Vexcel, Inc., the County of Maui, nor the State of Hawaii make any guarantees, expressed or implied, regarding its accuracy or fitness of use. Users should verify XYZ values through a licensed surveyor for any engineering application. This data should only be used as a guide, vs. a statement of fact regarding real-world conditions. 2.Vertical Datum - The originator of this LIDAR dataset, Vexcel Inc. of Boulder, Colorado referenced Z values to the North American Vertical Datum of 1988 (NAVD88). NAVD88 is not recognized as a valid vertical reference for the state of Hawaii. Currently Hawaii has no official (de jure or de facto) vertical datum, and NOAA's National Geodetic Survey (NGS) recommends that elevations be referenced to the nearest NOAA tidal gauge. A legacy LIDAR dataset produced in 2013 by the United States Army Corps of Engineers (USACE) used NAD83(PA11) as its vertical reference. In theory this approach should result in better accuracy for the Z dimension as PA11 is a Pacific plate-centric datum. In comparing flat areas containing neither structures or vegetation, it was found that the Vexcel values sit approximately 4 feet above the USACE dataset. The vertical datum issue was brought to the attention of Vexcel, Inc. Vexcel used the 2013 USACE LIDAR as vertical control to correct their LIDAR data. The (corrected) .las data is shared as it was delivered. As stated above, the use of this data transfers all risks and assumption of responsibility to the user. For more information see https://files.hawaii.gov/dbedt/op/gis/data/Maui_2019_DTM.html or contact County of Maui at GISMonitor@co.maui.hi.us or Hawaii Statewide GIS Program at gis@hawaii.gov.

  13. Simulated Maximum Flood Extent

    • figshare.com
    zip
    Updated Jun 18, 2020
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Alfred Kalyanapu; Tigstu Dullo (2020). Simulated Maximum Flood Extent [Dataset]. http://doi.org/10.6084/m9.figshare.12509846.v1
    Explore at:
    zipAvailable download formats
    Dataset updated
    Jun 18, 2020
    Dataset provided by
    Figsharehttp://figshare.com/
    Authors
    Alfred Kalyanapu; Tigstu Dullo
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Description

    This dataset is derived by performing Flood2D-GPU on ORNL's SUMMIT supercomputer. The observed high water mark data that is used to compared our simulated dataset can be found from the following study:Watson, K. M., Harwell, G. R., Wallace, D. S., Welborn, T. L., Stengel, V. G., and J. S. McDowell (2018), Characterization of peak streamflows and flood inundation of selected areas in southeastern Texas and southwestern Louisiana from the August and September 2017 flood resulting from Hurricane Harvey: U.S. Geological Survey Scientific Investigations Report 2018–5070, 44 p., https://doi.org/10.3133/sir20185070.The GIS dataset can be downloaded at the URL:https://doi.org/10.3133/sir20185070 .

  14. Engineering Properties:Bulking

    • data.europa.eu
    • cloud.csiss.gmu.edu
    • +4more
    unknown
    Updated Dec 18, 2015
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    British Geological Survey (BGS) (2015). Engineering Properties:Bulking [Dataset]. https://data.europa.eu/data/datasets/engineering-properties-bulking?locale=es
    Explore at:
    unknownAvailable download formats
    Dataset updated
    Dec 18, 2015
    Dataset provided by
    British Geological Surveyhttps://www.bgs.ac.uk/
    Authors
    British Geological Survey (BGS)
    Description

    This dataset is a characterisation of the soil and rocks and the potential bulking factor (likely excavated volume increases) at Formation (local to regional) level for Great Britain. The data is categorised into Class, characteristics of similar soils and rocks and Bulking Factor, range or ranges of % bulking. The excavation of rocks or soils is usually accompanied by a change in volume. This change in volume is referred to as ‘bulking’ and the measure of the change is the ‘bulking factor’. The bulking factor is used to estimate the likely excavated volumes that will need to be moved, stored on site, or removed from site. It is envisaged that the 'Engineering Properties: Bulking of soils and rocks' dataset will be of use to companies involved in the estimation of the volume of excavated material for civil engineering operations. These operations may include, but are not limited to, resource estimation, transportation, storage, disposal and the use of excavated materials as engineered fill. It forms part of the DiGMap Plus dataset series of GIS layers which describe the engineering properties of materials from the base of pedological soil down to c. 3m depth (ie the uppermost c.2m of geology). These deposits display a variable degree of weathering, but still exhibit core engineering characteristics relating to their lithologies.

  15. a

    Environment Wetlands CookInlet

    • gis.data.alaska.gov
    • data.matsugov.us
    • +3more
    Updated Jul 16, 2016
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Matanuska-Susitna Borough (2016). Environment Wetlands CookInlet [Dataset]. https://gis.data.alaska.gov/datasets/d162a28be9334b619f614badef370b80
    Explore at:
    Dataset updated
    Jul 16, 2016
    Dataset authored and provided by
    Matanuska-Susitna Borough
    Area covered
    Description

    Exact wetland boundaries are perhaps impossible to delineate. The definition of a wetland can change, and is somewhat open to interpretation. This file represents an attempt to map every polygon that could be considered a wetland using the criteria outlined in the 2007 supplement to the 1987 Army Corps Delineation Manual (Environmental Laboratory. (1987). "Corps of Engineers Wetland Delineation Manual", Technical Report Y-87-1, US Army Engineer Waterways Experiment Station. Vicksburg, MS). To generate the data, stereo paired aerial photos and relatively quick field visits, along with National Wetland Inventory maps and soils data were used. Wetlands that may be non-jurisdictional are also included, such as Depressions, inclusions along rivers and in braided river valleys. Environment

  16. d

    Traffic Counts

    • catalog.data.gov
    • res1catalogd-o-tdatad-o-tgov.vcapture.xyz
    • +2more
    Updated Apr 19, 2025
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Sioux Falls GIS (2025). Traffic Counts [Dataset]. https://catalog.data.gov/dataset/traffic-counts-fc3cd
    Explore at:
    Dataset updated
    Apr 19, 2025
    Dataset provided by
    City of Sioux Falls GIS
    Description

    Feature layer containing authoritative traffic count points for Sioux Falls, South Dakota.The traffic counts listed are 24-hour, weekday, two-directional counts. Traffic counts are normally collected during the summer months, but may be taken any season, as weather permits. The traffic counts are factored by the day of the week as well as by the month of the year to become an Average Annual Daily Total (AADT). Traffic volumes (i.e. count data) can fluctuate depending on the month, week, day of collection; the weather, type of road surface, nearby construction, etc. All of the historical data should be averaged to reflect the "normal" traffic count. More specific count data (time, date, hourly volume) can be obtained from the Sioux Falls Engineering Division at 367-8601.

  17. a

    OSE PODs

    • geospatialdata-ose.opendata.arcgis.com
    • hub.arcgis.com
    Updated Oct 6, 2017
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    New Mexico Office of the State Engineer (2017). OSE PODs [Dataset]. http://geospatialdata-ose.opendata.arcgis.com/datasets/ose-pods
    Explore at:
    Dataset updated
    Oct 6, 2017
    Dataset authored and provided by
    New Mexico Office of the State Engineer
    License

    MIT Licensehttps://opensource.org/licenses/MIT
    License information was derived automatically

    Area covered
    Description

    This dataset has a data dictionary that can be downloaded here. The NM Office of the State Engineer (OSE) "Point of Diversions" (POD) layer includes well locations, surface declarations, or surface permits. These data were extracted from the OSE W.A.T.E.R.S. (Water Administration Technical Engineering Resource System) database and geo-located (mapped). These data have varying degrees of accuracy and have not been validated. This message is to alert users of this data to various changes regarding how this POD data is generated and maintained by the NM Office of the State Engineer. In addition, all attribute fields are fully described in the metadata, including descriptions of field codes. Please read the metadata accompanying this GIS data layer for further information. Any questions regarding this GIS data should be directed NM OSE Information Technology Systems Bureau GIS at the contact information given below. Stephen N. Hayes NMOSE ITSB GIS Data Manager(505) 827-6321 PO Box 25102 Santa Fe, NM 87504 stephen.hayes@ose.nm.gov

  18. a

    Highway Subsections

    • hub.arcgis.com
    • data-phl.opendata.arcgis.com
    • +1more
    Updated Jun 3, 2015
    + more versions
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    City of Philadelphia (2015). Highway Subsections [Dataset]. https://hub.arcgis.com/datasets/phl::highway-subsections
    Explore at:
    Dataset updated
    Jun 3, 2015
    Dataset authored and provided by
    City of Philadelphia
    Area covered
    Description

    View metadata for key information about this dataset.The Highway Subsections layer was developed to aid the Highway Division in the planning, organizing, and maintaining of the streets within each of the fifty-six sections. Subsections can be aggregated into sections and districts. A Highway Engineer is responsible for each district. Examples of maintenance include: paving, snow removal, concrete maintenance, and the monitoring/repairing of ditches and potholes.Please note that the dataset below is a snapshot of data captured at one time and does not receive regular updates.This polygon layer also has an associated arc layer.For questions about this dataset, contact michael.matela@phila.gov. For technical assistance, email maps@phila.gov.

  19. Ports

    • geospatial-usace.opendata.arcgis.com
    Updated Jul 29, 2021
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    usace_iwr_cac (2021). Ports [Dataset]. https://geospatial-usace.opendata.arcgis.com/datasets/b7fd6cec8d8c43e4a141d24170e6d82f
    Explore at:
    Dataset updated
    Jul 29, 2021
    Dataset provided by
    United States Army Corps of Engineershttp://www.usace.army.mil/
    Authors
    usace_iwr_cac
    Area covered
    Description

    The Port and Port Statistical Area web service allows users to visualize and access two USACE enterprise-wide feature classes: the Port Feature Class and the Port Statistical Area Feature Class, both of which include polygon geometries used to generate statistics for commerce data and vessel movements. The GIS service includes attributes such as port name, boundary description, and associated legislative documentation.

    USACE works with port authorities from across the United States to develop the statistical port boundaries through an iterative and collaborative process. Port boundary information is prepared by USACE to increase transparency on public waterborne commerce statistic reporting, as well as to modernize how the data type is stored, analyzed, and reported.

    A Port Area is defined by the limits set by overarching legislative enactments of state, county, or city governments, or the corporate limits of a municipality. A port typically refers to a geographical area that includes operational activities related to maritime transport as well as acquisition, operation, and management of port infrastructure and property, such as might be associated with ownership, concession, construction approval, or policy decision-making authority.

    A Port Statistical Area (PSA) is a region with formally justified shared economic interests and collective reliance on infrastructure related to waterborne movements of commodities that is formally recognized by legislative enactments of state, county, or city governments. PSAs generally contain groups of county legislation for the sole purpose of statistical reporting. Through GIS mapping, legislative boundaries, and stakeholder collaboration, PSAs often serve as the primary unit for aggregating and reporting commerce statistics for broader geographical areas.

    Per Engineering Regulation 1130-2-520, the U.S. Army Corps of Engineers' Navigation Data Center is responsible to collect, compile, publish, and disseminate waterborne commerce statistics. This task has subsequently been charged to the Waterborne Commerce Statistics Center to perform. Performance of this work is in accordance with the Rivers and Harbors Appropriation Act of 1922. Included in this work is the definition of a port area. A port area is defined in Engineering Pamphlet 1130-2-520 as: (1) Port limits defined by legislative enactments of state, county, or city governments. (2) The corporate limits of a municipality. The USACE enterprise-wide port and port statistical area feature classes per EP 1130-2-520 are organized in SDSFIE 4.0.2 format.

  20. a

    Jurisdictions

    • hub.arcgis.com
    Updated Feb 11, 2025
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    JasonClay (2025). Jurisdictions [Dataset]. https://hub.arcgis.com/datasets/e6661515aaf341569502af43ae08cb20
    Explore at:
    Dataset updated
    Feb 11, 2025
    Dataset authored and provided by
    JasonClay
    Area covered
    Description

    Tax DuplicateItems in the Tax Duplicate are from the CADASTRE dataset and are exclusively maintained by the Lucas County Engineer’s Tax Map Department, and hosted by the Lucas County Auditor's Office GIS Department.The Cadastre dataset contains three polygon layers, one polyline layer, and sixteen annotation layers.Lucas County Engineers Tax Map Department maintains the tax maps and parcel mapping portion of the county's GIS. They review all legal descriptions before transfers are made and assign street numbers for addresses in the County outside of city limits.Cadastre Parcels are identified by Assessor number, which is a unique land identifier. Road Centerlines are provided by Lucas County EMA/911Inquiries about cadastral data should be directed to Shawn Shaffer, Engineer's Tax Map Department at 419-213-4658.Inquiries regarding the map and feature services should be directed to Jason Clay, Auditor's GIS Department at 419-213-2110.Inquiries regarding Road Centerlines should be directed to Greg Bonfiglio, Lucas County 911 Regional Council of Governments, 419-720-0275

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Amirehsan Charlang Bakhtyari (2025). Data for GIS-based spatial vulnerability analysis in the area of Alessandria in Italy in case of road network disruption [Dataset]. http://doi.org/10.17632/sg7267bcs6.2

Data from: Data for GIS-based spatial vulnerability analysis in the area of Alessandria in Italy in case of road network disruption

Related Article
Explore at:
Dataset updated
Mar 21, 2025
Authors
Amirehsan Charlang Bakhtyari
License

Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically

Area covered
Alessandria, Italy
Description

The input file contains supply data (based on data from geoportal of piedmont and OSM data) and flood map (based on data from geoportal of piedmont) for the Alessandria area in Italy, detailing both basic and disrupted flood scenarios to be analyzed in GIS software. It includes information on closed bridges during flood events. The output file presents the analysis results for both the basic and disrupted scenarios.

Search
Clear search
Close search
Google apps
Main menu