There's a lot going on in marine aquaculture in the United States! NOAA, with its partners, plays a major role in developing environmentally and economically sustainable marine aquaculture practices, technologies and industry in the U.S. Marine aquaculture creates jobs, supports working waterfronts and coastal communities, provides new international trade opportunities, and provides a domestic source of sustainable seafood to complement our wild fisheries. Use this map to check out just some of the recent developments in the domestic marine aquaculture industry in your region, and how NOAA is involved. Click on the individual images to get project details, materials and links.

The Story Map Basic application is a simple map viewer with a minimalist user interface. Apart from the title bar, an optional legend, and a configurable search box the map fills the screen. Use this app to let your map speak for itself. Your users can click features on the map to get more information in pop-ups. The Story Map Basic application puts all the emphasis on your map, so it works best when your map has great cartography and tells a clear story.You can create a Basic story map by sharing a web map as an application from the map viewer. You can also click the 'Create a Web App' button on this page to create a story map with this application. Optionally, the application source code can be downloaded for further customization and hosted on your own web server.For more information about the Story Map Basic application, a step-by-step tutorial, and a gallery of examples, please see this page on the Esri Story Maps website.

To create this app:

GIS is used to provide a visual representation of data by placing it on a map, providing an easy to understand, spatial view of information.GIS is used in all sorts of ways, from routing of delivery services and emergency vehicles to providing an interactive platform for viewing and understanding data within the county. Examples of this include Parcel data, election districts, the county's municipal boundaries, and much more!

In 2012 we started collaborating with commercial river guides (http://www.gcrg.org/) and Grand Canyon Youth (http://www.gcyouth.org/) to quantify insect emergence throughout the 240 mile long segment of the Colorado River in Marble and Grand Canyon. Each night in camp, guides put out a simple light trap to collect flying insects. After one hour, the light was turned off, the sample poured into a collection bottle, and some notes were recorded in a field book. After the conclusion of the river trip, guides dropped off samples and field notes at our office and we processed the samples in the laboratory. This project is ongoing and will be conducted annually. This web application shows data collected as part of this Citizen Science initiative for the years 2012 to 2014.

Open the Data Resource: https://geonarrative.usgs.gov/uscoastalwetlandsynthesis/ The U.S. Geological Survey is using field observations and remote-sensing data to assess the physical condition of coastal wetlands and their response to external forces. The Coastal Wetland Synthesis Story Maps collection introduces four use-cases of the data to address diverse stakeholder needs in the coastal zone.

The District of Columbia shares story maps that combine impacting narratives and multimedia with data and analytics. These examples support agency programs and help educate how DC is using its data.

The map displays examples from across the country of different organizations using MarineCadastre.gov data and products to meet their specific needs. A broad range of uses are covered, including evaluating impacts of offshore energy on navigation safety, researching how noise from large commercial vessels may affect marine mammals, and creating maps of proposed wave energy projects. Access to these data is provided by MarineCadastre.gov, a joint Bureau of Ocean Energy Management and National Oceanic and Atmospheric Administration initiative providing authoritative data to meet the needs of the offshore energy and marine planning communities.

Preserving and enhancing the discoverability of scientific information about geologic cores and samples.

This story map describes and demonstrates how OpenStreetMap (OSM) data is accessible in ArcGIS, and how ArcGIS users can help to improve OSM with their GIS data. Learn the various ways in which you can access OSM data for your work, and how you can share data to be used in OSM.OpenStreetMap is a free, editable map of the world built by a community of mappers that contribute and maintain geospatial data about our world. It includes a worldwide database that is maintained by over 8 million registered users, with millions of map changes each day. Esri provides access to OSM data to ArcGIS users in multiple ways, including hosted vector tiles, feature layers, and scene layers.This story map shows several examples of how you can access OSM data in your work, and how ArcGIS organizations (e.g. cities, counties, states, nations) can share data they maintain (e.g. buildings, addresses, roads) to be used in OSM. The story illustrates the open data pipeline between ArcGIS and OSM, where open data created and published with ArcGIS can flow to OpenStreetMap and then OSM data flows back again to ArcGIS.

Open the Data Resource: https://gis.chesapeakebay.net/viz/coastal/ This story map explains how 3-D landscape basecamps can be built, using an example that assesses the impacts of sea level rise on Norfolk, Virginia, within the context of global sea level rise.

This template is in Mature Support. Esri offers several other crowdsourcing and data collection apps. Story Map Crowdsource is a configurable application that lets you set up a Story Map that anyone can contribute to. Use it to engage a specific or general audience and collect their pictures and captions on any topic that interests you. Participants can log in with their social media account or ArcGIS account. When you configure a Crowdsource story, an interactive builder makes it easy to create your story and optionally review and approve contributions before they appear on the map.Use CasesStory Map Crowdsource can be used to create a crowdsourced map of photos related to any topic, event, or cause. The submissions can be all from a single neighborhood or from all over the world. Here are some examples:National Park MemoriesEsri 2016 User ConferenceGIS DayHonoring our VeteransUrban Food MovementConfigurable OptionsThe following aspects of a Story Map Crowdsource app can be configured using the Builder:Title, cover image, cover message, header logo and click-through link, button labels, social sharing options, and home map viewAuthentication services participants can use to sign inWhether new contributions are being acceptedWhether new contributions appear on the map immediately or only after the author approves themSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsStory Map Crowdsource does not require you to provide any geographic content, but a web map and feature service are created for your story in your account when the Builder is launched. An ArcGIS account with Publisher permissions is required to create a Crowdsource story.Get Started This application can be created in the following ways:Click the Create a Web App button on this page (sign in required)Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.For more information, see this FAQ and these blog posts..

This layer shows demographic context for emergency response efforts. 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 households who do not have access to internet. 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): B01001, B08201, B09021, B16003, B16004, B17020, B18101, B25040, B25117, B27010, B28001, B28002 Data 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.

General Accessibility Creative Commons All data products available from the data hub are provided on an 'as is' basis. The City of Sydney (City) makes no warranty, representation or guarantee of any type as to any errors and omissions, or as to the content, accuracy, timeliness, completeness or fitness for any particular purpose or use of any data product available from the data hub. If you find any information that you believe may be inaccurate, please email the City. In addition, please note that the data products available from the data hub are not intended to constitute advice and must not be used as a substitute for professional advice. The City may modify the data products available from the data hub and/or discontinue providing any or all of data products at any time and for any reason, without notice. Accordingly, the City recommends that you regularly check the data hub to ensure that the latest version of data products is used. The City recommends that when accessing data sets, you use APIs. We are committed to making our website as accessible and user-friendly as possible. Web Content Accessibility Guidelines (WCAG) cover a wide set of recommendations to make websites accessible. For more information on WCAG please visit https://www.w3.org/TR/WCAG21/ . This site is built using Esri's ArcGIS Hubs template, and their Accessibility status report is available online at https://hub.arcgis.com/pages/a11y. We create the maps and stories on this site using ArcGIS templates, each template having accessibility features. Examples include Instant Apps, Story maps, and Webapp builder. If you would like to request alternative formats for data products on this site please email the City. We encourage developers using our data to deliver maps and applications with consideration to accessibility for all. Design elements can include colour, contrast, symbol size and style, font size and style, basemap style, alternate text for images, and captions for video and audio. Alternative content such as static maps may sometimes be required. Unless otherwise stated, data products available from the data hub are published under Creative Commons licences. Creative Commons licences include terms and conditions about how licensed data products may be used, shared and/or adapted. Depending on the applicable licence, licensed data products may or may not be used for commercial purposes. The applicable Creative Commons licence for specific data is specified in the "Licence" section of the data description. By accessing, sharing and/or adapting licensed data products, you are deemed to have accepted the terms and conditions of the applicable Creative Common licence. For more information about Creative Commons licences, please visit https://creativecommons.org.au/ and https://creativecommons.org/faq/ If you believe that the applicable Creative Commons licence for the data product that you wish to use is overly restrictive for how you would like to use the data product, please email the City. Contact If you have a question, comments, or requests for interactive maps and data, we would love to hear from you. Council business For information on rates, development applications, strategies, reports and other council business, see the City of Sydney's main website.

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: 2015-2019ACS Table(s): B08303Data downloaded from: Census Bureau's API for American Community Survey Date of API call: December 10, 2020National 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. 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 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 layer shows population broken down by race and Hispanic origin. 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 predominant race living within an area. 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): B03002Data 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.

The datasets used for this manuscript were derived from multiple sources: Denver Public Health, Esri, Google, and SafeGraph. Any reuse or redistribution of the datasets are subjected to the restrictions of the data providers: Denver Public Health, Esri, Google, and SafeGraph and should consult relevant parties for permissions.1. COVID-19 case dataset were retrieved from Denver Public Health (Link: https://storymaps.arcgis.com/stories/50dbb5e7dfb6495292b71b7d8df56d0a )2. Point of Interests (POIs) data were retrieved from Esri and SafeGraph (Link: https://coronavirus-disasterresponse.hub.arcgis.com/datasets/6c8c635b1ea94001a52bf28179d1e32b/data?selectedAttribute=naics_code) and verified with Google Places Service (Link: https://developers.google.com/maps/documentation/javascript/reference/places-service)3. The activity risk information is accessible from Texas Medical Association (TMA) (Link: https://www.texmed.org/TexasMedicineDetail.aspx?id=54216 )The datasets for risk assessment and mapping are included in a geodatabase. Per SafeGraph data sharing guidelines, raw data cannot be shared publicly. To view the content of the geodatabase, users should have installed ArcGIS Pro 2.7. The geodatabase includes the following:1. POI. Major attributes are locations, name, and daily popularity.2. Denver neighborhood with weekly COVID-19 cases and computed regional risk levels.3. Simulated four travel logs with anchor points provided. Each is a separate point layer.

This layer shows median household income by race and by age of householder. 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. Median income and income source is based on income in past 12 months of survey. This layer is symbolized to show median household income. 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): B19013B, B19013C, B19013D, B19013E, B19013F, B19013G, B19013H, B19013I, B19049, B19053Data 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 is an Expansion and Subset of the Internal Knowledge Map dataset that focuses on Story Writing and Role Playing. I was curious to see if I could adapt my IKM structure and approach to improve Story Telling, Role Playing/Character/Discourse in an LLM. Here are 2,071 highly-detailed and unique examples that allow an LLM to exhibit more depth, diverse perspectives and novel interactions. Side benefit is the LLM also writes in well-formed, aesthetically pleasing formatting and is an… See the full description on the dataset page: https://huggingface.co/datasets/Severian/Internal-Knowledge-Map-StoryWriter-RolePlaying.

This resources contains PDF files and Python notebook files that demonstrate how to create geospatial resources in HydroShare and how to use these resources through web services provided by the built-in HydroShare GeoServer instance. Geospatial resources can be consumed directly into ArcMap, ArcGIS, Story Maps, Quantum GIS (QGIS), Leaflet, and many other mapping environments. This provides HydroShare users with the ability to store data and retrieve it via services without needing to set up new data services. All tutorials cover how to add WMS and WFS connections. WCS connections are available for QGIS and are covered in the QGIS tutorial. The tutorials and examples provided here are intended to get the novice user up-to-speed with WMS and GeoServer, though we encourage users to read further on these topic using internet searches and other resources. Also included in this resource is a tutorial designed to that walk users through the process of creating a GeoServer connected resource.

The current list of available tutorials: - Creating a Resource - ArcGIS Pro - ArcMap - ArcGIS Story Maps - QGIS - IpyLeaflet - Folium