This data is utilized in the Lesson 1.1 What is Climate activity on the MI EnviroLearning Hub Climate Change page.Station data accessed was accessed from NOAA. Data was imported into ArcGIS Pro where Coordinate Table to Point was used to spatially enable the originating CSV. This feature service, which incorporates Census Designated Places from the U.S. Census Bureau’s 2020 Census Demographic and Housing Characteristics, was used to spatially join weather stations to the nearest incorporated area throughout Michigan.Email Egle-Maps@Michigan.gov for questions.Former name: MichiganStationswAvgs19912020_WithinIncoproatedArea_UpdatedName Display Name Field Name Description

STATION_ID MichiganStationswAvgs19912020_W Station ID where weather data is collected

STATION MichiganStationswAvgs19912020_1 Station name where weather data is collected

ELEVATION MichiganStationswAvgs19912020_6 Elevation above mean sea level-meters

MLY-PRCP-NORMAL MichiganStationswAvgs19912020_8 Long-term averages of monthly precipitation total-inches

MLY-TAVG-NORMAL MichiganStationswAvgs19912020_9 Long-term averages of monthly average temperature -F

OID MichiganStationswAvgs1991202_10 Object ID for weather dataset

Join_Count MichiganStationswAvgs1991202_11 Spatial join count of weather station data to specific weather station

TARGET_FID MichiganStationswAvgs1991202_12 Spatial Join ID

Current place ANSI code MichiganStationswAvgs1991202_13 Census codes for identification of geographic entities (used for join)

Geographic Identifier MichiganStationswAvgs1991202_14 Geographic identifier (used for join)

Current class code MichiganStationswAvgs1991202_15 Class (CLASSFP) code defines the current class of a geographic entity

Current functional status MichiganStationswAvgs1991202_16 Status of weather station

Area of Land (Square Meters) MichiganStationswAvgs1991202_17 Area of land in square meters

Area of Water (Square Meters) MichiganStationswAvgs1991202_18 Area of water in square meters

Current latitude of the internal point MichiganStationswAvgs1991202_19 Latitude

Current longitude of the internal point MichiganStationswAvgs1991202_20 Longitude

Name MichiganStationswAvgs1991202_21 Location name of weather station

Current consolidated city GNIS code MichiganStationswAvgs1991202_22 Geographic Names Information System for an incorporated area

OBJECTID MichiganStationswAvgs1991202_23 Object ID for point dataset

Author: Titus, Maxwell (mtitus@esri.com)Last Updated: 3/4/2025Intended Environment: ArcGIS ProPurpose: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro and a spatial join of two live datasets.Description: This Notebook was designed to automate updates for Hosted Feature Services hosted in ArcGIS Online (or ArcGIS Portal) from ArcGIS Pro. An associated ArcGIS Dashboard would then reflect these updates. Specifically, this Notebook would:First, pull two datasets - National Weather Updates and Public Schools - from the Living Atlas and add them to an ArcGIS Pro map.Then, the Notebook would perform a spatial join on two layers to give Public Schools features information on whether they fell within an ongoing weather event or alert. Next, the Notebook would truncate the Hosted Feature Service in ArcGIS Online - that is, delete all the data - and then append the new data to the Hosted Feature ServiceAssociated Resources: This Notebook was used as part of the demo for FedGIS 2025. Below are the associated resources:Living Atlas Layer: NWS National Weather Events and AlertsLiving Atlas Layer: U.S. Public SchoolsArcGIS Demo Dashboard: Demo Impacted Schools Weather DashboardUpdatable Hosted Feature Service: HIFLD Public Schools with Event DataNotebook Requirements: This Notebook has the following requirements:This notebook requires ArcPy and is meant for use in ArcGIS Pro. However, it could be adjusted to work with Notebooks in ArcGIS Online or ArcGIS Portal with the advanced runtime.If running from ArcGIS Pro, connect ArcGIS Pro to the ArcGIS Online or ArcGIS Portal environment.Lastly, the user should have editable access to the hosted feature service to update.

This dataset is one of several segments of a regional high detailed stream flowpath dataset. The data was separated using the TOPO 50 map series extents.The stream network was originally created for the purpose of high detailed work along rivers and streams in the Wellington region. It was started as a pilot study for the Mangatarere subcatchment of the Waiohine River for the Environmental Sciences department who was attempting to measure riparian vegetation. The data was sourced from a modelled stream network created using the 2013 LiDAR digital elevation model. Once the Mangatarere was complete the process was expanded to cover the entire region on an as needed basis for each whaitua. This dataset is one of several that shows the finished stream datasets for the Wairarapa region.The base stream network was created using a mixture of tools found in ArcGIS Spatial Analyst under Hydrology along with processes located in the Arc Hydro downloadable add-on for ArcGIS. The initial workflow for the data was based on the information derived from the help files provided at the Esri ArcGIS 10.1 online help files. The updated process uses the core Spatial Analyst tools to generate the streamlines while digital dams are corrected using the DEM Reconditioning tool provided by the Arc Hydro toolset. The whaitua were too large for processing separated into smaller units according to the subcatchments within it. In select cases like the Taueru subcatchment of the Ruamahanga these subcatchments need to be further defined to allow processing. The catchment boundaries available are not as precise as the LiDAR information which causes overland flows that are on edges of the catchments to become disjointed from each other and required manual correction.Attributes were added to the stream network using the River Environment Classification (REC) stream network from NIWA. The Spatial Join tool in Arcmap was used to add the Reach ID to each segment of the generated flow path. This ID was used to join a table which had been created by intersecting stream names (generated from a point feature class available from LINZ) with the REC subcatchment dataset. Both of the REC datasets are available from NIWA's website.

For every address in the City of Kitchener, a GIS spatial join has been created to select the closest Park, Playground, Elementary School, etc

Snapshot img

GIS Market Size 2025-2029

The GIS market size is forecast to increase by USD 24.07 billion, at a CAGR of 20.3% between 2024 and 2029.

The Global Geographic Information System (GIS) market is experiencing significant growth, driven by the increasing integration of Building Information Modeling (BIM) and GIS technologies. This convergence enables more effective spatial analysis and decision-making in various industries, particularly in soil and water management. However, the market faces challenges, including the lack of comprehensive planning and preparation leading to implementation failures of GIS solutions. Companies must address these challenges by investing in thorough project planning and collaboration between GIS and BIM teams to ensure successful implementation and maximize the potential benefits of these advanced technologies.
By focusing on strategic planning and effective implementation, organizations can capitalize on the opportunities presented by the growing adoption of GIS and BIM technologies, ultimately driving operational efficiency and innovation.

What will be the Size of the GIS Market during the forecast period?

Explore in-depth regional segment analysis with market size data - historical 2019-2023 and forecasts 2025-2029 - in the full report.
Request Free Sample

The global Geographic Information Systems (GIS) market continues to evolve, driven by the increasing demand for advanced spatial data analysis and management solutions. GIS technology is finding applications across various sectors, including natural resource management, urban planning, and infrastructure management. The integration of Bing Maps, terrain analysis, vector data, Lidar data, and Geographic Information Systems enables precise spatial data analysis and modeling. Hydrological modeling, spatial statistics, spatial indexing, and route optimization are essential components of GIS, providing valuable insights for sectors such as public safety, transportation planning, and precision agriculture. Location-based services and data visualization further enhance the utility of GIS, enabling real-time mapping and spatial analysis.

The ongoing development of OGC standards, spatial data infrastructure, and mapping APIs continues to expand the capabilities of GIS, making it an indispensable tool for managing and analyzing geospatial data. The continuous unfolding of market activities and evolving patterns in the market reflect the dynamic nature of this technology and its applications.

How is this GIS Industry segmented?

The GIS industry research report provides comprehensive data (region-wise segment analysis), with forecasts and estimates in 'USD million' for the period 2025-2029, as well as historical data from 2019-2023 for the following segments.

Product

  Software
  Data
  Services


Type

  Telematics and navigation
  Mapping
  Surveying
  Location-based services


Device

  Desktop
  Mobile


Geography

  North America

    US
    Canada


  Europe

    France
    Germany
    UK


  Middle East and Africa

    UAE


  APAC

    China
    Japan
    South Korea


  South America

    Brazil


  Rest of World (ROW)

By Product Insights

The software segment is estimated to witness significant growth during the forecast period.

The Global Geographic Information System (GIS) market encompasses a range of applications and technologies, including raster data, urban planning, geospatial data, geocoding APIs, GIS services, routing APIs, aerial photography, satellite imagery, GIS software, geospatial analytics, public safety, field data collection, transportation planning, precision agriculture, OGC standards, location intelligence, remote sensing, asset management, network analysis, spatial analysis, infrastructure management, spatial data standards, disaster management, environmental monitoring, spatial modeling, coordinate systems, spatial overlay, real-time mapping, mapping APIs, spatial join, mapping applications, smart cities, spatial data infrastructure, map projections, spatial databases, natural resource management, Bing Maps, terrain analysis, vector data, Lidar data, and geographic information systems.

The software segment includes desktop, mobile, cloud, and server solutions. Open-source GIS software, with its industry-specific offerings, poses a challenge to the market, while the adoption of cloud-based GIS software represents an emerging trend. However, the lack of standardization and interoperability issues hinder the widespread adoption of cloud-based solutions. Applications in sectors like public safety, transportation planning, and precision agriculture are driving market growth. Additionally, advancements in technologies like remote sensing, spatial modeling, and real-time mapping are expanding the market's scope.

Request Free Sample

The Software segment was valued at USD 5.06 billion in 2019 and sho

Land Joins GIS Layer is a spatial dataset that maps out how individual land parcels are connected—either by shared borders (adjacency) or by spatial relationships (e.g., overlapping, touching, or within a buffer). This layer is important for managing land ownership, supporting land development and planning infrastructure

Data processed on 24/04/2020 for assignment 4 of the Coursera ArcGis fundamentals. Spatial join used to join the voting data on a counties level. Adjusted the scale, implemented different map items and made the map ready to be exported.

Several previously published reports and geographic information system (GIS) data layers were used to code information on site attributes for each assessment plot using the spatial join tool in ArcMap. This information was used for an analysis of dieback and non-dieback habitat characteristics. The results of this analysis are presented in this table which depicts the probability of heavy to severe canopy dieback occurring at some time at a particular 30 x 30 m pixel location within the study area.

Data Source: The primary data source used for this analysis are point-level business establishment data from InfoUSA. This commercial database produced by InfoGroup provides a comprehensive list of businesses in the SCAG region, including their industrial classification, number of employees, and several additional fields. Data have been post-processed for accuracy by SCAG staff and have an effective date of 2016. Locally-weighted regression: First, the SCAG region is overlaid with a grid, or fishnet, of 1km, 2km, and ½-km per cell. At the 1km cell size, there are 16,959 cells covering the SCAG region. Using the Spatial Join feature in ArcGIS, a sum total of business establishments and total employees (i.e., not separated by industrial classification) were joined to each grid cell. Note that since cells are of a standard size, the employment total in a cell is the equivalent of the employment density. A locally-weighted regression (LWR) procedure was developed using the R Statistical Software package in order to identify subcenters.The below procedure is described for 1km grid cells, but was repeated for 2km and 1/2km cells. Identify local maxima candidates.Using R’s lwr package, each cell’s 120 nearest neighbors, corresponding to roughly 5.5 km in each direction, was explored to identify high outliers or local maxima based on the total employment field. Cells with a z-score of above 2.58 were considered local maxima candidates.Identify local maxima. LWR can result in local maxima existing within close proximity. This step used a .dbf-format spatial weights matrix (knn=120 nearest neighbors) to identify only cells which are higher than all of their 120 nearest neighbors. At the 1km scale, 84 local maxima were found, which will form the “peak” of each individual subcenter. Search adjacent cells to include as part of each subcenter. In order to find which cells also are part of each local maximum’s subcenter, we use a queen (adjacency) contiguity matrix to search adjacent cells up to 120 nearest neighbors, adding cells if they are also greater than the average density in their neighborhood. A total of 695 cells comprise subcenters at the 1km scale. A video from Kane et al. (2018) demonstrates the above aspects of the methodology (please refer to 0:35 through 2:35 of https://youtu.be/ylTWnvCCO54), with several minor differences which result in a different final map of subcenters: different years and slightly different post-processing steps for InfoUSAdata, video study covers 5-county region (Imperial county not included), and limited to 1km scale subcenters.A challenge arises in that using 1km grid cells may fail to identify the correct local maximum for a particularly large employment center whose experience of high density occurs over a larger area. The process was repeated at a 2km scale, resulting in 54 “coarse scaled” subcenters. Similarly, some centers may exist with a particularly tightly-packed area of dense employment which is not detectable at the medium, 1km scale. The process was repeated again with ½-km grid cells, resulting in 95 “fine scaled” subcenters. In many instances, boundaries of fine, medium, and coarse scaled subcenters were similar, but differences existed. The next step was to qualitatively comparing results at each scale to create the final map of 72 job centers across the region. Most centers are medium scale, but some known areas of especially employment density were better captured at the 2km scale while . Giuliano and Small’s (1991) “ten jobs per acre” threshold was used as a rough guide to test for reasonableness when choosing a larger or smaller scale. For example, in some instances, a 1km scale included much additional land which reduced job density well below 10 jobs per acre. In this instance, an overlapping or nearby 1/2km scaled center provided a better reflection of the local employment peak. Ultimately, the goal was to identify areas where job density is distinct from nearby areas. Finally, in order to serve land use and travel demand modeling purposes for Connect SoCal, job centers were joined to their nearest TAZ boundaries. While the identification mechanism described above uses a combination of point and grid cell boundaries, the job centers boundaries expressed in this layer, and used for Connect SoCal purposes, are built from TAZ geographies. In Connect SoCal, job centers are associated with one of three strategies: focused growth, coworking space, or parking/AVR.Data Field/Value description:name: Name of job center based on name of local jurisdiction(s) or other discernable feature.Focused_Gr: Indicates whether job center was used for the 2020 RTP/SCS Focused Growth strategy, 1: center was used, 0: center was not used.Cowork: Indicates whether job center was used for the 2020 RTP/SCS Co-working space strategy, 1: center was used, 0: center was not used.Park_AVR: Indicates whether job center was used for the 2020 RTP/SCS parking and average vehicle ridership (AVR) strategies, 1: center was used, 0: center was not used. nTAZ: number of Transportation Analysis Zones (TAZs) which comprise this center.emp16: Estimated number of workers within job center boundaries based on 2016 InfoUSA point-based business establishment data. Values are rounded to the nearest 1000. acres: Land area within job center boundaries based on grid-based identification mechanism (i.e., not based on TAZ boundaries shown). Values are rounded to the nearest 100.

Number of incidents counted within census tracts based on different spatial join approaches.

This feature class was derived from the GIS polygon dataset BLM Grazing Allotments which was downloaded from the Geospatial Gateway in April 2025. Fields were added to the feature classes and calculated as needed to allow the Rangeland Administration System (RAS) tabular data to be joined to the GIS datasets. RAS tabular data for Authorized allotments and pastures (as of April 2025) was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025 and processed as dbfs, with fields added and calculated as needed to match the BLM GIS Grazing Allotments feature class. RAS tables and BLM GIS data for allotments were joined using the State Allotment Number, a concatenation of allotment number and BLM Administrative State for allotments (ST_ALLOT_NUM). RAS records for Authorized Allotments that did not match during a join operation were tracked in a separate excel sheet from the matching records. Matching records were then joined back to the BLM GIS Allotments grazing feature class and Allotment name fields were edited as necessary. A Status field was added to indicate if the data are either Billed or Authorized and a Source field was added to indicate that the data came from Allotments or Trailing Allotments. An additional field, TR_ALLOT_NUM, was added to designate any Trailing Allotments in the data. Trailing allotments were identified and processed separately for Nevada, since these allotments overlap portions of other allotments. Any overlaps in the data were removed via dissolve and Spatial Join.Input BLM GIS Grazing data:BLM Grazing Pastures and BLM Grazing Allotments are areas of land designated and managed for grazing of livestock. It may include private, state, and public lands under the jurisdiction of the Bureau of Land Management and/or other federal agencies. An allotment is derived from its pastures, where the grazing of livestock is occurring. The attributes of the BLM Grazing Allotment features may be duplicated in RAS, but are considered to be minimum information for unique identification and cartographic purposes.Input RAS Data:The Rangeland Administration System (RAS) provides grazing administrative support and management reports for the BLM and the public. The Rangeland Administration system serves as an electronic calendar for issuance of applications and grazing authorizations, including Permits, Leases, and Exchange-of-Use Agreements. The Authorized data is current as of April 2025 and was provided by BLM Rangeland Management Specialist Josh Robbins in April 2025.

This is a collaboration between City of Los Angeles Mayor's Office, StreetsLA, and USC. To consolidate / aggregate many datasets for Street Sweeping. Task 2: to perform spatial join between Centerlines and Tracts in order to get the Median HHI from 2018 Demographics.

The 1885 UK parliamentary constituencies for Ireland were re-created in 2017 as part of a conference paper delivered at the Southern Irish Loyalism in Context conference at Maynooth University. The intial map only included the territory of the Irish Free State and was created by Martin Charlton and Jack Kavanagh. The remaining six counties of Ulster were completed by Eoin McLaughlin in 2018-19, the combined result is a GIS map of all the parliamentary constituecies across the island of Ireland for the period 1885-1918. The map is available in both ESRI Shapefile format and as a GeoPackage (GPKG). The methodology for creating the constituencies is outlined in detail below.

Methodology

A map showing the outlines of the 1855 – 1918 Constituency boundaries can be found on page 401 of Parliamentary Elections in Ireland, 1801-1922 (Dublin, 1978) by Brian Walker. This forms the basis for the creation of a set of digital boundaries which can then be used in a GIS. The general workflow involves allocating an 1885 Constituency identifier to each of the 309 Electoral Divisions present in the boundaries made available for the 2011 Census of Population data release by CSO. The ED boundaries are available in ‘shapefile’ format (a de facto standard for spatial data transfer). Once a Constituency identifier has been given to each ED, the GIS operation known as ‘dissolve’ is used to remove the boundaries between EDs in the same Constituency. To begin with Walker’s map was scanned at 1200 dots per inch in JPEG form. A scanned map cannot be linked to other spatial data without undergoing a process known as georeferencing. The CSO boundaries are available with spatial coordinates in the Irish National Grid system. The goal of georeferencing is to produce a rectified version of the map together with a world file. Rectification refers to the process of recomputing the pixel positions in the scanned map so that they are oriented with the ING coordinate system; the world file contains the extent in both the east-west and north-south directions of each pixel (in metres) and the coordinates of the most north-westerly pixel in the rectified image.

Georeferencing involves the identification of Ground Control Points – these are locations on the scanned map for which the spatial coordinates in ING are known. The Georeferencing option in ArcGIS 10.4 makes this a reasonably pain free task. For this map 36 GCPs were required for a local spline transformation. The Redistribution of Seats Act 1885 provides the legal basis for the constituencies to be used for future elections in England, Wales, Scotland and Ireland. Part III of the Seventh Schedule of the Act defines the Constituencies in terms of Baronies, Parishes (and part Parishes) and Townlands for Ireland. Part III of the Sixth Schedule provides definitions for the Boroughs of Belfast and Dublin.

The CSO boundary collection also includes a shapefile of Barony boundaries. This makes it possible code a barony in two ways: (i) allocated completely to a Division or (ii) split between two Divisions. For the first type, the code is just the division name, and for the second the code includes both (or more) division names. Allocation of these names to the data in the ED shapefile is accomplished by a spatial join operation. Recoding the areas in the split Baronies is done interactively using the GIS software’s editing option. EDs or groups of EDs can be selected on the screen, and the correct Division code updated in the attribute table. There are a handful of cases where an ED is split between divisions, so a simple ‘majority’ rule was used for the allocation. As the maps are to be used at mainly for displaying data at the national level, a misallocation is unlikely to be noticed. The final set of boundaries was created using the dissolve operation mentioned earlier. There were a dozen ED that had initially escaped being allocated a code, but these were quickly updated. Similarly, a few of the EDs in the split divisions had been overlooked; again updating was painless. This meant that the dissolve had to be run a few more times before all the errors have been corrected.

For the Northern Ireland districts, a slightly different methodology was deployed which involved linking parishes and townlands along side baronies, using open data sources from the OSM Townlands.ie project and OpenData NI.

Title of reference article:Nine Days of Naptown Arrests: How and Why Spatial Data Should Discomfort UsAuthor J. Kevin ByrneDate authored: August 23, 2020Abstract: During nine successive days in 2019 Indianapolis (IN) police made arrests across six districts. Exploratory spatial data analysis (ESDA) revealed how variables of arrests, race, aggressive use of force (UOF), injuries, and their location interact with each other. Scatterplots with R-squared values > 0.6 suggested aggressive UOF contributed to injuries of arrested residents across all races, Caucasian officers may have excessively injured arrested residents, and aggressive UOF correlated with arrests of African-Americans. Findings for parallel-coordinate-plots dove deeper in terms of spatial implications and ethical considerations (e.g., by visually demonstrating presence of a cluster of observed residents’ arrests as coinciding with African-American census geodemographics). This “small-sample” can surprise the reader. My conclusion proposed two aims: 1) solidify hypotheses (for further ESDA) that may induce ethical discomfort (a good thing) pertaining to the subject of structural racism, and 2) use findings to usher civic policymakers down more strident paths to sociocultural change.Indianapolis (IN) police districts and zones shapefiles that were made public by ESRI were used by way of my ESDA. Path to shapefiles’ source:http://data.indy.gov/datasets/indianapolis-police-zonesN.B.: Safari web-browser not recommended. Shapefile metadata are here: https://www.arcgis.com/home/item.html?id=b59421675f2a40fda9b00beeb875996fUsing GeoDa I did a spatial join that permitted my ESDA to analyze variables with scatterplots, PCPs, and datamaps. My final GeoDa file – titled NapWorksProj.gda – is herewith.Also herewith are my GeoDa's shapefiles – created natively – titled as follows:· NapWorks.cpg· NapWorks.dbf· NapWorks.prj· NapWorks.shp· NapWorks.shx

AT_2003_BACI_1 File Geodatabase Feature Class Thumbnail Not Available Tags There are no tags for this item. Summary There is no summary for this item. Description MD Property View 2003 A&T Database. For more information on the A&T Database refer to the enclosed documentation. This layer was edited to remove spatial outliers in the A&T Database. Spatial outliers are those points that were not geocoded and as a result fell outside of the Baltimore City Boundary; 416 spatial outliers were removed from this layer. The field BLOCKLOT2 can be used to join this layer with the Baltimore City parcel layer. Credits There are no credits for this item. Use limitations There are no access and use limitations for this item. Extent West -76.713418 East -76.526031 North 39.374429 South 39.197452

This is a downloadable zip file of the shapefiles for the named map service "Class I and Class II Wells in Kentucky." It consists of 3,000 wells compiled from EPA's database as documented from Freedom of Information Act (FOIA) requests.These data were linked to a Kentucky oil-&-gas well location shapefile by spatial join to EPA-supplied locations using a buffered search method. Over 2000 Class II locations were matched to well locations in the KGS O&G well database. If successful match were not made by proximity, then EPA well information and location were provided as is.Updated July 2, 2019.

This data set was produced to show the number of titles (land parcels) for each township as a way to express a density per township that would mirror settlement. The data used is available through AltaLIS and involved merging both the rural and urban title data set, converting the polygons to points then using the spatial join in ArcGIS 10.2.2 to count the number of points for each township.

Connecticut Erosion Susceptibility a 1:24,000-scale, polygon feature-based layer that was developed as a predictive tool to show areas most susceptible to terrace escarpment type erosion. The layer compiled from the soils and quaternary geology data layers and was field tested during October-December, 2005. The Erosion Susceptilibity layer was developed as part of Project #03-02 Statewide GIS Analysis and Mapping of the Geologic Conditions Contributing to Eroding Terrace Escarpments. The layer does not represent eroding conditions at any one particular point in time, but rather base or general conditions which can be accounted for during planning or management strategies. The layer includes 4 types of areas susceptible to erosion, ranked 1 (most susceptible) through 4, and their descriptive attribute. Areas outside of the mapped polygons can be considered less susceptible to erosion. Data is compiled at 1:24,000 scale. This data is not updated. Connecticut Erosion Sites is a site specific, point feature-based layer developed at 1:24,000-scale that includes decriptive information regarding the character of the erosion (severity, slope, geologic factors) at selected locations through out the state. The layer is based on information collected and compiled during October-December, 2005 while field testing the applicability of the Erosion Susceptilibity layer developed as part of Project #03-02 Statewide GIS Analysis and Mapping of the Geologic Conditions Contributing to Eroding Terrace Escarpments. The layer represents conditions at a particular point in time. The layer includes 83 locations and descriptive attributes (site name, severity of erosion, description, etc) as well as attributes from a spatial join with merged soils and quaternary geology layers. Features are point locations that represent the selected study areas within the state; it is NOT a comprehensive inventory of erosion locations. Data is compiled at 1:24,000 scale. This data is not updated.

This service contains data on both spwaning and nursery grounds. These can be described as follows:

Fish Spawning Grounds: This layer is the nominal spawning distribution as gauged from the distribution and relative abundance of egg and/or larval stages from contemporary data and Coull et al. (1998). Areas with higher concentrations of eggs and/or larvae that are considered to relate to more important spawning grounds are designated as high intensity. This data is focused on species that are considered to be of conservation importance because it was developed for the Marine Conservation Zones project. This may be insufficient for other applications.

Fish Nursery Grounds: This layer provides the nominal nursery grounds for 17 highly mobile species distributed at a half ICES statistical rectangle resolution (0.5 by 0.5 degrees), Data were obtained from sampling surveys and Coull et al. (1998). Areas of higher concetrations of juveniles are considered to relate to more important nursery grounds. High intensity nursery grounds are those deemed as a main nursery ground with high relative abundance of juveniles.

Known Limitations: There are several data quality issues, especially regarding taxonomic identification (Section 2.3), that need to be considered when interpreting the data layers. For other elements of data quality, it is recommended by CEFAS that the users of the data layers refer to the associated report on the distribution of highly mobile species (Defra Project MB0102, Report No. 15, Task 2B). More intensive surveys have been undertaken in the Irish Sea, and higher resolution (HR) maps are provided for Cod, Sole and Plaice

Nominal spawning grounds for Ling are for a fringe of the distribution. The main distribution of Ling is not sampled appropriately for eggs & larvae, and no shapefile is provided.

Data for the North Sea population of mackerel were not available during this study.

For those areas (e.g. NW Scotland, parts of the English Channel and Irish Coasts) where there are no recent egg/larval data we recommend the user consult Coull et al. (1998) until more recent data become available.

In many cases, available data are limited or are of questionable quality (e.g. due to taxonomic problems, sampling artefacts etc.). Hence, there was a need to attach a measure of confidence for the data available (see Table 4 om ).

To enhance the way the data can be classified the Marine Management Organisation (MMO) carried out additional analysis to identify areas that were high or low intensity for multiple species. This allows the data to be classified by High/Low intensity and by the number of species. Each record contains attribution on the intensity, number of species and species type. Analysis was carried out using Geoprocessing tools in ArcGIS and ET Geowizard (Union, Advanced Edit, Dissolve and Spatial Join).

Export Data Access API

Metadata Portal Metadata Information

<td style='width:389.8pt; border-top:none; border-left:none; border-bottom:solid #CCCCCC 1.0pt; border-right:solid #CCCCCC 1.0pt; background:#E2EFDA; padding:.75pt .75pt .75pt .75pt;'

Content Title	Sydney City Council Join Features to Walking count sites
Content Type	Hosted Feature Layer
Description	Sydney City Council Join Features to Walking count sites
Initial Publication Date	06/10/2021
Data Currency	06/10/2021
Data Update Frequency	Other
Content Source
File Type	Map Feature Service
Attribution
Data Theme, Classification or Relationship to other Datasets
Accuracy
Spatial Reference System (dataset)	GDA2020
Spatial Reference System (web service)	EPSG:4326
WGS84 Equivalent To	GDA2020
Spatial Extent
Content Lineage
Data Classification