This resource was created by Esri Canada Education and Research. To browse our full collection of higher-education learning resources, please visit https://hed.esri.ca/resourcefinder/

ArcGIS Field Maps is a mobile app that allows you to view and collect field data using an Android or iOS smartphone or tablet. It is also a web app that allows you to configure web maps for use in the mobile app. The tutorials in this learning path will introduce you to the features of the Field Maps mobile app, how to create and configure web maps in Field Maps Designer that can be used in the Field Maps mobile app in online and offline mode, and how to collect data from a map and in the field with the mobile app.

As one of iCorridor applications, MEPDG dashboard provides site specific traffic data (Level 1) such as AADTT, vehicle class distribution, number of axle per truck, and axle load distribution for AASHTOWare Pavement ME Design. This dashboard provides the following three data files for any specific LHRS sections: Traffic data input file in XML format that contains the AADTT, vehicle class distribution, axle per truck, and axle spacing & configuration. Axle load spectrum file in ALF format that contains the axle load spectrum tables of single, tandem, tridem and quad axle types. A summary file in spreadsheet format that contains the above traffic data. The above XMF and ALF files can be directly input into AASHTOWare Pavement ME Design to run the analysis. If traffic data is insufficient within the LHRS section, the tables for Southern or Northern Ontario will be generated.NON-DIRECTIONAL option will provide an overall AADT and AADTT of the selected LHRS section in both directions. The pavement designer should enter the corresponding percent split of traffic volume for the design direction (typical 50%) to the ‘Percent trucks in design direction’ field. DIRECTIONAL option will provide the AADT and AADTT of the specific direction of the selected LHRS section, and the designer requires to enter 100% to the ‘Percent trucks in design direction’ field. Note that the designer requires to zoom in very close to the map in order to identify which direction to be chosen. Under rare circumstances should the designer require to select this option. If necessary, the data for AADT and AADTT as provided in iCorridor shall be overridden by the latest data provided by other sources, and the number of lanes at the design section should be verified with the designer or owner.If you have any question related to the AASHTOWare Pavement ME Design data, please contact: Susanne Chan, P.Eng.Senior Pavement Design Engineer,Materials Engineering & Research Office,Ontario Ministry of Transportation

As one of iCorridor applications, MEPDG web map provides site specific traffic data (Level 1) such as AADTT, vehicle class distribution, number of axle per truck, and axle load distribution for AASHTOWare Pavement ME Design. This program can generate the following three data files for any specific LHRS sections: Traffic data input file in XML format that contains the AADTT, vehicle class distribution, axle per truck, and axle spacing & configuration. Axle load spectrum file in ALF format that contains the axle load spectrum tables of single, tandem, tridem and quad axle types. A summary file in spreadsheet format that contains the above traffic data. The above XMF and ALF files can be directly input into AASHTOWare Pavement ME Design to run the analysis. If traffic data is insufficient within the LHRS section, the tables for Southern or Northern Ontario will be generated.NON-DIRECTIONAL option will provide an overall AADT and AADTT of the selected LHRS section in both directions. The pavement designer should enter the corresponding percent split of traffic volume for the design direction (typical 50%) to the ‘Percent trucks in design direction’ field. DIRECTIONAL option will provide the AADT and AADTT of the specific direction of the selected LHRS section, and the designer requires to enter 100% to the ‘Percent trucks in design direction’ field. Note that the designer requires to zoom in very close to the map in order to identify which direction to be chosen. Under rare circumstances should the designer require to select this option. If necessary, the data for AADT and AADTT as provided in iCorridor shall be overridden by the latest data provided by other sources, and the number of lanes at the design section should be verified with the designer or owner

In order to use the Romanian color standard for soil type map legends, a dataset of ESRI ArcMap-10 files, consisting of a shapefile set (.dbf, .shp, .shx, .sbn, and .sbx files), four different .lyr files, and three different .style files (https://desktop.arcgis.com/en/arcmap/10.3/map/ : saving-layers-and-layer-packages, about-creating-new-symbols, what-are-symbols-and-styles-), have been prepared. The shapefile set is not a “real” georeferenced layer/coverage; it is designed only to handle all the instants of soil types from the standard legend.

This legend contains 67 standard items: 63 proper colors (different color hues, each of them having, generally, 2 - 4 degrees of lightness and/or chroma, four shades of grey, and white color), and four hatching patterns on white background. The “color difference DE*ab” between any two legend colors, calculated with the color perceptually-uniform model CIELAB, is greater than 10 units, thus ensuring acceptably-distinguishable colors in the legend. The 67 standard items are assigned to 60 main soils existing in Romania, four main nonsoils, and three special cases of unsurveyed land. The soils are specified in terms of the current Romanian system of soil taxonomy, SRTS-2012+, and of the international system WRB-2014.

The four different .lyr files presented here are: legend_soilcode_srts_wrb.lyr, legend_soilcode_wrb.lyr, legend_colorcode_srts_wrb.lyr, and legend_colorcode_wrb.lyr. The first two of them are built using as value field the “Soil_codes” field, and as labels (explanation texts) the “Soil_name” field (storing the soil types according to SRTS/WRB classification), respectively, the “WRB” field (the soil type according to WRB classification), while the last two .lyr files are built using as value field the “color_code” field (storing the color codes) and as labels the soil name in SRTS and WRB, respectively, in WRB classification.

In order to exemplify how the legend is displayed, two .jpg files are also presented: legend_soil_srts_wrb.jpg and legend_color_wrb.jpg. The first displays the legend (symbols and labels) according to the SRTS classification order, the second according to the WRB classification.

The three different .style files presented here are: soil_symbols.style, wrb_codes.style, and color_codes.style. They use as name the soil acronym in SRTS classification, soil acronym in WRB classification, and, respectively, the color code.

The presented file set may be used to directly implement the Romanian color standard in digital soil type map legends, or may be adjusted/modified to other specific requirements.

Snapshot img

GIS In Utility Industry Market Size 2025-2029

The gis in utility industry market size is forecast to increase by USD 3.55 billion, at a CAGR of 19.8% between 2024 and 2029.

The utility industry's growing adoption of Geographic Information Systems (GIS) is driven by the increasing need for efficient and effective infrastructure management. GIS solutions enable utility companies to visualize, analyze, and manage their assets and networks more effectively, leading to improved operational efficiency and customer service. A notable trend in this market is the expanding application of GIS for water management, as utilities seek to optimize water distribution and reduce non-revenue water losses. However, the utility GIS market faces challenges from open-source GIS software, which can offer cost-effective alternatives to proprietary solutions. These open-source options may limit the functionality and support available to users, necessitating careful consideration when choosing a GIS solution. To capitalize on market opportunities and navigate these challenges, utility companies must assess their specific needs and evaluate the trade-offs between cost, functionality, and support when selecting a GIS provider. Effective strategic planning and operational execution will be crucial for success in this dynamic market.

What will be the Size of the GIS In Utility Industry 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 SampleThe Global Utilities Industry Market for Geographic Information Systems (GIS) continues to evolve, driven by the increasing demand for advanced data management and analysis solutions. GIS services play a crucial role in utility infrastructure management, enabling asset management, data integration, project management, demand forecasting, data modeling, data analytics, grid modernization, data security, field data capture, outage management, and spatial analysis. These applications are not static but rather continuously unfolding, with new patterns emerging in areas such as energy efficiency, smart grid technologies, renewable energy integration, network optimization, and transmission lines. Spatial statistics, data privacy, geospatial databases, and remote sensing are integral components of this evolving landscape, ensuring the effective management of utility infrastructure. Moreover, the adoption of mobile GIS, infrastructure planning, customer service, asset lifecycle management, metering systems, regulatory compliance, GIS data management, route planning, environmental impact assessment, mapping software, GIS consulting, GIS training, smart metering, workforce management, location intelligence, aerial imagery, construction management, data visualization, operations and maintenance, GIS implementation, and IoT sensors is transforming the industry. The integration of these technologies and services facilitates efficient utility infrastructure management, enhancing network performance, improving customer service, and ensuring regulatory compliance. The ongoing evolution of the utilities industry market for GIS reflects the dynamic nature of the sector, with continuous innovation and adaptation to meet the changing needs of utility providers and consumers.

How is this GIS In Utility Industry Industry segmented?

The gis in utility industry 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. ProductSoftwareDataServicesDeploymentOn-premisesCloudGeographyNorth AmericaUSCanadaEuropeFranceGermanyRussiaMiddle East and AfricaUAEAPACChinaIndiaJapanSouth AmericaBrazilRest of World (ROW).

By Product Insights

The software segment is estimated to witness significant growth during the forecast period.In the utility industry, Geographic Information Systems (GIS) play a pivotal role in optimizing operations and managing infrastructure. Utilities, including electricity, gas, water, and telecommunications providers, utilize GIS software for asset management, infrastructure planning, network performance monitoring, and informed decision-making. The GIS software segment in the utility industry encompasses various solutions, starting with fundamental GIS software that manages and analyzes geographical data. Additionally, utility companies leverage specialized software for field data collection, energy efficiency, smart grid technologies, distribution grid design, renewable energy integration, network optimization, transmission lines, spatial statistics, data privacy, geospatial databases, GIS services, project management, demand forecasting, data modeling, data analytics, grid modernization, data security, field data capture, outage ma

This report documents the research, field investigations and analyses used to compile a fault map and seismic acceleration coefficient contour maps for Arizona. The seismicity of adjacent regions which may potentially impact Arizona are factored into the analysis. Potential earthquake sources were evaluated using ground and airborne geological reconnaissance, photogeological interpretations and subsurface explorations of selected representative fault features. One hundred eighty-six faults or fault zones are identified. These data combined with other geological, seismological and geophysical.data define twenty-one seismic source zones influencing Arizona.Earthquake recurrence relations for each seismic source are derived. Energy release relationships based on slip rates and seismic moments are evaluated. Comparisons with recurrence relations defined by other researchers such as Algermissen, et al (1990) are made. The SEISRISK Ill computer program is used to conduct a probabilistic analysis to define acceleration coefficients with 90% probability of non-exceedance in 50 years in accordance with AASHTO seismic design guidelines. Additional maps for 90% probability of non-exceedance in 250 years and for peak ground velocity were also prepared.Ground acceleration coefficient (90-percent non-exceedance in 50 years) levels determined from the research program are higher than those in the existing AASHTO Seismic Guide specification in the northwestern and north-central parts of the state due to the significant number of potentially active faults identified in those regions. Coefficients are also higher in. the southwest corner of Arizona due largely to California and Mexico source zones. with high recurrence rates. Ground accelerations in the southeastern part of the state are significantly lower than previous estimates. Acceleration levels are essentially comparable to AASHTO guidelines in the remaining parts of the state.Maps of new seismic acceleration coefficient contours and compiled faults in Arizona have been prepared to a scale of 1:1,000,000. Electronic digital data files are compiled in a format that can be used to support site specific and regional studies for seismic design. The map of horizontal acceleration with 90-percent probability of non-exceedance in 50 years is recommended to the Arizona Department of Transportation for use in AASHTObased design of highway bridges.

The USGS Protected Areas Database of the United States (PAD-US) is the nation's inventory of protected areas, including public land and voluntarily provided private protected areas, identified as an A-16 National Geospatial Data Asset in the Cadastre Theme (https://communities.geoplatform.gov/ngda-cadastre/). The PAD-US is an ongoing project with several published versions of a spatial database including areas dedicated to the preservation of biological diversity, and other natural (including extraction), recreational, or cultural uses, managed for these purposes through legal or other effective means. The database was originally designed to support biodiversity assessments; however, its scope expanded in recent years to include all public and nonprofit lands and waters. Most are public lands owned in fee (the owner of the property has full and irrevocable ownership of the land); however, long-term easements, leases, agreements, Congressional (e.g. 'Wilderness Area'), Executive (e.g. 'National Monument'), and administrative designations (e.g. 'Area of Critical Environmental Concern') documented in agency management plans are also included. The PAD-US strives to be a complete inventory of public land and other protected areas, compiling “best available” data provided by managing agencies and organizations. The PAD-US geodatabase maps and describes areas using over twenty-five attributes and five feature classes representing the U.S. protected areas network in separate feature classes: Fee (ownership parcels), Designation, Easement, Marine, Proclamation and Other Planning Boundaries. Five additional feature classes include various combinations of the primary layers (for example, Combined_Fee_Easement) to support data management, queries, web mapping services, and analyses. This PAD-US Version 2.1 dataset includes a variety of updates and new data from the previous Version 2.0 dataset (USGS, 2018 https://doi.org/10.5066/P955KPLE ), achieving the primary goal to "Complete the PAD-US Inventory by 2020" (https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/science/pad-us-vision) by addressing known data gaps with newly available data. The following list summarizes the integration of "best available" spatial data to ensure public lands and other protected areas from all jurisdictions are represented in PAD-US, along with continued improvements and regular maintenance of the federal theme. Completing the PAD-US Inventory: 1) Integration of over 75,000 city parks in all 50 States (and the District of Columbia) from The Trust for Public Land's (TPL) ParkServe data development initiative (https://parkserve.tpl.org/) added nearly 2.7 million acres of protected area and significantly reduced the primary known data gap in previous PAD-US versions (local government lands). 2) First-time integration of the Census American Indian/Alaskan Native Areas (AIA) dataset (https://www2.census.gov/geo/tiger/TIGER2019/AIANNH) representing the boundaries for federally recognized American Indian reservations and off-reservation trust lands across the nation (as of January 1, 2020, as reported by the federally recognized tribal governments through the Census Bureau's Boundary and Annexation Survey) addressed another major PAD-US data gap. 3) Aggregation of nearly 5,000 protected areas owned by local land trusts in 13 states, aggregated by Ducks Unlimited through data calls for easements to update the National Conservation Easement Database (https://www.conservationeasement.us/), increased PAD-US protected areas by over 350,000 acres. Maintaining regular Federal updates: 1) Major update of the Federal estate (fee ownership parcels, easement interest, and management designations), including authoritative data from 8 agencies: Bureau of Land Management (BLM), U.S. Census Bureau (Census), Department of Defense (DOD), U.S. Fish and Wildlife Service (FWS), National Park Service (NPS), Natural Resources Conservation Service (NRCS), U.S. Forest Service (USFS), National Oceanic and Atmospheric Administration (NOAA). The federal theme in PAD-US is developed in close collaboration with the Federal Geographic Data Committee (FGDC) Federal Lands Working Group (FLWG, https://communities.geoplatform.gov/ngda-govunits/federal-lands-workgroup/); 2) Complete National Marine Protected Areas (MPA) update: from the National Oceanic and Atmospheric Administration (NOAA) MPA Inventory, including conservation measure ('GAP Status Code', 'IUCN Category') review by NOAA; Other changes: 1) PAD-US field name change - The "Public Access" field name changed from 'Access' to 'Pub_Access' to avoid unintended scripting errors associated with the script command 'access'. 2) Additional field - The "Feature Class" (FeatClass) field was added to all layers within PAD-US 2.1 (only included in the "Combined" layers of PAD-US 2.0 to describe which feature class data originated from). 3) Categorical GAP Status Code default changes - National Monuments are categorically assigned GAP Status Code = 2 (previously GAP 3), in the absence of other information, to better represent biodiversity protection restrictions associated with the designation. The Bureau of Land Management Areas of Environmental Concern (ACECs) are categorically assigned GAP Status Code = 3 (previously GAP 2) as the areas are administratively protected, not permanent. More information is available upon request. 4) Agency Name (FWS) geodatabase domain description changed to U.S. Fish and Wildlife Service (previously U.S. Fish & Wildlife Service). 5) Select areas in the provisional PAD-US 2.1 Proclamation feature class were removed following a consultation with the data-steward (Census Bureau). Tribal designated statistical areas are purely a geographic area for providing Census statistics with no land base. Most affected areas are relatively small; however, 4,341,120 acres and 37 records were removed in total. Contact Mason Croft (masoncroft@boisestate) for more information about how to identify these records. For more information regarding the PAD-US dataset please visit, https://usgs.gov/gapanalysis/PAD-US/. For more information about data aggregation please review the Online PAD-US Data Manual available at https://www.usgs.gov/core-science-systems/science-analytics-and-synthesis/gap/pad-us-data-manual .

This map's colors indicate which age group is has the most people in each area. Esri aggregated the Census data into 10-year age groups. Age groups include Under 10, 10 to 19, 20 to 29 and so forth. Data is from the U.S. Census Bureau’s 2020 Census Demographic and Housing Characteristics. The map's layers contain total population counts by sex, age, and race groups for Nation, State, County and Census Tract in the United States and Puerto Rico.About the dataYou can use this map as is and you can also modify it to use other attributes included in its layers. This map's layers contain total population counts by sex, age, and race groups data from the 2020 Census Demographic and Housing Characteristics. This is shown by Nation, State, County, Census Tract, Block Group boundaries. Each geography layer contains a common set of Census counts based on available attributes from the U.S. Census Bureau. There are also additional calculated attributes related to this topic, which can be mapped or used within analysis.Vintage of boundaries and attributes: 2020 Demographic and Housing Characteristics Table(s): P1, H1, H3, P2, P3, P5, P12, P13, P17, PCT12 (Not all lines of these DHC tables are available in this feature layer.)Data downloaded from: U.S. Census Bureau’s data.census.gov siteDate the Data was Downloaded: May 25, 2023Geography Levels included: Nation, State, County, Census Tract, Block GroupNational Figures: included in Nation layer The United States Census Bureau Demographic and Housing Characteristics: 2020 Census Results 2020 Census Data Quality Geography & 2020 Census Technical Documentation Data Table Guide: includes the final list of tables, lowest level of geography by table and table shells for the Demographic Profile and Demographic and Housing Characteristics.News & Updates This map is ready to be used in ArcGIS Pro, ArcGIS Online and its configurable apps, Story Maps, dashboards, Notebooks, Python, custom apps, and mobile apps. Data can also be exported for offline workflows. Please cite the U.S. Census Bureau when using this data. Data Processing Notes: These 2020 Census boundaries come from the US Census TIGER geodatabases. These are Census boundaries with water and/or coastlines erased for cartographic and mapping purposes. For Census tracts and block groups, 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 and block group boundaries, as well as additional important features. For state and county boundaries, the water and coastlines are derived from the coastlines of the 2020 500k TIGER Cartographic Boundary Shapefiles. These are erased to more accurately portray the coastlines and Great Lakes. The original AWATER and ALAND fields are unchanged and available as attributes within the data table (units are square meters).  The layer contains all US states, Washington D.C., and Puerto Rico. Census tracts with no population that occur in areas of water, such as oceans, are removed from this data service (Census Tracts beginning with 99). Block groups that fall within the same criteria (Block Group denoted as 0 with no area land) have also been removed.Percentages and derived counts, are calculated values (that can be identified by the "_calc_" stub in the field name). Field alias names were created based on the Table Shells file available from the Data Table Guide for the Demographic Profile and Demographic and Housing Characteristics. Not all lines of all tables listed above are included in this layer. Duplicative counts were dropped. For example, P0030001 was dropped, as it is duplicative of P0010001.To protect the privacy and confidentiality of respondents, their data has been protected using differential privacy techniques by the U.S. Census Bureau.Web map design by Maddie Haynes, Esri Professional Services