Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis 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 map 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.

This layer provides an estimate of flood frequency as one of seven classes:

None: No reasonable possibility of flooding; one chance out of 500 of flooding in any year or less than 1 time in 500 years.Very Rare: Flooding is very unlikely but is possible under extremely unusual weather conditions; less than 1 percent chance of flooding in any year or less than 1 time in 100 years but more than 1 time in 500 years.Rare: Flooding is unlikely but is possible under unusual weather conditions; 1 to 5 percent chance of flooding in any year or nearly 1 to 5 times in 100 years.Occasional: Flooding is expected infrequently under usual weather conditions; 5 to 50 percent chance of flooding in any year or 5 to 50 times in 100 years.Common: (Obsolete Class) Combination of Occasional and FrequentFrequent: Flooding is likely to occur often under usual weather conditions; more than a 50 percent chance of flooding in any year (i.e., 50 times in 100 years), but less than a 50 percent chance of flooding in all months in any year.Very Frequent: Flooding is likely to occur very often under usual weather conditions; more than a 50 percent chance of flooding in all months of any year.Dataset SummaryPhenomenon Mapped: Flooding frequencyUnits: 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 flooding frequency is derived from the gSSURGO map unit aggregated attribute table field Flooding Frequency - Dominant Condition (flodfreqdcd).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 "flooding frequency" 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 "flooding frequency" 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.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.

A layer item maintained by a Live Feed routine that regularly computes the approximate location of the Sun, perpendicular to the planet, using the current UTC date and time. Watch as the Sun, Day/Night Terminator, and Horizon pass over your map, highlighting what areas are in dusk, darkness, and dawn. Terminator Polygons include a GeoEnriched attribute containing the approximate Total Population experiencing twilight or darkness.Originally inspired by Jim Blaney's JSAPI item, the data is maintained by a modified Python routine adapted from John Gravois' GitHub JSAPI "midnight-commander" project. Small corrections and enhancements provide the Sub-Solar Point (Sun's location on the planet), the Horizon line (mid-line of the Sun that meets the horizon), and the Twilight features showing dusk and dawn as the Sun reflects light in the atmosphere.Twilight, also known as Dawn and Dusk, is the visible reflective light in the atmosphere as the Sun dips below (Dusk) or approaches (Dawn) the Horizon. Three stages of Twilight are classified at 6 degree increments, producing various shades of darkness and vibrant colors.Civil Twilight is the first stage as the Sun moves below the Horizon (Dusk) or the last as the Sun approaches the Horizon (Dawn). Enough natural light exists for people to see without needing artificial light. Celestial objects are not yet visible.Nautical Twilight is the second stage. Artificial light is now helpful and Celestial objects can be seen with ease. Ships find it difficult to navigate by the Horizon.Astronomical Twilight is the last stage before darkness sets in. Only distant clouds are a glow on the Horizon with bright stars in full view.What can I do with this layer?A continually updated visual representation of this daily cycle provides an additional source of information for planners and decision makers that operate in an environment that is impacted by the day/night cycle. This may include logistics and fleet management, maritime, law enforcement, as well as other first responders who are engaged in search and rescue operations where daylight is critical to mission execution.Example item using Terminator to blend the Earth at Night tile image.Source:Calculation for the Position of the Sun (declination angle of the Sun)Alternate calculation for Equation of time (used to compute Sun's position)Reference details for TwilightUpdate Frequency:  Every 10 minutes (at 5, 15, 25, ...) using the Aggregated Live Feed MethodologyArea Covered: The worldCoordinate System: GCS_WGS_1984, wkid: 4326, with Latitude limited to ±87.5 degrees for maximum compatibility.Layers:Celestial Bodies: Point layer containing current location of the Sun as it is passes directly overhead, perpendicular to the planet.Horizon: Polyline layer containing the mid-line of the Sun as it sets in the horizon.Terminator: Polygon layer containing the 6 degree transitions from sunlight to civil, nautical, and astronomical Twilight (dawn and dusk) plus areas experiencing the dark of night. Also includes output from ArcGIS Online GeoEnrichment attribute field "KeyGlobalFacts.TOTPOP" containing the approximate Total Population covered by each Polygon.Sample: See animation of data mapped at midnight each day for one year.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 point dataset contains information on the quality and condition of species-rich grassland communities recorded during field surveys in the Cairngorms National Park undertaken between 2020 and 2022, as part of a joint project delivered by NatureScot and the Cairngorms National Park Authority. The aim was to establish the location and extent of species-rich grassland (SRG) within enclosed (and formerly enclosed) farm land, up to a maximum altitudinal limit of 500 m, using a combination of remote sensing and targeted field survey. This dataset covers the Livet, Avon and Dee catchments. Patches of unimproved/semi-improved grassland, down to 0.04 ha in size, were identified and delineated by analysing high-resolution aerial photography (involving image segmentation and subsequent classification of the output). This provided a search map of polygons to visit in the field, targeting survey effort towards the areas where species-rich grassland was most likely to occur. The field survey was undertaken by contractors during July to September in 2020 and 2021, and July to October in 2022. For each polygon, grassland communities and their relative proportion cover were described using the National Vegetation Classification (NVC), and species-richness was assessed. Locations of any missed species-rich grassland, occurring outside the search map polygons, were captured in the field and added to the dataset. This information is stored in the associated CNPGrasslandMapping_2020to2022_Polygons dataset. When species-rich grassland was encountered, additional detailed attributes describing the quality and condition of these stands, plus photo attachments, were collected in this point dataset (which can be joined/related to the polygons using the POLY_ID/ PARENT_POLY fields). A rapid assessment of key features relating to species-richness, sward characteristics, management, and presence and abundance of notable species was undertaken following a structured walk through each SRG stand. Attributes are mostly categorical to promote a consistent, standardised response. The dataset contains the following fields: SRG_NVC – species-rich grassland NVC community; SRG_HAB – broad SRG habitat type; SPEC_SQ_M – number of species per square metre (≤10, 11-20, 21-30, >30); FORB_COV – % cover of forbs (≤10, 11-25, 26-50, 51-75, ≥75); SWRD_HT_CM – sward height range (cm) (≤5, 6-20, 21-30, >30); THATCH_ACCU – thatch accumulation (%) (≤10, 11-25, 26-50, 51-75, ≥75); BARE_GRN – bare ground (%) (<1, 1-5, 6-10, >10%); MANAGEMENT –obvious management at time of survey (grazing - sheep, grazing - cattle, grazing - sheep & cattle, grazing - deer, cutting - hay, cutting - silage, cutting - verge, no grazing / cutting, other - describe in comment);GRAZ_INTENS – grazing intensity (at time of survey) (none, low, moderate, high); PRESSURES – negative pressures impacting site condition (none, over-grazed, under-grazed, scrub / tree encroachment, under-grazed & scrub / tree encroachment, bracken encroachment, ruderals, heavy poaching, other - describe in comment); COMMENT – additional notes on quality/condition/management; Notable species, recorded using DAFOR scale (Dominant, Abundant, Frequent, Occasional, Rare, or Absent): CIRS_HETR – Cirsium heterophyllum; GENT_CAMP – Gentianella campestris; GALI_BORE – Galium boreale; HELI_NUMM – Helianthemum nummularium; LINU_CATH – Linum catharticum; LYCH_FLOS – Lychnis flos-cuculi; MEUM_ATHA – Meum athamanticum; PERS_VIVI – Persicaria vivipara; PIMP_SAXI – Pimpinella saxifraga; TROL_EURO – Trollius europaeus; VIOL_LUTE – Viola lutea; AVEN_PRAT – Avenula pratensis; BRIZ_MEDI – Briza media; BOTR_LUNA – Botrychium lunaria; COLE_VIRI – Coeloglossum viride; DACT_FUCH – Dactylorhiza fuchsii; DACT_MACU – Dactylorhiza maculata; DACT_PURP – Dactylorhiza purpurea; DACT_SP – Dactylorhizasp.; GYMN_BORE – Gymnadenia borealis; NEOT_OVAT – Neottia ovata; PLAT_BIFO – Platanthera bifolia; PLAT_CHLO – Platanthera chlorantha; PSUD_ALBI – Psudorchis albida; TOT_OTRCH_AB - Total orchid abundance (all species combined); WAXCAPS – presence of waxcap fungi (present/absent); OTH_NOTABLE – other notable species; PARENT_POLY – unique identifier of polygon in which the point was collected (can be used as join/relate field); GRIDREF – grid reference of point; SURV_YEAR – year of field survey; SURV_DATE – date of field survey; SURVEYOR – field surveyor; CATCHMENT – river catchment area; POINT_ID – unique identifier.

Complete project metadata on spatialdata.gov.scot

Wetlands are areas where water is present at or near the surface of the soil during at least part of the year. Wetlands provide habitat for many species of plants and animals that are adapted to living in wet habitats. Wetlands form characteristic soils, absorb pollutants and excess nutrients from aquatic systems, help buffer the effects of high flows, and recharge groundwater. Data on the distribution and type of wetland play an important role in land use planning and several federal and state laws require that wetlands be considered during the planning process.The National Wetlands Inventory (NWI) was designed to assist land managers in wetland conservation efforts. The NWI is managed by the US Fish and Wildlife Service.Dataset SummaryPhenomenon Mapped: WetlandsUnits: MetersCell Size: 10 metersSource Type: ThematicPixel Type: Unsigned integer 16 bitData Coordinate System: North America Albers Equal Area Conic (WKID 102008)Mosaic Projection: North America Albers Equal Area Conic (WKID 102008)Extent: 50 United States plus Puerto Rico, American Samoa, the US Virgin Islands, the Northern Mariana Islands, and US Minor Outlying IslandsSource: U.S. Fish and Wildlife ServicePublication Date: October 26, 2024 ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/This layer was created from the October 26, 2024 version of the NWI. The original NWI features were downloaded from USFWS and then converted to a single part feature class using the Multipart To Singlepart tool. After that, the Dice tool was used to break up features larger than 50,000 vertices. The diced, singlepart features were projected to North America Albers projection, then the Repair Geometry tool was run on the features, using tool defaults, to prepare it for a clean rasterization. The features were then converted to several rasters in North America Albers projection using the Polygon to Raster Tool. The National Land Cover Dataset was used as a snap raster for the rasterization process. The rasters representing different parts of the USA are served together as a single layer from a mosaic dataset on the server.This layer includes attributes from the original dataset as well as attributes added by Esri for use in the default pop-up and to allow the user to query and filter the data. NWI derived attributes:Wetland Code - a code that identifies specific attributes of the wetlandWetland Type - one of 8 wetland typesEsri created attributes:System - code indicating the system and subsystem of the wetlandClass - code indicating the class and subclass of the wetlandModifier 1, Modifier 2, Modifier 3, Modifier 4 - these four fields contain letter codes for modifiers applied to the wetland descriptionSystem Name - the name of the system (Marine, Estuarine, Riverine, Lacustrine, or Palustrine)Subsystem Name - the name of the subsystemClass Name - the name of the classSubclass Name - the name of the subclassModifier 1 Name, Modifier 2 Name, Modifier 3 Name , Modifier 4 Name - these four fields contain names for modifiers applied to the wetland descriptionPopup Header - this field contains a text string that is used to create the header in the default pop-up System Text - this field contains a text string that is used to create the system description text in the default pop-upClass Text - this field contains a text string that is used to create the class description text in the default pop-upModifier Text - this field contains a text string that is used to create the modifier description text in the default pop-upSpecies Text - this field contains a text string that is used to create the species description text in the default pop-upCodes, names, and text fields were derived from the publication Classification of Wetlands and Deepwater Habitats of the United States.The layer serves an index value from a mosaic dataset on the enterprise server. It uses an attribute table function on the mosaic to serve the attributes that appear in the popup for the layer. Because there are more than 2,000 integer values served by the layer, most map clients can not render a legend for this layer. A colormap is used after the attribute table function on the mosaic dataset to help the layer render in the colors intended for the layer.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 "USA Wetlands" 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 "USA Wetlands" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.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.

This street centerline lines feature class represents current right of way in the City of Los Angeles. It shows the official street names and is related to the official street name data. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works. Street Centerline layer was created in geographical information systems (GIS) software to display Dedicated street centerlines. The street centerline layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a line feature class and attribute data for the features. City of LA District Offices use Street Centerline layer to determine dedication and street improvement requirements. Engineering street standards are followed to dedicate the street for development. The Bureau of Street Services tracks the location of existing streets, who need to maintain that road. Additional information was added to Street Centerline layer. Address range attributes were added make layer useful for geocoding. Section ID values from Bureau of Street Services were added to make layer useful for pavement management. Department of City Planning added street designation attributes taken from Community Plan maps. The street centerline relates to the Official Street Name table named EASIS, Engineering Automated Street Inventory System, which contains data describing the limits of the street segment. A street centerline segment should only be added to the Street Centerline layer if documentation exists, such as a Deed or a Plan approved by the City Council. Paper streets are street lines shown on a recorded plan but have not yet come into existence on the ground. These street centerline segments are in the Street Centerline layer because there is documentation such as a Deed or a Plan for the construction of that street. Previously, some street line features were added although documentation did not exist. Currently, a Deed, Tract, or a Plan must exist in order to add street line features. Many street line features were edited by viewing the Thomas Bros Map's Transportation layer, TRNL_037 coverage, back when the street centerline coverage was created. When TBM and BOE street centerline layers were compared visually, TBM's layer contained many valid streets that BOE layer did not contain. In addition to TBM streets, Planning Department requested adding street line segments they use for reference. Further, the street centerline layer features are split where the lines intersect. The intersection point is created and maintained in the Intersection layer. The intersection attributes are used in the Intersection search function on NavigateLA on BOE's web mapping application NavigateLA. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. Note that there are named alleys in the BOE Street Centerline layer. Since the line features for named alleys are stored in the Street Centerline layer, there are no line features for named alleys in those areas that are geographically coincident in the Alley layer. For a named alley , the corresponding record contains the street designation field value of ST_DESIG = 20, and there is a name stored in the STNAME and STSFX fields.List of Fields:SHAPE: Feature geometry.OBJECTID: Internal feature number.STNAME_A: Street name Alias.ST_SUBTYPE: Street subtype.SV_STATUS: Status of street in service, whether the street is an accessible roadway. Values: • Y - Yes • N - NoTDIR: Street direction. Values: • S - South • N - North • E - East • W - WestADLF: From address range, left side.ZIP_R: Zip code right.ADRT: To address range, right side.INT_ID_TO: Street intersection identification number at the line segment's end node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.SECT_ID: Section ID used by the Bureau of Street Services. Values: • none - No Section ID value • private - Private street • closed - Street is closed from service • temp - Temporary • propose - Proposed construction of a street • walk - Street line is a walk or walkway • known as - • numeric value - A 7 digit numeric value for street resurfacing • outside - Street line segment is outside the City of Los Angeles boundary • pierce - Street segment type • alley - Named alleySTSFX_A: Street suffix Alias.SFXDIR: Street direction suffix Values: • N - North • E - East • W - West • S - SouthCRTN_DT: Creation date of the polygon feature.STNAME: Street name.ZIP_L: Zip code left.STSFX: Street suffix. Values: • BLVD - BoulevardADLT: To address range, left side.ID: Unique line segment identifierMAPSHEET: The alpha-numeric mapsheet number, which refers to a valid B-map or A-map number on the Cadastral tract index map. Values: • B, A, -5A - Any of these alpha-numeric combinations are used, whereas the underlined spaces are the numbers.STNUM: Street identification number. This field relates to the Official Street Name table named EASIS, to the corresponding STR_ID field.ASSETID: User-defined feature autonumber.TEMP: This attribute is no longer used. This attribute was used to enter 'R' for reference arc line segments that were added to the spatial data, in coverage format. Reference lines were temporary and not part of the final data layer. After editing the permanent line segments, the user would delete temporary lines given by this attribute.LST_MODF_DT: Last modification date of the polygon feature.REMARKS: This attribute is a combination of remarks about the street centerline. Values include a general remark, the Council File number, which refers the street status, or whether a private street is a private driveway. The Council File number can be researched on the City Clerk's website http://cityclerk.lacity.org/lacityclerkconnect/INT_ID_FROM: Street intersection identification number at the line segment's start node. The value relates to the intersection layer attribute table, to the CL_NODE_ID field. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline data layer and then the intersections data layer, during the creation of new intersection points. Each intersection identification number is a unique value.ADRF: From address range, right side.

This feature service depicts the National Weather Service (NWS) watches, warnings, and advisories within the United States. Watches and warnings are classified into well over 100 categories. See event descriptions for full details. A warning is issued when a hazardous weather or hydrologic event is occurring, imminent or likely. A warning means weather conditions pose a threat to life or property. People in the path of the storm need to take protective action.A watch is used when the risk of a hazardous weather or hydrologic event has increased significantly, but its occurrence, location or timing is still uncertain. It is intended to provide enough lead time so those who need to set their plans in motion can do so. A watch means that hazardous weather is possible. People should have a plan of action in case a storm threatens, and they should listen for later information and possible warnings especially when planning travel or outdoor activities.An advisory is issued when a hazardous weather or hydrologic event is occurring, imminent or likely. Advisories are for less serious conditions than warnings, that cause significant inconvenience and if caution is not exercised, could lead to situations that may threaten life or property.SourceNational Weather Service RSS-CAP Warnings and Advisories: Public AlertsNational Weather Service Boundary Overlays: AWIPS Shapefile DatabaseSample DataSee Sample Layer Item for sample data during Weather inactivity!Update FrequencyThe services is updated every 5 minutes using the Aggregated Live Feeds methodology.The overlay data is checked and updated daily from the official AWIPS Shapefile Database.Area CoveredUnited States and TerritoriesWhat can you do with this layer?Customize the display of each attribute by using the Change Style option for any layer.Query the layer to display only specific types of weather watches and warnings.Add to a map with other weather data layers to provide insight on hazardous weather events.Use ArcGIS Online analysis tools, such as Enrich Data, to determine the potential impact of weather events on populations.Revisions:Feb 25, 2021: Revised service data upate workflow, improving stability and update interval.Process now checks for data updates every 5 minutes!Mar 3, 2021: Revised data processing to leverage VTEC parameter details to better align Event 'effective' dates with reported dates on Alert pages.Apr 17, 2023: Turned off popups for boundary Layers by default.Feb 1, 2024: Revised to leverage CAP v1.2 source endpoint. Update event link to use alert search.Feb 16, 2024: Revised event link to accomodate change in alert search endpoint.Jan 19, 2025: Added event 'Description' and 'Instructions', updated Pop-up.Jan 22, 2025: Exposed 'Hours Old' fields supporting last 'Updated', 'Effective', and 'Expiration' as +- age values for events.This map 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!

Abstract The dataset was derived by the Bioregional Assessment Programme.This dataset is derived from Greater Hunter Native Vegetation Mapping supplied by NSW Office of Water on 19/12/2014. You can find a link to the parent datasets in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived. This is essentially the same as the original dataset (see History) except an additional field (Map _Class) has been added to the …Show full descriptionAbstract The dataset was derived by the Bioregional Assessment Programme.This dataset is derived from Greater Hunter Native Vegetation Mapping supplied by NSW Office of Water on 19/12/2014. You can find a link to the parent datasets in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived. This is essentially the same as the original dataset (see History) except an additional field (Map _Class) has been added to the polygon attribute table where the source vegetation classes have been collapsed into fewer more generic classes to facilitate the production of report map image. Additionally there is a 50m rasterised version of the re-classified data (HUN_GHM_Veg_50m) derved from the Map_Class field of the polygon features. This was generated to facilitate timely redrawing of the feature layer in the report map MXD. Dataset History The GHM geodatabase builds on a wealth of information and previous mapping from the Hunter region. Existing field data, mapping, classification and remote sensing interpretation were augmented with new survey data to produce the vegetation community classification used in this project. The classification used a series of well documented analyses as well as expert review to achieve its end-point. This document contains descriptions of the 252 native vegetation communities resulting from the data analysis and classification process. The GHM geodatabase contains two principal vegetation layers. The GHM Vegetation Type layer and the Canopy Cover (v2) layer (individual tree crowns or clumps of tree crowns). The GHM also contains field plot localities, associated species information and plot-specific photographs. Data specific to each polygon (e.g. crown cover) and to each native vegetation community type (e.g. common name, scientific name) are included. Polygons, the fundamental spatial units, are built from computer-based feature recognition which delineates landscapes patterns. The GHM Vegetation Type map is built by attributing individual polygons with vegetation type from the GHM floristic classification through a multi-stage process. The process includes visual interpretation of SPOT 5 and ADS40 imagery as well as species distribution modelling and expert review. The project included a review of existing mapping and classification and established equivalences between these and the GHM Classification. This was done for two main reasons; to allow the mapping team to draw the maximum benefit from existing mapping and, to ensure that mapping currently in common use has a recorded and explicit relationship with the current products. This is important considering that much of this existing mapping is at a very fine scale and may represent sub-classes of the GHM Classification. This document provides users with a description of 'standard' products and also provides examples of how more advanced use may be made of the GHM. In addition to the source polygon data, a 50m rasterised version of the Map Class has been included to facilitate fast re-draw for the large scale report map production. A comprehensive account of the lineage of this data is give in the accompanying document GHM_v4p0_Geodatabase_Guide_070812.pdf included in this dataset. Dataset Citation Bioregional Assessment Programme (2014) Greater Hunter Native Vegetation Mapping with Classification for Mapping. Bioregional Assessment Derived Dataset. Viewed 13 March 2019, http://data.bioregionalassessments.gov.au/dataset/73abc2f6-1b8a-43a0-b458-c67ee4275edc. Dataset Ancestors Derived From Greater Hunter Native Vegetation Mapping

This data package includes an ArcMap geodatabase for the Chihuahuan Desert Rangeland Research Center (CDRRC) pastures 1, 4, 14, and 15: one polygon feature class, one point feature class, associated attribute tables and metadata. The spatial data, CDRRC1_4_14_15_StateMap_v1.gdb.zip, represents the ecological sites and states on Pastures 1, 4, 14 and 15 on the Chihuahuan Desert Rangeland Research Center, and includes field traverse data. CDRRC1_4_14_15_StateMapMetadata.pdf and TraversePointsMetadata.pdf contain the geospatial metadata provided by ArcMap. CDRRC1_4_14_15_StateMap_v1.csv is the attribute table associated with the state map’s polygon feature class, and TraversePoints.xlsx is the attribute table associated with the traverse points feature class and includes a sheet containing detailed attribute metadata.

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.

This intersection points feature class represents current intersections in the City of Los Angeles. Few intersection points, named pseudo nodes, are used to split the street centerline at a point that is not a true intersection at the ground level. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most current geographic information of the public right of way. The right of way information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.Intersection layer was created in geographical information systems (GIS) software to display intersection points. Intersection points are placed where street line features join or cross each other and where freeway off- and on-ramp line features join street line features. The intersection points layer is a feature class in the LACityCenterlineData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The intersection points relates to the intersection attribute table, which contains data describing the limits of the street segment, by the CL_NODE_ID field. The layer shows the location of the intersection points on map products and web mapping applications, and the Department of Transportation, LADOT, uses the intersection points in their GIS system. The intersection attributes are used in the Intersection search function on BOE's web mapping application NavigateLA. The intersection spatial data and related attribute data are maintained in the Intersection layer using Street Centerline Editing application. The City of Los Angeles Municipal code states, all public right-of-ways (roads, alleys, etc) are streets, thus all of them have intersections. List of Fields:Y: This field captures the georeferenced location along the vertical plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, Y = in the record of a point, while the X = .CL_NODE_ID: This field value is entered as new point features are added to the edit layer, during Street Centerline application editing process. The values are assigned automatically and consecutively by the ArcGIS software first to the street centerline spatial data layer, then the intersections point spatial data layer, and then the intersections point attribute data during the creation of new intersection points. Each intersection identification number is a unique value. The value relates to the street centerline layer attributes, to the INT_ID_FROM and INT_ID_TO fields. One or more street centerline features intersect the intersection point feature. For example, if a street centerline segment ends at a cul-de-sac, then the point feature intersects only one street centerline segment.X: This field captures the georeferenced location along the horizontal plane of the point in the data layer that is projected in Stateplane Coordinate System NAD83. For example, X = in the record of a point, while the Y = .ASSETID: User-defined feature autonumber.USER_ID: The name of the user carrying out the edits.SHAPE: Feature geometry.LST_MODF_DT: Last modification date of the polygon feature.LAT: This field captures the Latitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.OBJECTID: Internal feature number.CRTN_DT: Creation date of the polygon feature.TYPE: This field captures a value for intersection point features that are psuedo nodes or outside of the City. A pseudo node, or point, does not signify a true intersection of two or more different street centerline features. The point is there to split the line feature into two segments. A pseudo node may be needed if for example, the Bureau of Street Services (BSS) has assigned different SECT_ID values for those segments. Values: • S - Feature is a pseudo node and not a true intersection. • null - Feature is an intersection point. • O - Intersection point is outside of the City of LA boundary.LON: This field captures the Longitude in deciaml degrees units of the point in the data layer that is projected in Geographic Coordinate System GCS_North_American_1983.

Tags soil survey, soils, Soil Survey Geographic, SSURGO Summary SSURGO depicts information about the kinds and distribution of soils on the landscape. The soil map and data used in the SSURGO product were prepared by soil scientists as part of the National Cooperative Soil Survey. Description This data set is a digital soil survey and generally is the most detailed level of soil geographic data developed by the National Cooperative Soil Survey. The information was prepared by digitizing maps, by compiling information onto a planimetric correct base and digitizing, or by revising digitized maps using remotely sensed and other information. This data set consists of georeferenced digital map data and computerized attribute data. The map data are in a 3.75 minute quadrangle format and include a detailed, field verified inventory of soils and nonsoil areas that normally occur in a repeatable pattern on the landscape and that can be cartographically shown at the scale mapped. A special soil features layer (point and line features) is optional. This layer displays the location of features too small to delineate at the mapping scale, but they are large enough and contrasting enough to significantly influence use and management. The soil map units are linked to attributes in the National Soil Information System relational database, which gives the proportionate extent of the component soils and their properties. Credits There are no credits for this item. Use limitations The 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. Extent West -76.713689 East -76.526117 North 39.374398 South 39.194856 Scale Range There is no scale range for this item.

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.

This submission offers a link to a web mapping application hosted instance of the Global Oil & Gas Features Database (GOGI), via EDX Spatial. This offers users with the ability to visualize, interact, and create maps with data of their choice, as well as download specific attributes or fields of view from the database. This data can also be downloaded as a File Geodatabse from EDX at https://edx.netl.doe.gov/dataset/global-oil-gas-features-database. Access the technical report describing how this database was produced using the following link: https://edx.netl.doe.gov/dataset/development-of-an-open-global-oil-and-gas-infrastructure-inventory-and-geodatabase” This data was developed using a combination of big data computing, custom search and data integration algorithms, and expert driven search to collect open oil and gas data resources worldwide. This approach identified over 380 data sets and integrated more than 4.8 million features into the GOGI database. Acknowledgements: This work was funded under the Climate and Clean Air Coalition (CCAC) Oil and Gas Methane Science Studies. The studies are managed by United Nations Environment in collaboration with the Office of the Chief Scientist, Steven Hamburg of the Environmental Defense Fund. Funding was provided by the Environmental Defense Fund, OGCI Companies (Shell, BP, ENI, Petrobras, Repsol, Total, Equinor, CNPC, Saudi Aramco, Exxon, Oxy, Chevron, Pemex) and CCAC.

This layer contains digital mapping of the native vegetation communities of the Sydney Metropolitan area. Vegetation communities have been derived from the analysis of 2200 floristic sites collated for the study area. Identified vegetation communities have been related to currently listed threatened ecological communities listed under the NSW TSC Act, 1995 and the Commonwealth EPBC Act, 1999. Native vegetation communities have been mapped using a combination of detailed image interpretation, relationships between sample sites and abiotic environmental variables. The derived digital data layer includes fields that describe the vegetation community, interpreted dominant species and understorey characteristics, interpretation confidence, disturbance type and severity, NSW vegetation formation and classes and related NSW Plant Community Types. These are described in detail in technical reports OEH (2016) The Native Vegetation of the Sydney Metropolitan Area. Volume 1: Technical Report. Version 3.0. Office of Environment and Heritage Sydney. OEH (2016) The Native Vegetation of the Sydney Metropolitan Area. Volume 2: Vegetation Community Profiles. Version 3.0. NSW Office of Environment and Heritage, Sydney. Version 3.0 of the Native Vegetation of the Sydney Metropolitan Area updates the Plant Community Type and Biometric Vegetation Type of each map unit.

Version 3.0 replaced version 2.0 (VIS_ID 3817) and created a seamless alignment between the GIS layer and the Plant Community and Biometric Vegetation Types in the Biodiversity Assessment Method tool. These were the only significant updates from version 2.0.

Version 3.1 is a minor update. Two new attribute fields were added - PCTID and PCTName. These fields align with the Bionet Vegetation map data standard v1.0(https://www.environment.nsw.gov.au/research-and-publications/publications-search/bionet-vegetation-map-data-standard-version-1). PCTID was populated by the v3.0 attribute field, PCT_code. PCTName was populated by extracting the corresponding PCT common name from the Bionet Vegetation Classification web service (https://data.bionet.nsw.gov.au/). No other changes were made to the vegetation map.

VIS_ID 4489

Abstract

The dataset was derived by the Bioregional Assessment Programme. This dataset was derived from the Surface Geology of Australia, 1:1 000 000 scale, 2012 edition dataset. You can find a link to the parent dataset in the Lineage Field in this metadata statement. The History Field in this metadata statement describes how this dataset was derived.

Geological units extracted from the national geodatabase for the Hunter subregion.

The Surface Geology of Australia 1:1M scale dataset (2012 edition) is a seamless national coverage of outcrop and surficial geology, compiled for use at or around 1:1 million scale. The data maps outcropping bedrock geology and unconsolidated or poorly consolidated regolith material covering bedrock. Geological units are represented as polygon and line geometries, and are attributed with information regarding stratigraphic nomenclature and hierarchy, age, lithology, and primary data source. The dataset also contains geological contacts, structural features such as faults and shears, and miscellaneous supporting lines like the boundaries of water and ice bodies.

The 2012 dataset has been updated from the previous 2010 data by updating geological unit data to 2012 information in the Australian Stratigraphic Units Database (http://www.ga.gov.au/products-services/data-applications/reference-databases/stratigraphic-units.html), incorporating new published mapping in the Northern Territory and Queensland, and correcting errors or inconsistent data identified in the previous edition, particularly in the Phanerozoic geology of Western Australia. The attribute structure of the dataset has also been revised to be more compatible with the GeoSciML data standard, published by the IUGS Commission for Geoscience Information.

The first edition of this national dataset was first released in 2008, with map data compiled largely from simplifying and edgematching existing 1:250 000 scale geological maps. Where these maps were not current, more recent source maps ranging in scale from 1:50 000 to 1:1 million were used. In some areas where the only available geological maps were old and poorly located, some repositioning of mapping using recent satellite imagery or geophysics was employed.

Dataset History

Geological units extracted from the national geodatabase for the Hunter subregion.

The 2012 dataset has been updated from the previous 2010 data by updating geological unit data to 2012 information in the Australian Stratigraphic Units Database (http://www.ga.gov.au/products-services/data-applications/reference-databases/stratigraphic-units.html), incorporating new published mapping in the Northern Territory and Queensland, and correcting errors or inconsistent data identified in the previous edition, particularly in the Phanerozoic geology of Western Australia. The attribute structure of the dataset has also been revised to be more compatible with the GeoSciML data standard, published by the IUGS Commission for Geoscience Information.

The first edition of this national dataset was first released in 2008, with map data compiled largely from simplifying and edgematching existing 1:250 000 scale geological maps. Where these maps were not current, more recent source maps ranging in scale from 1:50 000 to 1:1 million were used. In some areas where the only available geological maps were old and poorly located, some repositioning of mapping using recent satellite imagery or geophysics was employed.

Dataset Citation

Bioregional Assessment Programme (2014) Hunter 1 million scale geological units. Bioregional Assessment Derived Dataset. Viewed 07 February 2017, http://data.bioregionalassessments.gov.au/dataset/6d8c6d87-c397-4b84-be39-4b7831fb293e.

Dataset Ancestors

• Derived From Surface Geology of Australia, 1:1 000 000 scale, 2012 edition

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. This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows: This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology …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. This dataset was sourced from the Queensland Department of Natural Resources and Mines in 2012. Information provided by the Department describes the dataset as follows: This data was originally provided on DVD and contains the converted shapefiles, layer files, raster images and project .mxd files used on the Queensland geology and structural framework map. The maps were done in ArcGIS 9.3.1 and the data stored in file geodatabases, topology created and validated. This provides greater data quality by performing topological validation on the feature's spatial relationships. For the purposes of the DVD, shapefiles were created from the file geodatabases and for MapInfo users MapInfo .tab and .wor files. The shapefiles on the DVD are a revision of the 1975 Queensland geology data, and are both are available for display, query and download on the department's online GIS application. The Queensland geology map is a digital representation of the distribution or extent of geological units within Queensland. In the GIS, polygons have a range of attributes including unit name, type of unit, age, lithological description, dominant rock type, and an abbreviated symbol for use in labelling the polygons. The lines in this dataset are a digital representation of the position of the boundaries of geological units and other linear features such as faults and folds. The lines are attributed with a description of the type of line represented. Approximately 2000 rock units were grouped into the 250 map units in this data set. The digital data was generalised and simplified from the Department's detailed geological data and was captured at 1:500 000 scale for output at 1:2 000 000 scale. In the ESRI version, a layer file is provided which presents the units in the colours and patterns used on the printed hard copy map. For Map Info users, a simplified colour palette is provided without patterns. However a georeferenced image of the hard copy map is included and can be displayed as a background in both Arc Map and Map Info. The geological framework of Queensland is classified by structural or tectonic unit (provinces and basins) in which the rocks formed. These are referred to as basins (or in some cases troughs and depressions) where the original form and structure are still apparent. Provinces (and subprovinces) are generally older basins that have been strongly tectonised and/or metamorphosed so that the original basin extent and form are no longer preserved. Note that intrusive and some related volcanic rocks that overlap these provinces and basins have not been included in this classification. The map was compiled using boundaries modified and generalised from the 1:2 000 000 Queensland Geology map (2012). Outlines of subsurface basins are also shown and these are based on data and published interpretations from petroleum exploration and geophysical surveys (seismic, gravity and magnetics). For the structural framework dataset, two versions are provided. In QLD_STRUCTURAL_FRAMEWORK, polygons are tagged with the name of the surface structural unit, and names of underlying units are imbedded in a text string in the HIERARCHY field. In QLD_STRUCTURAL_FRAMEWORK_MULTI_POLYS, the data is structured into a series of overlapping, multi-part polygons, one for each structural unit. Two layer files are provided with the ESRI data, one where units are symbolised by name. Because the dataset has been designed for units display in the order of superposition, this layer file assigns colours to the units that occur at the surface with concealed units being left uncoloured. Another layer file symbolises them by the orogen of which they are part. A similar set of palettes has been provided for Map Info. Dataset History Details on the source data can be found in the xml file associated with data layer. Data in this release *ESRI.shp and MapInfo .tab files of rock unit polygons and lines with associated layer attributes of Queensland geology *ESRI.shp and MapInfo .tab files of structural unit polygons and lines with associated layer attributes of structural framework *ArcMap .mxd and .lyr files and MapInfo .wor files containing symbology *Georeferenced Queensland geology map, gravity and magnetic images *Queensland geology map, structural framework and schematic diagram PDF files *Data supplied in geographical coordinates (latitude/longitude) based on Geocentric Datum of Australia - GDA94 Accessing the data Programs exist for the viewing and manipulation of the digital spatial data contained on this DVD. Accessing the digital datasets will require GIS software. The following GIS viewers can be downloaded from the internet. ESRI ArcExplorer can be found by a search of www.esriaustralia.com.au and MapInfo ProViewer by a search on www.pbinsight.com.au collectively ("the websites"). Metadata Metadata is contained in .htm files placed in the root folder of each vector data folder. For ArcMap users metadata for viewing in ArcCatalog is held in an .xml file with each shapefile within the ESRI Shapefile folders. Disclaimer The State of Queensland is not responsible for the privacy practices or the content of the websites and makes no statements, representations, or warranties about the content or accuracy or completeness of, any information or products contained on the websites. Despite our best efforts, the State of Queensland makes no warranties that the information or products available on the websites are free from infection by computer viruses or other contamination. The State of Queensland disclaims all responsibility and all liability (including without limitation, liability in negligence) for all expenses, losses, damages and costs you might incur as a result of accessing the websites or using the products available on the websites in any way, and for any reason. The State of Queensland has included the websites in this document as an information source only. The State of Queensland does not promote or endorse the websites or the programs contained on them in any way. WARNING: The Queensland Government and the Department of Natural Resources and Mines accept no liability for and give no undertakings, guarantees or warranties concerning the accuracy, completeness or fitness for the purposes of the information provided. The consumer must take all responsible steps to protect the data from unauthorised use, reproduction, distribution or publication by other parties. Please view the 'readme.html' and 'licence.html' file for further, more complete information Dataset Citation Geological Survey of Queensland (2012) Queensland geology and structural framework - GIS data July 2012. Bioregional Assessment Source Dataset. Viewed 07 December 2018, http://data.bioregionalassessments.gov.au/dataset/69da6301-04c1-4993-93c1-4673f3e22762.

Here we present a geospatial dataset representing local- and regional-scale aquifer system boundaries, defined on the basis of an extensive literature review and published in GebreEgziabher et al. (2022). Nature Communications, 13, 2129, https://www.nature.com/articles/s41467-022-29678-7

The database contains 440 polygons, each representing one study area analyzed in GebreEgziabher et al. (2022). The attribute table associated with the shapefile has two fields (column headings): (1) aquifer system title (Ocala Uplift sub-area of the broader Floridan Aquifer System), and (2) broader aquifer system title (e.g., the Floridan Aquifer System).

• to explore the available data via an interactive app please visit the following URL: https://ucsb.maps.arcgis.com/apps/instant/nearby/index.html?appid=2a238e4ed2434d21b3b53c861a064d8f
• to explore the 3D nature of a dozen aquifer systems please see the following storymap: https://storymaps.arcgis.com/stories/a91f061759e64e44af38daf6cefa4259

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

The Federal Emergency Management Agency (FEMA) produces Flood Insurance Rate maps and identifies Special Flood Hazard Areas as part of the National Flood Insurance Program's floodplain management. Special Flood Hazard Areas have regulations that include the mandatory purchase of flood insurance for holders of federally regulated mortgages. In addition, in the USA, this layer can help planners and firms avoid areas of flood risk and also avoid additional cost to carry insurance for certain planned activities.Dataset SummaryPhenomenon Mapped: Flood Hazard AreasUnits: NoneCell Sizes: 10 meters (default), 30 meters, and 90 metersSource Type: ThematicPixel Type: Unsigned integerData Coordinate System: USA Contiguous Albers Equal Area Conic USGS version (contiguous US, Puerto Rico, US Virgin Islands), WGS 1984 Albers (Alaska), Hawaii Albers Equal Area Conic (Hawaii), Western Pacific Albers Equal Area Conic (Guam, Northern Mariana Islands, and American Samoa)Mosaic Projection: Web Mercator Auxiliary SphereExtents: Contiguous United States, Alaska, Hawaii, Puerto Rico, Guam, US Virgin Islands, Northern Mariana Islands and American Samoa.Source: Federal Emergency Management Agency (FEMA)Publication Date: June 27, 2024ArcGIS Server URL: https://landscape11.arcgis.com/arcgis/This layer is derived from the June 27, 2024 version Flood Insurance Rate Map feature class S_FLD_HAZ_AR. The vector data were then flagged with an index of 88 classes, representing a unique combination of values displayed by three renderers. (In three resolutions the three renderers make nine processing templates.) Repair Geometry was run on the set of features, then the features were rasterized using the 88 class index at a resolutions of 10, 30, and 90 meters, using the Polygon to Raster tool and the "MAXIMUM_COMBINED_AREA" option. Not every part of the United States is covered by flood rate maps. This layer compiles all the flood insurance maps available at the time of publication. To make analysis easier, areas that were NOT mapped by FEMA for flood insurance rates no longer are served as NODATA but are filled in with a value of 250, representing any unmapped areas which appear in the US Census' boundary of the USA states and territories. The attribute table corresponding to value 250 will indicate that the area was not mapped.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 "flood hazard areas" 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 "flood hazard areas" in the search box, browse to the layer then click OK.In ArcGIS Pro you can use the built-in raster functions to create custom extracts of the data. Imagery layers provide fast, powerful inputs to geoprocessing tools, models, or Python scripts in Pro.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.Processing TemplatesCartographic Renderer - The default. These are meaningful classes grouped by FEMA which group its own Flood Zone Type and Subtype fields. This renderer uses FEMA's own cartographic interpretations of its flood zone and zone subtype fields to help you identify and assess risk. Flood Zone Type Renderer - Specifically renders FEMA FLD_ZONE (flood zone) attribute, which distinguishes the original, broadest categories of flood zones. This renderer displays high level categories of flood zones, and is less nuanced than the Cartographic Renderer. For example, a fld_zone value of X can either have moderate or low risk depending on location. This renderer will simply render fld_zone X as its own color without identifying "500 year" flood zones within that category.Flood Insurance Requirement Renderer - Shows Special Flood Hazard Area (SFHA) true-false status. This may be helpful if you want to show just the places where flood insurance is required. A value of True means flood insurance is mandatory in a majority of the area covered by each 10m pixel.Each of these three renderers have templates at three different raster resolutions depending on your analysis needs. To include the layer in web maps to serve maps and queries, the 10 meter renderers are the preferred option. These are served with overviews and render at all resolutions. However, when doing analysis of larger areas, we now offer two coarser resolutions of 30 and 90 meters in processing templates for added convenience and time savings.