Facebook
TwitterThe establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making. BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions. Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself. For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise. Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery. See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt
Facebook
TwitterCurrently filtered for Storm Date is after 12/1/2023Purpose: This is a feature layer of tornado swaths for the NWS Damage Assessment Toolkit.The National Weather Service (NWS) Damage Assessment Toolkit (DAT) has been utilized experimentally since 2009 to assess damage following tornadoes and convective wind events. The DAT is a GIS-based framework for collecting, storing, and analyzing damage survey data, utilizing the Enhanced Fujita (EF) scale for the classification of damage. Data collected from individual locations via mobile device are transmitted to a central geospatial database where they are quality controlled and analyzed to assign the official EF rating. In addition to the individual point, the data are analyzed to generate track centerlines and damage swaths. High resolution satellite imagery and radar data, through partnership with the NASA Short-term Prediction Research and Transition Center, are also available to aid in the analysis. The subsequent dataset is then made available through a web-based graphical interface and GIS services.Here is the full REST service: https://services.dat.noaa.gov/arcgis/rest/services/nws_damageassessmenttoolkitGeoplatform website: https://communities.geoplatform.gov/disasters/noaa-damage-assessment-toolkit-dat/More InformationWelcome to the National Weather Service Damage Assessment Toolkit. Data on this interface is collected during NWS Post-Event Damage Assessments. While the data has been quality controlled, it is still considered preliminary. Official statistics for severe weather events can be found in the Storm Data publication, available from the National Centers for Environmental Information (NCEI) at: https://www.ncdc.noaa.gov/IPS/sd/sd.html Questions regarding this data can be addressed to: parks.camp@noaa.gov.
Facebook
TwitterThe Oregon Watershed Restoration Inventory database (OWRI) contains information about completed restoration projects that were implemented in Oregon beginning in 1995. The complete dataset consists of point, line, and polygon features. Data for projects not funded by the Oregon Watershed Enhancement Board (OWEB) are acquired through a voluntary "Annual Call for Data"; while reporting is required for projects funded by OWEB and Oregon Department of Fish and Wildlife R & E grant programs. Restoration practitioners submit a standardized reporting form and attach project location maps. Once acquired, data sheets and maps are each assigned a unique project identification number. This number links spatial project data with tabular project data that are stored in a relational database using Microsoft SQL software.
Facebook
TwitterThis draft data is being submitted to FEMA to update the National Flood Hazard Layer (NFHL) and Flood Insurance Rate Maps (FIRMs). It is subject to change until FEMA issues the final data. The Layer is symbolized by the field, "ZONE_SUBTY" showing the following:"1% Annual Chance Flood Hazard" = blank and null values"Future Conditions 1% Annual Chance Flood Hazard" = 0300"0.2% Annual Chance Flood Hazard" = 0500"Regulatory Floodway" = 1100Workspace: \srvrgisfs1-1\gisdata\WebApps\WSE_DraftFloodplainViewer\DraftFloodplainViewer_CloudSource data: Database Connections\OS@gisAncillary@gissql.sde\gisAncillary.DBO.AppData\Published in Feb 2023 by the GIS Team to update the symbology. Published to ArcGIS Online Cloud
Facebook
TwitterNOTE: This dataset holds 'static' data that we don't expect to change. We have removed it from the SDE database and placed it in ArcGIS Online, but it is still considered part of the SGID and shared on opendata.gis.utah.gov.
Facebook
TwitterA combination of stormwater system data throughout Stark County, Ohio. The data is combined using an ETL via the data interoperability extension for ArcGIS Pro. Each weekend, the ETL is automatically ran via Python/Windows Task Scheduler to update the data with any changes from the past week from each of the source datasets. The source data is stored in ArcGIS SDE databases that Stark County GIS (SCGIS) provides for departments, cities, villages, and townships within the county. SCGIS currently maintains SDE databases for Canton, Alliance, Louisville, North Canton, Beach City, Easton Canton, Minerva, Meyers Lake, Stark County Engineer (SCE), and each of the townships. In addition to those datasets (which are updated weekly), this layer also includes data from the cities of Massillon and Canal Fulton, which are not stored in databases maintained by SCGIS. Data for those two cities is updated separately as new iterations become available.As this layer encompasses the entire county, source feature classes are consolidated into 4 layers to improve performance on ArcGIS Online. Discharge points are the point at which water exits part of the stormwater system, such as the outlet of a pipe or ditch. It includes outfalls defined under NPDES Phase II. Structures includes both inlets (catch basins, yard drains, etc.) and manholes. Pipes includes storm sewers, as well as culverts (pipes in which both ends are daylit). Finally, the ditches layer includes roadside ditches, as well as off-road ditches in some areas/instances.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
NOTE: This dataset holds 'static' data that we don't expect to change. We have removed it from the SDE database and placed it in ArcGIS Online, but it is still considered part of the SGID and shared on opendata.gis.utah.gov. The Utah Geochronology Database contains ages and related dating information of sampled geologic materials (soil and rock) using argon (40Ar/39Ar), optically-stimulated luminescence (OSL), or radiocarbon (14C) dating methods and were analyzed for a variety of geologic-related projects by the UGS and others. These ages were used in fault trench investigations to determine the timing of past earthquakes and to develop other paleoseismic parameters, in the dating of basalt flows for eruption histories and in dating fault movement, and similar projects.Since geochronologic methods have significantly evolved and improved through time, older data is often not as reliable or usable as more recently dated materials. The user should use caution in using this data, as significant knowledge and experience is often needed to interpret and apply geochronologic data to projects correctly.As the database is expanded in the future, age results from other geochronologic dating methods are anticipated to be added. Various geochronologic data from geologic mapping projects may be found here. Donations of geochronologic data in Utah are appreciated, so that these data can be permanently archived and discoverable and available to all users. Contact the UGS for more details.The GeochronProject feature class contains metadata specific to each geochronology project, including the organization and Principal Investigator who conducted the project (where known).
Facebook
TwitterPrivate Green Stormwater Infrastructure Project data in a tabular relational database. Location point data is digitized manually with a tracking number. Tabular data is queried and joined to point feature class before export to GEODB2 SDE databases.
Facebook
TwitterThis dataset represents wetland CEFs identified during the development review process since 1995. Prior to 1995, data is either unavailable or lost.Wetland CEFs were digitized from construction plans, environmental assessments, and City of Austin staff field observations. Features were digitized into a versioned SDE database in ArcMap. Wetland delineation may be determined through a process of negotiation with land development interests and generally reflect the most protective arrangement that could be obtained. Additionally, “fringe wetlands” were drawn using a standard 2’ width on either side of a waterway.
Facebook
TwitterR2GIS Combined county boundary data from TANA, Navteq and Census: TANA county boundaries.(static.R2GIS.TANA_BOUNDARY_COUNTY) for all of Region 2 except the Virgin Islands which were not found in the data set. TANA provided more detailed county coastlines. Navteq.County(static.R2GIS.NAVTEQ_BOUNDARY_2014_COUNTY) for the smaller surrounding islands of the Virgin Islands which had more detail than the CENSUS representations. Counties (CENSUS) VI. The CENSUS county boundaries were used only for the three main islands of the Virgin Islands which had finer detail than that provided by Navteq. The Dynamap(R)/2000 County Boundary file is a non-generalized polygon layer that represents all U.S. government-defined entities named County. A County is a type of governmental unit that is the primary legal subdivision of every U.S. state. In Louisiana, the County-equivalent entity is 'parish.' In Alaska, the statistically equivalent entities are the organized 'boroughs,' 'city and boroughs,' 'municipalities' and 'census areas.' The Dynamap(R)/2000 County Boundary file is a non-generalized polygon layer that represents all U.S. government-defined entities named County. A County is a type of governmental unit that is the primary legal subdivision of every U.S. state. In Louisiana, the County-equivalent entity is 'parish.' In Alaska, the statistically equivalent entities are the organized 'boroughs,' 'city and boroughs,' 'municipalities' and 'census areas.'
Facebook
TwitterBY USING THIS WEBSITE OR THE CONTENT THEREIN, YOU AGREE TO THE TERMS OF USE.
The downloaded SSURGO data included an ArcGIS Shapefile of the soil type features for Oakland County, tabular data in text file format, and an empty pre-formatted Microsoft Access database containing queries, macros and reports. The Shapefile was intially projected in State Plane Michigan South Meters NAD 83, but was then reprojected by Oakland County staff to State Plane Michigan South International Feet NAD 83. The USDA-NRCS provided instructions for automatically importing the tabular text files into the Microsoft Access database. The key attribute of this feature class is the map unit key (MUSYM field), which relates the polygon features to the SoilAttribute table stored within SDE. The related SoilAttribute table in SDE contains some of the tabular data which was initially imported into the aforementioned Microsoft Access database.
Facebook
TwitterThis dataset represents Rock Outcrop Critical Environmental Features (CEFs) identified during the development review process since 1995. Prior to 1995, data is either unavailable or lost. Rock Outcrop CEFs were digitized from construction plans, environmental assessments, and City of Austin staff field observations into a versioned SDE database using ArcMap.
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This dataset contains the official listing of all public educational organizations in Connecticut. Data elements include district name, school name, organization type, organization code, address, open date, interdistrict magnet status and grades offered.
Included data are collected by the CT State Department of Education (CSDE) through the Directory Manager (DM) portal in accordance with Connecticut General Statute (C.G.S.) 10-4. This critical information is used by other data collection systems and for state and federal reporting.
For more information regarding DM, please visit http://www.csde.state.ct.us/public/directorymanager/default.asp
Facebook
Twitterhttp://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse/conditionsUnknownhttp://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse/conditionsUnknown
https://services.cuzk.gov.cz/registry/codelist/ConditionsApplyingToAccessAndUse/copyrighthttps://services.cuzk.gov.cz/registry/codelist/ConditionsApplyingToAccessAndUse/copyright
SDE database of Slope deformations register contains basic data of registered and authenticated slope deformations (landslides, solifluction, rock falls, etc.). Landslides are classified as active, suspended and stabilized. Database is based on verified mapping in 1 : 10,000 and landslide description and photodocumentation. Data actuality, professionality and its processing is maintained by experts from CGS.
Facebook
TwitterThis dataset represents CEF buffers identified during the development review process since 1995. Prior to 1995, data is either unavailable or lost. CEF buffers were digitized from construction plans, environmental assessments, and City of Austin staff field observations into a versioned SDE database using ArcMap. Actual buffers size for any particular feature may be determined through a process of negotiation with land development interests, and may differ from standard dimensions stated in the Land Development Code.
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
NOTE: This dataset is an older dataset that we have removed from the SGID and 'shelved' in ArcGIS Online. There may (or may not) be a newer vintage of this dataset in the SGID.NOTE: This dataset holds 'static' data that we don't expect to change. We have removed it from the SDE database and placed it in ArcGIS Online, but it is still considered part of the SGID and shared on opendata.gis.utah.gov.
Facebook
TwitterThis dataset represents CEF buffers identified during the development review process since 1995. Prior to 1995, data is either unavailable or lost. CEF buffers were digitized from construction plans, environmental assessments, and City of Austin staff field observations into a versioned SDE database using ArcMap. Actual buffers size for any particular feature may be determined through a process of negotiation with land development interests, and may differ from standard dimensions stated in the Land Development Code.
Facebook
TwitterThis Feature Service was created on request of C-5 Fire Department Assistant Fire Chief John Alquist on 1/24/2022, for anyone in working within the C-5 Bowie County Area for hydrant maintenance.It works with the web map of C-5 Hydrants Map which supports the desktop web appliation C-5 Hydrants. Please use when working on the C-5 Hydrants desktop.All services except the image layer are hosted on ArcOnline and not affected by the authoritive data on GIS SDE, the image layer utilizes data from Texarkana Water Utilities GIS DepartmentThe thumbnail uses a static QR code for easy scanning on a mobile device.The information was created by:Pulling in the volunteer fire districts from the COG, and running a definition query to show only C-5.Pulling in Hydrants from the SDE (the authoritive data), and saving them in a Auxiliary database under a feature database called water.Pulling in Water Mains from the SDE (the authoritive data), and saving them in a Auxiliary database under a feature database called water.Selecting by location using the Auxiliary databases Hydrants and the Volunteer Fire Districts as the selecting item, give a 30 ft buffer.Then create a field in the attribute table called District.Run a mass calculation to chanage the selected to change the selected records in the District to say Near C-5.Run a another selecting by location using the Auxiliary databases Hydrants and the Volunteer Fire Districts as the selecting item, but do not give a buffer. Run a mass calculation to chanage the selected to change the selected records in the District to say C-5.Run a definition query to show only Districts equally to C-5 or Districts equally to Near C-5.Selecting by location using the Auxiliary databases Water Mains and the Volunteer Fire Districts as the selecting item, give a 30 ft buffer, select the check box to allow invert.The lines outside of the C-5 should be selected, delete them. Now go to the Water Mains from the Auxiliary database and change the symbology to be unique, and filter by pipe size. Change the sizes to range from 1 to 3.5 in line thickness with each size up a little darker blue. GIS uses three-step verification process for any correction, or addition.This web map is pulled from the listed layers below. Please note: This layer is NOT updated. If you encounter a issue with the addresses please reach out to us at the GIS department.See details on the right for when data was last updated categories and full length of credits. Layer availability is unaffected during updates.If you have any questions regarding ArcOnline, please feel free to reach out to the GIS department at gis@txkusa.org.
Facebook
TwitterThis NYC Reservoirs Watershed Areas (HUC 12) GIS layer was derived from the 12-Digit National Watershed Boundary Database (WBD) at 1:24,000 for EPA Region 2 and Surrounding States. HUC 12 polygons were selected from the source based on interactively comparing these HUC 12s in our GIS with images of the New York City's Water Supply System Map found at http://www.nyc.gov/html/dep/html/drinking_water/wsmaps_wide.shtml. The 12 digit Hydrologic Units (HUCs) for EPA Region 2 and surrounding states (Northeastern states, parts of the Great Lakes, Puerto Rico and the USVI) are a subset of the National Watershed Boundary Database (WBD), downloaded from the Natural Resources Conservation Service (NRCS) Geospatial Gateway and imported into the EPA Region 2 Oracle/SDE database. This layer reflects 2009 updates to the WBD that included new boundary data for New York and New Jersey.
Facebook
TwitterU.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
These grasslands were digitized from construction plans, environmental assessments, and City of Austin staff field observations into a versioned SDE database using ArcMap. Actual areas for any particular feature may be fluctuate due to antecedent rainfall, subsequent development activity or the invasion of woody species, Grasslands are not, at the time of this writing, a protected Critical Environmental Feature.
Facebook
TwitterThe establishment of a BES Multi-User Geodatabase (BES-MUG) allows for the storage, management, and distribution of geospatial data associated with the Baltimore Ecosystem Study. At present, BES data is distributed over the internet via the BES website. While having geospatial data available for download is a vast improvement over having the data housed at individual research institutions, it still suffers from some limitations. BES-MUG overcomes these limitations; improving the quality of the geospatial data available to BES researches, thereby leading to more informed decision-making. BES-MUG builds on Environmental Systems Research Institute's (ESRI) ArcGIS and ArcSDE technology. ESRI was selected because its geospatial software offers robust capabilities. ArcGIS is implemented agency-wide within the USDA and is the predominant geospatial software package used by collaborating institutions. Commercially available enterprise database packages (DB2, Oracle, SQL) provide an efficient means to store, manage, and share large datasets. However, standard database capabilities are limited with respect to geographic datasets because they lack the ability to deal with complex spatial relationships. By using ESRI's ArcSDE (Spatial Database Engine) in conjunction with database software, geospatial data can be handled much more effectively through the implementation of the Geodatabase model. Through ArcSDE and the Geodatabase model the database's capabilities are expanded, allowing for multiuser editing, intelligent feature types, and the establishment of rules and relationships. ArcSDE also allows users to connect to the database using ArcGIS software without being burdened by the intricacies of the database itself. For an example of how BES-MUG will help improve the quality and timeless of BES geospatial data consider a census block group layer that is in need of updating. Rather than the researcher downloading the dataset, editing it, and resubmitting to through ORS, access rules will allow the authorized user to edit the dataset over the network. Established rules will ensure that the attribute and topological integrity is maintained, so that key fields are not left blank and that the block group boundaries stay within tract boundaries. Metadata will automatically be updated showing who edited the dataset and when they did in the event any questions arise. Currently, a functioning prototype Multi-User Database has been developed for BES at the University of Vermont Spatial Analysis Lab, using Arc SDE and IBM's DB2 Enterprise Database as a back end architecture. This database, which is currently only accessible to those on the UVM campus network, will shortly be migrated to a Linux server where it will be accessible for database connections over the Internet. Passwords can then be handed out to all interested researchers on the project, who will be able to make a database connection through the Geographic Information Systems software interface on their desktop computer. This database will include a very large number of thematic layers. Those layers are currently divided into biophysical, socio-economic and imagery categories. Biophysical includes data on topography, soils, forest cover, habitat areas, hydrology and toxics. Socio-economics includes political and administrative boundaries, transportation and infrastructure networks, property data, census data, household survey data, parks, protected areas, land use/land cover, zoning, public health and historic land use change. Imagery includes a variety of aerial and satellite imagery. See the readme: http://96.56.36.108/geodatabase_SAL/readme.txt See the file listing: http://96.56.36.108/geodatabase_SAL/diroutput.txt