This is an Allegheny County extract of the 2016 US Census Block Groups downloaded from the following website: https://www.census.gov/geo/maps-data/data/tiger-cart-boundary.html.

This dataset was previously harvested on a weekly basis from Allegheny County’s GIS data portal (http://openac.alcogis.opendata.arcgis.com/). The full metadata record for this dataset can also be found on Allegheny County’s GIS portal, at https://openac-alcogis.opendata.arcgis.com/datasets/AlCoGIS::public-wifi-locations/explore.

Department: Geographic Information Systems Group; Department of Administrative Services

Data Dictionary

See https://www.census.gov/geo/about/contact.html for more information.

Public view of the parcel layer. This view is limited to only the attributes that can be seen by the general public.The data table includes the following fields: Shape Type (Shape), Shape.STArea() (Shape_Area), Shape.STLength() (Shape_Area), Name (APN), Created By Record (CreatedbyR), Retired By Record (RetiredbyR), Stated Area, Stated Area Unit (StatedAr_1), Calculated Area (Calculated), Misclose Ratio (MiscloseRa), Misclose Distance (MiscloseDi), Is Seed (IsSeed), Created By (created_us), Created Date (created_da), Modified By (last_edite), Modified Date (last_edi_1), Validation Status (VALIDATION), APN Dashed (APN_Dashed), Map Page (Map_Page), Municipality (Municipali), FloorOrder, HideThere are approximately 51,300 real property parcels in Napa County. Parcels delineate the approximate boundaries of property ownership as described in Napa County deeds, filed maps, and other source documents. GIS parcel boundaries are maintained by the Information Technology Services GIS team. Assessor Parcel Maps are created and maintained by the Assessor Division Mapping Section. Each parcel has an Assessor Parcel Number (APN) that is its unique identifier. The APN is the link to various Napa County databases containing information such as owner name, situs address, property value, land use, zoning, flood data, and other related information. Data for this map service is sourced from the Napa County Parcels dataset which is updated nightly with any recent changes made by the mapping team. There may at times be a delay between when a document is recorded and when the new parcel boundary configuration and corresponding information is available in the online GIS parcel viewer.From 1850 to early 1900s assessor staff wrote the name of the property owner and the property value on map pages. They began using larger maps, called “tank maps” because of the large steel cabinet they were kept in, organized by school district (before unification) on which names and values were written. In the 1920s, the assessor kept large books of maps by road district on which names were written. In the 1950s, most county assessors contracted with the State Board of Equalization for board staff to draw standardized 11x17 inch maps following the provisions of Assessor Handbook 215. Maps were originally drawn on linen. By the 1980’s Assessor maps were being drawn on mylar rather than linen. In the early 1990s Napa County transitioned from drawing on mylar to creating maps in AutoCAD. When GIS arrived in Napa County in the mid-1990s, the AutoCAD images were copied over into the GIS parcel layer. Sidwell, an independent consultant, was then contracted by the Assessor’s Office to convert these APN files into the current seamless ArcGIS parcel fabric for the entire County. Beginning with the 2024-2025 assessment roll, the maps are being drawn directly in the parcel fabric layer.Parcels in the GIS parcel fabric are drawn according to the legal description using coordinate geometry (COGO) drawing tools and various reference data such as Public Lands Survey section boundaries and road centerlines. The legal descriptions are not defined by the GIS parcel fabric. Any changes made in the GIS parcel fabric via official records, filed maps, and other source documents are uploaded overnight. There is always at least a 6-month delay between when a document is recorded and when the new parcel configuration and corresponding information is available in the online parcel viewer for search or download.Parcel boundary accuracy can vary significantly, with errors ranging from a few feet to several hundred feet. These distortions are caused by several factors such as: the map projection - the error derived when a spherical coordinate system model is projected into a planar coordinate system using the local projected coordinate system; and the ground to grid conversion - the distortion between ground survey measurements and the virtual grid measurements. The aim of the parcel fabric is to construct a visual interpretation that is adequate for basic geographic understanding. This digital data is intended for illustration and demonstration purposes only and is not considered a legal resource, nor legally authoritative.

This is a collection of 124 global and free datasets allowing for spatial (and temporal) analyses of floods, droughts and their interactions with human societies. We have structured the datasets into seven categories: hydrographic baseline, hydrological dynamics, hydrological extremes, land cover & agriculture, human presence, water management, and vulnerability. Please refer to Lindersson et al. (accepted february 2020 in WIREs Water) for further information about review methodology.

The collection is a descriptive list, holding the following information for each dataset:

• Category - as structured in Lindersson et al. (in preparation).
• Sub-category- as structured in Lindersson et al. (in preparation).
• Abbreviation - official or as specified in Lindersson et al. (in preparation).
• Title - full title of dataset.
• Product(s) - type of product(s) offered by the dataset.
• Period - time period covered by the dataset, not defined for all datasets.
• Temporal resolution - not defined for static datasets.
• Angular spatial resolution - only defined for gridded datasets.
• Metric spatial resolution - only defined for gridded datasets.
• Map scale
• Extent - geographic coverage of dataset given in latitude limits.
• Description
• Creating institute(s)
• Data type - raster, vector or tabular.
• File format
• Primary EO type - specifies if the product primarily is based on remote sensing, ground-based data, or a hybrid between remote sensing and ground-based data.
• Data sources - lists the data sources behind the dataset, to the extent this is feasible.
• Data sources also in this table - data sources that are also included as datasets in this collection.
• Intentionally compatible with - defines other datasets in this collection that the dataset is intentinoally compatible with.
• Citation - dataset reference or credit.
• Documentation - dataset documentation.
• Web address - dataset access link.

NOTE: Carefully consult the data usage licenses as given by the data providers, to assure that the exact permissions and restrictions are followed.

The High Resolution Digital Elevation Model (HRDEM) product is derived from airborne LiDAR data (mainly in the south) and satellite images in the north. The complete coverage of the Canadian territory is gradually being established. It includes a Digital Terrain Model (DTM), a Digital Surface Model (DSM) and other derived data. For DTM datasets, derived data available are slope, aspect, shaded relief, color relief and color shaded relief maps and for DSM datasets, derived data available are shaded relief, color relief and color shaded relief maps. The productive forest line is used to separate the northern and the southern parts of the country. This line is approximate and may change based on requirements. In the southern part of the country (south of the productive forest line), DTM and DSM datasets are generated from airborne LiDAR data. They are offered at a 1 m or 2 m resolution and projected to the UTM NAD83 (CSRS) coordinate system and the corresponding zones. The datasets at a 1 m resolution cover an area of 10 km x 10 km while datasets at a 2 m resolution cover an area of 20 km by 20 km. In the northern part of the country (north of the productive forest line), due to the low density of vegetation and infrastructure, only DSM datasets are generally generated. Most of these datasets have optical digital images as their source data. They are generated at a 2 m resolution using the Polar Stereographic North coordinate system referenced to WGS84 horizontal datum or UTM NAD83 (CSRS) coordinate system. Each dataset covers an area of 50 km by 50 km. For some locations in the north, DSM and DTM datasets can also be generated from airborne LiDAR data. In this case, these products will be generated with the same specifications as those generated from airborne LiDAR in the southern part of the country. The HRDEM product is referenced to the Canadian Geodetic Vertical Datum of 2013 (CGVD2013), which is now the reference standard for heights across Canada. Source data for HRDEM datasets is acquired through multiple projects with different partners. Since data is being acquired by project, there is no integration or edgematching done between projects. The tiles are aligned within each project. The product High Resolution Digital Elevation Model (HRDEM) is part of the CanElevation Series created in support to the National Elevation Data Strategy implemented by NRCan. Collaboration is a key factor to the success of the National Elevation Data Strategy. Refer to the “Supporting Document” section to access the list of the different partners including links to their respective data.

This dynamic World Elevation Terrain service provides numeric values representing ground surface heights, based on a digital terrain model (DTM). The ground heights are based on multiple sources. Heights are orthometric (sea level = 0), and water bodies that are above sea level have approximated nominal water heights.What can you do with this layer?Use for Visualization: This layer is generally not optimal for direct visualization. By default, 32 bit floating point values are returned, resulting in higher bandwidth requirements. Therefore, usage should be limited to applications requiring elevation data values. Alternatively, client applications can select from numerous additional functions, applied on the server, that return rendered data. For visualizations such as multi-directional hillshade, hillshade, elevation tinted hillshade, and slope, consider using the appropriate server-side function defined on this service.Use for Analysis: Yes. This layer provides data as floating point elevation values suitable for use in analysis.Note: This image services combine data from different sources and resample the data dynamically to the requested projection, extent and pixel size. For analyses using ArcGIS Desktop, you can filter a dataset, specify the projection, extent and cell size using the Make Image Server Layer geoprocessing tool.Server Functions: This layer has server functions defined for the following elevation derivatives. In ArcGIS desktop, server function can be invoked from Layer Properties - Processing Templates.

Slope Degrees Slope Percent Aspect Ellipsoidal height Hillshade Multi-Directional Hillshade Dark Multi-Directional Hillshade Elevation Tinted Hillshade Slope Map Aspect Map Data Sources and Coverage: This layer is compiled from a variety of best available sources from several data providers. To see the coverage and extents of various datasets comprising this service in an interactive map, see Elevation Coverage Map.Mosaic Method: This image service uses a default mosaic method of "By Attribute”, using Field 'Best' and target of 0. Each of the rasters has been attributed with ‘Best’ field value that is generally a function of the pixel size such that higher resolution datasets are displayed at higher priority. Other mosaic methods can be set, but care should be taken as the order of the rasters may change. Where required, queries can also be set to display only specific datasets such as only NED or the lock raster mosaic rule used to lock to a specific dataset.Accuracy: The accuracy of these services will vary as a function of location and data source. Please refer to the metadata available in the services, and follow the links to the original sources for further details. An estimate of CE90 and LE90 are included as attributes, where available.This layer allows query, identify, and export image requests. The layer is restricted to a 5,000 x 5,000 pixel limit in a single request.This layer is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.

Medical Emergency Response StructuresThis feature layer, utilizing National Geospatial Data Asset (NGDA) data from the U.S. Geological Survey, displays hospitals, medical centers, ambulance services, fire stations and EMS stations in the U.S. Per the USGS, "Structures data are designed to be used in general mapping and in the analysis of structure related activities using geographic information system technology. The National Map structures data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and transportation, to produce general reference base maps. The types of structures collected are largely determined by the needs of disaster planning and emergency response, and homeland security organizations."Greendale Fire DepartmentData currency: This cached Esri federal service is checked weekly for updates from its enterprise federal source (Medical & Emergency Response) and will support mapping, analysis, data exports and OGC API – Feature access.NGDAID: 135 (USGS National Structures Dataset - USGS National Map Downloadable Data Collection)OGC API Features Link: (Medical Emergency Response Structures - OGC Features) copy this link to embed it in OGC Compliant viewersFor more information, please visit: The National MapFor feedback please contact: Esri_US_Federal_Data@esri.comNGDA Theme CommunityThis data set is part of the NGDA Real Property Theme Community. Per the Federal Geospatial Data Committee (FGDC), Real Property is defined as "the spatial representation (location) of real property entities, typically consisting of one or more of the following: unimproved land, a building, a structure, site improvements and the underlying land. Complex real property entities (that is "facilities") are used for a broad spectrum of functions or missions. This theme focuses on spatial representation of real property assets only and does not seek to describe special purpose functions of real property such as those found in the Cultural Resources, Transportation, or Utilities themes."For other NGDA Content: Esri Federal Datasets

In 2007, the California Ocean Protection Council initiated the California Seafloor Mapping Program (CSMP), designed to create a comprehensive seafloor map of high-resolution bathymetry, marine benthic habitats, and geology within California’s State Waters. The program supports a large number of coastal-zone- and ocean-management issues, including the California Marine Life Protection Act (MLPA) (California Department of Fish and Wildlife, 2008), which requires information about the distribution of ecosystems as part of the design and proposal process for the establishment of Marine Protected Areas. A focus of CSMP is to map California’s State Waters with consistent methods at a consistent scale. The CSMP approach is to create highly detailed seafloor maps through collection, integration, interpretation, and visualization of swath sonar data (the undersea equivalent of satellite remote-sensing data in terrestrial mapping), acoustic backscatter, seafloor video, seafloor photography, high-resolution seismic-reflection profiles, and bottom-sediment sampling data. The map products display seafloor morphology and character, identify potential marine benthic habitats, and illustrate both the surficial seafloor geology and shallow (to about 100 m) subsurface geology. It is emphasized that the more interpretive habitat and geology data rely on the integration of multiple, new high-resolution datasets and that mapping at small scales would not be possible without such data. This approach and CSMP planning is based in part on recommendations of the Marine Mapping Planning Workshop (Kvitek and others, 2006), attended by coastal and marine managers and scientists from around the state. That workshop established geographic priorities for a coastal mapping project and identified the need for coverage of “lands” from the shore strand line (defined as Mean Higher High Water; MHHW) out to the 3-nautical-mile (5.6-km) limit of California’s State Waters. Unfortunately, surveying the zone from MHHW out to 10-m water depth is not consistently possible using ship-based surveying methods, owing to sea state (for example, waves, wind, or currents), kelp coverage, and shallow rock outcrops. Accordingly, some of the data presented in this series commonly do not cover the zone from the shore out to 10-m depth. This data is part of a series of online U.S. Geological Survey (USGS) publications, each of which includes several map sheets, some explanatory text, and a descriptive pamphlet. Each map sheet is published as a PDF file. Geographic information system (GIS) files that contain both ESRI ArcGIS raster grids (for example, bathymetry, seafloor character) and geotiffs (for example, shaded relief) are also included for each publication. For those who do not own the full suite of ESRI GIS and mapping software, the data can be read using ESRI ArcReader, a free viewer that is available at http://www.esri.com/software/arcgis/arcreader/index.html (last accessed September 20, 2013). The California Seafloor Mapping Program is a collaborative venture between numerous different federal and state agencies, academia, and the private sector. CSMP partners include the California Coastal Conservancy, the California Ocean Protection Council, the California Department of Fish and Wildlife, the California Geological Survey, California State University at Monterey Bay’s Seafloor Mapping Lab, Moss Landing Marine Laboratories Center for Habitat Studies, Fugro Pelagos, Pacific Gas and Electric Company, National Oceanic and Atmospheric Administration (NOAA, including National Ocean Service–Office of Coast Surveys, National Marine Sanctuaries, and National Marine Fisheries Service), U.S. Army Corps of Engineers, the Bureau of Ocean Energy Management, the National Park Service, and the U.S. Geological Survey. These web services for the Offshore Fort Ross map area includes data layers that are associated to GIS and map sheets available from the USGS CSMP web page at https://walrus.wr.usgs.gov/mapping/csmp/index.html. Each published CSMP map area includes a data catalog of geographic information system (GIS) files; map sheets that contain explanatory text; and an associated descriptive pamphlet. This web service represents the available data layers for this map area. Data was combined from different sonar surveys to generate a comprehensive high-resolution bathymetry and acoustic-backscatter coverage of the map area. These data reveal a range of physiographic including exposed bedrock outcrops, large fields of sand waves, as well as many human impacts on the seafloor. To validate geological and biological interpretations of the sonar data, the U.S. Geological Survey towed a camera sled over specific offshore locations, collecting both video and photographic imagery; these “ground-truth” surveying data are available from the CSMP Video and Photograph Portal at https://doi.org/10.5066/F7J1015K. The “seafloor character” data layer shows classifications of the seafloor on the basis of depth, slope, rugosity (ruggedness), and backscatter intensity and which is further informed by the ground-truth-survey imagery. The “potential habitats” polygons are delineated on the basis of substrate type, geomorphology, seafloor process, or other attributes that may provide a habitat for a specific species or assemblage of organisms. Representative seismic-reflection profile data from the map area is also include and provides information on the subsurface stratigraphy and structure of the map area. The distribution and thickness of young sediment (deposited over the past about 21,000 years, during the most recent sea-level rise) is interpreted on the basis of the seismic-reflection data. The geologic polygons merge onshore geologic mapping (compiled from existing maps by the California Geological Survey) and new offshore geologic mapping that is based on integration of high-resolution bathymetry and backscatter imagery seafloor-sediment and rock samplesdigital camera and video imagery, and high-resolution seismic-reflection profiles. The information provided by the map sheets, pamphlet, and data catalog has a broad range of applications. High-resolution bathymetry, acoustic backscatter, ground-truth-surveying imagery, and habitat mapping all contribute to habitat characterization and ecosystem-based management by providing essential data for delineation of marine protected areas and ecosystem restoration. Many of the maps provide high-resolution baselines that will be critical for monitoring environmental change associated with climate change, coastal development, or other forcings. High-resolution bathymetry is a critical component for modeling coastal flooding caused by storms and tsunamis, as well as inundation associated with longer term sea-level rise. Seismic-reflection and bathymetric data help characterize earthquake and tsunami sources, critical for natural-hazard assessments of coastal zones. Information on sediment distribution and thickness is essential to the understanding of local and regional sediment transport, as well as the development of regional sediment-management plans. In addition, siting of any new offshore infrastructure (for example, pipelines, cables, or renewable-energy facilities) will depend on high-resolution mapping. Finally, this mapping will both stimulate and enable new scientific research and also raise public awareness of, and education about, coastal environments and issues. Web services were created using an ArcGIS service definition file. The ArcGIS REST service and OGC WMS service include all Offshore Fort Ross map area data layers. Data layers are symbolized as shown on the associated map sheets.

This dynamic World Elevation TopoBathy service combines topography (land elevation) and bathymetry (water depths) around the world. Heights are based on multiple sources and are orthometric (sea level = 0, and bathymetric values are negative downward from sea level). The source data of land elevation in this service is same as in the Terrain layer. When possible, the water areas are represented by the best available bathymetry. What can you do with this layer?Use for Visualization: This layer is generally not optimal for direct visualization. By default, 32 bit floating point values are returned, resulting in higher bandwidth requirements. Therefore, usage should be limited to applications requiring elevation data values. Alternatively, client applications can select additional functions, applied on the server, that return rendered data. For visualizations such as hillshade or elevation tinted hillshade, consider using the appropriate server-side function defined on this service. Use for Analysis: Yes. This layer provides data as floating point elevation values suitable for use in analysis. NOTE: This image services combine data from different sources and resample the data dynamically to the requested projection, extent and pixel size. For analyses using ArcGIS Desktop, you can filter a dataset, specify the projection, extent and cell size using the Make Image Server Layer geoprocessing tool. Server Functions: This layer has server functions defined for the following elevation derivatives. In ArcGIS desktop, server function can be invoked from Layer Properties - Processing Templates.

Slope Degrees Slope Percentage Hillshade Multi-Directional Hillshade Elevation Tinted HillshadeSlope MapData Sources and Coverage: This layer is compiled from a variety of best available sources from several data providers. To see the coverage and extents of various datasets comprising this service in an interactive map, see Elevation Coverage Map.Mosaic Method: This image service uses a default mosaic method of "By Attribute”, using Field 'Best' and target of 0. Each of the rasters has been attributed with ‘Best’ field value that is generally a function of the pixel size such that higher resolution datasets are displayed at higher priority. Other mosaic methods can be set, but care should be taken as the order of the rasters may change. Where required, queries can also be set to display only specific datasets such as only NED or the lock raster mosaic rule used to lock to a specific dataset.Accuracy: The accuracy of these services will vary as a function of location and data source. Please refer to the metadata available in the services, and follow the links to the original sources for further details. An estimate of CE90 and LE90 is included as attributes, where available.This layer allows query, identify, and export image requests. The layer is restricted to a 5,000 x 5,000 pixel limit in a single request. This layer is part of a larger collection of elevation layers that you can use to perform a variety of mapping analysis tasks.Disclaimer: Bathymetry data sources are not to be used for navigation/safety at sea.

Hydric soils are defined as those soils that are sufficiently wet in the upper part to develop anaerobic conditions during the growing season. The Hydric Soils section presents the most current information about hydric soils. The lists of hydric soils were created by using National Soil Information System (NASIS) database selection criteria that were developed by the National Technical Committee for Hydric Soils. These criteria are selected soil properties that are documented in Soil Taxonomy (Soil Survey Staff, 1999) and were designed primarily to generate a list of potentially hydric soils from the National Soil Information System (NASIS) database. It updates information that was previously published in Hydric Soils of the United States and coordinates it with information that has been published in the Federal Register. It also includes the most recent set of field indicators of hydric soils. The database selection criteria are selected soil properties that are documented in Soil Taxonomy and were designed primarily to generate a list of potentially hydric soils from soil survey databases. Only criteria 1, 3, and 4 can be used in the field to determine hydric soils; however, proof of anaerobic conditions must also be obtained for criteria 1, 3, and 4 either through data or best professional judgment (from Tech Note 1). The primary purpose of these selection criteria is to generate a list of soil map unit components that are likely to meet the hydric soil definition. Caution must be used when comparing the list of hydric components to soil survey maps. Many of the soils on the list have ranges in water table depths that allow the soil component to range from hydric to nonhydric depending on the location of the soil within the landscape as described in the map unit. Lists of hydric soils along with soil survey maps are good off-site ancillary tools to assist in wetland determinations, but they are not a substitute for observations made during on-site investigations. The list of field indicators of hydric soils — The field indicators are morphological properties known to be associated with soils that meet the definition of a hydric soil. Presence of one or more field indicators suggests that the processes associated with hydric soil formation have taken place on the site being observed. The field indicators are essential for hydric soil identification because once formed, they persist in the soil during both wet and dry seasonal periods. The Hydric Soil Technical Notes — Contain National Technical Committee for Hydric Soils (NTCHS) updates, insights, standards, and clarifications. Users can query the database by State or by Soil Survey Area. Resources in this dataset:Resource Title: Website Pointer to Hydric Soils . File Name: Web Page, url: https://www.nrcs.usda.gov/wps/portal/nrcs/main/soils/use/hydric/ Includes description of Criteria, Query by State or Soil Survey Area, national Technical Committee for Hydric Soils. Technical Notes, and Related Links. Report Metadata:

• Area_Symbol: A symbol that uniquely identifies a single occurrence of a particular type of area (e.g. Dane Co., Wisconsin is WI025).
• Area_Name: The name given to the specified geographic area.
• mukey: A non-connotative string of characters used to uniquely identify a record in the Mapunit table.
• Mapunit_SYM: The symbol used to uniquely identify the soil mapunit in the soil survey.
• Mapunit_Name: Correlated name of the mapunit (recommended name or field name for surveys in progress).
• Comp_Name_phase: Component name - Name assigned to a component based on its range of properties. Local Phase - Phase criterion to be used at a local level, in conjunction with "component name" to help identify a soil component.
• muacres: The number of acres of a particular mapunit.
• Comp_RV_Pct: The percentage of the component of the mapunit.
• majcompflag: Indicates whether or not a component is a major component in the mapunit.
• Comp_Acres: The number of acres of a particular component in a mapunit. ((muacres*comppct_r)/100)
• Comp_Landform: A word or group of words used to name a feature on the earth's surface, expressed in the plural form. Column Physical
• Hydric_Rating: A yes/no field that indicates whether or not a map unit component is classified as a "hydric soil". If rated as hydric, the specific criteria met are listed in the Component Hydric Criteria table.
• Hydric_criteria: Criterion code for the soil characteristic(s) and/or feature(s) that cause the map unit component to be classified as a "hydric soil." These codes are the paragraph numbers in the hydric soil criteria publication.

Criteria:

1. All Histels except Folistels and Histosols except Folists; or
2. Map unit components in Aquic suborders, great groups, or subgroups, Albolls suborder, Historthels great group, Histoturbels great group, or Andic, Cumulic, Pachic, or Vitrandic subgroups that: a. Based on the range of characteristics for the soil series, will at least in part meet one or more Field Indicators of Hydric Soils in the United States, or b. Show evidence that the soil meets the definition of a hydric soil;
3. Map unit components that are frequently ponded for long duration or very long duration during the growing season that: a. Based on the range of characteristics for the soil series, will at least in part meet one or more Field Indicators of Hydric Soils in the United States, or b. Show evidence that the soil meets the definition of a hydric soil; or
4. Map unit components that are frequently flooded for long duration or very long duration during the growing season that: a. Based on the range of characteristics for the soil series, will at least in part meet one or more Field Indicators of Hydric Soils in the United States, or b. Show evidence that the soils meet the definition of a hydric soil.

Access APINSW Features of Interest Category - Place Point Please Note WGS 84 = GDA94 service This dataset has a spatial reference of [WGS 84 = GDA94] and can NOT be easily consumed into GDA2020 …Show full description Access APINSW Features of Interest Category - Place Point Please Note WGS 84 = GDA94 service This dataset has a spatial reference of [WGS 84 = GDA94] and can NOT be easily consumed into GDA2020 environments. A similar service with a ‘multiCRS’ suffix is available which can support GDA2020, GDA94 and WGS84 = GDA2020 environments. In due course, and allowing time for user feedback and testing, it is intended that these original services will adopt the new multiCRS functionally. Place point is a point feature class within the Features of interest Category. There is no overall accuracy reported in the database, however accuracy of the individual feature instances of each feature class can be found in the database tables. The currency of the feature instances in this dataset can be found in “feature reliability date” or “attribute reliability date” attributes. All feature instances in this class are attributed with a planimetric accuracy value. It is expected that the 90% of well-defined points with the same planimetric accuracy are within 0.5mm of that map scale. Depending on the capture source, capture method, digital update and control point upgrade, every feature instance reported has a positional accuracy within the range of 1m - 100m. Place Points included in the layer include: City - A centre of population, commerce and culture with all essential services; a town of significant size and importance, generally accorded the legal right to call itself a city under, either, the Local Government Act, the Crown Lands Act or other instruments. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. City data points are positioned within the cadastral parcel in which they are located. Locality - A bounded area within the landscape that has a rural character. Locality data points are positioned within the cadastral parcel in which they are located. Region - A region is a relatively large tract of land distinguished by certain common characteristics, natural or cultural. Natural unifying features could include same drainage basin, similar landforms, or climatic conditions, a special flora or fauna, or the like. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Region data points are positioned within the cadastral parcel in which they are located.Rural Place - A place, site or precinct in a rural landscape, generally of small extent, the name of which is in current use. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Rural place data points are positioned within the cadastral parcel in which they are located. Suburb - A gazetted boundary of a suburb or locality area as defined by the Geographical Names Board of NSW. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Suburb data points are positioned within the cadastral parcel in which they are located. Town - A commercial nucleus offering a wide range of services and a large number of shops, often several of the same type. Depending on size, the residential area can be relatively compact or (in addition) dispersed in clusters on the periphery. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Town data points are positioned within the cadastral parcel in which they are located. Urban Place - A place, site or precinct in an urban landscape, the name of which is in current use, but the limits of which have not been defined under the address locality program. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Urban place data points are positioned within the cadastral parcel in which they are located. Village - A cohesive populated place in a rural landscape, which may provide a limited range of services to the local area. Residential subdivisions are in urban lot sizes. This point feature dataset is part of Spatial Services Defined Administrative Data Sets. Village data points are positioned within the cadastral parcel in which they are located. MetadataType Esri Feature Service Update Frequency As required Contact Details Contact us via the Spatial Services Customer Hub Relationship to Themes and Datasets Features of Interest Category of the Foundation Spatial Data Framework (FSDF) Accuracy The dataset maintains a positional relationship to, and alignment with, a range of themes from the NSW FSDF including, transport, imagery, positioning, water and land cover. This dataset was captured by digitising the best available cadastral mapping at a variety of scales and accuracies, ranging from 1:500 to 1:250 000 according to the National Mapping Council of Australia, Standards of Map Accuracy (1975). Therefore, the position of the feature instance will be within 0.5mm at map scale for 90% of the well-defined points. That is, 1:500 = 0.25m, 1:2000 = 1m, 1:4000 = 2m, 1:25000 = 12.5m, 1:50000 = 25m and 1:100000 = 50m. A program of positional upgrade (accuracy improvement) is currently underway. Spatial Reference System (dataset) Geocentric Datum of Australia 1994 (GDA94), Australian Height Datum (AHD) Spatial Reference System    (web service) EPSG 4326: WGS84 Geographic 2D WGS84 Equivalent To GDA94 Spatial Extent Full state Standards and Specifications Open Geospatial Consortium (OGC) implemented and compatible for consumption by common GIS platforms. Available as either cache or non-cache, depending on client use or requirement. Distributors Service Delivery, DCS Spatial Services 346 Panorama Ave Bathurst NSW 2795Dataset Producers and Contributors Administrative Spatial Programs, DCS Spatial Services 346 Panorama Ave Bathurst NSW 2795

Land use data is critically important to the work of the Department of Water Resources (DWR) and other California agencies. Understanding the impacts of land use, crop location, acreage, and management practices on environmental attributes and resource management is an integral step in the ability of Groundwater Sustainability Agencies (GSAs) to produce Groundwater Sustainability Plans (GSPs) and implement projects to attain sustainability. Land IQ was contracted by DWR to develop a comprehensive and accurate spatial land use database for the Water Year 2018, covering over 9.4 million acres of Irrigable agriculture on a field scale and additional areas of urban extent. The primary objective of this effort was to produce a spatial land use database with accuracies exceeding 95% using remote sensing, statistical, and temporal analysis methods. This project is an extension of the 2014 and 2016 land use mapping, which classified over 14 million acres of land into Irrigable agriculture and urban area. Unlike the 2014 and 2016 datasets, the Water Year 2018 dataset includes multi-cropping and incorporates ground-truth data from Siskiyou, Modoc, Lassen and Shasta counties. Land IQ integrated crop production knowledge with detailed ground truth information and multiple satellite and aerial image resources to conduct remote sensing land use analysis at the field scale. Individual fields (boundaries of homogeneous crop types representing true Irrigable area, rather than legal parcel boundaries) were classified using a crop category legend and a more specific crop type legend. A supervised classification algorithm using a random forest approach was used to classify delineated fields and was carried out county by county where training samples were available. Random forest approaches are currently some of the highest performing methods for data classification and regression. To determine frequency and seasonality of multiple-cropped fields, peak growth dates were determined for annual crops. Fields were attributed with DWR crop categories and included citrus/subtropical, deciduous fruits and nuts, field crops, grain and hay, idle, pasture, rice, truck crops, urban, vineyards, young perennials and wetland. These categories represent aggregated groups of specific crop types in the Land IQ dataset. Accuracy was calculated for the crop mapping using both DWR and Land IQ crop legends. The overall accuracy result for the crop mapping statewide was 96.5% using the Land IQ legend and 98.3% using the DWR legend. Accuracy and error results varied among crop types. In particular, some less extensive crops that have very few validation samples may have a skewed accuracy result depending on the number and nature of validation sample points. Revised crops and conditions were encoded using standard DWR land use codes added to feature attributes, and each modified classification is indicated by the value 'r' in the 'DWR_revised' data field. The value ‘n’ in the ‘DWR_REVISE’ data field indicates a Regional Office added a boundary and attributes where none was included in the Land IQ data set. Each polygon classification is consistent with DWR attribute standards, however some of DWR's traditional attribute definitions are modified and extended to accommodate unavoidable constraints within remote-sensing classifications, or to make data more specific for DWR's water balance computation needs. The original Land IQ classifications reported for each polygon are preserved for comparison, and are also expressed as DWR standard attributes. Comments, problems, improvements, updates, or suggestions about local conditions or revisions in the final data set should be forwarded to the appropriate Regional Office Senior Land Use Supervisor. Revisions were made if: - DWR corrected the original crop classification based on local knowledge and analysis, - young versus mature stages of perennial orchards and vineyards were identified (DWR added ‘Young’ to Special Condition attributes), - DWR determined that a field originally classified ‘Idle’ was actually cropped one or more times during the year, - the percent of cropped area was less than 100% of the original acres reported by Land IQ (values indicated in DWR ‘Percent’ column), - DWR determined that the field boundary should have been split to better reflect separate crops within the same polygon (‘Mixed’ was added to the MULTIUSE column; the crop classification and corresponding area percentages were indicated), - DWR determined that the crop was not irrigated. - DWR identified a distinct early or late crop on the field before the main season crop (‘Double’ was added to the MULTIUSE column); if the 1st and 2nd sequential crops occupied different portions of the total field acreage, the area percentages were indicated for each crop). DWR added Adjusted Day Of Year (ADOY) for peak NDVI date corresponding to CROPTYP category. The date received by Land IQ was delivered in a Julian date format (YYYYDDD) and was converted into the ADOY by DWR for statistical purposes. Land use boundaries delineated by Land IQ were not revised by DWR.

This dataset represents above- and below-ground terrestrial carbon storage (tonnes (t) of C per hectare (ha)) for circa 2010. This layer supports analysis but, if needed, a direct download of the data can be accessed here.

The dataset was constructed by combining the most reliable publicly available datasets and overlying them with the ESA CCI landcover map for the year 2010 [ESA, 2017], assigning to each grid cell the corresponding above-ground biomass value from the biomass map that was most appropriate for the grid cell’s landcover type.

Input carbon datasets were identified through a literature review of existing datasets on biomass carbon in terrestrial ecosystems published in peer-reviewed literature. To determine which datasets to combine to produce the global carbon density map, identified datasets were evaluated based on resolution, accuracy, biomass definition and reference date (see table 1 for further information on datasets selected).

Dataset

Scope

Year

Resolution

Definition

Santoro et al. 2018

Global

2010

100 m

Above-ground woody biomass for trees that are >10 cm diameter-at-breast-height, masked to Landsat-derived canopy cover for 2010; biomass is expressed as oven-dry weight of the woody parts (stem, bark, branches and twigs) of all living trees excluding stump and roots.

Xia et al. 2014

Global

1982-2006

8 km

Above-ground grassland biomass.

Bouvet et al. 2018

Africa

2010

25 m

Above-ground woodland and savannah biomass; low woody biomass areas, which therefore exclude dense forests and deserts.

Spawn et al. 2017

Global

2010

300 m

Synthetic, global above- and below-ground biomass maps that combine recently released satellite-based data of standing forest biomass with novel estimates for non-forest biomass stocks.

After aggregating each selected dataset to a nominal scale of 300 m resolution, forest categories in the CCI ESA 2010 landcover dataset were used to extract above-ground biomass from Santoro et al. 2018 for forest areas. Woodland and savanna biomass were then incorporated for Africa from Bouvet et al. 2018., and from Santoro et al. 2018 for areas outside of Africa and outside of forest. Biomass from croplands, sparse vegetation and grassland landcover classes from CCI ESA, in addition to shrubland areas outside Africa missing from Santoro et al. 2018, were extracted from were extracted from Xia et al. 2014. and Spawn et al. 2017 averaged by ecological zone for each landcover type.

Below-ground biomass were added using root-to-shoot ratios from the 2006 IPCC guidelines for National Greenhouse Gas Inventories (IPCC, 2006). No below-ground values were assigned to croplands as ratios were unavailable. Above- and below-ground biomass were then summed together and multiplied by 0.5 to convert to carbon, generating a single above-and-below-ground biomass carbon layer.