The Digital Geologic-GIS Map of the Ready Quadrangle, Kentucky is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (read_geology.gdb), and a 2.) Open Geospatial Consortium (OGC) geopackage. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (read_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (read_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) a readme file (maca_abli_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (maca_abli_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (read_geology_metadata_faq.pdf). Please read the maca_abli_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. QGIS software is available for free at: https://www.qgis.org/en/site/. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: U.S. Geological Survey. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (read_geology_metadata.txt or read_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

The National Highway System consists of roadways important to the nation’s economy, defense, and mobility. The National Highway System (NHS) includes the following subsystems of roadways: Interstate - The Eisenhower Interstate System of highways, Other Principal Arterials - highways in rural and urban areas which provide access between an arterial and a major port, airport, public transportation facility, or other intermodal transportation facility, Strategic Highway Network (STRAHNET) - a network of highways which are important to the United States’ strategic defense policy and which provide defense access, continuity and emergency capabilities for defense purposes, Major Strategic Highway Network Connectors - highways which provide access between major military installations and highways which are part of the Strategic Highway Network, Intermodal Connectors - highways providing access between major intermodal facilities and the other four subsystems making up the National Highway System. A specific highway route may be on more than one subsystem.The primary purpose of this map is to serve the FHWA needs in highway planning, policy analysis, visualization of the NHS database and keep track the NHS approval as well as the technical corrections.

Yarrrrrrrr maps are too crisp and clean! You need a hand-painted grubby tattered treasure map from antiquity to make yer point. Download this here style for ArrrrrrcGIS Pro and be off to makin dern-near realistic maps ready for an eager public (or set designerrrr).To be used in conjunction with these tattered paper assets, available here (seriously, it's a pretty important bit). Or you can use them with an assortment of paper textures, available in Living Atlas here.Also, there's two cool hand-inked looking north arrows in the style. You can see them in the sample maps above.Happy Mapping! John Nelson

AquaMaps are computer-generated predictions of natural occurrence of marine species, based on the environmental tolerance of a given species with respect to depth, salinity, temperature, primary productivity, and its association with sea ice or coastal areas. These 'environmental envelopes' are matched against an authority file which contains respective information for the Oceans of the World. Independent knowledge such as distribution by FAO areas or bounding boxes are used to avoid mapping species in areas that contain suitable habitat, but are not occupied by the species. Maps show the color-coded likelihood of a species to occur in a half-degree cell, with about 50 km side length near the equator. Experts are able to review, modify and approve maps.

Environmental envelopes are created in part (FAO areas, bounding boxes, depth ranges) from respective information in species databases such as FishBase and in part from occurrence records available from OBIS or GBIF. AquaMaps predictions have been validated successfully for a number of species using independent data sets and the model was shown to perform equally well or better than other standard species distribution models, when faced with the currently existing suboptimal input data sets (Ready et al. 2010).

The creation of AquaMaps is supported by the following projects: MARA, Pew Fellows Program in Marine Conservation, INCOFISH, Sea Around Us, and Biogeoinformatics of Hexacorals.

Kaschner, K., D.P. Tittensor, J. Ready, T Gerrodette and B. Worm (2011). Current and Future Patterns of Global Marine Mammal Biodiversity. PLoS ONE 6(5): e19653. PDF

Ready, J., K. Kaschner, A.B. South, P.D Eastwood, T. Rees, J. Rius, E. Agbayani, S. Kullander and R. Froese (2010). Predicting the distributions of marine organisms at the global scale. Ecological Modelling 221(3): 467-478. PDF

Copyright Creative Commons License This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License. (CC-BY-NC) You are welcome to include maps from www.aquamaps.org in your own web sites for non-commercial use, given that such inserts are clearly identified as coming from AquaMaps, with a backward link to the respective source page.

Contacts Rainer Froese, GEOMAR, Coordinator rfroese@geomar.de Kristin Kaschner, Uni Freiburg, model development Kristin.Kaschner@biologie.uni-freiburg.de Ma. Lourdes D. Palomares, UBC, extension to non-fish marine organisms m.palomares@fisheries.ubc.ca Sven Kullander, NRM, extension to freshwater ve-sven@nrm.se Jonathan Ready, NRM, implementation jonathan.ready@gmail.com Tony Rees, formerly with CSIRO, mapping tools Tony.Rees@marinespecies.org Paul Eastwood, SOPAC, validation Paul.Eastwood@sopac.org Andy South, CEFAS, validation andy.south@cefas.co.uk Josephine Rius-Barile, Q-quatics, database programming / data collection j.barile@q-quatics.org Cristina Garilao, GEOMAR, web programming cgarilao@geomar.de Kathleen Kesner-Reyes, Q-quatics, map validation k.reyes@q-quatics.org Elizabeth Bato, Q-quatics, map validation (non-fish) e.david@q-quatics.org

Citing AquaMaps

General citation Kaschner, K., K. Kesner-Reyes, C. Garilao, J. Rius-Barile, T. Rees, and R. Froese. 2019. AquaMaps: Predicted range maps for aquatic species. World wide web electronic publication, www.aquamaps.org, version 10/2019.

Cite individual maps as, e.g., Computer Generated Map for Gadus morhua (Atlantic cod). www.aquamaps.org, version 10/2019 (accessed 01 Oct 2019).

Reviewed Native Distribution Map for Gadus morhua (Atlantic cod). www.aquamaps.org, version 10/2019 (accessed 01 Oct 2019).

Cite biodiversity maps as, e.g., Shark and Ray Biodiversity Map. www.aquamaps.org, version 10/2019 (accessed 01 Oct 2019).

Cite the environmental dataset as, e.g., Kesner-Reyes, K., Segschneider, J., Garilao, C., Schneider, B., Rius-Barile, J., Kaschner, K., and Froese, R.(editors). AquaMaps Environmental Dataset: Half-Degree Cells Authority File (HCAF). World Wide Web electronic publication, www.aquamaps.org/main/envt_main.php, ver. 7, 10/2019.

Using Full or Large Sets of AquaMaps Data We encourage partnering with the AquaMaps team for larger research projects or publications that would make intensive use of AquaMaps to ensure that you have access to the latest version and/or reviewed maps, the limitations of the data set are clearly understood and addressed, and that critical maps and/or unlikely results are recognized as such and double-checked for correctness prior to drawing conclusions and/or subsequent publication.

The AquaMaps team can be contacted through Rainer Froese (rfroese@geomar.de) or Kristin Kaschner (Kristin.Kaschner@biologie.uni-freiburg.de).

Privacy Policy AquaMaps uses log data generate usage statistics. Like most websites, AquMaps gathers information about internet protocol (IP) addresses, browser, referring pages, operating system, date/time, clicks, and visited pages, and store it in log files. This information is used to find errors in our website, analyze trends, and determine country of origin of our users. The log files are stored indefinitely. Only the administrators of the AquaMaps server has direct access to the log files. The information is used to inform further development of AquaMaps. Usage statistics may be shared with third parties for non-commercial purposes.

Disclaimer AquaMaps generates standardized computer-generated and fairly reliable large scale predictions of marine and freshwater species. Although the AquaMaps team and their collaborators have obtained data from sources believed to be reliable and have made every reasonable effort to ensure its accuracy, many maps have not yet been verified by experts and we strongly suggest you verify species occurrences with independent sources before usage. We will not be held responsible for any consequence from the use or misuse of these data and/or maps by any organization or individual.

Copyright This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License (CC-BY-NC). You are welcome to include text, numbers and maps from AquaMaps in your own web sites for non-commercial use, given that such inserts are clearly identified as coming from AquaMaps, with a backward link to the respective source page. Note that although species photos and drawings draw mainly from FishBase and SeaLifeBase, they belong to the indicated persons or organizations and have their own copyright statements.

This historical map series consists of the Planimetric Series printed monochrome maps named using the National Topographic System (NTS) map sheet identifier within Alberta. The Planimetric Series base maps were initiated in 1949 and derived from aerial photographs taken during the years 1949 to 1952. These maps display: Alberta Township System (ATS) - hydrographic features - provincial highways - roads - pipelines - transmission lines - municipalities. These maps are not available as GIS-ready data. All available maps are provided in Adobe PDF and TIF format. To obtain the TIF format, please contact the distributor. Geo-referenced PNG files are also available for some maps, but some are roughly georeferenced with only a few control points. Please note that the coverage for the province is incomplete and it is not known if further coverage will be added. Some maps were also updated after their initial publication, please refer to the maps for the most current dates.

The European Copernicus Coastal Flood Awareness System (ECFAS) project aimed at contributing to the evolution of the Copernicus Emergency Management Service (https://emergency.copernicus.eu/) by demonstrating the technical and operational feasibility of a European Coastal Flood Awareness System. Specifically, ECFAS provides a much-needed solution to bolster coastal resilience to climate risk and reduce population and infrastructure exposure by monitoring and supporting disaster preparedness, two factors that are fundamental to damage prevention and recovery if a storm hits.

The ECFAS Proof-of-Concept development ran from January 2021 to December 2022. The ECFAS project was a collaboration between Scuola Universitaria Superiore IUSS di Pavia (Italy, ECFAS Coordinator), Mercator Ocean International (France), Planetek Hellas (Greece), Collecte Localisation Satellites (France), Consorzio Futuro in Ricerca (Italy), Universitat Politecnica de Valencia (Spain), University of the Aegean (Greece), and EurOcean (Portugal), and was funded by the European Commission H2020 Framework Programme within the call LC-SPACE-18-EO-2020 - Copernicus evolution: research activities in support of the evolution of the Copernicus services.

Description of the product

The deliverable includes a document and a compressed directory with ready-to-print maps, the associated geospatial datasets and symbology files. All products were developed under Task 5.5 – Mapping products.
The document reports on the activities conducted during Task 5.5 – Mapping products that aimed at demonstrating the added value of the ECFAS products and propose adequate representation for communication and integration into the Copernicus Emergency Management Services. Five Demonstration cases, corresponding each to one recent coastal event and one location, were selected to highlight the ECFAS products resulting of the coastal Flood, Impacts and Shoreline position tools developed previously during the ECFAS activities. The Mapping products prepared for each demonstration case are provided along the document in cartographic formats (ready-to-print maps), along with the symbology files and geospatial datasets that were used to create the products.

This dataset is made available under the Open Database License: http://opendatacommons.org/licenses/odbl/1.0/. Any rights in individual contents of this dataset are licensed under the Open Database License: http://opendatacommons.org/licenses/dbcl/1.0/.

This Report is made available under the Creative Commons Attribution 4.0 International License.

Disclaimer:

ECFAS partners provide the data "as is" and "as available" without warranty of any kind. The ECFAS partners shall not be held liable resulting from the use of the information and data provided.

This project has received funding from the Horizon 2020 research and innovation programme under grant agreement No. 101004211

This map was last updated March 2014. World Imagery provides one meter or better satellite and aerial imagery in many parts of the world and lower resolution satellite imagery worldwide. The map includes NASA Blue Marble: Next Generation 500m resolution imagery at small scales (above 1:1,000,000), i-cubed 15m eSAT imagery at medium-to-large scales (down to 1:70,000) for the world, and USGS 15m Landsat imagery for Antarctica. The map features 0.3m resolution imagery in the continental United States and parts of Western Europe from DigitalGlobe. Additional DigitalGlobe sub-meter imagery is featured in many parts of the world, with concentrations in South America, Eastern Europe, India, Japan, the Middle East and Northern Africa, Southern Africa, Australia, and New Zealand. In other parts of the world, 1 meter resolution imagery is available from GeoEye IKONOS, Getmapping, AeroGRID, IGN Spain, and IGP Portugal. Additionally, imagery at different resolutions has been contributed by the GIS User Community. To view this map service now, along with useful reference overlays, click here to open the Imagery with Labels web map.Tip: This service is one of the basemaps used in the ArcGIS.com map viewer and ArcGIS Explorer Online. Simply click one of those links to launch the interactive application of your choice, and then choose Imagery or Imagery with Labels from the Basemap control to start browsing the imagery. You'll also find this service in the Basemap gallery in ArcGIS Explorer Desktop and ArcGIS Desktop 10.The coverage for Europe includes AeroGRID 1m resolution imagery for Belgium, France (Region Nord-Pas-de-Calais only), Germany, Luxembourg, and The Netherlands and 2m resolution imagery for the Czech Republic, plus 1m resolution imagery for Portugal from the Instituto Geográfico Português.For details on the coverage in this map service, view the list of Contributors for the World Imagery Map.View the coverage map below to learn more about the coverage for the high-resolution imagery:Updated imagery coverage map: Areas updated in the most recent release. World coverage map: Areas with high-resolution imagery throughout the world.Metadata: This service is metadata-enabled. With the Identify tool in ArcMap or the ArcGIS Online Content Viewer, you can see the resolution, collection date, and source of the imagery at the location you click. The metadata applies only to the best available imagery at that location. You may need to zoom in to view the best available imagery.Reference overlays: The World Boundaries and Places service is designed to be drawn on top of this service as a reference overlay. This is what gets drawn on top of the imagery if you choose the Imagery With Labels basemap in any of the ArcGIS clients.The World Transportation service is designed to be drawn on top of this service to provide street labels when you are zoomed in and streets and roads when you are zoomed out.There are three ready to use web maps that use the World Imagery service as their basemap, Imagery, in which both reference layers are turned off, Imagery with Labels, which has World Boundaries and Places turned on but World Transportation turned off, and Imagery with Labels and Transportation, which has both reference layers turned on.Feedback: Have you ever seen a problem in the Esri World Imagery Map that you wanted to see fixed? You can use the Imagery Map Feedback web map to provide feedback on issues or errors that you see. The feedback will be reviewed by the ArcGIS Online team and considered for one of our updates.ArcGIS Desktop use: This service requires ArcGIS 9.3 or more recent.The World Imagery map service is not available as a globe service. If you need a globe service containing imagery use the Prime Imagery (3D) globe service. However note that this is no longer being updated by Esri.Tip: Here are some famous locations as they appear in this map service. The following URLs launch the Imagery With Labels and Transportation web map (which combines this map service with the two reference layers designed for it) and take you to specific locations on the map using location parameters included in the URL.Grand Canyon, Arizona, USAGolden Gate, California, USATaj Mahal, Agra, IndiaVatican CityBronze age white horse, Uffington, UKUluru (Ayres Rock), AustraliaMachu Picchu, Cusco, PeruOkavango Delta, BotswanaScale Range: 1:591,657,528 down to 1:1,128Coordinate System: Web Mercator Auxiliary Sphere (WKID 102100)Tiling Scheme: Web Mercator Auxiliary SphereMap Service Name: World_ImageryArcGIS Desktop/Explorer URL: http://services.arcgisonline.com/arcgis/services ArcGIS Desktop files: MXD LYR (These ready-to-use files contain this service and associated reference overlay services. ArcGIS 9.3 or more recent required).ArcGIS Server Manager and Web ADF URL: http://server.arcgisonline.com/arcgis/services/World_Imagery/MapServerREST URL for ArcGIS Web APIs: http://server.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServerSOAP API URL: http://services.arcgisonline.com/ArcGIS/services/World_Imagery/MapServer?wsdl

This dataset contains the common Map Unit attributes for each polygon within the gSSURGO database plus NRCS derived attributes from a data summary table called the National Valu Added Look Up (valu) Table #1. It is comprised of 57 pre-summarized or "ready to map" derived soil survey geographic database attributes including soil organic carbon, available water storage, crop productivity indices, crop root zone depths, available water storage within crop root zone depths, drought vulnerable soil landscapes, and potential wetland soil landscapes. Related metadata values for themes are included. These attribute data are pre-summarized to the map unit level using best practice generalization methods intended to meet the needs of most users. The generalization methods include map unit component weighted averages and percent of the map unit meeting a given criteria. These themes were prepared to better meet the mapping needs of users of soil survey information and can be used with both SSURGO and Gridded SSURGO (gSSURGO) datasets. Gridded SSURGO (gSSURGO) Database is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO is generally the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes, and are derived from properties and characteristics stored in the National Soil Information System (NASIS). The gSSURGO data were prepared by merging traditional SSURGO digital vector map and tabular data into State-wide extents, and adding a State-wide gridded map layer derived from the vector, plus a new value added look up (valu) table containing "ready to map" attributes. The gridded map layer is offered in an ArcGIS file geodatabase raster format. The raster and vector map data have a State-wide extent. The raster map data have a 10 meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link to raster cells and polygons to attribute tables, including the new value added look up (valu) table that contains additional derived data.VALU Table Content:The map unit average Soil Organic Carbon (SOC) values are given in units of g C per square meter for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), o-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average Available Water Storage (AWS) values are given in units of millimeters for eleven standard layer or zone depths. The average thickness of soil map unit component horizons used in these layer/zone calcuations is also included. The standard layers include: 0-5cm, 5-20cm, 20-50cm, 50-100cm, 100-150cm, and 150-150+cm (maximum reported soil depth). The standard zones include: 0-5cm (also a standard layer), 0-20cm, 0-30cm, 0-100cm, and 0-150+cm (full reported soil depth). Zero cm represents the soil surface.The map unit average National Commodity Crop Productivity Index (NCCPI) values (low index values indicate low productivity and high index values indicate high productivity) are provided for major earthy components. NCCPI values are included for corn/soybeans, small grains, and cotton crops. Of these crops, the highest overall NCCPI value is also identified. Earthy components are those soil series or higher level taxa components that can support crop growth. Major components are those soil components where the majorcompflag = 'Yes' in the SSURGO component table. A map unit percent composition for earthy major components is provided. See Dobos, R. R., H. R. Sinclair, Jr, and M. P. Robotham. 2012. National Commodity Crop Productivity Index (NCCPI) User Guide, Version 2. USDA-NRCS. Available at: ftp://ftp-fc.sc.egov.usda.gov/NSSC/NCCPI/NCCPI_user_guide.pdfThe map unit average root zone depth values for commodity crops are given in centimeters for major earthy components. Criteria for root-limiting soil depth include: presence of hard bedrock, soft bedrock, a fragipan, a duripan, sulfuric material, a dense layer, a layer having a pH of less than 3.5, or a layer having an electrical conductivity of more than 12 within the component soil profile. If no root-restricting zone is identified, a depth of 150 cm is used to approximate the root zone depth (Dobos et al., 2012). The map unit average available water storage within the root zone depth for major earthy components value is given in millimeters.Drought vulnerable soil landscapes comprise those map units that have available water storage within the root zone for commodity crops that is less than or equal to 6 inches (152 mm) expressed as "1" for a drought vulnerable soil landscape map unit or "0" for a nondroughty soil landscape map unit or NULL for miscellaneous areas (includes water bodies).The potential wetland soil landscapes (PWSL version 1) information is given as the percentage of the map unit (all components) that meet the criteria for a potential wetland soil landscape. See table column (field) description for criteria details. If water was determined to account for 80 or greater percent of a map unit, a value of 999 was used to indicate a water body. This is not a perfect solution, but is helpful to identifying a general water body class for mapping.The map unit sum of the component percentage representative values is also provided as useful metadata. For all valu table columns, NULL values are presented where data are incomplete or not available. How NoData or NULL values and incomplete data were handled during VALU table SOC and AWS calculations:The gSSURGO calculations for SOC and AWS as reported in the VALU table use the following data checking and summarization rules. The guiding principle was to only use the official data in the SSURGO database, and not to make assumptions in case there were some data entry errors. However, there were a few exceptions to this principle if there was a good reason for a Null value in a critical variable, or to accommodate the data coding conventions used in some soil surveys.Horizon depths considerations:If the depth to the top of the surface horizon was missing, but otherwise the horizon depths were all okay, then the depth to the top of the surface horizon (hzdept_r) was set to zero.If the depth to the bottom of the last horizon was missing, and the horizon represented bedrock or had missing bulk density, the depth to the bottom was set to equal to the depth to the top of the same horizon (hzdepb_r = hzdept_r), effectively giving the horizon zero thickness (and thus zero SOC or AWS), but not blocking calculation of other horizons in the profile due to horizon depth errors.Other types of horizon depth errors were considered uncorrectable, and led to all horizon depths for the component being set to a NoData value, effectively eliminating the component from the analysis. The errors included gaps or overlaps in the horizon depths of the soil profile, other cases of missing data for horizon depths, including missing data for the bottom depth of the last horizon if the soil texture information did not indicate bedrock and a bulk density value was coded. The SOC or AWS values were effectively set to zero for components eliminated in this way, so the values at the map unit level could be an underestimate for some soils.Horizon rock fragment considerations:Part of the algorithm for calculating the SOC requires finding the volume of soil that is not rock. This requires three SSURGO variables that indicate rock fragments (fraggt10_r, frag3to10_r, and sieveno10_r). If the soil is not organic, and any of these are missing, then the ratio of the volume of soil fines to the total soil volume was set to “NoData†, and the SOC results were coded as “NoData†and effectively set to zero for the horizon. If the soil is organic, then it may be logical that no measurement of rock fragments was made, and default values for the “zero rock†situation was assumed for these variables (i.e., fraggt10_r = 0, frag3to10_r = 0, sieveno10_r = 100). Organic soils were identified by an “O†in the horizon designator or the texture code represented “Peat†, “Muck†or “Decomposed Plant Material†. If all three of the fragment variables were present, but indicated more than 100% rock, then 100% rock was assumed (zero volume of soil and thus zero for SOC). The rock fragment variables do not influence the AWS calculation because rock content is already accounted for in the available water capacity (awc_r) variable at the horizon level.Horizon to component summary:To summarize data from the horizon level to the component level, the evaluation proceeded downward from the surface. If a valid value for AWS could not be calculated for any horizon, then the result for that horizon and all deeper horizons was set to NoData. The same rule was separately applied to the SOC calculation, so it was possible to have results for SOC but not AWS, or vice versa.Component to mapunit summary:To summarize data from the component level to the map unit level, the component percentages must be valid. There are tests both of the individual component percentage (comppct_r) data, and also of the sum of the component percentages at the map unit level (mu_sum_comppct_r). For the gSSURGO VALU table, the following rules were applied for the individual components: 1) The comppct_r must be in the range from 0 to 100, inclusive. 2) Individual components with a comppct_r that was Null (nothing coded) were ignored. A zero comppct_r value excludes

This historical map series consists of the Planimetric Series printed monochrome maps named using the National Topographic System (NTS) map sheet identifier within Alberta. The Planimetric Series base maps were initiated in 1949 and derived from aerial photographs taken during the years 1949 to 1952. These maps display: Alberta Township System (ATS) - hydrographic features - provincial highways - roads - pipelines - transmission lines - municipalities. These maps are not available as GIS-ready data. All available maps are provided in Adobe PDF and TIF format. To obtain the TIF format, please contact the distributor. Geo-referenced PNG files are also available for some maps, but some are roughly georeferenced with only a few control points. Please note that the coverage for the province is incomplete and it is not known if further coverage will be added. Some maps were also updated after their initial publication, please refer to the maps for the most current dates.

The gSSURGO dataset provides detailed soil survey mapping in raster format with ready-to-map attributes organized in statewide tiles for desktop GIS. gSSURGO is derived from the official Soil Survey Geographic (SSURGO) Database. SSURGO generally has the most detailed level of soil geographic data developed by the National Cooperative Soil Survey (NCSS) in accordance with NCSS mapping standards. The tabular data represent the soil attributes and are derived from properties and characteristics stored in the National Soil Information System (NASIS).

The gSSURGO data were prepared by merging the traditional vector-based SSURGO digital map data and tabular data into statewide extents, adding a statewide gridded map layer derived from the vector layer, and adding a new value-added look up table (valu) containing ready-to-map attributes. The gridded map layer is in an ArcGIS file geodatabase in raster format, thus it has the capacity to store significantly more data and greater spatial extents than the traditional SSURGO product. The raster map data have a 10-meter cell size that approximates the vector polygons in an Albers Equal Area projection. Each cell (and polygon) is linked to a map unit identifier called the map unit key. A unique map unit key is used to link the raster cells and polygons to attribute tables.

For more information, see the gSSURGO webpage: https://www.nrcs.usda.gov/resources/data-and-reports/description-of-gridded-soil-survey-geographic-gssurgo-database

Welcome to Apiscrapy, your ultimate destination for comprehensive location-based intelligence. As an AI-driven web scraping and automation platform, Apiscrapy excels in converting raw web data into polished, ready-to-use data APIs. With a unique capability to collect Google Address Data, Google Address API, Google Location API, Google Map, and Google Location Data with 100% accuracy, we redefine possibilities in location intelligence.

Key Features:

Unparalleled Data Variety: Apiscrapy offers a diverse range of address-related datasets, including Google Address Data and Google Location Data. Whether you seek B2B address data or detailed insights for various industries, we cover it all.

Integration with Google Address API: Seamlessly integrate our datasets with the powerful Google Address API. This collaboration ensures not just accessibility but a robust combination that amplifies the precision of your location-based insights.

Business Location Precision: Experience a new level of precision in business decision-making with our address data. Apiscrapy delivers accurate and up-to-date business locations, enhancing your strategic planning and expansion efforts.

Tailored B2B Marketing: Customize your B2B marketing strategies with precision using our detailed B2B address data. Target specific geographic areas, refine your approach, and maximize the impact of your marketing efforts.

Use Cases:

Location-Based Services: Companies use Google Address Data to provide location-based services such as navigation, local search, and location-aware advertisements.

Logistics and Transportation: Logistics companies utilize Google Address Data for route optimization, fleet management, and delivery tracking.

E-commerce: Online retailers integrate address autocomplete features powered by Google Address Data to simplify the checkout process and ensure accurate delivery addresses.

Real Estate: Real estate agents and property websites leverage Google Address Data to provide accurate property listings, neighborhood information, and proximity to amenities.

Urban Planning and Development: City planners and developers utilize Google Address Data to analyze population density, traffic patterns, and infrastructure needs for urban planning and development projects.

Market Analysis: Businesses use Google Address Data for market analysis, including identifying target demographics, analyzing competitor locations, and selecting optimal locations for new stores or offices.

Geographic Information Systems (GIS): GIS professionals use Google Address Data as a foundational layer for mapping and spatial analysis in fields such as environmental science, public health, and natural resource management.

Government Services: Government agencies utilize Google Address Data for census enumeration, voter registration, tax assessment, and planning public infrastructure projects.

Tourism and Hospitality: Travel agencies, hotels, and tourism websites incorporate Google Address Data to provide location-based recommendations, itinerary planning, and booking services for travelers.

Discover the difference with Apiscrapy – where accuracy meets diversity in address-related datasets, including Google Address Data, Google Address API, Google Location API, and more. Redefine your approach to location intelligence and make data-driven decisions with confidence. Revolutionize your business strategies today!

This layer shows workers' place of residence by commute length. This is shown by tract, county, and state boundaries. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. This layer is symbolized to show the percentage of commuters whose commute is 90 minutes or more. To see the full list of attributes available in this service, go to the "Data" tab, and choose "Fields" at the top right. Current Vintage: 2019-2023ACS Table(s): B08303Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. For more information about ACS layers, visit the FAQ. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer is updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases, specifically, the National Sub-State Geography Database (named tlgdb_(year)_a_us_substategeo.gdb). Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For census tracts, the water cutouts are derived from a subset of the 2020 Areal Hydrography boundaries offered by TIGER. Water bodies and rivers which are 50 million square meters or larger (mid to large sized water bodies) are erased from the tract level boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2023 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters).The States layer contains 52 records - all US states, Washington D.C., and Puerto RicoCensus tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -4444...) have been set to null, with the exception of -5555... which has been set to zero. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small.

This application is intended for informational purposes only and is not an operational product. The tool provides the capability to access, view and interact with satellite imagery, and shows the latest view of Earth as it appears from space.This website should not be used to support operational observation, forecasting, emergency, or disaster mitigation operations, either public or private. In addition, we do not provide weather forecasts on this site — that is the mission of the National Weather Service. Please contact them for any forecast questions or issues.Using the Maps​What does the Layering Options icon mean?The Layering Options widget provides a list of operational layers and their symbols, and allows you to turn individual layers on and off. The order in which layers appear in this widget corresponds to the layer order in the map. The top layer ‘checked’ will indicate what you are viewing in the map, and you may be unable to view the layers below.Layers with expansion arrows indicate that they contain sublayers or subtypes.Do these maps work on mobile devices and different browsers?Yes!Why are there black stripes / missing data on the map?NOAA Satellite Maps is for informational purposes only and is not an operational product; there are times when data is not available.Why are the North and South Poles dark?The raw satellite data used in these web map apps goes through several processing steps after it has been acquired from space. These steps translate the raw data into geospatial data and imagery projected onto a map. NOAA Satellite Maps uses the Mercator projection to portray the Earth's 3D surface in two dimensions. This Mercator projection does not include data at 80 degrees north and south latitude due to distortion, which is why the poles appear black in these maps. NOAA's polar satellites are a critical resource in acquiring operational data at the poles of the Earth and some of this imagery is available on our website (for example, here ).Why does the imagery load slowly?This map viewer does not load pre-generated web-ready graphics and animations like many satellite imagery apps you may be used to seeing. Instead, it downloads geospatial data from our data servers through a Map Service, and the app in your browser renders the imagery in real-time. Each pixel needs to be rendered and geolocated on the web map for it to load.How can I get the raw data and download the GIS World File for the images I choose?The geospatial data Map Service for the NOAA Satellite Maps GOES satellite imagery is located on our Satellite Maps ArcGIS REST Web Service ( available here ).We support open information sharing and integration through this RESTful Service, which can be used by a multitude of GIS software packages and web map applications (both open and licensed).Data is for display purposes only, and should not be used operationally.Are there any restrictions on using this imagery?NOAA supports an open data policy and we encourage publication of imagery from NOAA Satellite Maps; when doing so, please cite it as "NOAA" and also consider including a permalink (such as this one) to allow others to explore the imagery.For acknowledgment in scientific journals, please use:We acknowledge the use of imagery from the NOAA Satellite Maps application: LINKThis imagery is not copyrighted. You may use this material for educational or informational purposes, including photo collections, textbooks, public exhibits, computer graphical simulations and internet web pages. This general permission extends to personal web pages.About this satellite imageryWhat am I seeing in the Global Archive Map?In this map, you will see the whole Earth as captured each day by our polar satellites, based on our multi-year archive of data. This data is provided by NOAA’s polar orbiting satellites (NOAA/NASA Suomi NPP from January 2014 to April 19, 2018 and NOAA-20 from April 20, 2018 to today). The polar satellites circle the globe 14 times a day taking in one complete view of the Earth every 24 hours. This complete view is what is projected onto the flat map scene each morning.What is global true color imagery?The global ‘true color’ map displays land, water and clouds as they would appear to our eye from space, captured each day by NOAA-20.This ‘true color’ imagery is created using the VIIRS sensors onboard the NOAA-20 and Suomi NPP polar orbiting satellites. Although true-color images like this may appear to be photographs of Earth, they aren't. They are created by combining data from the three color bands on the VIIRS instrument sensitive to the red, green and blue (or RGB) wavelengths of light into one composite image. In addition, data from several other bands are often also included to cancel out or correct atmospheric interference that may blur parts of the image. Learn more about the VIIRS sensor here.About the satellitesWhat is the NOAA-20 satellite?Launched in November 2017, NOAA-20 is NOAA's newest polar-orbiting satellite, and the first of the Joint Polar Satellite System (JPSS) series, a collaborative effort between NOAA and NASA. As the backbone of the global satellite observing system, NOAA-20 circles the Earth from pole to pole and crosses the equator about 14 times daily, providing full global coverage twice daily - from 512 miles away. The satellite's instruments measure temperature, water vapor, ozone, precipitation, fire and volcanic eruptions, and can distinguish snow and ice cover under clouds. This data enables more accurate weather forecasting for the United States and the world.

During a search and rescue (SAR) operation, officials don't have time to wait until a GIS specialist is on scene. They need maps immediately. Preconfigured and ready-to-use GIS tools must be available to SAR teams before an incident occurs.

In this lesson, you'll create a web map to prepare data for search operations. Your map will contain static base data showing regional boundaries and key features, as well as editable layers that can be changed as an incident develops. Then, you'll use the map to create a web app that even non-GIS professionals can use. Finally, you'll use the app to track a fictional SAR mission.

In this lesson you will build skills in the these areas:

• Mapping base and incident data
• Configure widgets in a web app
• Adding Situational Awareness and Smart Editor widgets
• Plotting Initial Planning Point and adding trail blocks
• Creating search assignments
• Mapping incident data

Learn ArcGIS is a hands-on, problem-based learning website using real-world scenarios. Our mission is to encourage critical thinking, and to develop resources that support STEM education.

Services: This segment encompasses consulting, map development and customization, and data collection and processing services.Solutions: Includes ready-to-use mapping solutions for specific industries and applications, such as fleet management, navigation, and disaster response.Functionality: Categorized based on map capabilities, including scientific mapping for research and analysis, GPS navigation for vehicle navigation, and computerized mapping for computer-aided design.Application: Segmented by indoor and outdoor mapping, catering to different use cases and requirements.Technology: Includes Geographic Information Systems (GIS), Digital Orthophotography (DOP), Aerial Photography, and others, each offering unique capabilities for map creation and analysis. Recent developments include: July 2022: Google declared the launch of its Street View experience in India in collaboration with Genesys International, an advanced mapping solutions company, and Tech Mahindra, a provider of digital transformation, consulting, and business re-engineering solutions and services. Google, Tech Mahindra, and Genesys International also plan to extend this to more than around 50 cities by the end of the year 2022.. Potential restraints include: Lack of Skilled Expertise, High Deployment Cost.

The Vermont Flood Ready Atlas is an online-map tool that can help you identify critical facilities, transportation services and buildings in your community that are at risk of damage from flooding. The Atlas can also help you identify local watersheds and the extent of natural flood protection provided by forests, wetlands, floodplains and river corridors.The Vermont Flood Ready Atlas allows you to easily find data about your community and watershed. Nonetheless, you may want to refer to theTips and Tricks section below to get your bearings. If you have any questions, ideas or problems – let us know! Thank you.

For the purposes of training AI-based models to identify (map) road features in rural/remote tropical regions on the basis of true-colour satellite imagery, and subsequently testing the accuracy of these AI-derived road maps, we produced a dataset of 8904 satellite image ‘tiles’ and their corresponding known road features across Equatorial Asia (Indonesia, Malaysia, Papua New Guinea). Methods

1. INPUT 200 SATELLITE IMAGES

The main dataset shared here was derived from a set of 200 input satellite images, also provided here. These 200 images are effectively ‘screenshots’ (i.e., reduced-resolution copies) of high-resolution true-colour satellite imagery (~0.5-1m pixel resolution) observed using the Elvis Elevation and Depth spatial data portal (https://elevation.fsdf.org.au/), which here is functionally equivalent to the more familiar Google Earth. Each of these original images was initially acquired at a resolution of 1920x886 pixels. Actual image resolution was coarser than the native high-resolution imagery. Visual inspection of these 200 images suggests a pixel resolution of ~5 meters, given the number of pixels required to span features of familiar scale, such as roads and roofs, as well as the ready discrimination of specific land uses, vegetation types, etc. These 200 images generally spanned either forest-agricultural mosaics or intact forest landscapes with limited human intervention. Sloan et al. (2023) present a map indicating the various areas of Equatorial Asia from which these images were sourced.
IMAGE NAMING CONVENTION A common naming convention applies to satellite images’ file names: XX##.png where:

XX – denotes the geographical region / major island of Equatorial Asia of the image, as follows: ‘bo’ (Borneo), ‘su’ (Sumatra), ‘sl’ (Sulawesi), ‘pn’ (Papua New Guinea), ‘jv’ (java), ‘ng’ (New Guinea [i.e., Papua and West Papua provinces of Indonesia])

– denotes the ith image for a given geographical region / major island amongst the original 200 images, e.g., bo1, bo2, bo3…

1. INTERPRETING ROAD FEATURES IN THE IMAGES For each of the 200 input satellite images, its road was visually interpreted and manually digitized to create a reference image dataset by which to train, validate, and test AI road-mapping models, as detailed in Sloan et al. (2023). The reference dataset of road features was digitized using the ‘pen tool’ in Adobe Photoshop. The pen’s ‘width’ was held constant over varying scales of observation (i.e., image ‘zoom’) during digitization. Consequently, at relatively small scales at least, digitized road features likely incorporate vegetation immediately bordering roads. The resultant binary (Road / Not Road) reference images were saved as PNG images with the same image dimensions as the original 200 images.

2. IMAGE TILES AND REFERENCE DATA FOR MODEL DEVELOPMENT

The 200 satellite images and the corresponding 200 road-reference images were both subdivided (aka ‘sliced’) into thousands of smaller image ‘tiles’ of 256x256 pixels each. Subsequent to image subdivision, subdivided images were also rotated by 90, 180, or 270 degrees to create additional, complementary image tiles for model development. In total, 8904 image tiles resulted from image subdivision and rotation. These 8904 image tiles are the main data of interest disseminated here. Each image tile entails the true-colour satellite image (256x256 pixels) and a corresponding binary road reference image (Road / Not Road).
Of these 8904 image tiles, Sloan et al. (2023) randomly selected 80% for model training (during which a model ‘learns’ to recognize road features in the input imagery), 10% for model validation (during which model parameters are iteratively refined), and 10% for final model testing (during which the final accuracy of the output road map is assessed). Here we present these data in two folders accordingly:

'Training’ – contains 7124 image tiles used for model training in Sloan et al. (2023), i.e., 80% of the original pool of 8904 image tiles. ‘Testing’– contains 1780 image tiles used for model validation and model testing in Sloan et al. (2023), i.e., 20% of the original pool of 8904 image tiles, being the combined set of image tiles for model validation and testing in Sloan et al. (2023).

IMAGE TILE NAMING CONVENTION A common naming convention applies to image tiles’ directories and file names, in both the ‘training’ and ‘testing’ folders: XX##_A_B_C_DrotDDD where

XX – denotes the geographical region / major island of Equatorial Asia of the original input 1920x886 pixel image, as follows: ‘bo’ (Borneo), ‘su’ (Sumatra), ‘sl’ (Sulawesi), ‘pn’ (Papua New Guinea), ‘jv’ (java), ‘ng’ (New Guinea [i.e., Papua and West Papua provinces of Indonesia])

– denotes the ith image for a given geographical region / major island amongst the original 200 images, e.g., bo1, bo2, bo3…

A, B, C and D – can all be ignored. These values, which are one of 0, 256, 512, 768, 1024, 1280, 1536, and 1792, are effectively ‘pixel coordinates’ in the corresponding original 1920x886-pixel input image. They were recorded within the names of image tiles’ sub-directories and file names merely to ensure that names/directory were uniquely named)

rot – implies an image rotation. Not all image tiles are rotated, so ‘rot’ will appear only occasionally.

DDD – denotes the degree of image-tile rotation, e.g., 90, 180, 270. Not all image tiles are rotated, so ‘DD’ will appear only occasionally.

Note that the designator ‘XX##’ is directly equivalent to the filenames of the corresponding 1920x886-pixel input satellite images, detailed above. Therefore, each image tiles can be ‘matched’ with its parent full-scale satellite image. For example, in the ‘training’ folder, the subdirectory ‘Bo12_0_0_256_256’ indicates that its image tile therein (also named ‘Bo12_0_0_256_256’) would have been sourced from the full-scale image ‘Bo12.png’.

Note: These layers were compiled by Esri's Demographics Team using data from the Census Bureau's American Community Survey. These data sets are not owned by the City of Rochester.Overview of the map/data: This map shows the percentage of the population living below the federal poverty level over the previous 12 months, shown by tract, county, and state boundaries. Estimates are from the 2018 ACS 5-year samples. This service is updated annually to contain the most currently released American Community Survey (ACS) 5-year data, and contains estimates and margins of error. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis. Current Vintage: 2019-2023ACS Table(s): B17020, C17002Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 12, 2024National Figures: data.census.govThe United States Census Bureau's American Community Survey (ACS):About the SurveyGeography & ACSTechnical DocumentationNews & UpdatesThis ready-to-use layer can be used within ArcGIS Pro, ArcGIS Online, its configurable apps, dashboards, Story Maps, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the Census and ACS when using this data.Data Note from the Census:Data are based on a sample and are subject to sampling variability. The degree of uncertainty for an estimate arising from sampling variability is represented through the use of a margin of error. The value shown here is the 90 percent margin of error. The margin of error can be interpreted as providing a 90 percent probability that the interval defined by the estimate minus the margin of error and the estimate plus the margin of error (the lower and upper confidence bounds) contains the true value. In addition to sampling variability, the ACS estimates are subject to nonsampling error (for a discussion of nonsampling variability, see Accuracy of the Data). The effect of nonsampling error is not represented in these tables.Data Processing Notes:This layer will be updated automatically when the most current vintage of ACS data is released each year, usually in December. The layer always contains the latest available ACS 5-year estimates. It is updated annually within days of the Census Bureau's release schedule. Click here to learn more about ACS data releases.Boundaries come from the US Census TIGER geodatabases. Boundaries are updated at the same time as the data updates (annually), and the boundary vintage appropriately matches the data vintage as specified by the Census. These are Census boundaries with water and/or coastlines clipped for cartographic purposes. For census tracts, the water cutouts are derived from a subset of the 2010 AWATER (Area Water) boundaries offered by TIGER. For state and county boundaries, the water and coastlines are derived from the coastlines of the 500k TIGER Cartographic Boundary Shapefiles. The original AWATER and ALAND fields are still available as attributes within the data table (units are square meters). The States layer contains 52 records - all US states, Washington D.C., and Puerto Rico.Census tracts with no population are removed from this data service (Census Tracts beginning with 99).Percentages and derived counts, and associated margins of error, are calculated values (that can be identified by the "_calc_" stub in the field name), and abide by the specifications defined by the American Community Survey.Field alias names were created based on the Table Shells file available from the American Community Survey Summary File Documentation page.Negative values (e.g., -555555...) have been set to null. These negative values exist in the raw API data to indicate the following situations:The margin of error column indicates that either no sample observations or too few sample observations were available to compute a standard error and thus the margin of error. A statistical test is not appropriate.Either no sample observations or too few sample observations were available to compute an estimate, or a ratio of medians cannot be calculated because one or both of the median estimates falls in the lowest interval or upper interval of an open-ended distribution.The median falls in the lowest interval of an open-ended distribution, or in the upper interval of an open-ended distribution. A statistical test is not appropriate.The estimate is controlled. A statistical test for sampling variability is not appropriate.The data for this geographic area cannot be displayed because the number of sample cases is too small. NOTE: any calculated percentages or counts that contain estimates that have null margins of error yield null margins of error for the calculated fields.

This WebMapService (WMS) provides the Digital Map 1: 5000 ready. The Digital Card 1: 5000 (DK5) contains a realistic picture of the Hamburg state territory complemented by topographic content and information as a detailed basis for various applications in business, administration and planning. For a more detailed description of the data and data responsibility, please use the reference to the data record description.