Facebook
Twitterhttps://services3.arcgis.com/6LvtIYUSMXW8Tb6o/ArcGIS/rest/serviceshttps://services3.arcgis.com/6LvtIYUSMXW8Tb6o/ArcGIS/rest/services
Services:2015_Parking (FeatureServer)AGO_MAP_2019 (FeatureServer)Bike_Racks_2020 (FeatureServer)BikeParking2017 (FeatureServer)Chicago_Central_Business_District (FeatureServer)Chicago_Wards_hosted (FeatureServer)ChicagoMayHwys (FeatureServer)Control_Points_Interlockings (FeatureServer)ControlPoints_Interlockings (FeatureServer)Cook_County_Districts_hosted (FeatureServer)CTA_Bus_Routes (FeatureServer)CTA_Bus_Routes_2019 (FeatureServer)cta_rail_lines (FeatureServer)CTABusRoutes2019 (FeatureServer)FRA_Crossings (FeatureServer)FreightRailroads (FeatureServer)Grade_Crossings (FeatureServer)Illinois_House_Districts (FeatureServer)Illinois_Senate_Districts (FeatureServer)Lines_COVID19 (FeatureServer)Metra_Bridges (FeatureServer)Metra_facilities (FeatureServer)metra_lines_2018 (FeatureServer)Metra_Routes_Test (FeatureServer)metra_stations_2018 (FeatureServer)MetraLines_2016 (FeatureServer)MetraLines2017 (FeatureServer)MetraLines2019_CreateRoutes (FeatureServer)MetraPoliceBeats (FeatureServer)MetraStations2017new (FeatureServer)Municipalities (FeatureServer)NICTD_South_Shore_Line (FeatureServer)NICTD_Stations (FeatureServer)Pace_ParkNRide_Facilities (FeatureServer)Pace_Routes_03_25_2019 (FeatureServer)PaceRoutes2020 (FeatureServer)Parking_Lots_2016 (FeatureServer)parking_lots_2017 (FeatureServer)Parking_Survey_2018_AGO_Published (FeatureServer)Parking_Survey_2018_Final (FeatureServer)Parking_Survey_2019_Final (FeatureServer)ParkingLots2017 (FeatureServer)Police_Beats_2020_Draft (FeatureServer)Police_tows (FeatureServer)Six_County_Service_Area (FeatureServer)Stations_COVID19 (FeatureServer)Tie_Substations (FeatureServer)TrainsPerDay (FeatureServer)US_Congressional_Districts (FeatureServer)Yards_Points (FeatureServer)yards_points_2019 (FeatureServer)Yards_Polygons (FeatureServer)yards_polygons_2018 (FeatureServer)
Facebook
TwitterThis data set contains geolocation information of the infrastructure locations for the SnowEx20 Intensive Observation Period (IOP) and Time Series (TS) campaigns. Available scientific infrastructure locations in this data set are tower and sensor locations, aircraft flight lines, planned and actual snow pit locations, and time-lapse camera locations. Additionally, this data set contains areal snow depth and tree density classification matrix over the Grand Mesa, CO study area.
Facebook
TwitterThe 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.
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
ArcGIS Map Packages and GIS Data for Gillreath-Brown, Nagaoka, and Wolverton (2019)
**When using the GIS data included in these map packages, please cite all of the following:
Gillreath-Brown, Andrew, Lisa Nagaoka, and Steve Wolverton. A Geospatial Method for Estimating Soil Moisture Variability in Prehistoric Agricultural Landscapes, 2019. PLoSONE 14(8):e0220457. http://doi.org/10.1371/journal.pone.0220457
Gillreath-Brown, Andrew, Lisa Nagaoka, and Steve Wolverton. ArcGIS Map Packages for: A Geospatial Method for Estimating Soil Moisture Variability in Prehistoric Agricultural Landscapes, Gillreath-Brown et al., 2019. Version 1. Zenodo. https://doi.org/10.5281/zenodo.2572018
OVERVIEW OF CONTENTS
This repository contains map packages for Gillreath-Brown, Nagaoka, and Wolverton (2019), as well as the raw digital elevation model (DEM) and soils data, of which the analyses was based on. The map packages contain all GIS data associated with the analyses described and presented in the publication. The map packages were created in ArcGIS 10.2.2; however, the packages will work in recent versions of ArcGIS. (Note: I was able to open the packages in ArcGIS 10.6.1, when tested on February 17, 2019). The primary files contained in this repository are:
Raw DEM and Soils data
Digital Elevation Model Data (Map services and data available from U.S. Geological Survey, National Geospatial Program, and can be downloaded from the National Elevation Dataset)
DEM_Individual_Tiles: Individual DEM tiles prior to being merged (1/3 arc second) from USGS National Elevation Dataset.
DEMs_Merged: DEMs were combined into one layer. Individual watersheds (i.e., Goodman, Coffey, and Crow Canyon) were clipped from this combined DEM.
Soils Data (Map services and data available from Natural Resources Conservation Service Web Soil Survey, U.S. Department of Agriculture)
Animas-Dolores_Area_Soils: Small portion of the soil mapunits cover the northeastern corner of the Coffey Watershed (CW).
Cortez_Area_Soils: Soils for Montezuma County, encompasses all of Goodman (GW) and Crow Canyon (CCW) watersheds, and a large portion of the Coffey watershed (CW).
ArcGIS Map Packages
Goodman_Watershed_Full_SMPM_Analysis: Map Package contains the necessary files to rerun the SMPM analysis on the full Goodman Watershed (GW).
Goodman_Watershed_Mesa-Only_SMPM_Analysis: Map Package contains the necessary files to rerun the SMPM analysis on the mesa-only Goodman Watershed.
Crow_Canyon_Watershed_SMPM_Analysis: Map Package contains the necessary files to rerun the SMPM analysis on the Crow Canyon Watershed (CCW).
Coffey_Watershed_SMPM_Analysis: Map Package contains the necessary files to rerun the SMPM analysis on the Coffey Watershed (CW).
For additional information on contents of the map packages, please see see "Map Packages Descriptions" or open a map package in ArcGIS and go to "properties" or "map document properties."
LICENSES
Code: MIT year: 2019 Copyright holders: Andrew Gillreath-Brown, Lisa Nagaoka, and Steve Wolverton
CONTACT
Andrew Gillreath-Brown, PhD Candidate, RPA Department of Anthropology, Washington State University andrew.brown1234@gmail.com β Email andrewgillreathbrown.wordpress.com β Web
Facebook
TwitterAttribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
These boundaries define the regions based on terrestrial and marine areas. These are intended to be used in by CA Nature to support activities related to Executive Order N-82-20. These include California's 30x30 effort, Climate Smart Land Strategies, and equitable access to open space. This layer is derived from the 4th California Climate Assessment regions, and enhanced using the California County Boundaries dataset (version 19.1) maintained by the California Department of Forestry and Fire Protection's Fire Resource Assessment Program, and the 3 Nautical Mile marine boundary for California sourced from the California Department of Fish and Wildlife.
Facebook
TwitterLearn Geographic Mapping with Altair, Vega-Lite and Vega using Curated Datasets
Complete geographic and geophysical data collection for mapping and visualization. This consolidation includes 18 complementary datasets used by 31+ Vega, Vega-Lite, and Altair examples π. Perfect for learning geographic visualization techniques including projections, choropleths, point maps, vector fields, and interactive displays.
Source data lives on GitHub and can also be accessed via CDN. The vega-datasets project serves as a common repository for example datasets used across these visualization libraries and related projects.
airports.csv), lines (like londonTubeLines.json), and polygons (like us-10m.json).windvectors.csv, annual-precip.json).This pack includes 18 datasets covering base maps, reference points, statistical data for choropleths, and geophysical data.
| Dataset | File | Size | Format | License | Description | Key Fields / Join Info |
|---|---|---|---|---|---|---|
| US Map (1:10m) | us-10m.json | 627 KB | TopoJSON | CC-BY-4.0 | US state and county boundaries. Contains states and counties objects. Ideal for choropleths. | id (FIPS code) property on geometries |
| World Map (1:110m) | world-110m.json | 117 KB | TopoJSON | CC-BY-4.0 | World country boundaries. Contains countries object. Suitable for world-scale viz. | id property on geometries |
| London Boroughs | londonBoroughs.json | 14 KB | TopoJSON | CC-BY-4.0 | London borough boundaries. | properties.BOROUGHN (name) |
| London Centroids | londonCentroids.json | 2 KB | GeoJSON | CC-BY-4.0 | Center points for London boroughs. | properties.id, properties.name |
| London Tube Lines | londonTubeLines.json | 78 KB | GeoJSON | CC-BY-4.0 | London Underground network lines. | properties.name, properties.color |
| Dataset | File | Size | Format | License | Description | Key Fields / Join Info |
|---|---|---|---|---|---|---|
| US Airports | airports.csv | 205 KB | CSV | Public Domain | US airports with codes and coordinates. | iata, state, `l... |
Facebook
TwitterA wide variety of state-wide GIS layers with periodic updates from various agencies and sources: Borough Parcels β’ North Slope Borough Boundaries β’ ACMP Coastal Districts β’ ACMP Coastal Zone Management β’ ACMP Permit Notification Area β’ ACMP Special Area Management Plan β’ ADEC Contingency Planning Regions β’ ADFG Game Management Units β’ ANCSA Corporations β’ Administrative Large Parcels β’ Alaska Seaward Boundary β’ Borough Boundary β’ Conservation System Units β’ DNR Regions β’ Election District 1994 β’ Election District 2002 β’ Election District 2006 β’ Incorporated City Boundary β’ Recording Districts β’ Rural Education Attendance Areas β’ Soil and Water Conservation Districts β’ State Park Units through ILMA Cultural β’ Cities β’ GNIS Concise Features β’ GNIS Features β’ GNIS Historical Features β’ GNIS Populated Places β’ Populated Places β’ Recording District Offices β’ USGS Place Names DNR Land Records β’ Base β’ Airstrips 63,360 β’ Alaska Seaward Boundary β’ BLM Monument - Digitized β’ BLM Monument - GCDB β’ BLM Monument - SDMS β’ Borough Boundary β’ Conservation System Units β’ Fiberoptic Cables 63,360 β’ Highways 63,360 β’ Hydrography 63,360 β’ Incorporated City Boundary β’ National Geodetic Survey Monuments β’ Pipelines 63,360 β’ Power Lines 63,360 β’ Railroads 63,360 β’ Recording Districts β’ Secondary Roads 63,360 β’ Sections β’ State Control Monuments β’ Survey Boundary β’ Telephone Lines 63,360 β’ Townships β’ Trails 63,360 β’ Land Estate β’ Agreement, Settlement, Reconveyance β’ Easements β’ Federal Actions β’ Land Disposal - Available β’ Land Disposal - Conveyed β’ Land Disposal - Other β’ Management Agreement β’ Mental Health Trust Land β’ Municipal Entitlement β’ Municipal Tideland β’ Native Allotment β’ Other Activities β’ Other State Acquired Land - LE β’ Permit or Lease - LE β’ RS2477 Trails β’ Resource Sale β’ State Selected or Top Filed Land - LE β’ State Tentatively Approved or Patented - LE β’ Mineral Estate β’ Agreement, Settlement, Reconveyance β’ Annual Placer Mining Application β’ Federal Actions β’ Federal Mining Claims β’ Leasehold Location β’ Management Agreement β’ Mental Health Trust Land β’ Mineral Order β’ Native Allotment β’ Oil & Gas Lease Sale Tracts β’ Other State Acquired Land - ME β’ Permit or Lease - ME β’ State Mining Claim β’ State Prospecting Site β’ State Selected or Top Filed Land - ME β’ State Tentatively Approved or Patented - ME β’ Well Site β’ Ownership β’ ANILCA Top Filed - All β’ Agreement, Settlement, Reconveyance β’ Federal Actions β’ Land Disposal - Conveyed β’ Management Agreement β’ Mental Health Trust Land β’ Municipal Entitlement β’ Municipal Tideland β’ Native Allotment β’ Other State Acquired Land - All β’ RS2477 Trails β’ State Selected Land - ALL β’ State Tentatively Approved or Patented - All β’ Surface Classification β’ Disposable Interest β’ General Land β’ Habitat Land β’ Legislatively Designated Areas β’ Miscellaneous β’ Recreation Land β’ Reserved Use β’ Special Use Land β’ Water Estate β’ Instream Flow Reservation β’ Subsurface Temporary Water Use Permit β’ Subsurface Water Rights β’ Surface Temporary Water Use Permit β’ Surface Water Rights Environmental β’ Environmental Sensitivity Index β’ ESI North Slope β’ ESI Northwest Arctic β’ NOAA Shorezone β’ Shorezone Biobands β’ Shorezone Combined Video and Photo Pts β’ Shorezone Photo Points β’ Shorezone Unit Information β’ Shorezone Video Points General Land Status β’ BLM Native Allotment β’ Borough Parcels β’ Federal Parcels β’ GLS Current Edition β’ State Land Activity by Case β’ State Land Activity by Feature β’ State Parcels β’ State, Federal, Borough Parcels Graticule β’ Latitude Longitude Lines 1 Degree β’ Latitude Longitude Lines 2 Degrees β’ NOAA Nautical Charts β’ PLSS Section Grid β’ PLSS Township Grid β’ State Plane Zone β’ USGS Quadrangle 250,000 β’ USGS Quadrangle 63,360 β’ UTM Zones Monuments β’ BLM Monument - Digitized β’ BLM Monument - GCDB β’ BLM Monument - SDMS β’ National Geodetic Survey Monuments β’ State Control Monuments Natural Resources β’ Aquaculture and Tidelands β’ Tidal Conveyances β’ Tidal Easements β’ Tidal Leases β’ Geothermal β’ Mining β’ Alaska Resource Data File β’ Coal Basin β’ Coal Districts β’ Coal Field β’ Coal Occurrence β’ Coal Unit β’ Federal Mining Claims β’ Mining Districts β’ Placer Districts β’ Significant Metalliferous Lode Deposits β’ State Mining Claim β’ State Mining Claim Closed β’ State Mining Lease β’ State Offshore Permit or Lease β’ State Prospecting Site β’ Oil and Gas β’ Oil And Gas Basins β’ Statewide Unit Tracts β’ Statewide PA Boundaries β’ Statewide PA Tracts β’ Statewide Sale Boundaries β’ Statewide Sale Tracts β’ Statewide Unit Boundaries β’ Water β’ Hydrologic Units β’ Navigable Water β’ Water Information Parks and Recreation Physical Features β’ Alaska Coast 1,000,000 β’ Alaska Coast 250,000 β’ Alaska Coast 63,360 β’ Alaska Coast 63,360 Excluding Small Islands β’ Alaska Coast Simplified β’ Canada Coast β’ Contours 1,000,000 β’ Elevation Points 1,000,000 β’ Glaciers 1,000,000 β’ Glaciers 2,000,000 β’ Hydrography 1,000,000 β’ Hydrography 2,000,000 β’ Hydrography 63,360 β’ Major Lakes β’ Major Rivers β’ Russia Coast β’ Summit Points 1,000,000 β’ Biotic β’ ANHP Biotic Areas β’ Anadromous Fish Line β’ Anadromous Fish Point β’ Caribou β’ Dall Sheep Point β’ Dall Sheep Polygon β’ Duck Habitat Areas β’ Eagle Point β’ Eagle Polygon β’ Moose Habitat Areas β’ Seabirds Point β’ Seabirds Polygon β’ Seal Point β’ Seal Polygon β’ Swan Polygon β’ Trumpeter Swan β’ Environmental β’ Geology β’ Beikman 1980 β’ Exploration Points β’ Geotech Photo Points β’ Hydrology Base β’ NHD Flowline β’ NHD Waterbody β’ Watersheds β’ Ice Study 2012 β’ Open Lead Points β’ Permafrost β’ Wetlands β’ Reference β’ Administrative β’ Game Management Units β’ Bridges β’ CEA Service Area β’ Crossings β’ Dam Sites β’ Legacy β’ Transmission Lines Corridor β’ Recreation β’ Trails β’ Transportation β’ Local Airstrip Points Transportation β’ Airstrips 63,360 β’ DOT Centerline Milepost β’ DOT Centerline Route β’ FAA Airports and Runways β’ Fiberoptic Cables 63,360 β’ Highways 63,360 β’ Iditarod Trail β’ Infrastructure 63,360 β’ Major Roads β’ Pipelines 63,360 β’ Power Lines 63,360 β’ RS2477 Trails β’ Railroads 1,000,000 β’ Railroads 2,000,000 β’ Railroads 63,360 β’ Roads 1,000,000 β’ Roads 2,000,000 β’ Secondary Roads 63,360 β’ State Park Trails through ILMA β’ Telephone Lines 63,360 β’ Trails 63,360 β’ Trans Alaska Pipeline System
Facebook
TwitterThis is a collection of all GPS- and computer-generated geospatial data specific to the Alpine Treeline Warming Experiment (ATWE), located on Niwot Ridge, Colorado, USA. The experiment ran between 2008 and 2016, and consisted of three sites spread across an elevation gradient. Geospatial data for all three experimental sites and cone/seed collection locations are included in this package. βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Geospatial files include cone collection, experimental site, seed trap, and other GPS location/terrain data. File types include ESRI shapefiles, ESRI grid files or Arc/Info binary grids, TIFFs (.tif), and keyhole markup language (.kml) files. Trimble-imported data include plain text files (.txt), Trimble COR (CorelDRAW) files, and Trimble SSF (Standard Storage Format) files. Microsoft Excel (.xlsx) and comma-separated values (.csv) files corresponding to the attribute tables of many files within this package are also included. A complete list of files can be found in this document in the βData File Organizationβ section in the included Data User's Guide. Maps are also included in this data package for reference and use. These maps are separated into two categories, 2021 maps and legacy maps, which were made in 2010. Each 2021 map has one copy in portable network graphics (.png) format, and the other in .pdf format. All legacy maps are in .pdf format. .png image files can be opened with any compatible programs, such as Preview (Mac OS) and Photos (Windows). All GIS files were imported into geopackages (.gpkg) using QGIS, and double-checked for compatibility and data/attribute integrity using ESRI ArcGIS Pro. Note that files packaged within geopackages will open in ArcGIS Pro with βmain.β preceding each file name, and an extra column named βgeomβ defining geometry type in the attribute table. The contents of each geospatial file remain intact, unless otherwise stated in βniwot_geospatial_data_list_07012021.pdf/.xlsxβ. This list of files can be found as an .xlsx and a .pdf in this archive. As an open-source file format, files within gpkgs (TIFF, shapefiles, ESRI grid or βArc/Info Binaryβ) can be read using both QGIS and ArcGIS Pro, and any other geospatial softwares. Text and .csv files can be read using TextEdit/Notepad/any simple text-editing software; .csvβs can also be opened using Microsoft Excel and R. .kml files can be opened using Google Maps or Google Earth, and Trimble files are most compatible with Trimbleβs GPS Pathfinder Office software. .xlsx files can be opened using Microsoft Excel. PDFs can be opened using Adobe Acrobat Reader, and any other compatible programs. A selection of original shapefiles within this archive were generated using ArcMap with associated FGDC-standardized metadata (xml file format). We are including these original files because they contain metadata only accessible using ESRI programs at this time, and so that the relationship between shapefiles and xml files is maintained. Individual xml files can be opened (without a GIS-specific program) using TextEdit or Notepad. Since ESRIβs compatibility with FGDC metadata has changed since the generation of these files, many shapefiles will require upgrading to be compatible with ESRIβs latest versions of geospatial software. These details are also noted in the βniwot_geospatial_data_list_07012021β file.
Facebook
TwitterMadison County Reference Data
Facebook
TwitterThis is a link to the New Jersey Office of GIS Geospatial Data Portal.
Facebook
TwitterGIS DATA IS FOR REFERENCE ONLY AND SHOULD NOT BE USED FOR THE BASIS OF DESIGN OR CONSTRUCTIONIn accordance with Federal and City guidelines this data should not be published or retransmitted. Keep in mind that this data-set represents known floorplan and or site information for said structures and or areas. Parties wishing to know comprehensively what infrastructure exists in the project area are advised to conduct their own site surveys and other due-diligence prior making decisions, analysis, and/or digging and demo. The contained data-sets are meant to serve as a reference file only, not a comprehensive site survey.DATA DISCLAIMERData contained on this Web page/site is Copyright Β© San Francisco City and County (CCSF), California. The GIS data are proprietary to CCSF and title to this information remains in CCSF. All applicable common law and statutory rights in the GIS data including, but not limited to, rights in copyright, shall and will remain the property of CCSF. Information shown on these maps are derived from public records that are constantly undergoing change and do not replace a site survey, and is not warranted for content or accuracy. CCSF does not guarantee the positional or thematic accuracy of the GIS data. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. Areas and/or boundaries contained in this dataset are approximate. Any implied warranties, including warranties of merchantability or fitness for a particular purpose, shall be expressly excluded. All the data on this web page, whether in written, numerical, or graphical form is derived from the San Francisco International Airportβs Asset Management Geospatial Information System (GIS) and is not guaranteed to be accurate. San Francisco International Airport (SFO) makes no warranty of any kind, expressed or implied, including any warranty of merchantability, fitness for a particular purpose, or any other matter. SFO is not responsible for errors, omissions, misuse, or misinterpretation in or of the material. SFOβs digital information is prepared for reference purposes only and should not be used, and is not intended for, survey or engineering purposes. No representation is made concerning the legal status of any apparent route of access identified in digital or hardcopy mapping of geospatial information or data. The requestor acknowledges and accepts all limitations, including the fact that the data, information, and maps are being updated on an ongoing basis, and agrees not to hold SFO or the City and County of San Francisco responsible or liable for any damages that may arise from the use of the data. San Francisco International Airport. Infrastructure Information Management.
Facebook
TwitterODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
This map data layer represents the GIS Map Panel Boundaries for the City of Bloomington, Indiana. The GIS Map Panel Boundaries data layer was created as a reference grid for the GIS map data. The grid tiles are 3000' by 2000' and cover a total of 86.3 square miles of central Monroe County in Indiana. The panel tiles are located arbitrary to any geographic features
Facebook
TwitterThis is a link to the Automated Geographic Reference Center (AGRC) that houses GIS data for the state of Utah. This includes geoscience, cadastre, elevation and terrain, digital aerial photography, roads, aquifer data, etc. Several GIS datasets used in the Utah FORGE project originated from this site.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The Advanced Weather Interactive Processing System (AWIPS) uses shapefiles for base maps in the system. These shapefiles contain boundaries of areas used by NWS for forecasts and warnings as well as map backgrounds.NWS BordersThe County Warning Area boundaries are the counties/zones for which each Weather Forecast Office (WFO) is responsible for issuing forecasts and warnings. The shapefile was created by aggregating public zones with the same CWA designation into a single polygon and manually adjusting the boundaries of the exceptions to the rule.The NWS county and state borders are background map used internally in NWS.Coastal Marine Zone ForecastThis map layer contains links to NWS marine weather forecasts for coastal or nearshore waters within 20nm of shore out to Day 5. It includes predictions on the likelihood of precipitation and/or reduced visibility, surface wind direction and speed, seas or combined seas, and icing. Air temperature forecasts are optional. The forecasts will also include any marine weather advisories, watches, and/or warnings. The purpose of the forecasts is to support and promote safe transportation across the coastal waters. The forecasts are issued twice per day with updates as necessary by NWS Weather Forecast Offices (WFOs) along the coast and Great Lakes.Offshore Zone ForecastsThis map layer contains links to NWS marine weather forecasts for offshore waters beyond 20 or 30nm of shore out to Day 5. The forecast provides information to mariners who travel on the oceanic waters adjacent to the U.S., its territorial coastal waters and the Caribbean Sea. The forecasts include predictions on the likelihood of precipitation and/or reduced visibility, surface wind direction and speed, seas and likelihood of icing out to Day 5 along with information about any warnings. The offshore forecasts for the Western North Atlantic and Eastern North Pacific Oceans are produced by NWS/NCEP's Ocean Prediction Center. The offshore forecasts for the Gulf of Mexico and Caribbean Sea are issued by the NWS/NCEP National Hurricane Center's Tropical Analysis and Forecast Branch (TAFB). OPC and NHC/TAFB issues the forecasts four times daily at regular intervals, with updates when necessary. The offshore forecast for the waters around Hawaii are issued by the NWS Weather Forecast Office in Honolulu, HI four times daily at regular intervals, with updates when necessary. The offshore forecasts for Alaska waters in the Bering Sea and Gulf of Alaska are issued by NWS Weather Forecast Offices in Alaska at least twice a day with updates as necessary. The WFOs in Alaska include WFO Anchorage, WFO Fairbanks, and WFO Juneau.Public Weather Zone ForecastsThis layer includes links to NWS web pages posting the latest NWS surface weather forecasts, a zone-type forecast providing the average forecast conditions across the zone, usually at the county-scale or sub-county scale. These text forecasts include predictions of weather, sky cover, maximum and minimum surface air temperatures, surface wind direction and speed, and probability of precipitation out to 7 days into the future. In addition, the forecast highlights at the top include any active weather advisories, watches, and/or warnings. These zone predictions are derived from gridded forecasts created by NWS Weather Forecast Offices throughout the U.S. The text weather forecasts are usually issued in the early morning (e.g. 4AM LT) and early evening (4PM LT). They are updated during late mornings and late night and during fast changing weather conditions.Fire Weather Zone ForecastsThis layer includes links to NWS web pages posting the latest NWS Fire Weather Planning Forecasts, a zone-type forecast providing the average fire weather conditions across the zone. According to the NWS, the forecast is "used by land management personnel primarily for input in decision-making related to pre-suppression and other planning." The forecast is valid from the time of issuance through day five and sometimes through day seven and usually has a minimum of three 12-hour time periods. The forecast will have included a discussion of weather patterns affecting the forecast zone or area, identification of any active fire weather watches/warnings and a table of predicted fire weather variables for the next two days: 1) sky/weather conditions, 2) max/min air temperatures, 3) max/min relative humidity, 4) 0-minute average wind direction/speed at 20 feet and sometimes at another height (e.g. 10,000, 15,000 ft), 5) precipitation amount, duration, and timing, 6) mixing height, 7) transport winds, 8) vent category, and 9) several fire weather indices such as Haines Index, Lightning Activity (LAL), Chance of Wetting Rainfall (CWR), Dispersion Index, Low Visibility Occurrence Risk Index (LVORI), and Max LVORI. In addition, it will usually have a forecast in plain text for days 3 to 7. Sometimes an optional outlook of expected conditions for day 6 or possibly for day 6 and 7 is expected. The forecasts are issued by NWS WFOs at least once daily during the local fire season.Metadata:CWA: https://www.weather.gov/gis/CWAmetadataCoastal Marine: https://www.weather.gov/gis/CoastalMarineMetadataOffshore: https://www.weather.gov/gis/OffshoreZoneMetadataPublic Zones: https://www.weather.gov/gis/PublicZoneMetadataFire Zones: https://www.weather.gov/gis/FireZoneMetadataCounties: https://www.weather.gov/gis/CountyMetadataStates: https://www.weather.gov/gis/StateMetadataLink to data download: https://www.weather.gov/gis/AWIPSShapefilesQuestions/Concerns about the service, please contact the DISS GIS teamTime Information:This service is not time enabled
Facebook
TwitterMIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
In Spring 2019, with funding from several State partners, MassGIS contracted with the U.S. Geological Survey for statewide, 15 cm resolution, 16-bit, 4-band (RGB-IR) digital orthophotos. The data were delivered in early 2020 as 10,218 individual 1,500 m x 1,500 m tiles in a GeoTIFF format. To allow for easier distribution of this free imagery, MassGIS compressed the GeoTIFFS into the JPEG 2000 format, which retains the IR band. The tile naming convention is based on the U.S. National Grid (USNG), taking the coordinates of the southwest corner of the tile.Project specifications are based on the American Society of Photogrammetry and Remote Sensing (ASPRS) standards. The data were developed based on a horizontal projection/datum of NAD 1983 2011 UTM zones 18N and 19N meters and a vertical projection/datum of NAVD 88 (GEOID 12B) meters.This digital orthoimagery was created to provide easily accessible geospatial data which are readily available to enhance the capability of federal, state, and local emergency responders, as well as to plan for homeland security efforts. These data also support The National Map.These images can serve a variety of purposes, from general planning to field reference for spatial analysis, to a tool for data development and revision of vector maps. The imagery can also serve as a reference layer or basemap for myriad applications inside geographic information system (GIS) software and web-based maps.This image service was created using JPEG 2000 versions of the imagery that MassGIS converted from GeoTiffs and distributes online.For more information see the imagery's MassGIS metadata page.
Facebook
Twitterhttps://louisville-metro-opendata-lojic.hub.arcgis.com/pages/terms-of-use-and-licensehttps://louisville-metro-opendata-lojic.hub.arcgis.com/pages/terms-of-use-and-license
A list of all uniform citations from the Louisville Metro Police Department, the CSV file is updated daily, including case number, date, location, division, beat, offender demographics, statutes and charges, and UCR codes can be found in this Link.INCIDENT_NUMBER or CASE_NUMBER links these data sets together:Crime DataUniform Citation DataFirearm intakeLMPD hate crimesAssaulted OfficersCITATION_CONTROL_NUMBER links these data sets together:Uniform Citation DataLMPD Stops DataNote: When examining this data, make sure to read the LMPDCrime Data section in our Terms of Use.AGENCY_DESC - the name of the department that issued the citationCASE_NUMBER - the number associated with either the incident or used as reference to store the items in our evidence rooms and can be used to connect the dataset to the following other datasets INCIDENT_NUMBER:1. Crime Data2. Firearms intake3. LMPD hate crimes4. Assaulted OfficersNOTE: CASE_NUMBER is not formatted the same as the INCIDENT_NUMBER in the other datasets. For example: in the Uniform Citation Data you have CASE_NUMBER 8018013155 (no dashes) which matches up with INCIDENT_NUMBER 80-18-013155 in the other 4 datasets.CITATION_YEAR - the year the citation was issuedCITATION_CONTROL_NUMBER - links this LMPD stops dataCITATION_TYPE_DESC - the type of citation issued (citations include: general citations, summons, warrants, arrests, and juvenile)CITATION_DATE - the date the citation was issuedCITATION_LOCATION - the location the citation was issuedDIVISION - the LMPD division in which the citation was issuedBEAT - the LMPD beat in which the citation was issuedPERSONS_SEX - the gender of the person who received the citationPERSONS_RACE - the race of the person who received the citation (W-White, B-Black, H-Hispanic, A-Asian/Pacific Islander, I-American Indian, U-Undeclared, IB-Indian/India/Burmese, M-Middle Eastern Descent, AN-Alaskan Native)PERSONS_ETHNICITY - the ethnicity of the person who received the citation (N-Not Hispanic, H=Hispanic, U=Undeclared)PERSONS_AGE - the age of the person who received the citationPERSONS_HOME_CITY - the city in which the person who received the citation livesPERSONS_HOME_STATE - the state in which the person who received the citation livesPERSONS_HOME_ZIP - the zip code in which the person who received the citation livesVIOLATION_CODE - multiple alpha/numeric code assigned by the Kentucky State Police to link to a Kentucky Revised Statute. For a full list of codes visit: https://kentuckystatepolice.org/crime-traffic-data/ASCF_CODE - the code that follows the guidelines of the American Security Council Foundation. For more details visit https://www.ascfusa.org/STATUTE - multiple alpha/numeric code representing a Kentucky Revised Statute. For a full list of Kentucky Revised Statute information visit: https://apps.legislature.ky.gov/law/statutes/CHARGE_DESC - the description of the type of charge for the citationUCR_CODE - the code that follows the guidelines of the Uniform Crime Report. For more details visit https://ucr.fbi.gov/UCR_DESC - the description of the UCR_CODE. For more details visit https://ucr.fbi.gov/
Facebook
TwitterGIS DATA IS FOR REFERENCE ONLY AND SHOULD NOT BE USED FOR THE BASIS OF DESIGN OR CONSTRUCTIONIn accordance with Federal and City guidelines this data should not be published or retransmitted. Keep in mind that this data-set represents known floorplan and or site information for said structures and or areas. Parties wishing to know comprehensively what infrastructure exists in the project area are advised to conduct their own site surveys and other due-diligence prior making decisions, analysis, and/or digging and demo. The contained data-sets are meant to serve as a reference file only, not a comprehensive site survey.DATA DISCLAIMERData contained on this Web page/site is Copyright Β© San Francisco City and County (CCSF), California. The GIS data are proprietary to CCSF and title to this information remains in CCSF. All applicable common law and statutory rights in the GIS data including, but not limited to, rights in copyright, shall and will remain the property of CCSF. Information shown on these maps are derived from public records that are constantly undergoing change and do not replace a site survey, and is not warranted for content or accuracy. CCSF does not guarantee the positional or thematic accuracy of the GIS data. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. Areas and/or boundaries contained in this dataset are approximate. Any implied warranties, including warranties of merchantability or fitness for a particular purpose, shall be expressly excluded. All the data on this web page, whether in written, numerical, or graphical form is derived from the San Francisco International Airportβs Asset Management Geospatial Information System (GIS) and is not guaranteed to be accurate. San Francisco International Airport (SFO) makes no warranty of any kind, expressed or implied, including any warranty of merchantability, fitness for a particular purpose, or any other matter. SFO is not responsible for errors, omissions, misuse, or misinterpretation in or of the material. SFOβs digital information is prepared for reference purposes only and should not be used, and is not intended for, survey or engineering purposes. No representation is made concerning the legal status of any apparent route of access identified in digital or hardcopy mapping of geospatial information or data. The requestor acknowledges and accepts all limitations, including the fact that the data, information, and maps are being updated on an ongoing basis, and agrees not to hold SFO or the City and County of San Francisco responsible or liable for any damages that may arise from the use of the data. San Francisco International Airport. Infrastructure Information Management.
Facebook
TwitterCC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
The GIS database has been developed by under the Small Hydropower Mapping and Improved Geospatial Electrification Planning in Indonesia Project [Project ID: P145273]. The scope of the project was to facilitate and improve the planning and investment process for small hydro development both grid and isolated systems through: building up a central database on smal hydro at national scale and validating the mapping of small hydro in NTT, Maluku, Maluku Utara and Sulawesi improved electrification planning by integrating small hydro potential for the provinces of NTT, Maluku, Maluku Utara and Sulawesi into the planning process. Please refer to the country project page for additional outputs and reports: http://esmap.org/re_mapping_indonesia The GIS database contains the following datasets: SHP(promising sites) Admin Divisions Topomas_grid Rivers, Geology Forest_areas Roads RainfallGauges RunoffGauges ElectricSystem, each accompanied by a metadata file. Please cite as: [Data/information/map obtained from the] βWorld Bank via ENERGYDATA.info, under a project funded by the Energy Sector Management Assistance Program (ESMAP). For more information: Indonesia - Small Hydro GIS Atlas, 2017, https://energydata.info/dataset/indonesia-small-hydro-gis-database-2017"
Facebook
TwitterGIS DATA IS FOR REFERENCE ONLY AND SHOULD NOT BE USED FOR THE BASIS OF DESIGN OR CONSTRUCTIONIn accordance with Federal and City guidelines this data should not be published or retransmitted. Keep in mind that this data-set represents known floorplan and or site information for said structures and or areas. Parties wishing to know comprehensively what infrastructure exists in the project area are advised to conduct their own site surveys and other due-diligence prior making decisions, analysis, and/or digging and demo. The contained data-sets are meant to serve as a reference file only, not a comprehensive site survey.DATA DISCLAIMERData contained on this Web page/site is Copyright Β© San Francisco City and County (CCSF), California. The GIS data are proprietary to CCSF and title to this information remains in CCSF. All applicable common law and statutory rights in the GIS data including, but not limited to, rights in copyright, shall and will remain the property of CCSF. Information shown on these maps are derived from public records that are constantly undergoing change and do not replace a site survey, and is not warranted for content or accuracy. CCSF does not guarantee the positional or thematic accuracy of the GIS data. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. The GIS data or cartographic digital files are not a legal representation of any of the features in which it depicts, and disclaims any assumption of the legal status of which it represents. Areas and/or boundaries contained in this dataset are approximate. Any implied warranties, including warranties of merchantability or fitness for a particular purpose, shall be expressly excluded. All the data on this web page, whether in written, numerical, or graphical form is derived from the San Francisco International Airportβs Asset Management Geospatial Information System (GIS) and is not guaranteed to be accurate. San Francisco International Airport (SFO) makes no warranty of any kind, expressed or implied, including any warranty of merchantability, fitness for a particular purpose, or any other matter. SFO is not responsible for errors, omissions, misuse, or misinterpretation in or of the material. SFOβs digital information is prepared for reference purposes only and should not be used, and is not intended for, survey or engineering purposes. No representation is made concerning the legal status of any apparent route of access identified in digital or hardcopy mapping of geospatial information or data. The requestor acknowledges and accepts all limitations, including the fact that the data, information, and maps are being updated on an ongoing basis, and agrees not to hold SFO or the City and County of San Francisco responsible or liable for any damages that may arise from the use of the data. San Francisco International Airport. Infrastructure Information Management.
Facebook
TwitterODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
This layer represents the primary GIS mapped area for the City of Bloomington, Indiana. It covers the City of Bloomington plus the Bloomington Utilities service area. Detailed planimetric data such as edge of pavement and early aerial orthophotography is limited to this area.
Facebook
Twitterhttps://services3.arcgis.com/6LvtIYUSMXW8Tb6o/ArcGIS/rest/serviceshttps://services3.arcgis.com/6LvtIYUSMXW8Tb6o/ArcGIS/rest/services
Services:2015_Parking (FeatureServer)AGO_MAP_2019 (FeatureServer)Bike_Racks_2020 (FeatureServer)BikeParking2017 (FeatureServer)Chicago_Central_Business_District (FeatureServer)Chicago_Wards_hosted (FeatureServer)ChicagoMayHwys (FeatureServer)Control_Points_Interlockings (FeatureServer)ControlPoints_Interlockings (FeatureServer)Cook_County_Districts_hosted (FeatureServer)CTA_Bus_Routes (FeatureServer)CTA_Bus_Routes_2019 (FeatureServer)cta_rail_lines (FeatureServer)CTABusRoutes2019 (FeatureServer)FRA_Crossings (FeatureServer)FreightRailroads (FeatureServer)Grade_Crossings (FeatureServer)Illinois_House_Districts (FeatureServer)Illinois_Senate_Districts (FeatureServer)Lines_COVID19 (FeatureServer)Metra_Bridges (FeatureServer)Metra_facilities (FeatureServer)metra_lines_2018 (FeatureServer)Metra_Routes_Test (FeatureServer)metra_stations_2018 (FeatureServer)MetraLines_2016 (FeatureServer)MetraLines2017 (FeatureServer)MetraLines2019_CreateRoutes (FeatureServer)MetraPoliceBeats (FeatureServer)MetraStations2017new (FeatureServer)Municipalities (FeatureServer)NICTD_South_Shore_Line (FeatureServer)NICTD_Stations (FeatureServer)Pace_ParkNRide_Facilities (FeatureServer)Pace_Routes_03_25_2019 (FeatureServer)PaceRoutes2020 (FeatureServer)Parking_Lots_2016 (FeatureServer)parking_lots_2017 (FeatureServer)Parking_Survey_2018_AGO_Published (FeatureServer)Parking_Survey_2018_Final (FeatureServer)Parking_Survey_2019_Final (FeatureServer)ParkingLots2017 (FeatureServer)Police_Beats_2020_Draft (FeatureServer)Police_tows (FeatureServer)Six_County_Service_Area (FeatureServer)Stations_COVID19 (FeatureServer)Tie_Substations (FeatureServer)TrainsPerDay (FeatureServer)US_Congressional_Districts (FeatureServer)Yards_Points (FeatureServer)yards_points_2019 (FeatureServer)Yards_Polygons (FeatureServer)yards_polygons_2018 (FeatureServer)