To create this app:Make a map of the AfDB projects CSV file in the Training Materials group.Download the CSV file, click Map (at the top of the page), and drag and drop the file onto your mapFrom the layer menu on your Projects layer choose Change Symbols and show the projects using Unique Symbols and the Status of field.Make a second map of the AfDB projects shown using Unique Symbols and the Sector field.HINT: Create a copy of your first map using Save As... and modify the copy.Assemble your story map on the Esri Story Maps websiteGo to storymaps.arcgis.comAt the top of the site, click AppsFind the Story Map Tabbed app and click Build a Tabbed Story MapFollow the instructions in the app builder. Add the maps you made in previous steps and copy the text from this sample app to your app. Explore and experiment with the app configuration settings.=============OPTIONAL - Make a third map of the AFDB projects summarized by country and add it to your story map.Add the World Countries layer to your map (Add > Search for Layers)From the layer menu on your Projects layer choose Perform Analysis > Summarize Data > Aggregate Points and run the tool to summarize the projects in each country.HINT: UNCHECK "Keep areas with no points"Experiment with changing the symbols and settings on your new layer and remove other unnecessary layers.Save AS... a new map.At the top of the site, click My Content.Find your story map application item, open its Details page, and click Configure App.Use the builder to add your third map and a description to the app and save it.
The Community Map (WGS84) (World Edition) web map provides a customized world basemap that is uniquely symbolized and optimized to display special areas of interest (AOIs) that have been created and edited by Community Maps contributors. These special areas of interest include landscaping features such as grass, trees, and sports amenities like tennis courts, football and baseball field lines, and more. This basemap, included in the ArcGIS Living Atlas of the World, uses the Community (WGS84) vector tile layer.The vector tile layer in this web map is built using the same data sources used for other Esri Vector Basemaps. For details on data sources contributed by the GIS community, view the map of Community Maps Basemap Contributors. Esri Vector Basemaps WGS84 are updated quarterly.Check out other WGS84 basemaps in the World Basemaps (WGS84) group. Use this MapThis map is designed to be used as a basemap for overlaying other layers of information or as a stand-alone reference map. You can add layers to this web map and save as your own map. If you like, you can add this web map to a custom basemap gallery for others in your organization to use in creating web maps. If you would like to add this map as a layer in other maps you are creating, you may use the layer referenced in this map.Precise Tile Registration The map uses the improved tiling scheme “WGS84 Geographic, Version 2” to ensure proper tile positioning at higher resolutions (neighborhood level and beyond). The new tiling scheme is much more precise than tiling schemes of the legacy basemaps Esri released years ago. We recommend that you start using this new basemap for any new web maps in WGS84 that you plan to author. Due to the number of differences between the old and new tiling schemes, some web clients will not be able to overlay tile layers in the old and new tiling schemes in one web map.
Map Information
This nowCOAST time-enabled map service provides maps depicting the latest global forecast guidance of water currents, water temperature, and salinity at forecast projections: 0, 12, 24, 36, 48, 60, 72, 84, and 96-hours from the NWS/NCEP Global Real-Time Ocean Forecast System (GRTOFS). The surface water currents velocity maps displays the direction using white or black streaklets. The magnitude of the current is indicated by the length and width of the streaklet. The maps of the GRTOFS surface forecast guidance are updated on the nowCOAST map service once per day. For more detailed information about the update schedule, see: http://new.nowcoast.noaa.gov/help/#section=updateschedule
Background Information
GRTOFS is based on the Hybrid Coordinates Ocean Model (HYCOM), an eddy resolving, hybrid coordinate numerical ocean prediction model.
GRTOFS has global coverge and a horizontal resolution of 1/12 degree and 32 hybrid vertical layers. It has one forecast cycle per day
(i.e. 0000 UTC) which generates forecast guidance out to 144 hours (6 days). However, nowCOAST only provides guidance out to 96 hours (4 days).
The forecast cycle uses 3-hourly momentum and radiation fluxes along
with precipitation predictions from the NCEP Global Forecast System (GFS). Each forecast cycle is preceded with a 48-hr long nowcast cycle.
The nowcast cycle uses daily initial 3-D fields from the NAVOCEANO operational HYCOM-based forecast system which assimilates situ profiles
of temperature and salinity from a variety of sources and remotely sensed SST, SSH and sea-ice concentrations. GRTOFS was developed by
NCEP/EMC/Marine Modeling and Analysis Programs. GRTOFS is run once per day (0000 UTC forecast cycle) on the NOAA Weather and Climate Operational Supercomputer System
(WCOSS) operated by NWS/NCEP Central Operations.
The maps are generated using a visualization technique was developed by the Data Visualization Research Lab at The University of New Hampshire Center for Coastal and Ocean Mapping (http://www.ccom.unh.edu/vislab/). The method combines two techniques. First, equally spaced streamlines are computed in the flow field using Jobard and Lefer's (1977) algorithm. Second, a series of "streaklets" are rendered head to tail along each streamline to show the direction of flow. Each of these varies along its length in size, color and transparency using a method developed by Fowler and Ware (1989), and later refined by Mr. Pete Mitchell and Dr. Colin Ware (Mitchell, 2007).
Time Information
This map is time-enabled, meaning that each individual layer contains time-varying data and can be utilized by clients capable of making map requests that include a time component.
This particular service can be queried with or without the use of a time component. If the time parameter is specified in a request, the data or imagery most relevant to the provided time value, if any, will be returned. If the time parameter is not specified in a request, the latest data or imagery valid for the present system time will be returned to the client. If the time parameter is not specified and no data or imagery is available for the present time, no data will be returned.
In addition to ArcGIS Server REST access, time-enabled OGC WMS 1.3.0 access is also provided by this service.
Due to software limitations, the time extent of the service and map layers displayed below does not provide the most up-to-date start and end times of available data. Instead, users have three options for determining the latest time information about the service:
Issue a returnUpdates=true request for an individual layer or for
the service itself, which will return the current start and end times of
available data, in epoch time format (milliseconds since 00:00 January 1,
1970). To see an example, click on the "Return Updates" link at the bottom of
this page under "Supported Operations". Refer to the
ArcGIS REST API Map Service Documentation
for more information.
Issue an Identify (ArcGIS REST) or GetFeatureInfo (WMS) request against
the proper layer corresponding with the target dataset. For raster
data, this would be the "Image Footprints with Time Attributes" layer
in the same group as the target "Image" layer being displayed. For
vector (point, line, or polygon) data, the target layer can be queried
directly. In either case, the attributes returned for the matching
raster(s) or vector feature(s) will include the following:
validtime: Valid timestamp.
starttime: Display start time.
endtime: Display end time.
reftime: Reference time (sometimes reffered to as
issuance time, cycle time, or initialization time).
projmins: Number of minutes from reference time to valid
time.
desigreftime: Designated reference time; used as a
common reference time for all items when individual reference
times do not match.
desigprojmins: Number of minutes from designated
reference time to valid time.
Query the nowCOAST LayerInfo web service, which has been created to
provide additional information about each data layer in a service,
including a list of all available "time stops" (i.e. "valid times"),
individual timestamps, or the valid time of a layer's latest available
data (i.e. "Product Time"). For more information about the LayerInfo
web service, including examples of various types of requests, refer to
the nowCOAST help documentation at:
http://new.nowcoast.noaa.gov/help/#section=layerinfo
References
Fowler, D. and C. Ware, 1989: Strokes for Representing Vector Field Maps. Proceedings: Graphics Interface '98 249-253. Jobard, B and W. Lefer,1977: Creating evenly spaced streamlines of arbitrary density. Proceedings: Eurographics workshop on Visualization in Scientific Computing. 43-55. Mitchell, P.W., 2007: The Perceptual optimization of 2D Flow Visualizations Using Human in the Loop Local Hill Climbing. University of New Hampshire Masters Thesis. Department of Computer Science. NWS, 2013: About Global RTOFS, NCEP/EMC/MMAB, College Park, MD (Available at http://polar.ncep.noaa.gov/global/about/). Chassignet, E.P., H.E. Hurlburt, E.J. Metzger, O.M. Smedstad, J. Cummings, G.R. Halliwell, R. Bleck, R. Baraille, A.J. Wallcraft, C. Lozano, H.L. Tolman, A. Srinivasan, S. Hankin, P. Cornillon, R. Weisberg, A. Barth, R. He, F. Werner, and J. Wilkin, 2009: U.S. GODAE: Global Ocean Prediction with the HYbrid Coordinate Ocean Model (HYCOM). Oceanography, 22(2), 64-75. Mehra, A, I. Rivin, H. Tolman, T. Spindler, and B. Balasubramaniyan, 2011: A Real-Time Operational Global Ocean Forecast System, Poster, GODAE OceanView –GSOP-CLIVAR Workshop in Observing System Evaluation and Intercomparisons, Santa Cruz, CA.
When rain falls over land, a portion of it runs off into stream channels and storm water systems while the remainder infiltrates into the soil or returns to the atmosphere directly through evaporation.Physical properties of soil affect the rate that water is absorbed and the amount of runoff produced by a storm. Hydrologic soil group provides an index of the rate that water infiltrates a soil and is an input to rainfall-runoff models that are used to predict potential stream flow.For more information on using hydrologic soil group in hydrologic modeling see the publication Urban Hydrology for Small Watersheds (Natural Resources Conservation Service, United States Department of Agriculture, Technical Release–55).Dataset SummaryPhenomenon Mapped: Soil hydrologic groupUnits: ClassesCell Size: 30 metersSource Type: DiscretePixel Type: Unsigned integerData Coordinate System: WKID 5070 USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WKID 3338 WGS 1984 Albers (Alaska), WKID 4326 WGS 1984 Decimal Degrees (Guam, Republic of the Marshall Islands, Northern Mariana Islands, Republic of Palau, Federated States of Micronesia, American Samoa, and Hawaii).Mosaic Projection: Web Mercator Auxiliary SphereExtent: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands, Republic of Palau, Republic of the Marshall Islands, Federated States of Micronesia, and American Samoa.Source: Natural Resources Conservation ServicePublication Date: November 2023ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/Data from the gNATSGO database was used to create the layer for the for the contiguous United States and Alaska. The remaining areas were created with the gSSURGO database (Hawaii, Guam, Puerto Rico, the U.S. Virgin Islands, Northern Marianas Islands, Palau, Federated States of Micronesia, Republic of the Marshall Islands, and American Samoa).This layer is derived from the 30m (contiguous U.S.) and 10m rasters (all other regions) produced by the Natural Resources Conservation Service (NRCS). The value for hydrologic group is derived from the gSSURGO map unit aggregated attribute table field Hydrologic Group - Dominant Conditions (hydgrpdcd).The seven classes of hydrologic soil group followed by definitions:Group A - Group A soils consist of deep, well drained sands or gravelly sands with high infiltration and low runoff rates.Group B - Group B soils consist of deep well drained soils with a moderately fine to moderately coarse texture and a moderate rate of infiltration and runoff.Group C - Group C consists of soils with a layer that impedes the downward movement of water or fine textured soils and a slow rate of infiltration.Group D - Group D consists of soils with a very slow infiltration rate and high runoff potential. This group is composed of clays that have a high shrink-swell potential, soils with a high water table, soils that have a clay pan or clay layer at or near the surface, and soils that are shallow over nearly impervious material.Group A/D - Group A/D soils naturally have a very slow infiltration rate due to a high water table but will have high infiltration and low runoff rates if drained.Group B/D - Group B/D soils naturally have a very slow infiltration rate due to a high water table but will have a moderate rate of infiltration and runoff if drained.Group C/D - Group C/D soils naturally have a very slow infiltration rate due to a high water table but will have a slow rate of infiltration if drained.What can you do with this Layer? This layer is suitable for both visualization and analysis across the ArcGIS system. This layer can be combined with your data and other layers from the ArcGIS Living Atlas of the World in ArcGIS Online and ArcGIS Pro to create powerful web maps that can be used alone or in a story map or other application.Because this layer is part of the ArcGIS Living Atlas of the World it is easy to add to your map:In ArcGIS Online, you can add this layer to a map by selecting Add then Browse Living Atlas Layers. A window will open. Type "soil hydrologic group" in the search box and browse to the layer. Select the layer then click Add to Map.In ArcGIS Pro, open a map and select Add Data from the Map Tab. Select Data at the top of the drop down menu. The Add Data dialog box will open on the left side of the box, expand Portal if necessary, then select Living Atlas. Type "soil hydrologic group" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions or create your own to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.Online you can filter the layer to show subsets of the data using the filter button and the layer's built-in raster functions.The ArcGIS Living Atlas of the World provides an easy way to explore many other beautiful and authoritative maps on hundreds of topics like this one.
In 2016 NYC Parks contracted with the UVM Spatial Analysis Lab to use modern remote sensing and object-based image analysis to create a new wetlands map for New York City. Data inputs include Light Detection and Ranging Data, State and Federal Wetland Inventories, soils, and field data. Because the map was conservative in its wetlands predictions, NYC Parks staff improved the map through a series of desktop and field verification efforts. From June to November 2020, NYC Parks staff field verified the majority of wetlands on NYC Parks' property. The map will be opportunistically updated depending on available field information and delineations. Another dedicated field verification effort has not been planned. As of June 2021, no subsequent updates to the data are scheduled. Original field names were updated to field names that are easier to understand. This dataset was developed to increase awareness regarding the location and extent of wetlands to promote restoration and conservation in New York City. This map does not supersede U.S. Fish and Wildlife Service National Wetlands Inventory (NWI) and New York State Department of Environmental Conservation (NYSDEC) wetlands maps and has no jurisdictional authority. It should be used alongside NWI and NYSDEC datasets as a resource for identifying likely locations of wetlands in New York City. Mapped features vary in the confidence of their verification status, ranging from "Unverified" (meaning the feature exists in its original remotely mapped form and has not been ground truthed) to "Verified - Wetland Delineation" (meaning the boundaries and type of wetland have been verified during an official wetland delineation). Because of the rapid nature of the protocol and the scale of data collection, this product is not a subsitute for on-site investigations and field delineations. The dataset also includes broad classifications for each wetland type, e.g. estuarine, emergent wetland, forested wetland, shrub/scrub wetland, or water. Cowardin classifcations were not used given rapid verfication methods. The accuracy of the wetlands map has improved over time as a result of the verification process. Fields were added over time as necessitated by the workflow and values were updated with information, either from the field verifications, delineation reports, or desktop analysis. OBJECTID, Shape, Class_Name_Final, Verification_Status, Create_Date, Last_Edited_Date, Verification_Status_Year, SHAPE_Length, SHAPE_Area https://www.nycgovparks.org/greening/natural-resources-group Data Dictionary: https://docs.google.com/spreadsheets/d/1a45qCho45MV-AuOlGxyaRp0cg3cRFKw4lAYBIaU3zi4/edit#gid=260500519 Map: https://data.cityofnewyork.us/dataset/NYC-Wetlands/7piy-bhr9
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
This Coastal Barrier Resources System (CBRS) data set, produced by the U.S. Fish and Wildlife Service (Service), contains areas designated as undeveloped coastal barriers in accordance with the Coastal Barrier Resources Act (CBRA), 16 U.S.C. 3501 et seq., as amended. The boundaries used to create the polygons herein were compiled from the official John H. Chafee Coastal Barrier Resources System CBRS maps, which are accessible at the Service’s Headquarters office or https://www.fws.gov/program/coastal-barrier-resources-act/maps-and-data. These digital polygons are only representations of the CBRS boundaries shown on the official CBRS maps and are not to be considered authoritative. The Service is not responsible for any misuse or misinterpretation of this digital data set, including use of the data to determine eligibility for federal financial assistance such as federal flood insurance. As maps are revised, this data set will be updated with the new boundaries. CBRS boundaries viewed using the CBRS Mapper or the shapefile are subject to misrepresentations beyond the Service’s control, including misalignments of the boundaries with third party base layers and mis-projections of spatial data. The official CBRS map is the controlling document and should be consulted for all official determinations. Official determinations are recommended for all properties that are in close proximity (within 20 feet) of a CBRS boundary. For an official determination of whether or not an area or specific property is located within the CBRS, please follow the procedures found at https://www.fws.gov/service/coastal-barrier-resources-system-property-documentation. For any questions regarding the CBRS, please contact your local Service field office or email CBRA@fws.gov. Contact information for Service field offices can be found at https://www.fws.gov/our-facilities.Data Set Contact: U.S. Fish and Wildlife Service Natural Resource Program Center, GIS Team Lead, richard_easterbrook@fws.gov
Crowdsource Reporter is a configurable group app template that can be used for submitting a variety of issues or observations in a single application. Reports can be submitted anonymously, by ArcGIS named users or Twitter users. The app can also be configured to support voting for and commenting on reports submitted by others.Use CasesCrowdsource Reporter can be configured to collect information for a wide variety of topics including:citizen service requestscommunity health and safety reportscitizen science reportsreporting damaged utility assetscollecting real estate property listingsConfigurable OptionsConfigure Crowdsource Reporter to present a group of maps with editable layers, and personalize the app by modifying the following options: Customize the splash screen with a background image, title, subtitle, and options for signing in to the appSet a theme color, icon, and app messaging that suit your organizationChoose to allow users to vote and/or comment on reportsSupported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsCrowdsource Reporter requires an ArcGIS Online group that contains at least one map with at least one editable feature layer. In addition, the following requirements must be met to expose full app functionality:To enable votes, this layer must have a numeric field for storing the number of votes on each featureTo collect comments, the feature layer must have a related tableTo allow authenticated users to track reports they have submitted, the layer must have a text field for storing a GUID associated with their accountTo allow users to submit supporting documents with the reports, the layer must support attachmentsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a group and choose to Create a Web AppOn the Content page, click Create - App - From Template 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.Learn MoreFor release notes and more information on configuring this app, see the Crowdsource Reporter documentation.
RECOVER supports assessment of vegetation community structure and landscape pattern via various means: ground truthing and related mapping of field morphometrics, community and species identification along elevation gradients (marl prairie to ridge and slough gradients), and community typing via photogrammetry. The focus of this initiative is on methods development using new satellite imagery (with greater spectral and spatial resolution). New imagery and new methods (including technological advancements) make remote sensing using the Digital Globe WorldView 2 imagery a strong candidate to track landscape and vegetative change within the Everglades CERP footprint. Information gained from this and related efforts is expected to provide future guidance relevant to CERP project implementation and structure operations. This scope is written as part of the RECOVER Monitoring and Assessment Plan (MAP) section 3.1.3 and 3.1.4. The objectives include: • Develop vegetation/landscape community maps and assess effectiveness of mapping using WorldView 2 imagery. 1) Acquire needed imagery (in consultation with RECOVER GE working group to determine most relevant areas of expected change given expected CERP project sequencing and implementation. As well as considering the location of available or expected ground truthing information- GRTS panels, marl prairie- slough transects and photogrammetric mapping in ENP). 2) Create map above and below Tamiami trail upstream and downstream of 1 mile bridge 3) Create map of Ridge and Slough, Tree Island, wet prairie habitat in WCA3A (using the same panels as the RECOVER R&S landscape contract- Heffernan)
• Investigate and characterize the spectral and metric qualities of the Worldview-2 data as related to specific aspects of the sensor, data acquisition, and level of processing (including available band combinations, angle of acquisition, sun elevation angle, method of geo-referencing, etc). • Investigate and characterize the outcome of spatial re-sampling on the spectral integrity of the imagery and on the type of landscape information that can be derived at various spatial scales with the intent of comparing the results to similar work of this type (e.g. 30 m Landsat classification of the Everglades.
This layer presents the best-known point and perimeter locations of wildfire occurrences within the United States over the past 7 days. Points mark a location within the wildfire area and provide current information about that wildfire. Perimeters are the line surrounding land that has been impacted by a wildfire.Consumption Best Practices:
As a service that is subject to very high usage, ensure peak performance and accessibility of your maps and apps by avoiding the use of non-cacheable relative Date/Time field filters. To accommodate filtering events by Date/Time, we suggest using the included "Age" fields that maintain the number of days or hours since a record was created or last modified, compared to the last service update. These queries fully support the ability to cache a response, allowing common query results to be efficiently provided to users in a high demand service environment. When ingesting this service in your applications, avoid using POST requests whenever possible. These requests can compromise performance and scalability during periods of high usage because they too are not cacheable.Source: Wildfire points are sourced from Integrated Reporting of Wildland-Fire Information (IRWIN) and perimeters from National Interagency Fire Center (NIFC). Current Incidents: This layer provides a near real-time view of the data being shared through the Integrated Reporting of Wildland-Fire Information (IRWIN) service. IRWIN provides data exchange capabilities between participating wildfire systems, including federal, state and local agencies. Data is synchronized across participating organizations to make sure the most current information is available. The display of the points are based on the NWCG Fire Size Classification applied to the daily acres attribute.Current Perimeters: This layer displays fire perimeters posted to the National Incident Feature Service. It is updated from operational data and may not reflect current conditions on the ground. For a better understanding of the workflows involved in mapping and sharing fire perimeter data, see the National Wildfire Coordinating Group Standards for Geospatial Operations.Update Frequency: Every 15 minutes using the Aggregated Live Feed Methodology based on the following filters:Events modified in the last 7 daysEvents that are not given a Fire Out DateIncident Type Kind: FiresIncident Type Category: Prescribed Fire, Wildfire, and Incident Complex
Area Covered: United StatesWhat can I do with this layer? The data includes basic wildfire information, such as location, size, environmental conditions, and resource summaries. Features can be filtered by incident name, size, or date keeping in mind that not all perimeters are fully attributed.Attribute InformationThis is a list of attributes that benefit from additional explanation. Not all attributes are listed.Incident Type Category: This is a breakdown of events into more specific categories.Wildfire (WF) -A wildland fire originating from an unplanned ignition, such as lightning, volcanos, unauthorized and accidental human caused fires, and prescribed fires that are declared wildfires.Prescribed Fire (RX) - A wildland fire originating from a planned ignition in accordance with applicable laws, policies, and regulations to meet specific objectives.Incident Complex (CX) - An incident complex is two or more individual incidents in the same general proximity that are managed together under one Incident Management Team. This allows resources to be used across the complex rather than on individual incidents uniting operational activities.IrwinID: Unique identifier assigned to each incident record in both point and perimeter layers.
Acres: these typically refer to the number of acres within the current perimeter of a specific, individual incident, including unburned and unburnable islands.Discovery: An estimate of acres burning upon the discovery of the fire.Calculated or GIS: A measure of acres calculated (i.e., infrared) from a geospatial perimeter of a fire.Daily: A measure of acres reported for a fire.Final: The measure of acres within the final perimeter of a fire. More specifically, the number of acres within the final fire perimeter of a specific, individual incident, including unburned and unburnable islands.
Dates: the various systems contribute date information differently so not all fields will be populated for every fire.FireDiscovery: The date and time a fire was reported as discovered or confirmed to exist. May also be the start date for reporting purposes.
Containment: The date and time a wildfire was declared contained. Control: The date and time a wildfire was declared under control.ICS209Report: The date and time of the latest approved ICS-209 report.Current: The date and time a perimeter is last known to be updated.FireOut: The date and time when a fire is declared out.ModifiedOnAge: (Integer) Computed days since event last modified.DiscoveryAge: (Integer) Computed days since event's fire discovery date.CurrentDateAge: (Integer) Computed days since perimeter last modified.CreateDateAge: (Integer) Computed days since perimeter entry created.
GACC: A code that identifies one of the wildland fire geographic area coordination centers. A geographic area coordination center is a facility that is used for the coordination of agency or jurisdictional resources in support of one or more incidents within a geographic coordination area.Fire Mgmt Complexity: The highest management level utilized to manage a wildland fire event.Incident Management Organization: The incident management organization for the incident, which may be a Type 1, 2, or 3 Incident Management Team (IMT), a Unified Command, a Unified Command with an IMT, National Incident Management Organization (NIMO), etc. This field is null if no team is assigned.Unique Fire Identifier: Unique identifier assigned to each wildland fire. yyyy = calendar year, SSUUUU = Point Of Origin (POO) protecting unit identifier (5 or 6 characters), xxxxxx = local incident identifier (6 to 10 characters)RevisionsJan 4, 2021: Added Integer fields 'Days Since...' to Current_Incidents point layer and Current_Perimeters polygon layer. These fields are computed when the data is updated, reflecting the current number of days since each record was last updated. This will aid in making 'age' related, cache friendly queries.Mar 12, 2021: Added second set of 'Age' fields for Event and Perimeter record creation, reflecting age in Days since service data update.Apr 21, 2021: Current_Perimeters polygon layer is now being populated by NIFC's newest data source. A new field was added, 'IncidentTypeCategory' to better distinguish Incident types for Perimeters and now includes type 'CX' or Complex Fires. Five fields were not transferrable, and as a result 'Comments', 'Label', 'ComplexName', 'ComplexID', and 'IMTName' fields will be Null moving forward.Apr 26, 2021: Updated Incident Layer Symbology to better clarify events, reduce download size and overhead of symbols. Updated Perimeter Layer Symbology to better distingish between Wildfires and Prescribed Fires.May 5, 2021: Slight modification to Arcade logic for Symbology, refining Age comparison to Zero for fires in past 24-hours.Aug 16, 2021: Enabled Time Series capability on Layers (off by default) using 'Fire Discovery Date' for Incidents and 'Creation Date' for Perimeters.This layer is provided for informational purposes and is not monitored 24/7 for accuracy and currency.If you would like to be alerted to potential issues or simply see when this Service will update next, please visit our Live Feed Status Page!
This layer shows total population count by sex and age group. 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 the population that are considered dependent (ages 65+ and <18). 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): B01001Data 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.
MIT Licensehttps://opensource.org/licenses/MIT
License information was derived automatically
The Cooperative Land Cover Map is a project to develop an improved statewide land cover map from existing sources and expert review of aerial photography. The project is directly tied to a goal of Florida's State Wildlife Action Plan (SWAP) to represent Florida's diverse habitats in a spatially-explicit manner. The Cooperative Land Cover Map integrates 3 primary data types: 1) 6 million acres are derived from local or site-specific data sources, primarily on existing conservation lands. Most of these sources have a ground-truth or local knowledge component. We collected land cover and vegetation data from 37 existing sources. Each dataset was evaluated for consistency and quality and assigned a confidence category that determined how it was integrated into the final land cover map. 2) 1.4 million acres are derived from areas that FNAI ecologists reviewed with high resolution aerial photography. These areas were reviewed because other data indicated some potential for the presence of a focal community: scrub, scrubby flatwoods, sandhill, dry prairie, pine rockland, rockland hammock, upland pine or mesic flatwoods. 3) 3.2 million acres are represented by Florida Land Use Land Cover data from the FL Department of Environmental Protection and Water Management Districts (FLUCCS). The Cooperative Land Cover Map integrates data from the following years: NWFWMD: 2006 - 07 SRWMD: 2005 - 08 SJRWMD: 2004 SFWMD: 2004 SWFWMD: 2008 All data were crosswalked into the Florida Land Cover Classification System. This project was funded by a grant from FWC/Florida's Wildlife Legacy Initiative (Project 08009) to Florida Natural Areas Inventory. The current dataset is provided in 10m raster grid format.Changes from Version 1.1 to Version 2.3:CLC v2.3 includes updated Florida Land Use Land Cover for four water management districts as described above: NWFWMD, SJRWMD, SFWMD, SWFWMDCLC v2.3 incorporates major revisions to natural coastal land cover and natural communities potentially affected by sea level rise. These revisions were undertaken by FNAI as part of two projects: Re-evaluating Florida's Ecological Conservation Priorities in the Face of Sea Level Rise (funded by the Yale Mapping Framework for Biodiversity Conservation and Climate Adaptation) and Predicting and Mitigating the Effects of Sea-Level Rise and Land Use Changes on Imperiled Species and Natural communities in Florida (funded by an FWC State Wildlife Grant and The Kresge Foundation). FNAI also opportunistically revised natural communities as needed in the course of species habitat mapping work funded by the Florida Department of Environmental Protection. CLC v2.3 also includes several new site specific data sources: New or revised FNAI natural community maps for 13 conservation lands and 9 Florida Forever proposals; new Florida Park Service maps for 10 parks; Sarasota County Preserves Habitat Maps (with FNAI review); Sarasota County HCP Florida Scrub-Jay Habitat (with FNAI Review); Southwest Florida Scrub Working Group scrub polygons. Several corrections to the crosswalk of FLUCCS to FLCS were made, including review and reclassification of interior sand beaches that were originally crosswalked to beach dune, and reclassification of upland hardwood forest south of Lake Okeechobee to mesic hammock. Representation of state waters was expanded to include the NOAA Submerged Lands Act data for Florida.Changes from Version 2.3 to 3.0: All land classes underwent revisions to correct boundaries, mislabeled classes, and hard edges between classes. Vector data was compared against high resolution Digital Ortho Quarter Quads (DOQQ) and Google Earth imagery. Individual land cover classes were converted to .KML format for use in Google Earth. Errors identified through visual review were manually corrected. Statewide medium resolution (spatial resolution of 10 m) SPOT 5 images were available for remote sensing classification with the following spectral bands: near infrared, red, green and short wave infrared. The acquisition dates of SPOT images ranged between October, 2005 and October, 2010. Remote sensing classification was performed in Idrisi Taiga and ERDAS Imagine. Supervised and unsupervised classifications of each SPOT image were performed with the corrected polygon data as a guide. Further visual inspections of classified areas were conducted for consistency, errors, and edge matching between image footprints. CLC v3.0 now includes state wide Florida NAVTEQ transportation data. CLC v3.0 incorporates extensive revisions to scrub, scrubby flatwoods, mesic flatwoods, and upland pine classes. An additional class, scrub mangrove – 5252, was added to the crosswalk. Mangrove swamp was reviewed and reclassified to include areas of scrub mangrove. CLC v3.0 also includes additional revisions to sand beach, riverine sand bar, and beach dune previously misclassified as high intensity urban or extractive. CLC v3.0 excludes the Dry Tortugas and does not include some of the small keys between Key West and Marquesas.Changes from Version 3.0 to Version 3.1: CLC v3.1 includes several new site specific data sources: Revised FNAI natural community maps for 31 WMAs, and 6 Florida Forever areas or proposals. This data was either extracted from v2.3, or from more recent mapping efforts. Domains have been removed from the attribute table, and a class name field has been added for SITE and STATE level classes. The Dry Tortugas have been reincorporated. The geographic extent has been revised for the Coastal Upland and Dry Prairie classes. Rural Open and the Extractive classes underwent a more thorough reviewChanges from Version 3.1 to Version 3.2:CLC v3.2 includes several new site specific data sources: Revised FNAI natural community maps for 43 Florida Park Service lands, and 9 Florida Forever areas or proposals. This data is from 2014 - 2016 mapping efforts. SITE level class review: Wet Coniferous plantation (2450) from v2.3 has been included in v3.2. Non-Vegetated Wetland (2300), Urban Open Land (18211), Cropland/Pasture (18331), and High Pine and Scrub (1200) have undergone thorough review and reclassification where appropriate. Other classification errors were opportunistically corrected as found or as reported by users to landcovermap@myfwc.com.Changes from Version 3.2.5 to Version 3.3: The CLC v3.3 includes several new site specific data sources: Revised FNAI natural community maps for 14 FWC managed or co-managed lands, including 7 WMA and 7 WEA, 1 State Forest, 3 Hillsboro County managed areas, and 1 Florida Forever proposal. This data is from the 2017 – 2018 mapping efforts. Select sites and classes were included from the 2016 – 2017 NWFWMD (FLUCCS) dataset. M.C. Davis Conservation areas, 18331x agricultural classes underwent a thorough review and reclassification where appropriate. Prairie Mesic Hammock (1122) was reclassified to Prairie Hydric Hammock (22322) in the Everglades. All SITE level Tree Plantations (18333) were reclassified to Coniferous Plantations (183332). The addition of FWC Oyster Bar (5230) features. Other classification errors were opportunistically corrected as found or as reported by users to landcovermap@myfwc.com, including classification corrections to sites in T.M. Goodwin and Ocala National Forest. CLC v3.3 utilizes the updated The Florida Land Cover Classification System (2018), altering the following class names and numbers: Irrigated Row Crops (1833111), Wet Coniferous Plantations (1833321) (formerly 2450), Major Springs (4131) (formerly 3118). Mixed Hardwood-Coniferous Swamps (2240) (formerly Other Wetland Forested Mixed).Changes from Version 3.4 to Version 3.5: The CLC v3.5 includes several new site specific data sources: Revised FNAI natural community maps for 16 managed areas, and 10 Florida Forever Board of Trustees Projects (FFBOT) sites. This data is from the 2019 – 2020 mapping efforts. Other classification errors were opportunistically corrected as found or as reported by users to landcovermap@myfwc.com. This version of the CLC is also the first to include land identified as Salt Flats (5241).Changes from Version 3.5 to 3.6: The CLC v3.6 includes several new site specific data sources: Revised FNAI natural community maps for 11 managed areas, and 24 Florida Forever Board of Trustees Projects (FFBOT) sites. This data is from the 2018 – 2022 mapping efforts. Other classification errors were opportunistically corrected as found or as reported by users to landcovermap@myfwc.com.Changes from Version 3.6 to 3.7: The CLC 3.7 includes several new site specific data sources: Revised FNAI natural community maps for 5 managed areas (2022-2023). Revised Palm Beach County Natural Areas data for Pine Glades Natural Area (2023). Other classification errors were opportunistically corrected as found or as reported by users to landcovermap@myfwc.com. In this version a few SITE level classifications are reclassified for the STATE level classification system. Mesic Flatwoods and Scrubby Flatwoods are classified as Dry Flatwoods at the STATE level. Upland Glade is classified as Barren, Sinkhole, and Outcrop Communities at the STATE level. Lastly Upland Pine is classified as High Pine and Scrub at the STATE level.
Important Note: This item is in mature support as of April 2024 and will be retired in December 2026. A new version of this item is available for your use. Esri recommends updating your maps and apps to use the new version. Soil is a key natural resource that provides the foundation of basic ecosystem services. Soil determines the types of farms and forests that can grow on a landscape. Soil filters water. Soil helps regulate the Earth's climate by storing large amounts of carbon. Activities that degrade soils reduce the value of the ecosystem services that soil provides. For example, since 1850 35% of human caused green house gas emissions are linked to land use change. The Soil Science Society of America is a good source of of additional information.In the soil, clay and humus have static electrical charges that attract and hold positively charged particles known as cations. These positively charged particles are often plant nutrients and their abundance can be used as a measure of soil fertility.Dataset SummaryThis layer provides access to a 30 arc-second (roughly 1 km) cell-sized raster with attributes related to the exchange capacity of the soil derived from the Harmonized World Soil Database v 1.2. The values in this layer are for the dominant soil in each mapping unit (sequence field = 1).Fields for topsoil (0-30 cm) and subsoil (30-100 cm) are available for each of these attributes related to exchange capacity:Cation Exchange Capacity – Clay - cmol/kgCation Exchange Capacity – Soil - cmol/kgBase Saturation - %Total Exchangeable Bases - cmol/kg Total Sodicity (ESP) - % Additionally, class description fields based on the document Harmonized World Soil Database Version 1.2 were added by Esri for the Base Saturation and Total Sodicity fields for the topsoil and subsoil layers of each map unit. These fields are designed for use in web map pop-ups.The layer is symbolized with the Topsoil Base Saturation field.The document Harmonized World Soil Database Version 1.2 provides more detail on the soil exchange capacity attributes contained in this layer.Other attributes contained in this layer include:Soil Mapping Unit Name - the name of the spatially dominant major soil groupSoil Mapping Unit Symbol - a two letter code for labeling the spatially dominant major soil group in thematic mapsData Source - the HWSD is an aggregation of datasets. The data sources are the European Soil Database (ESDB), the 1:1 million soil map of China (CHINA), the Soil and Terrain Database Program (SOTWIS), and the Digital Soil Map of the World (DSMW).Percentage of Mapping Unit covered by dominant componentMore information on the Harmonized World Soil Database is available here.Other layers created from the Harmonized World Soil Database are available on ArcGIS Online:World Soils Harmonized World Soil Database - Bulk DensityWorld Soils Harmonized World Soil Database – ChemistryWorld Soils Harmonized World Soil Database – GeneralWorld Soils Harmonized World Soil Database – HydricWorld Soils Harmonized World Soil Database – TextureThe authors of this data set request that projects using these data include the following citation:FAO/IIASA/ISRIC/ISSCAS/JRC, 2012. Harmonized World Soil Database (version 1.2). FAO, Rome, Italy and IIASA, Laxenburg, Austria.What can you do with this layer?This layer is suitable for both visualization and analysis. It can be used in ArcGIS Online in web maps and applications and can be used in ArcGIS Desktop.This layer has query, identify, and export image services available. This layer is restricted to a maximum area of 16,000 x 16,000 pixels - an area 4,000 kilometers on a side or an area approximately the size of Europe. The source data for this layer are available here.This layer is part of a larger collection of landscape layers that you can use to perform a wide variety of mapping and analysis tasks.The Living Atlas of the World provides an easy way to explore the landscape layers and many other beautiful and authoritative maps on hundreds of topics.Geonet is a good resource for learning more about landscape layers and the Living Atlas of the World. To get started follow these links:Living Atlas Discussion GroupSoil Data Discussion GroupThe Esri Insider Blog provides an introduction to the Ecophysiographic Mapping project.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
We used Digital Soil Mapping (DSM) technologies combined with the real-time collations of soil attribute data from TERN's recently developed Soil Data Federation System, to produce a map of Australian Soil Classification Soil Order classes with quantified estimates of mapping reliability at a 90m resolution.
The map gives an estimate of the spatial distribution of soil types across Australia.
Soil classes are based on The Australian Soil Classification - Second Edition by the National Committee on Soil and Terrain, R Isbell - https://ebooks.publish.csiro.au/content/australian-soil-classification-9781486304646
Detailed information about the Soil and Landscape Grid of Australia can be found at - https://esoil.io/TERNLandscapes/Public/Pages/SLGA/index.html
Period (temporal coverage; approximately): 1950-2021; Spatial resolution: 3 arc seconds (approx 90m); Number of pixels with coverage per layer: 2007M (49200 * 40800); Data license : Creative Commons Attribution 4.0 (CC BY); Format: Cloud Optimised GeoTIFF; Lineage: The map was produced as per methods described at - https://aussoilsdsm.esoil.io/slga-version-2-products/australian-soil-classification-map
Soil classification data was extracted from the SoilDataFederator (SDF) - https://esoil.io/TERNLandscapes/Public/Pages/SoilDataFederator/SoilDataFederator.html)
A total of 195,383 observations with either an Australian Soil Classification (ASC) or a Principal Profile Form (PPF) classification or a Great Soil Group (GSG) classification were extracted (Figure 1). Of these observations 130,570 of them had an ASC directly assigned by a pedologist. The remaining 64,813 observations either had a PPF or an ASC assigned to them by pedologists. The PPF and GSG classification where then transformed to an ASC using these remap tables.
The 90m raster covariate data was obtained from TERNs publicly available raster covariate stack - https://esoil.io/TERNLandscapes/Public/Products/TERN/Covariates/Mosaics .A parsimonious set of these covariates was used in the modelling.
We used the R "Ranger" Random Forest package to implement a machine learning model as per standard Digital Soil Mapping (DSM) methodologies.
The observed geographic locations in the ASC data set were used to extract cell values from the raster covariate stack using the R "raster" package. This data set was then divided into a 90/10% split of training and external validation sets. The training data was then bootstrapped sampled 50 times to create 50 bootstrap training sets. These training sets were then used to generate 50 Random Forest model realisations.
Using the CSIRO Pearcey High Performance Compute (HPC) cluster the Random Forest models were evaluated against the input covariate raster data stack. This was done for each 90m raster cell across the nation for each of the 50 bootstrapped model realisations. The modal ASC value across the 50 realisations for each cell was determined and assigned as the most probable soil type for that cell in the output raster. The ratio of the second most probable soil to the most probable soil was also calculated to generate a model confusion index, an estimate of the structural uncertainty in the Random Forest model.
The Australian Soil Resource Information System (ASRIS) contains a product that is a compilation of all existing polygon mapping conducted by state and federal soil survey agencies across all of Australia. This product is made up of a diverse range of field mapping products at a range of mapping scales. From this product we extracted all polygons that were mapped at a scale of 1:100,000 or finer, as defined in the Guidelines For Surveying Soil And Land Resources (Blue Book). Polygons mapped at this scale are high quality spatial estimates of the distribution of soil attributes. We then rasterised these polygon ASC values and merged these values into our final estimates of ASC, i.e., where an ASRIS 100,000 scale polygon exists it will replace the modelled ASC value.
All processing for the generation of these products was undertaken using the R programming language. R Core Team (2020). R: A language and environment for statistical computing. R Foundation for Statistical Computing, Vienna, Austria. URL https://www.R-project.org/.
Code - https://github.com/AusSoilsDSM/SLGA Observation data - https://esoil.io/TERNLandscapes/Public/Pages/SoilDataFederator/SoilDataFederator.html Covariate rasters - https://esoil.io/TERNLandscapes/Public/Pages/SLGA/GetData-COGSDataStore.html
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Abstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. Resource contains an ArcGIS …Show full descriptionAbstract This dataset and its metadata statement were supplied to the Bioregional Assessment Programme by a third party and are presented here as originally supplied. Resource contains an ArcGIS file geodatabase raster for the National Vegetation Information System (NVIS) Major Vegetation Groups - Australia-wide, present extent (FGDB_NVIS4_1_AUST_MVG_EXT). Related datasets are also included: FGDB_NVIS4_1_KEY_LAYERS_EXT - ArcGIS File Geodatabase Feature Class of the Key Datasets that make up NVIS Version 4.1 - Australia wide; and FGDB_NVIS4_1_LUT_KEY_LAYERS - Lookup table for Dataset Key Layers. This raster dataset provides the latest summary information (November 2012) on Australia's present (extant) native vegetation. It is in Albers Equal Area projection with a 100 m x 100 m (1 Ha) cell size. A comparable Estimated Pre-1750 (pre-european, pre-clearing) raster dataset is available: - NVIS4_1_AUST_MVG_PRE_ALB. State and Territory vegetation mapping agencies supplied a new version of the National Vegetation Information System (NVIS) in 2009-2011. Some agencies did not supply new data for this version but approved re-use of Version 3.1 data. Summaries were derived from the best available data in the NVIS extant theme as at June 2012. This product is derived from a compilation of data collected at different scales on different dates by different organisations. Please refer to the separate key map showing scales of the input datasets. Gaps in the NVIS database were filled by non-NVIS data, notably parts of South Australia and small areas of New South Wales such as the Curlewis area. The data represent on-ground dates of up to 2006 in Queensland, 2001 to 2005 in South Australia (depending on the region) and 2004/5 in other jurisdictions, except NSW. NVIS data was partially updated in NSW with 2001-09 data, with extensive areas of 1997 data remaining from the earlier version of NVIS. Major Vegetation Groups were identified to summarise the type and distribution of Australia's native vegetation. The classification contains different mixes of plant species within the canopy, shrub or ground layers, but are structurally similar and are often dominated by a single genus. In a mapping sense, the groups reflect the dominant vegetation occurring in a map unit where there are a mix of several vegetation types. Subdominant vegetation groups which may also be present in the map unit are not shown. For example, the dominant vegetation in an area may be mapped as dominated by eucalypt open forest, although it contains pockets of rainforest, shrubland and grassland vegetation as subdominants. The (related) Major Vegetation Subgroups represent more detail about the understorey and floristics of the Major Vegetation Groups and are available as separate raster datasets: - NVIS4_1_AUST_MVS_EXT_ALB - NVIS4_1_AUST_MVS_PRE_ALB A number of other non-vegetation and non-native vegetation land cover types are also represented as Major Vegetation Groups. These are provided for cartographic purposes, but should not be used for analyses. For further background and other NVIS products, please see the links on http://www.environment.gov.au/erin/nvis/index.html. The current NVIS data products are available from http://www.environment.gov.au/land/native-vegetation/national-vegetation-information-system. Purpose For use in Bioregional Assessment land classification analyses Dataset History NVIS Version 4.1 The input vegetation data were provided from over 100 individual projects representing the majority of Australia's regional vegetation mapping over the last 50 years. State and Territory custodians translated the vegetation descriptions from these datasets into a common attribute framework, the National Vegetation Information System (ESCAVI, 2003). Scales of input mapping ranged from 1:25,000 to 1:5,000,000. These were combined into an Australia-wide set of vector data. Non-terrestrial areas were mostly removed by the State and Territory custodians before supplying the data to the Environmental Resources Information Network (ERIN), Department of Sustainability Environment Water Population and Communities (DSEWPaC). Each NVIS vegetation description was written to the NVIS XML format file by the custodian, transferred to ERIN and loaded into the NVIS database at ERIN. A considerable number of quality checks were performed automatically by this system to ensure conformity to the NVIS attribute standards (ESCAVI, 2003) and consistency between levels of the NVIS Information Hierarchy within each description. Descriptions for non-vegetation and non-native vegetation mapping codes were transferred via CSV files. The NVIS vector (polygon) data for Australia comprised a series of jig-saw pieces, eachup to approx 500,000 polygons - the maximum tractable size for routine geoprocesssing. The spatial data was processed to conform to the NVIS spatial format (ESCAVI, 2003; other papers). Spatial processing and attribute additions were done mostly in ESRI File Geodatabases. Topology and minor geometric corrections were also performed at this stage. These datasets were then loaded into ESRI Spatial Database Engine as per the ERIN standard. NVIS attributes were then populated using Oracle database tables provided by custodians, mostly using PL/SQL Developer or in ArcGIS using the field calculator (where simple). Each spatial dataset was joined to and checked against a lookup table for the relevant State/Territory to ensure that all mapping codes in the dominant vegetation type of each polygon (NVISDSC1) had a valid lookup description, including an allocated MVG. Minor vegetation components of each map unit (NVISDSC2-6) were not checked, but could be considered mostly complete. Each NVIS vegetation description was allocated to a Major Vegetation Group (MVG) by manual interpretation at ERIN. The Australian Natural Resources Atlas (http://www.anra.gov.au/topics/vegetation/pubs/native_vegetation/vegfsheet.html) provides detailed descriptions of most Major Vegetation Groups. Three new MVGs were created for version 4.1 to better represent open woodland formations and forests (in the NT) with no further data available. NVIS vegetation descriptions were reallocated into these classes, if appropriate: Unclassified Forest Other Open Woodlands Mallee Open Woodlands and Sparse Mallee Shublands (Thus there are a total of 33 MVGs existing as at June 2012). Data values defined as cleared or non-native by data custodians were attributed specific MVG values such as 25 - Cleared or non native, 27 - naturally bare, 28 - seas & estuaries, and 99 - Unknown. As part of the process to fill gaps in NVIS, the descriptive data from non-NVIS sources was also referenced in the NVIS database, but with blank vegetation descriptions. In general. the gap-fill data comprised (a) fine scale (1:250K or better) State/Territory vegetation maps for which NVIS descriptions were unavailable and (b) coarse-scale (1:1M) maps from Commonwealth and other sources. MVGs were then allocated to each description from the available desciptions in accompanying publications and other sources. Parts of New South Wales, South Australia, QLD and the ACT have extensive areas of vector "NoData", thus appearing as an inland sea. The No Data areas were dealt with differently by state. In the ACT and SA, the vector data was 'gap-filled' and attributed using satellite imagery as a guide prior to rasterising. Most of these areas comprised a mixture of MVG 24 (inland water) and 25 (cleared), and in some case 99 (Unknown). The NSW & QLD 'No Data' areas were filled using a raster mask to fill the 'holes'. These areas were attributed with MVG 24, 26 (water & unclassified veg), MVG 25 (cleared); or MVG 99 Unknown/no data, where these areas were a mixture of unknown proportions. Each spatial dataset with joined lookup table (including MVG_NUMBER linked to NVISDSC1) was exported to a File Geodatabase as a feature class. These were reprojected into Albers Equal Area projection (Central_Meridian: 132.000000, Standard_Parallel_1: -18.000000, Standard_Parallel_2: -36.000000, Linear Unit: Meter (1.000000), Datum GDA94, other parameters 0). Each feature class was then rasterised to a 100m raster with extents to a multiple of 1000 m, to ensure alignment. In some instances, areas of 'NoData' had to be modelled in raster. For example, in NSW where non-native areas (cleared, water bodies etc) have not been mapped. The rasters were then merged into a 'state wide' raster. State rasters were then merged into this 'Australia wide' raster dataset. November 2012 Corrections Closer inspection of the original 4.1 MVG Extant raster dataset highlighted some issues with the raster creation process which meant that raster pixels in some areas did not align as intended. These were corrected, and the new properly aligned rasters released in November 2012. Dataset Citation Department of the Environment (2012) Australia - Present Major Vegetation Groups - NVIS Version 4.1 (Albers 100m analysis product). Bioregional Assessment Source Dataset. Viewed 10 July 2017, http://data.bioregionalassessments.gov.au/dataset/57c8ee5c-43e5-4e9c-9e41-fd5012536374.
U.S. Government Workshttps://www.usa.gov/government-works
License information was derived automatically
This is a MD iMAP hosted service layer. Find more information at http://imap.maryland.gov. userdata and unzip the LayerFiles.zip folder.Data from the four SSURGO tables were assembled into the single table included in each map package. Data from the component table were aggregated using a dominant component model (listed below under Component Table - Dominant Component) or a weighted average model (listed below under Component Table - Weighted Average) using custom Python scripts. The the Mapunit table - the MUAGATTAT table and the processed Component table data were joined to the Mapunit Feature Class. Field aliases were added and indexes calculated. A field named Map Symbol was created and populated with random integers from 1-10 for symbolizing the soil units in the map package.For documentation of the SSURGO dataset see:http://soildatamart.nrcs.usda.gov/SSURGOMetadata.aspxFor documentation of the Watershed Boundary Dataset see: http://www.nrcs.usda.gov/wps/portal/nrcs/main/national/water/watersheds/datasetThe map packages contain the following attributes in the Map Units layer:Mapunit Feature Class:Survey AreaSpatial VersionMapunit SymbolMapunit KeyNational Mapunit SymbolMapunit Table:Mapunit NameMapunit KindFarmland ClassHighly Erodible Lands Classification - Wind and WaterHighly Erodible Lands Classification - WaterHighly Erodible Lands Classification - WindInterpretive FocusIntensity of MappingLegend KeyMapunit SequenceIowa Corn Suitability RatingLegend Table:Project ScaleTabular VersionMUAGGATT Table:Slope Gradient - Dominant ComponentSlope Gradient - Weighted AverageBedrock Depth - MinimumWater Table Depth - Annual MinimumWater Table Depth - April to June MinimumFlooding Frequency - Dominant ConditionFlooding Frequency - MaximumPonding Frequency - PresenceAvailable Water Storage 0-25 cm - Weighted AverageAvailable Water Storage 0-50 cm - Weighted AverageAvailable Water Storage 0-100 cm - Weighted AverageAvailable Water Storage 0-150 cm - Weighted AverageDrainage Class - Dominant ConditionDrainage Class - WettestHydrologic Group - Dominant ConditionIrrigated Capability Class - Dominant ConditionIrrigated Capability Class - Proportion of Mapunit with Dominant ConditionNon-Irrigated Capability Class - Dominant ConditionNon-Irrigated Capability Class - Proportion of Mapunit with Dominant ConditionRating for Buildings without Basements - Dominant ConditionRating for Buildings with Basements - Dominant ConditionRating for Buildings with Basements - Least LimitingRating for Buildings with Basements - Most LimitingRating for Septic Tank Absorption Fields - Dominant ConditionRating for Septic Tank Absorption Fields - Least LimitingRating for Septic Tank Absorption Fields - Most LimitingRating for Sewage Lagoons - Dominant ConditionRating for Sewage Lagoons - Dominant ComponentRating for Roads and Streets - Dominant ConditionRating for Sand Source - Dominant ConditionRating for Sand Source - Most ProbableRating for Paths and Trails - Dominant ConditionRating for Paths and Trails - Weighted AverageErosion Hazard of Forest Roads and Trails - Dominant ComponentHydric Classification - PresenceRating for Manure and Food Processing Waste - Weighted AverageComponent Table - Weighted Average:Mean Annual Air Temperature - High Value Mean Annual Air Temperature - Low Value Mean Annual Air Temperature - Representative Value Albedo - High Value Albedo - Low Value Albedo - Representative Value Slope - High Value Slope - Low Value Slope - Representative Value Slope Length - High Value Slope Length - Low Value Slope Length - Representative Value Elevation - High Value Elevation - Low Value Elevation - Representative Value Mean Annual Precipitation - High Value Mean Annual Precipitation - Low Value Mean Annual Precipitation - Representative Value Days between Last and First Frost - High Value Days between Last and First Frost - Low Value Days between Last and First Frost - Representative Value Crop Production Index Range Forage Annual Potential Production - High Value Range Forage Annual Potential Production - Low Value Range Forage Annual Potential Production - Representative Value Initial Subsidence - High Value Initial Subsidence - Low Value Initial Subsidence - Representative Value Total Subsidence - High ValueTotal Subsidence - Low Value Total Subsidence - Representative Value Component Table - Dominant Component:Component KeyComponent Percentage - Low ValueComponent Percentage - Representative ValueComponent Percentage - High ValueComponent NameComponent KindOther Criteria Used to Identify ComponentsCriteria Used to Identify Components at the Local LevelRunoffSoil Loss Tolerance FactorWind Erodibility IndexWind Erodibility GroupErosion ClassEarth Cover 1Earth Cover 2Hydric ConditionAspect Range - Counter Clockwise LimitAspect - Representative ValueAspect Range - Clockwise LimitGeomorphic DescriptionNon-Irrigated Capability SubclassNon-Irrigated Unit Capability ClassIrrigated Capability SubclassIrrigated Unit Capability ClassConservation Tree Shrub GroupForage Suitability GroupGrain Wildlife HabitatGrass Wildlife HabitatHerbaceous Wildlife HabitatShrub Wildlife HabitatConifer Wildlife HabitatHardwood Wildlife HabitatWetland Wildlife HabitatShallow Water Wildlife HabitatRangeland Wildlife HabitatOpenland Wildlife HabitatWoodland Wildlife HabitatWetland Wildlife HabitatSoil Slip PotentialSusceptibility to Frost HeavingConcrete CorrosionSteel CorrosionTaxonomic Class NameOrderSuborderGreat GroupSubgroupParticle SizeParticle Size ModifierCation Exchange Activity ClassCarbonate ReactionTemperature ClassMoisture SubclassSoil Temperature RegimeEdition of Keys to Soil Taxonomy Used to Classify SoilThe U.S. Department of Agriculture - Natural Resources Conservation Service - should be acknowledged as the data source in products derived from these data. This data set is not designed for use as a primary regulatory tool in permitting or citing decisions - but may be used as a reference source. This is public information and may be interpreted by organizations - agencies - units of government - or others based on needs; however - they are responsible for the appropriate application. Federal - State - or local regulatory bodies are not to reassign to the Natural Resources Conservation Service any authority for the decisions that they make. The Natural Resources Conservation Service will not perform any evaluations of these maps for purposes related solely to State or local regulatory programs. Photographic or digital enlargement of these maps to scales greater than at which they were originally mapped can cause misinterpretation of the data. If enlarged - maps do not show the small areas of contrasting soils that could have been shown at a larger scale. The depicted soil boundaries - interpretations - and analysis derived from them do not eliminate the need for onsite sampling - testing - and detailed study of specific sites for intensive uses. Thus - these data and their interpretations are intended for planning purposes only. Digital data files are periodically updated. Files are dated - and users are responsible for obtaining the latest version of the data.The attribute accuracy is tested by manual comparison of the source with hard copy plots and/or symbolized display of the map data on an interactive computer graphic system. Selected attributes that cannot be visually verified on plots or on screen are interactively queried and verified on screen. In addition - the attributes are tested against a master set of valid attributes. All attribute data conform to the attribute codes in the signed classification and correlation document and amendment(s). Last Updated: Feature Service Layer Link: http://geodata.md.gov/imap/rest/services/Geoscientific/MD_SSURGOSoils/MapServer/0 ADDITIONAL LICENSE TERMS: The Spatial Data and the information therein (collectively "the Data") is provided "as is" without warranty of any kind either expressed implied or statutory. The user assumes the entire risk as to quality and performance of the Data. No guarantee of accuracy is granted nor is any responsibility for reliance thereon assumed. In no event shall the State of Maryland be liable for direct indirect incidental consequential or special damages of any kind. The State of Maryland does not accept liability for any damages or misrepresentation caused by inaccuracies in the Data or as a result to changes to the Data nor is there responsibility assumed to maintain the Data in any manner or form. The Data can be freely distributed as long as the metadata entry is not modified or deleted. Any data derived from the Data must acknowledge the State of Maryland in the metadata.
From gridded National Soil Survey Geographic Database (gNATSGO). Used Soil Data Development Toolbox > gSSURGO Mapping Toolset > Create Soil Map Tool, Exported Data Layer to TIFF, and Used Spatial Analyst > Reclass > Lookup Tool to create this data layer and display the HYDROLGRP_. Follow instructions in "How to Create an On-Demand Soil Property or Interpretation Grid from gNATSGO". Shows sSSURGO data for California. A - sand, loamy sand, sandy loam B - loam, silt, loam or silt C - sandy clay loam D - clay loam, silty clay loam, sandy clay, silty clay, or clay The gridded National Soil Survey Geographic Database (gNATSGO) is a USDA-NRCS Soil & Plant Science Division (SPSD) composite database that provides complete coverage of the best available soils information for all areas of the United States and Island Territories. It was created by combining data from the Soil Survey Geographic Database (SSURGO), State Soil Geographic Database (STATSGO2), and Raster Soil Survey Databases (RSS) into a single seamless ESRI file geodatabase. The state-wide gNATSGO databases contain a 10-meter raster of the soil map units and 70 related tables of soil properties and interpretations. It is designed to work with the SPSD gSSURGO ArcTools. Users can create full coverage thematic maps and grids of soil properties and interpretations for large geographic areas, such as the extent of a State or the conterminous United States. Please note that for the CONUS database, only a 30 meter raster is included. SSURGO is the SPSD flagship soils database that has over 100 years of field-validated detailed soil mapping data. SSURGO contains soils information for more than 90 percent of the United States and island territories, but unmapped land remains. Click here for the current completion status of SSURGO mapping. STATSGO2 is a general soil map that has soils data for all of the United States and island territories, but the data is not as detailed as the SSURGO data. The Raster Soil Surveys (RSSs) are the next generation soil survey databases developed using advanced digital soil mapping methods. https://www.nrcs.usda.gov/wps/portal/nrcs/detail/soils/survey/geo/?cid=nrcseprd1464625) Use the Create A Soil Map ArcTool from the gSSURGO Mapping Toolset in the Soil Data Development Toolbox to make a TIFF data layer (Instructions: https://www.nrcs.usda.gov/wps/portal/nrcs/detail/soils/survey/geo/?cid=nrcseprd1464625#grid). Make a Hydrological Soils Group Map, and display it using the Hydrolgrp_ attribute. NotesThe SPSD refreshes all published soil databases annually. gNATSGO will be included in the refresh cycle, which will provide a new up-to-date version of the database each year. gNATSGO is an ESRI file geodatabase. The soil map units are delivered only as a 10-meter raster version and are uniquely identified by the mukey, which is included in the attribute table. No vectorized version of the soil map units is included in gNATSGO. The database has 70 tables that contain soil attributes, and relationship classes are built into the database to define relationships among tables. The raster can be joined to the Mapunit and Muaggatt tables in the MUKEY field. The database contains a feature class called SAPOLYGON. The “source” field in this feature class indicates whether the data was derived from SSURGO, STATSGO2, or an RSS. A gNATSGO database was created for the conterminous United States and for each state or island territory that does not have complete coverage in SSURGO or has a published RSS. If you encounter an ArcMap error when working with a gNATSGO dataset that reads “The number of unique values exceeds the limit” try increasing the maximum number of unique values to render in your Raster ArcMap Options. Specific instructions can be obtained here: https://support.esri.com/en/technical-article/000010117
FIA Modeled Abundance:�This dataset portrays the live tree mean basal area (square feet per acre) of the species across the contiguous United States. The underlying data publication contains raster maps of live tree basal area for each tree species along with corresponding assessment data. An efficient approach for mapping multiple individual tree species over large spatial domains was used to develop these raster datasets. The method integrates vegetation phenology derived from MODIS imagery and raster data describing relevant environmental parameters with extensive field plot data of tree species basal area to create maps of tree species abundance and distribution at a 250-meter (m) pixel size for the contiguous United States. The approach uses the modeling techniques of k-nearest neighbors and canonical correspondence analysis, where model predictions are calculated using a weighting of nearest neighbors based on proximity in a feature space derived from the model. The approach also utilizes a stratification derived from the 2001 National Land-Cover Database tree canopy cover layer.�This data depicts current species abundance and distribution across the contiguous United States, modeled by using FIA field plot data. Although the absolute values associated with the maps differ from species to species, the highest values within each map are always associated with darker colors. The Little's Range Boundaries show the historical tree species ranges across North America. This is a digital representation of maps by Elbert L. Little, Jr., published between 1971 and 1977. These maps were based on botanical lists, forest surveys, field notes and herbarium specimens.Forest-type Groups:This dataset portrays the forest type group. Each group is a subset of the National Forest Type dataset which portrays 28 forest type groups across the contiguous United States. These data were derived from MODIS composite images from the 2002 and 2003 growing seasons in combination with nearly 100 other geospatial data layers, including elevation, slope, aspect, ecoregions, and PRISM climate data.Harvest Growth:This data shows the percentage of timber that is harvested when compared to the total live volume, at a county-by-county level. Timber volume in forests is constantly in flux, and harvest plays an important role in shaping forests. While most counties have some timber harvest, harvest volumes represent low percentages of standing timber volume.Carbon Harvest:The Carbon Harvest raster dataset represents Mg of annual pulpwood harvested (carbon) by county, derived from the Forest Inventory Analysis in 2016.
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
Napa County has used a 2004 edition vegetation map produced using the Manual of California Vegetation classification system (Thorne et al. 2004) as one of the input layers for land use decision and policy. The county decided to update the map because of its utility. A University of California, Davis (UCD) group was engaged to produce the map. The earlier map used black and white digital orthophoto quadrangles from 1993, with a pixel resolution of 3 meters. This image was delineated using a heads up digitization technique produced by ASI (Aerial Services Incorporated). The resulting polygons were the provided vegetation and landcover attributes following the classification system used by California State Department of Fish and Wildlife mappers in the Manual of California Vegetation. That effort included a brief field campaign in which surveyors drove accessible roads and verified or corrected the dominant vegetation of polygons adjacent to roadways or visible using binoculars. There were no field relevé or rapid assessment plots conducted. This update version uses a 2016 edition of 1 meter color aerial imagery taken by the National Agriculture Imagery Program (NAIP) as the base imagery. In consultation with the county we decided to use similar methods to the previous mapping effort, in order to preserve the capacity to assess change in the county over time. This meant forgoing recent data and innovations in remote sensing such as the use LiDAR and Ecognition’s segmentation of imagery to delineate stands, which have been recently used in a concurrent project mapping of Sonoma County. The use of such technologies would have made it more difficult to track changes in landcover, because differences between publication dates would not be definitively attributable to either actual land cover change or to change in methodology. The overall cost of updating the map in the way was approximately 20% of the cost of the Sonoma vegetation mapping program.Therefore, we started with the original map, and on-screen inspections of the 2004 polygons to determine if change had occurred. If so, the boundaries and attributes were modified in this new edition of the map. We also used the time series of imagery available on Google Earth, to further inspect many edited polygons. While funding was not available to do field assessments, we incorporated field expertise and other map data from four projects that overlap with parts of Napa Count: the Angwin Experimental Forest; a 2014 vegetation map of the Knoxville area; agricultural rock piles were identified by Amber Manfree; and parts of a Sonoma Vegetation Map that used 2013 imagery.The Angwin Experimental Forest was mapped by Peter Lecourt from Pacific Union College. He identified several polygons of redwoods in what are potentially the eastern-most extent of that species. We reviewed those polygons with him and incorporated some of the data from his area into this map.The 2014 Knoxville Vegetation map was developed by California Department of Fish and Wildlife. It was made public in February of 2019, close to the end of this project. We reviewed the map, which covers part of the northeast portion of Napa County. We incorporated polygons and vegetation types for 18 vegetation types including the rare ones, we reviewed and incorporated some data for another 6 types, and we noted in comments the presence of another 5 types. There is a separate report specifically addressing the incorporation of this map to our map.Dr Amber Manfree has been conducting research on fire return intervals for parts of Napa County. In her research she identified that large piles of rocks are created when vineyards are put in. These are mapable features. She shared the locations of rock piles she identified, which we incorporated into the map. The Sonoma Vegetation Map mapped some distance into the western side of Napa County. We reviewed that map’s polygons for coast redwood. We then examined our imagery and the Google imagery to see if we could discern the whorled pattern of tree branches. Where we could, we amended or expanded redwood polygons in our map.The Vegetation classification systems used here follows California’s Manual of California Vegetation and the National Vegetation Classification System (MCV and NVCS). We started with the vegetation types listed in the 2004 map. We predominantly use the same set of species names, with modifications/additions particularly from the Knoxville map. The NVCS uses Alliance and Association as the two most taxonomically detailed levels. This map uses those levels. It also refers to vegetation types that have not been sampled in the field and that has 3-6 species and a site descriptor as Groups, which is the next more general level in the NVCS classification. We conducted 3 rounds of quality assessment/quality control exercises.
WARNING: This is a pre-release dataset and its fields names and data structures are subject to change. It should be considered pre-release until the end of 2024. Expected changes:
Purpose
County and incorporated place (city) boundaries along with third party identifiers used to join in external data. Boundaries are from the authoritative source the California Department of Tax and Fee Administration (CDTFA), altered to show the counties as one polygon. This layer displays the city polygons on top of the County polygons so the area isn"t interrupted. The GEOID attribute information is added from the US Census. GEOID is based on merged State and County FIPS codes for the Counties. Abbreviations for Counties and Cities were added from Caltrans Division of Local Assistance (DLA) data. Place Type was populated with information extracted from the Census. Names and IDs from the US Board on Geographic Names (BGN), the authoritative source of place names as published in the Geographic Name Information System (GNIS), are attached as well. Finally, coastal buffers are removed, leaving the land-based portions of jurisdictions. This feature layer is for public use.
Related Layers
This dataset is part of a grouping of many datasets:
Point of Contact
California Department of Technology, Office of Digital Services, odsdataservices@state.ca.gov
Field and Abbreviation Definitions
Accuracy
CDTFA"s source data notes the following about accuracy:
City boundary changes and county boundary line adjustments filed with the Board of Equalization per Government Code 54900. This GIS layer contains the boundaries of the unincorporated county and incorporated cities within the state of California. The initial dataset was created in March of 2015 and was based on the State Board of Equalization tax rate area boundaries. As of April 1, 2024, the maintenance of this dataset is provided by the California Department of Tax and Fee Administration for the purpose of determining sales and use tax rates. The boundaries are continuously being revised to align with aerial imagery when areas of conflict are discovered between the original boundary provided by the California State Board of Equalization and the boundary made publicly available by local, state, and federal government. Some differences may occur between actual recorded boundaries and the boundaries used for sales and use tax purposes. The boundaries in this map are representations of taxing jurisdictions for the purpose of determining sales and use tax rates and should not be used to determine precise city or county boundary line locations. COUNTY = county name; CITY = city name or unincorporated territory; COPRI =
Hydrological Information Products for the Off-Project Water Program of the Klamath Basin Restoration Agreement U.S. Geological Survey Open-File Report 2012-1199 U.S. Department of the Interior By Daniel T. Snyder, John C. Risley, and Jonathan V. Haynes Prepared in cooperation with The Klamath Tribes Access complete report at: https://pubs.usgs.gov/of/2012/1199 Suggested citation: Snyder, D.T., Risley, J.C., and Haynes, J.V., 2012, Hydrological information products for the Off-Project Water Program of the Klamath Basin Restoration Agreement: U.S. Geological Survey Open-File Report 2012–1199, 17 p., https://pubs.usgs.gov/of/2012/1199 Summary The Klamath Basin Restoration Agreement (KBRA) was developed by a diverse group of stakeholders, Federal and State resource management agencies, Tribal representatives, and interest groups to provide a comprehensive solution to ecological and water-supply issues in the Klamath Basin. The Off-Project Water Program (OPWP), one component of the KBRA, has as one of its purposes to permanently provide an additional 30,000 acre-feet of water per year on an average annual basis to Upper Klamath Lake through “voluntary retirement of water rights or water uses or other means as agreed to by the Klamath Tribes, to improve fisheries habitat and also provide for stability of irrigation water deliveries.” The geographic area where the water rights could be retired encompasses approximately 1,900 square miles. The OPWP area is defined as including the Sprague River drainage, the Sycan River drainage downstream of Sycan Marsh, the Wood River drainage, and the Williamson River drainage from Kirk Reef at the southern end of Klamath Marsh downstream to the confluence with the Sprague River. Extensive, broad, flat, poorly drained uplands, valleys, and wetlands characterize much of the study area. Irrigation is almost entirely used for pasture. To assist parties involved with decisionmaking and implementation of the OPWP, the U.S. Geological Survey (USGS), in cooperation with the Klamath Tribes and other stakeholders, created five hydrological i nformation products. These products include GIS digital maps and datasets containing spatial information on evapotranspiration, subirrigation indicators, water rights, subbasin streamflow statistics, and return-flow indicators. The evapotranspiration (ET) datasets were created under contract for this study by Evapotranspiration, Plus, LLC, of Twin Falls, Idaho. A high-resolution remote sensing technique known as Mapping Evapotranspiration at High Resolution and Internalized Calibration (METRIC) was used to create estimates of the spatial distribution of ET. The METRIC technique uses thermal infrared Landsat imagery to quantify actual evapotranspiration at a 30-meter resolution that can be related to individual irrigated fields. Because evaporation uses heat energy, ground surfaces with large ET rates are left cooler as a result of ET than ground surfaces that have less ET. As a consequence, irrigated fields appear in the Landsat images as cooler than nonirrigated fields. Products produced from this study include total seasonal and total monthly (April–October) actual evapotranspiration maps for 2004 (a dry year) and 2006 (a wet year). Maps showing indicators of natural subirrigation were also provided by this study. “Subirrigation” as used here is the evapotranspiration of shallow groundwater by plants with roots that penetrate to or near the water table. Subirrigation often occurs at locations where the water table is at or above the plant rooting depth. Natural consumptive use by plants diminishes the benefit of retiring water rights in subirrigated areas. Some agricultural production may be possible, however, on subirrigated lands for which water rights are retired. Because of the difficulty in precisely mapping and quantifying subirrigation, this study presents several sources of spatially mapped data that can be used as indicators of higher subirrigation probability. These include the floodplain boundaries defined by stream geomorphology, water-table depth defined in Natural Resources Conservation Service (NRCS) soil surveys, and soil rooting depth defined in NRCS soil surveys. The two water-rights mapping products created in the study were “points of diversion” (POD) and “place of use” (POU) for surface-water irrigation rights. To create these maps, all surface-water rights data, decrees, certificates, permits, and unadjudicated claims within the entire 1,900 square mile study area were aggregated into a common GIS geodatabase. Surface-water irrigation rights within a 5-mile buffer of the study area were then selected and identified. The POU area was then totaled by water right for primary and supplemental water rights. The maximum annual volume (acre-feet) allowed under each water right also was calculated using the POU area and duty (allowable annual irrigation application in feet). In cases where a water right has more than one designated POD, the total volume for the water right was equally distributed to each POD listed for the water right. Because of this, mapped distribution of diversion rates for some rights may differ from actual practice. Water-right information in the map products was from digital datasets obtained from the Oregon Water Resources Department and was, at the time acquired, the best available compilation of water-right information available. Because the completeness and accuracy of the water-right data could not be verified, users are encouraged to check directly with the Oregon Water Resources Department where specific information on individual rights or locations is essential. A dataset containing streamflow statistics for 72 subbasins in the study area was created for the study area. The statistics include annual flow durations (5-, 10-, 25-, 50-, and 95-percent exceedances) and 7-day, 10-year (7Q10) and 7-day, 2-year (7Q2) low flows, and were computed using regional regression equations based on measured streamflow records in the region. Daily streamflow records used were adjusted as needed for crop consumptive use; therefore the statistics represent streamflow under more natural conditions as though irrigation diversions did not exist. Statistics are provided for flow rates resulting from streamflow originating from within the entire drainage area upstream of the subbasin pour point (referring to the outlet of the contributing drainage basin). The statistics were computed for the purpose of providing decision makers with the ability to estimate streamflow that would be expected after water conservation techniques have been implemented or a water right has been retired. A final product from the study are datasets of indicators of the potential for subsurface return flow of irrigation water from agricultural areas to nearby streams. The datasets contain information on factors such as proximity to surface-water features, geomorphic floodplain characteristics, and depth to water. The digital data, metadata, and example illustrations for the datasets described in this report are available on-line from the USGS Water Resources National Spatial Data Infrastructure (NSDI) Node Website http://water.usgs.gov/lookup/getgislist or from the U.S. Government website DATA.gov at http://www.data.gov with links provided in a Microsoft® Excel® workbook in appendix A. Introduction Program Background The Klamath Basin Restoration Agreement (KBRA) was developed by a diverse group of stakeholders, Federal and State resource management agencies, Tribal representatives, and interest groups to provide a comprehensive solution to ecological and water-supply issues in the basin. The KBRA covers the entire Klamath Basin, from headwater areas in southern Oregon and northern California to the Pacific Ocean, and addresses a wide range of issues that include hydropower, fisheries, and water resources. The Water Resources Program (Part IV of the KBRA) includes a section (16) known as the Off-Project Water Program (OPWP) (Klamath Basin Restoration Agreement, 2010, p. 105). Program Goals The primary goals of the OPWP include developing an Off-Project Water Settlement to resolve upper basin water issues, improve fish habitat, and provide for stability in irrigation deliveries (Klamath Basin Restoration Agreement, 2010, p. 105). One of the approaches to achieving these objectives is a water-use retirement program. The water-use retirement program is an effort to permanently provide an additional 30,000 acre-ft of water per year on an average annual basis to Upper Klamath Lake through “voluntary retirement of water rights or water uses, or other means as agreed to by the Klamath Tribes, to improve fisheries habitat and also provide for stability of irrigation water deliveries” (Klamath Basin Restoration Agreement, 2010, p. 105–111). The KBRA sets a 24-month window after the “effective date” for development of a proposal for the Off-Project Water Settlement. There is interest on the part of the Klamath Watershed Partnership (and others) in having a decisionmaking process in place before this time line. To assist parties in the OPWP involved with decisionmaking and implementation, the USGS proposed a two-phase approach. The first phase, which is described in this report, includes compilation and evaluation of relevant existing work and data in the upper basin, and synthesizing that information into a set of five hydrological information products. These products include GIS digital maps and datasets containing spatial information on evapotranspiration, subirrigation indicators, water rights, subbasin streamflow statistics, and return-flow indicators. Should efforts continue, a second phase could be developed to implement a monitoring program to evaluate the level of success of the first phase and to address additional information needs. Understanding the response of streams and groundwater to various land-use changes (such as
To create this app:Make a map of the AfDB projects CSV file in the Training Materials group.Download the CSV file, click Map (at the top of the page), and drag and drop the file onto your mapFrom the layer menu on your Projects layer choose Change Symbols and show the projects using Unique Symbols and the Status of field.Make a second map of the AfDB projects shown using Unique Symbols and the Sector field.HINT: Create a copy of your first map using Save As... and modify the copy.Assemble your story map on the Esri Story Maps websiteGo to storymaps.arcgis.comAt the top of the site, click AppsFind the Story Map Tabbed app and click Build a Tabbed Story MapFollow the instructions in the app builder. Add the maps you made in previous steps and copy the text from this sample app to your app. Explore and experiment with the app configuration settings.=============OPTIONAL - Make a third map of the AFDB projects summarized by country and add it to your story map.Add the World Countries layer to your map (Add > Search for Layers)From the layer menu on your Projects layer choose Perform Analysis > Summarize Data > Aggregate Points and run the tool to summarize the projects in each country.HINT: UNCHECK "Keep areas with no points"Experiment with changing the symbols and settings on your new layer and remove other unnecessary layers.Save AS... a new map.At the top of the site, click My Content.Find your story map application item, open its Details page, and click Configure App.Use the builder to add your third map and a description to the app and save it.