The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a format usable in a geographic information system (GIS) by employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM), Zone 16, using the North American Datum of 1983 (NAD83). Orthorectify: We orthorectified the interpreted overlays by using OrthoMapper, a softcopy photogrammetric software for GIS. One function of OrthoMapper is to create orthorectified imagery from scanned and unrectified imagery (Image Processing Software, Inc., 2002). The software features a method of visual orientation involving a point-and-click operation that uses existing orthorectified horizontal and vertical base maps. Of primary importance to us, OrthoMapper also has the capability to orthorectify the photointerpreted overlays of each photograph based on the reference information provided. Digitize: To produce a polygon vector layer for use in ArcGIS (Environmental Systems Research Institute [ESRI], Redlands, California), we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format by using ArcGIS. In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map-attribute codes (both map-class codes and physiognomic modifier codes) to the polygons and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer. Geodatabase: At this stage, the map layer has only map-attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

The ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) Project Package includes all of the layers that are in the NTIA Permitting and Environmental Information Application as well as the APPEIT Tool which will allow users to input a project area and determine what layers from the application overlap with it. An overview of the project package and the APPEIT tool is provided below. User instructions on how to use the tool are available here. Instructions now include how to customize the tool by adding your own data. A video explaining how to use the Project Package is also available here. Project Package OverviewThis map package includes all of the layers from the NTIA Permitting and Environmental Information Application. The layers included are all feature services from various Federal and State agencies. The map package was created with ArcGIS Pro 3.4.0. The map package was created to allow users easy access to all feature services including symbology. The map package will allow users to avoid downloading datasets individually and easily incorporate into their own GIS system. The map package includes three maps.1. Permitting and Environmental Information Application Layers for GIS Analysis - This map includes all of the map tabs shown in the application, except State Data which is provided in another tab. This map includes feature services that can be used for analysis with other project layers such as a route or project area. 2. Permitting and Environmental Information Application Layers – For Reference Only - This map includes layers that cannot be used for analysis since they are either imagery or tile layers.3. State Data - Reference Only - This map includes all relevant state data that is shown in the application.The NTIA Permitting and Environmental Information Application was created to help with your permitting planning and environmental review preparation efforts by providing access to multiple maps from publicly available sources, including federal review, permitting, and resource agencies. The application should be used for informational purposes only and is intended solely to assist users with preliminary identification of areas that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. Multiple maps are provided in the application which are created from public sources. This application does not have an exhaustive list of everything you need for permitting or environmental review for a project but is an initial starting point to see what might be required.APPEIT Tool OverviewThe Department of Commerce’s National Telecommunications and Information Administration (NTIA) is providing the ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) to help federal broadband grant recipients and subgrantees identify permits and environmental factors as they plan routes for their broadband deployments. Identifying permit requirements early, initiating pre-application coordination with permitting agencies, and avoiding environmental impacts help drive successful infrastructure projects. NTIA’s public release of the APPEIT tool supports government-wide efforts to improve permitting and explore how online and digital technologies can promote efficient environmental reviews. This Esri ArcGIS Pro tool is included in the map package and was created to support permitting, planning, and environmental review preparation efforts by providing access to data layers from publicly available sources, including federal review, permitting, and resource agencies. An SOP on how to use the tool is available here. For the full list of APPEIT layers, see Appendix Table 1 in the SOP. The tool is comprised of an ArcGIS Pro Project containing a custom ArcGIS Toolbox tool, linked web map shared by the NTIA’s National Broadband Map (NBAM), a report template, and a Tasks item to guide users through using the tool. This ArcGIS Pro project and its contents (maps and data) are consolidated into this (.ppkx) project file. To use APPEIT, users will input a project area boundary or project route line in a shapefile or feature class format. The tool will return as a CSV and PDF report that lists any federal layers from the ArcGIS Pro Permitting and Environmental Information Web Map that intersect the project. Users may only input a single project area or line at a time; multiple projects or project segments will need to be screened separately. For project route lines, users are required to specify a buffer distance. The buffer distance that is used for broadband projects should be determined by the area of anticipated impact and should generally not exceed 500 feet. For example, the State of Maryland recommends a 100-foot buffer for broadband permitting. The tool restricts buffers to two miles to ensure relevant results. DisclaimerThis document is intended solely to assist federal broadband grant recipients and subgrantees in better understanding Infrastructure Investment and Jobs Act (IIJA) broadband grant programs and the requirements set forth in the Notice of Funding Opportunity (NOFO) for this program. This document does not and is not intended to supersede, modify, or otherwise alter applicable statutory or regulatory requirements, the terms and conditions of the award, or the specific application requirements set forth in the NOFO. In all cases, statutory and regulatory mandates, the terms and conditions of the award, the requirements set forth in the NOFO, and follow-on policies and guidance, shall prevail over any inconsistencies contained in this document. NTIA’s ArcGIS Pro Permitting and Environmental Information Tool (APPEIT) should be used for informational purposes only and is intended solely to assist users with preliminary identification of broadband deployments that may require permits or planning to avoid potentially significant impacts to environmental resources subject to the National Environmental Policy Act (NEPA) and other statutory requirements. The tool is not an exhaustive or complete resource and does not and is not intended to substitute for, supersede, modify, or otherwise alter any applicable statutory or regulatory requirements, or the specific application requirements set forth in any NTIA NOFO, Terms and Conditions, or Special Award Condition. In all cases, statutory and regulatory mandates, and the requirements set forth in NTIA grant documents, shall prevail over any inconsistencies contained in these templates. The tool relies on publicly available data available on the websites of other federal, state, local, and Tribal agencies, and in some instances, private organizations and research institutions. Layers identified with a double asterisk include information relevant to determining if an “extraordinary circumstance” may warrant more detailed environmental review when a categorical exclusion may otherwise apply. While NTIA continues to make amendments to its websites to comply with Section 508, NTIA cannot ensure Section 508 compliance of federal and non-federal websites or resources users may access from links on NTIA websites. All data is presented “as is,” “as available” for informational purposes. NTIA does not warrant the accuracy, adequacy, or completeness of this information and expressly disclaims liability for any errors or omissions. Please e-mail NTIAanalytics@ntia.gov with any questions.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We developed 75 map classes (including map-class phases) to map the SLBE and environs. Of these 75 map classes, 67 represent natural/semi-natural vegetation types within the NVCS, four represent cultural vegetation types (agriculture and developed) within the NVCS, and four represent non-vegetation features (open water, barren land). To assign meaningful information to each polygon (e.g., map-class names, physiognomic definitions, links to NVCS types), we produced a feature-class table, along with other supportive tables, and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature-class layers produced from this project, including vegetation sample plots, accuracy assessment (AA) sites, aerial photo locations, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. We converted the photointerpreted data into a GIS-usable format employing three fundamental processes: (1) orthorectify, (2) digitize, and (3) develop the geodatabase. All digital map automation was projected in Universal Transverse Mercator (UTM) projection, Zone 16, using North American Datum of 1983 (NAD83). To produce a polygon vector layer for use in ArcGIS, we converted each raster-based image mosaic of orthorectified overlays containing the photointerpreted data into a grid format using ArcGIS (Version 9.2, © 2006 Environmental Systems Research Institute, Redlands, California). In ArcGIS, we used the ArcScan extension to trace the raster data and produce ESRI shapefiles. We digitally assigned map attribute codes (both map class codes and physiognomic modifier codes) to the polygons, and checked the digital data against the photointerpreted overlays for line and attribute consistency. Ultimately, we merged the individual layers into a seamless layer of INDU and immediate environs. At this stage, the map layer has only map attribute codes assigned to each polygon. To assign meaningful information to each polygon (e.g., map class names, physiognomic definitions, link to NVC association and alliance codes), we produced a feature class table along with other supportive tables and subsequently related them together via an ArcGIS Geodatabase. This geodatabase also links the map to other feature class layers produced from this project, including vegetation sample plots, accuracy assessment sites, and project boundary extent. A geodatabase provides access to a variety of interlocking data sets, is expandable, and equips resource managers and researchers with a powerful GIS tool.

The construction of this data model was adapted from the Telvent Miner & Miner ArcFM MultiSpeak data model to provide interface functionality with Milsoft Utility Solutions WindMil engineering analysis program. Database adaptations, GPS data collection, and all subsequent GIS processes were performed by Southern Geospatial Services for the Town of Apex Electric Utilities Division in accordance to the agreement set forth in the document "Town of Apex Electric Utilities GIS/GPS Project Proposal" dated March 10, 2008. Southern Geospatial Services disclaims all warranties with respect to data contained herein. Questions regarding data quality and accuracy should be directed to persons knowledgeable with the forementioned agreement.The data in this GIS with creation dates between March of 2008 and April of 2024 were generated by Southern Geospatial Services, PLLC (SGS). The original inventory was performed under the above detailed agreement with the Town of Apex (TOA). Following the original inventory, SGS performed maintenance projects to incorporate infrastructure expansion and modification into the GIS via annual service agreements with TOA. These maintenances continued through April of 2024.At the request of TOA, TOA initiated in house maintenance of the GIS following delivery of the final SGS maintenance project in April of 2024. GIS data created or modified after April of 2024 are not the product of SGS.With respect to SGS generated GIS data that are point features:GPS data collected after January 1, 2013 were surveyed using mapping grade or survey grade GPS equipment with real time differential correction undertaken via the NC Geodetic Surveys Real Time Network (VRS). GPS data collected prior to January 1, 2013 were surveyed using mapping grade GPS equipment without the use of VRS, with differential correction performed via post processing.With respect to SGS generated GIS data that are line features:Line data in the GIS for overhead conductors were digitized as straight lines between surveyed poles. Line data in the GIS for underground conductors were digitized between surveyed at grade electric utility equipment. The configurations and positions of the underground conductors are based on TOA provided plans. The underground conductors are diagrammatic and cannot be relied upon for the determination of the actual physical locations of underground conductors in the field.The Service Locations feature class was created by Southern Geospatial Services (SGS) from a shapefile of customer service locations generated by dataVoice International (DV) as part of their agreement with the Town of Apex (TOA) regarding the development and implemention of an Outage Management System (OMS).Point features in this feature class represent service locations (consumers of TOA electric services) by uniquely identifying the features with the same unique identifier as generated for a given service location in the TOA Customer Information System (CIS). This is also the mechanism by which the features are tied to the OMS. Features are physically located in the GIS based on CIS address in comparison to address information found in Wake County GIS property data (parcel data). Features are tied to the GIS electric connectivity model by identifying the parent feature (Upline Element) as the transformer that feeds a given service location.SGS was provided a shapefile of 17992 features from DV. Error potentially exists in this DV generated data for the service location features in terms of their assigned physical location, phase, and parent element.Regarding the physical location of the features, SGS had no part in physically locating the 17992 features as provided by DV and cannot ascertain the accuracy of the locations of the features without undertaking an analysis designed to verify or correct for error if it exists. SGS constructed the feature class and loaded the shapefile objects into the feature class and thus the features exist in the DV derived location. SGS understands that DV situated the features based on the address as found in the CIS. No features were verified as to the accuracy of their physical location when the data were originally loaded. It is the assumption of SGS that the locations of the vast majority of the service location features as provided by DV are in fact correct.SGS understands that as a general rule that DV situated residential features (individually or grouped) in the center of a parcel. SGS understands that for areas where multiple features may exist in a given parcel (such as commercial properties and mobile home parks) that DV situated features as either grouped in the center of the parcel or situated over buildings, structures, or other features identifiable in air photos. It appears that some features are also grouped in roads or other non addressed locations, likely near areas where they should physically be located, but that these features were not located in a final manner and are either grouped or strung out in a row in the general area of where DV may have expected they should exist.Regarding the parent and phase of the features, the potential for error is due to the "first order approximation" protocol employed by DV for assigning the attributes. With the features located as detailed above, SGS understands that DV identified the transformer closest to the service location (straight line distance) as its parent. Phase was assigned to the service location feature based on the phase of the parent transformer. SGS expects that this protocol correctly assigned parent (and phase) to a significant portion of the features, however this protocol will also obviously incorretly assign parent in many instances.To accurately identify parent for all 17992 service locations would require a significant GIS and field based project. SGS is willing to undertake a project of this magnitude at the discretion of TOA. In the meantime, SGS is maintaining (editing and adding to) this feature class as part of the ongoing GIS maintenance agreement that is in place between TOA and SGS. In lieu of a project designed to quality assess and correct for the data provided by DV, SGS will verify the locations of the features at the request of TOA via comparison of the unique identifier for a service location to the CIS address and Wake County parcel data address as issues arise with the OMS if SGS is directed to focus on select areas for verification by TOA. Additionally, as SGS adds features to this feature class, if error related to the phase and parent of an adjacent feature is uncovered during a maintenance, it will be corrected for as part of that maintenance.With respect to the additon of features moving forward, TOA will provide SGS with an export of CIS records for each SGS maintenance, SGS will tie new accounts to a physical location based on address, SGS will create a feature for the CIS account record in this feature class at the center of a parcel for a residential address or at the center of a parcel or over the correct (or approximately correct) location as determined via air photos or via TOA plans for commercial or other relevant areas, SGS will identify the parent of the service location as the actual transformer that feeds the service location, and SGS will identify the phase of the service address as the phase of it's parent.Service locations with an ObjectID of 1 through 17992 were originally physically located and attributed by DV.Service locations with an ObjectID of 17993 or higher were originally physically located and attributed by SGS.DV originated data are provided the Creation User attribute of DV, however if SGS has edited or verified any aspect of the feature, this attribute will be changed to SGS and a comment related to the edits will be provided in the SGS Edits Comments data field. SGS originated features will be provided the Creation User attribute of SGS. Reference the SGS Edits Comments attribute field Metadata for further information.

Geostrat Report – The Sequence Stratigraphy and Sandstone Play Fairways of the Late Jurassic Humber Group of the UK Central Graben

This non-exclusive report was purchased by the OGA from Geostrat as part of the Data Purchase tender process (TRN097012017) that was carried out during Q1 2017. The contents do not necessarily reflect the technical view of the OGA but the report is being published in the interests of making additional sources of data and interpretation available for use by the wider industry and academic communities.

The Geostrat report provides stratigraphic analyses and interpretations of data from the Late Jurassic to Early Cretaceous Humber Group across the UK Central Graben and includes a series of depositional sequence maps for eight stratigraphic intervals. Stratigraphic interpretations and tops from 189 wells (up to Release 91) are also included in the report.

The outputs as published here include a full PDF report, ODM/IC .dat format sequence maps, and all stratigraphic tops (lithostratigraphy, ages, sequence stratigraphy) in .csv format (for import into different interpretation platforms).

In addition, the OGA has undertaken to provide the well tops, stratigraphic interpretations and sequence maps in an ESRI ArcGIS format that is intended to facilitate the integration of these data into projects and data storage systems held by individual organisations. As part of this process, the Geostrat well names have been matched as far as possible to the OGA well names from the OGA Offshore Wells shapefile (as provided on the OGA’s Open Data website) and the original polygon files have been incorporated into an ArcGIS project. All the files within the GIS folder of this delivery have been created by the OGA. OGA web feature services (WFSs) have been included in the map document in this delivery. They replace the use of a shapefile or feature class to represent block, licence and quadrant data. By using a WFS, the data is automatically updated when it becomes available via the OGA.

A version of this delivery containing shapefiles for well tops, stratigraphic interpretations and sequence maps is available on the OGA’s Open Data website for use in other GIS software packages.

All releases included in the Data Purchase tender process that have been made openly available are summarised in a mapping application available from the OGA website. The application includes an area of interest outline for each of the products and an overview of which wellbores have been included in the products.

Geostrat Report – The Sequence Stratigraphy and Sandstone Play Fairways of the Late Jurassic Humber Group of the UK Central Graben This non-exclusive report was purchased by the NSTA from Geostrat as part of the Data Purchase tender process (TRN097012017) that was carried out during Q1 2017. The contents do not necessarily reflect the technical view of the NSTA but the report is being published in the interests of making additional sources of data and interpretation available for use by the wider industry and academic communities. The Geostrat report provides stratigraphic analyses and interpretations of data from the Late Jurassic to Early Cretaceous Humber Group across the UK Central Graben and includes a series of depositional sequence maps for eight stratigraphic intervals. Stratigraphic interpretations and tops from 189 wells (up to Release 91) are also included in the report. The outputs as published here include a full PDF report, ODM/IC .dat format sequence maps, and all stratigraphic tops (lithostratigraphy, ages, sequence stratigraphy) in .csv format (for import into different interpretation platforms). In addition, the NSTA has undertaken to provide the well tops, stratigraphic interpretations and sequence maps in an ESRI ArcGIS format that is intended to facilitate the integration of these data into projects and data storage systems held by individual organisations. As part of this process, the Geostrat well names have been matched as far as possible to the NSTA well names from the NSTA Offshore Wells shapefile (as provided on the NSTA’s Open Data website) and the original polygon files have been incorporated into an ArcGIS project. All the files within the GIS folder of this delivery have been created by the NSTA. NSTA web feature services (WFSs) have been included in the map document in this delivery. They replace the use of a shapefile or feature class to represent block, licence and quadrant data. By using a WFS, the data is automatically updated when it becomes available via the NSTA. A version of this delivery containing shapefiles for well tops, stratigraphic interpretations and sequence maps is available on the NSTA’s Open Data website for use in other GIS software packages. All releases included in the Data Purchase tender process that have been made openly available are summarised in a mapping application available from the NSTA website. The application includes an area of interest outline for each of the products and an overview of which wellbores have been included in the products.

Buildings_BACI

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   Buildings, structures, ruins, storage tanks, silos, water towers, Baltimore City Planimetric, Biophysical Resources, Land, Socio-Economic Resources, Capital




   Summary


   This data was created as a landbase feature as part of the planimetric data.


   Description


   This dataset represents photogrammetrically captured Building footprints => 100sq. ft. including storage tanks, silos, water towers, power plants, substations, and structures under construction and ruins. Feature capture rules:


   Buildings - Outline edge of roofline. All buildings shall be captured as polygons. In commercial areas especially, it is important that the plotted building represent the face of the building where it meets the sidewalk. Polygons shall be created for the outer boundary of the building when a partywall exists. Does not include sheds and small temporary structures. Attached garages shall be represented as part of the building structure. Large structures such as stadiums shall also be represented.

   Structures under construction or demolition - Delineate the rooflines of all buildings under construction as interpreted from aerial photography. If roofline is not visible compile visible foundation or walls

   Ruins - Delineate old overgrown areas of old structures that have been demolished or are in disrepair. Original data will be reclassified to define as separate subtype.

   Storage tanks, silos, and water towers - Outlines of all storage tanks, silos and water towers. . Original data will be reclassified to define as separate subtype.

   Power plants and substations - Outline of power plant and substation structure. . Original data will be reclassified to define as separate subtype.


   Credits

   There are no credits for this item.


   Use limitations


   Every reasonable effort has been made to ensure the accuracy of these data. The City of Baltimore, Maryland makes no representations nor warranties, either express or implied, regarding the accuracy of this information or its suitability for any particular purpose whatsoever. The data is licensed "as is" and the City of Baltimore will not be liable for its use or misuse by any party. Reliance of these data is at the risk of the user.


   Extent



   West -76.714715  East -76.525355 

   North 39.375162  South 39.193953 




   Scale Range

   There is no scale range for this item.

This archive contains a geology map of the general Roosevelt Hot Springs region, both in PDF and ArcGIS geodatabase formats, that was created as part of the Utah FORGE project. This archive contains an ArcGIS geodatabase containing the GIS feature classes and symbology for the geology of the general Roosevelt Hot Springs region in Utah.

This feature class is a spatial representation of the Sidewalk Cafe regulations in the New York City Zoning Resolution, Chapter 1, Article 4.”

All previously released versions of this data are available at BYTES of the BIG APPLE- Archive

The feature class indicates the specific types of motorized vehicles allowed on the designated routes and their seasons of use. The feature class is designed to be consistent with the MVUM (Motor Vehicle Use Map). It is compiled from the GIS Data Dictionary data and NRM Infra tabular data that the administrative units have prepared for the creation of their MVUMs. Only roads with a SYMBOL attribute value of 1, 2, 3, 4, 11, and 12 are Forest Service System roads and contain data concerning their availability for OHV (Off Highway Vehicle) use. This data is published and refreshed on a unit by unit basis as needed. Data for each individual unit must be verified and proved consistent with the published MVUMs prior to publication.The Forest Service's Natural Resource Manager (NRM) Infrastructure (Infra) is the agency standard for managing and reporting information about inventory of constructed features and land units as well as the permits sold to the general public and to partners. MetadataThis record was taken from the USDA Enterprise Data Inventory that feeds into the https://data.gov catalog. Data for this record includes the following resources: ISO-19139 metadata ArcGIS Hub Dataset ArcGIS GeoService OGC WMS CSV Shapefile GeoJSON KML https://apps.fs.usda.gov/arcx/rest/services/EDW/EDW_MVUM_01/MapServer/1 Metadata For complete information, please visit https://data.gov.

This digital dataset was created as part of a U.S. Geological Survey study, done in cooperation with the Monterey County Water Resource Agency, to conduct a hydrologic resource assessment and develop an integrated numerical hydrologic model of the hydrologic system of Salinas Valley, CA. As part of this larger study, the USGS developed this digital dataset of geologic data and three-dimensional hydrogeologic framework models, referred to here as the Salinas Valley Geological Framework (SVGF), that define the elevation, thickness, extent, and lithology-based texture variations of nine hydrogeologic units in Salinas Valley, CA. The digital dataset includes a geospatial database that contains two main elements as GIS feature datasets: (1) input data to the 3D framework and textural models, within a feature dataset called “ModelInput”; and (2) interpolated elevation, thicknesses, and textural variability of the hydrogeologic units stored as arrays of polygonal cells, within a feature dataset called “ModelGrids”. The model input data in this data release include stratigraphic and lithologic information from water, monitoring, and oil and gas wells, as well as data from selected published cross sections, point data derived from geologic maps and geophysical data, and data sampled from parts of previous framework models. Input surface and subsurface data have been reduced to points that define the elevation of the top of each hydrogeologic units at x,y locations; these point data, stored in a GIS feature class named “ModelInputData”, serve as digital input to the framework models. The location of wells used a sources of subsurface stratigraphic and lithologic information are stored within the GIS feature class “ModelInputData”, but are also provided as separate point feature classes in the geospatial database. Faults that offset hydrogeologic units are provided as a separate line feature class. Borehole data are also released as a set of tables, each of which may be joined or related to well location through a unique well identifier present in each table. Tables are in Excel and ascii comma-separated value (CSV) format and include separate but related tables for well location, stratigraphic information of the depths to top and base of hydrogeologic units intercepted downhole, downhole lithologic information reported at 10-foot intervals, and information on how lithologic descriptors were classed as sediment texture. Two types of geologic frameworks were constructed and released within a GIS feature dataset called “ModelGrids”: a hydrostratigraphic framework where the elevation, thickness, and spatial extent of the nine hydrogeologic units were defined based on interpolation of the input data, and (2) a textural model for each hydrogeologic unit based on interpolation of classed downhole lithologic data. Each framework is stored as an array of polygonal cells: essentially a “flattened”, two-dimensional representation of a digital 3D geologic framework. The elevation and thickness of the hydrogeologic units are contained within a single polygon feature class SVGF_3DHFM, which contains a mesh of polygons that represent model cells that have multiple attributes including XY location, elevation and thickness of each hydrogeologic unit. Textural information for each hydrogeologic unit are stored in a second array of polygonal cells called SVGF_TextureModel. The spatial data are accompanied by non-spatial tables that describe the sources of geologic information, a glossary of terms, a description of model units that describes the nine hydrogeologic units modeled in this study. A data dictionary defines the structure of the dataset, defines all fields in all spatial data attributer tables and all columns in all nonspatial tables, and duplicates the Entity and Attribute information contained in the metadata file. Spatial data are also presented as shapefiles. Downhole data from boreholes are released as a set of tables related by a unique well identifier, tables are in Excel and ascii comma-separated value (CSV) format.

This Quarter Section feature class depicts PLSS Second Divisions . PLSS townships are subdivided in a spatial hierarchy of first, second, and third division. These divisions are typically aliquot parts ranging in size from 640 acres to 160 to 40 acres, and subsequently all the way down to 2.5 acres. The data in this feature class was translated from the PLSSSecondDiv feature class in the original production data model, which defined the second division for a specific parcel of land. Metadata

Parcels_PROW_LU_2003_BACI

   File Geodatabase Feature Class


   Thumbnail Not Available

   Tags

   BES, Parcel, Land Use, Urban, Land




   Summary


   BES research


   Description


   Parcel-based land use (LU) and public rights-of-way (PROW), for Baltimore City. Land use (LU) codes were obtained from the 2003 MD Property View A&Tdatabase.


   Credits


   Jarlath O'Neil-Dunne, UVM Spatial Analysis Lab


   Use limitations


   Approved BES research only


   Extent



   West -76.713449  East -76.525885 

   North 39.374474  South 39.195049 




   Scale Range

   There is no scale range for this item.

This polygon feature class is a data set compiled by DWR employees in 2013 and represents the statewide Groundwater Management Plan (Plan) boundaries predating the Sustainable Groundwater Management Act (SGMA) requirements. Each polygon represents the area in which a Plan is to be implemented. The boundaries were provided to DWR by the affiliated public agency and compiled into a single statewide data set. Spatial plan boundaries were provided by agencies to DWR either via shapefiles or PDFs. PDFs were georeferenced and turned into GIS layers by DWR employees. This feature class is for legacy purposes only and will not be changed nor updated. It needs to be memorialized for spatial coverage of Groundwater Management Plans prior to SGMA and because SGMA only requires medium and high priority basins to have a Groundwater Sustainability Plan. The Plans outlined in this shapefile by medium and high priority basins are in effect until SGMA goes into effect. Some low and very low priority basins will likely use the existing plans to get funding for future basin management (since it is only voluntary for them to provide a Plan under SGMA, but they already have one in place). The data set is considered complete because of its legacy status. However, anyone using the data set will notice boundary inconsistencies, agency plan overlaps, mismatches, and other topology errors. The data set is based on boundary estimations and in the cases of medium and high priority basins will be outdated with in implementation of SGMA.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. This data set was not produced by DWR. Data were originally developed and supplied by each individual plan agency and compiled by DWR. 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.

(See USGS Digital Data Series DDS-69-E) A geographic information system focusing on the Cretaceous Travis Peak and Hosston Formations was developed for the U.S. Geological Survey's (USGS) 2002 assessment of undiscovered, technically recoverable oil and natural gas resources of the Gulf Coast Region. The USGS Energy Resources Science Center has developed map and metadata services to deliver the 2002 assessment results GIS data and services online. The Gulf Coast assessment is based on geologic elements of a total petroleum system (TPS) as described in Dyman and Condon (2005). The estimates of undiscovered oil and gas resources are within assessment units (AUs). The hydrocarbon assessment units include the assessment results as attributes within the AU polygon feature class (in geodatabase and shapefile format). Quarter-mile cells of the land surface that include single or multiple wells were created by the USGS to illustrate the degree of exploration and the type and distribution of production for each assessment unit. Other data that are available in the map documents and services include the TPS and USGS province boundaries. To easily distribute the Gulf Coast maps and GIS data, a web mapping application has been developed by the USGS, and customized ArcMap (by ESRI) projects are available for download at the Energy Resources Science Center Gulf Coast website. ArcGIS Publisher (by ESRI) was used to create a published map file (pmf) from each ArcMap document (.mxd). The basemap services being used in the GC map applications are from ArcGIS Online Services (by ESRI), and include the following layers: -- Satellite imagery -- Shaded relief -- Transportation -- States -- Counties -- Cities -- National Forests With the ESRI_StreetMap_World_2D service, detailed data, such as railroads and airports, appear as the user zooms in at larger scales. This map service shows the structural configuration of the top of the Travis Peak or Hosston Formations in feet below sea level. The map was produced by calculating the difference between a datum at the land surface (either the Kelly bushing elevation or the ground surface elevation) and the reported depth of the Travis Peak or Hosston. This map service also shows the thickness of the interval from the top of the Travis Peak or Hosston Formations to the top of the Cotton Valley Group.

The mission of the USGS Gap Analysis Program (GAP) is providing state, regional and national assessments of the conservation status of native vertebrate species and natural land cover types and facilitating the application of this information to land management activities. The PAD-US geodatabase is required to organize and assess the management status (i.e. apply GAP Status Codes) of elements of biodiversity protection. The goal of GAP is to 'keep common species common' by identifying species and plant communities not adequately represented in existing conservation lands. Common species are those not currently threatened with extinction. By identifying their habitats, gap analysis gives land managers and policy makers the information they need to make better-informed decisions when identifying priority areas for conservation. In cooperation with UNEP-World Conservation Monitoring Centre, GAP ensures PAD-US also supports global analyses to inform policy decisions by maintaining World Database for Protected Areas (WDPA) Site Codes and data for International Union for the Conservation of Nature (IUCN) categorized protected areas in the United States. GAP seeks to increase the efficiency and accuracy of PAD-US updates by leveraging resources in protected areas data aggregation and maintenance as described in "A Map of the Future", published following the PAD-US Design Project (July, 2009). While PAD-US was originally developed to support the GAP Mission stated above, the dataset is robust and has been expanded to support the conservation, recreation and public health communities as well. Additional applications become apparent over time.

Tags Social system, socio-economic resources, justice, BES, Environmental Justice, Environmental disamentities, Zoning Board of Appeals Summary For use in the environmental injustices study of Baltimore relating to patterns of environmental disamenties in relation to low income/minority communities. Description This feature class layer is a point dataset of appeals to the Zoning Board of Appeals (ZBA) from 1938 to 1999 concerning identified environmental disamentities. The data was gathered from records from the Zoning Board of Appeals decisions since 1931 relating to environmental disamentities and to be used to examine environmental injustices involving low income/minority communities in Baltimore. To see if environmental injustices exist in Baltimore, this point layer will be overlayed with race/income data to determine if patterns of inequity exist. Points were placed manually using the associated addresses from the ZBA_master dataset. The ID number associated with each point is related to its appeal number from the Zoning Board of Appeals. Multiple points on the data layer have the same ZBA_ID number, making it a one-to-many relationship. This layer can be joined with the ZBA_master table using the "ZBA_point_relationship" and the field "ZBA_ID". Credits UVM Spatial Analysis Lab Use limitations None. There are no restrictions on the use of this dataset. The authors of this dataset make no representations of any kind, including but not limited to the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the data. Extent West -76.708848 East -76.527906 North 39.371642 South 39.199548 This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The Geodatabase to Shapefile Warning Tool examines feature classes in input file geodatabases for characteristics and data that would be lost or altered if it were transformed into a shapefile. Checks include:
1) large files (feature classes with more than 255 fields or over 2GB), 2) field names longer than 10 characters
string fields longer than 254 characters, 3) date fields with time values 4) NULL values, 5) BLOB, guid, global id, and raster field types, 6) attribute domains or subtypes, and 7) annotation or topology

The results of this inspection are written to a text file ("warning_report_[geodatabase_name]") in the directory where the geodatabase is located. A section at the top provides a list of feature classes and information about the geodatabase as a whole. The report has a section for each valid feature class that returned a warning, with a summary of possible warnings and then more details about issues found.

The tool can process multiple file geodatabases at once. A separate text file report will be created for each geodatabase. The toolbox was created using ArcGIS Pro 3.7.11.

For more information about this and other related tools, explore the Geospatial Data Curation toolkit

The feature class is a sheet of the Regional Technical Charter 1:5000. The data was received by the Molise Region in shapefile format. The feature class is a sheet of the Regional Technical Charter 1:5000. The data was received by the Molise Region in shapefile format. The feature class is a sheet of the Regional Technical Charter 1:5000. The data was received by the Molise Region in shapefile format. The feature class is a sheet of the Regional Technical Charter 1:5000. The data was received by the Molise Region in shapefile format. The feature class is a sheet of the Regional Technical Charter 1:5000. The data was received by the Molise Region in shapefile format.