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.

Seattle Parks and Recreation ARCGIS park feature map layer web services are hosted on Seattle Public Utilities' ARCGIS server. This web services URL provides a live read only data connection to the Seattle Parks and Recreations Rugby Field dataset.

This guide will teach you everything you need to know to successfully migrate your field workflows to Field Maps.

Seattle Parks and Recreation ARCGIS park feature map layer web services are hosted on Seattle Public Utilities' ARCGIS server. This web services URL provides a live read only data connection to the Seattle Parks and Recreations T-ball Field dataset.

This dashboard is best viewed using a mobile device. For an enhanced viewing experience on a desktop or laptop computer please use the NV Wildfire Info desktop version dashboardAll data displayed on this map is near real-time. There are two ways in which this happens: Web service based data and a mobile mapping application called Field Maps. Web services are updated regularly ranging from every minute to once a month. All web services in this map are refreshed automatically to ensure the latest data being provided is displayed. Data collected through the use of Field Maps is done so by firefighters on the ground. The Field Maps application is consuming, creating, and editing data that are stored in ArcGIS Online. These data are then fed directly in to this map. To learn more about these web mapping technologies, visit the links below:Web ServicesArcGIS Field MapsArcGIS OnlineWeb Services used in this map:(visit link to learn more about each service)IRWIN - A central hub that orchestrates data between various fire reporting applications. When a new incident is created and/or updated by a dispatch center or other fire reporting system, it is then displayed on the map using the Integrated Reporting of Wildland-Fire Information (IRWIN) service. All layers below are derived from the same IRWIN service and automatically refresh every five minutes:New Starts (last 24hrs) - Any incident that has occurred within the last rolling 24 hour time period.Current Large Incidents - Incidents that have created an ICS 209 document at the type 3 Incident Commander (IC) level and above and are less than 100% contained.Ongoing - Incidents that do not have a containment, control, or out date.Contained - Incidents with a containment date but no control or out date.Controlled/Out (last 24hrs) - Incidents with a containment, control, and/or out date within the last rolling 24 hour time period.Controlled/Out - Incidents with a containment, control, and/or out date. Layer turned off by default.Season Summary - All incidents year to date. Layer turned off by default.ArcGIS Online/Field Maps - Part of the Esri Geospatial Cloud, ArcGIS Online and Collector enables firefighters to use web maps created in ArcGIS Online on mobile devices using the Collector application to capture and edit data on the fireline. Data may be captured and edited in both connected and disconnected environments. When data is submitted back to the web service in ArcGIS Online, it is then checked for accuracy and approved for public viewing.Fire Perimeter - Must be set to 'Approved' and 'Public' to be displayed on the map. Automatically refreshes every five minutes.NOAA nowCOAST - Provides web services of near real-time observations, analyses, tide predictions, model guidance, watches/warnings, and forecasts for the coastal United States by integrating data and information across NOAA, other federal agencies and regional ocean and weather observing systems (source). All layers below automatically refresh every five minutes.Tornado Warning - National Weather Service warning for short duration hazard.Severe Thunderstorm Warning - National Weather Service warning for short duration hazard.Flash Flood Warning - National Weather Service warning for short duration hazard.Red Flag Warning - National Weather Service warning for long duration hazard.nowCOAST Lightning Strike Density - 15-minute Satellite Emulated Lightning Strike Density imagery for the last several hours.nowCOAST Radar - Weather Radar (NEXRAD) Reflectivity Mosaics from NOAA MRMS for Alaska, CONUS, Puerto Rico, Guam, and Hawaii for last several hours.

Essential tasks and best practices for taking your web maps offline and into the field with ArcGIS Field Maps.

The Digital Geologic-GIS Map of San Miguel Island, California is composed of GIS data layers and GIS tables, and is available in the following GRI-supported GIS data formats: 1.) a 10.1 file geodatabase (smis_geology.gdb), a 2.) Open Geospatial Consortium (OGC) geopackage, and 3.) 2.2 KMZ/KML file for use in Google Earth, however, this format version of the map is limited in data layers presented and in access to GRI ancillary table information. The file geodatabase format is supported with a 1.) ArcGIS Pro map file (.mapx) file (smis_geology.mapx) and individual Pro layer (.lyrx) files (for each GIS data layer), as well as with a 2.) 10.1 ArcMap (.mxd) map document (smis_geology.mxd) and individual 10.1 layer (.lyr) files (for each GIS data layer). The OGC geopackage is supported with a QGIS project (.qgz) file. Upon request, the GIS data is also available in ESRI 10.1 shapefile format. Contact Stephanie O'Meara (see contact information below) to acquire the GIS data in these GIS data formats. In addition to the GIS data and supporting GIS files, three additional files comprise a GRI digital geologic-GIS dataset or map: 1.) this file (chis_geology_gis_readme.pdf), 2.) the GRI ancillary map information document (.pdf) file (chis_geology.pdf) which contains geologic unit descriptions, as well as other ancillary map information and graphics from the source map(s) used by the GRI in the production of the GRI digital geologic-GIS data for the park, and 3.) a user-friendly FAQ PDF version of the metadata (smis_geology_metadata_faq.pdf). Please read the chis_geology_gis_readme.pdf for information pertaining to the proper extraction of the GIS data and other map files. Google Earth software is available for free at: https://www.google.com/earth/versions/. QGIS software is available for free at: https://www.qgis.org/en/site/. Users are encouraged to only use the Google Earth data for basic visualization, and to use the GIS data for any type of data analysis or investigation. The data were completed as a component of the Geologic Resources Inventory (GRI) program, a National Park Service (NPS) Inventory and Monitoring (I&M) Division funded program that is administered by the NPS Geologic Resources Division (GRD). For a complete listing of GRI products visit the GRI publications webpage: For a complete listing of GRI products visit the GRI publications webpage: https://www.nps.gov/subjects/geology/geologic-resources-inventory-products.htm. For more information about the Geologic Resources Inventory Program visit the GRI webpage: https://www.nps.gov/subjects/geology/gri,htm. At the bottom of that webpage is a "Contact Us" link if you need additional information. You may also directly contact the program coordinator, Jason Kenworthy (jason_kenworthy@nps.gov). Source geologic maps and data used to complete this GRI digital dataset were provided by the following: American Association of Petroleum Geologists. Detailed information concerning the sources used and their contribution the GRI product are listed in the Source Citation section(s) of this metadata record (smis_geology_metadata.txt or smis_geology_metadata_faq.pdf). Users of this data are cautioned about the locational accuracy of features within this dataset. Based on the source map scale of 1:24,000 and United States National Map Accuracy Standards features are within (horizontally) 12.2 meters or 40 feet of their actual location as presented by this dataset. Users of this data should thus not assume the location of features is exactly where they are portrayed in Google Earth, ArcGIS, QGIS or other software used to display this dataset. All GIS and ancillary tables were produced as per the NPS GRI Geology-GIS Geodatabase Data Model v. 2.3. (available at: https://www.nps.gov/articles/gri-geodatabase-model.htm).

Use the Attachment Viewer template to provide an app for users to explore a layer's features and review attachments with the option to update attribute data. Present your images, videos, and PDF files collected using ArcGIS Field Maps or ArcGIS Survey123 workflows. Choose an attachment-focused layout to display individual images beside your map or a map-focused layout to highlight your map next to a gallery of images. Examples: Review photos collected during emergency response damage inspections. Display the results of field data collection and support downloading images for inclusion in a report. Present a map of land parcel along with associated documents stored as attachments. Data requirements The Attachment Viewer template requires a feature layer with attachments. It includes the capability to view attachments of a hosted feature service or an ArcGIS Server feature service (10.8 or later). Currently, the app can display JPEG, JPG, PNG, GIF, MP4, QuickTime (.mov), and PDF files in the viewer window. All other attachment types are displayed as a link. Key app capabilities App layout - Choose between an attachment-focused layout, which displays one attachment at a time in the main panel of the app with the map on the side, or a map-focused layout, which displays the map in the main panel of the app with a gallery of attachments. Feature selection - Allows users to select features in the map and view associated attachments. Review data - Enable tools to review and update existing records. Zoom, pan, download images - Allow users to interact with and download attachments. Language switcher - Provide translations for custom text and create a multilingual app. Home, Zoom controls, Legend, Layer List, Search Supportability This web app is designed responsively to be used in browsers on desktops, mobile phones, and tablets. We are committed to ongoing efforts towards making our apps as accessible as possible. Please feel free to leave a comment on how we can improve the accessibility of our apps for those who use assistive technologies.

Contains:World HillshadeWorld Street Map (with Relief) - Base LayerLarge Scale International Boundaries (v11.3)World Street Map (with Relief) - LabelsDoS Country Labels DoS Country LabelsCountry (admin 0) labels that have been vetted for compliance with foreign policy and legal requirements. These labels are part of the US Federal Government Basemap, which contains the borders and place names that have been vetted for compliance with foreign policy and legal requirements.Source: DoS Country Labels - Overview (arcgis.com)Large Scale International BoundariesVersion 11.3Release Date: December 19, 2023DownloadFor more information on the LSIB click here: https://geodata.state.gov/ A direct link to the data is available here: https://data.geodata.state.gov/LSIB.zipAn ISO-compliant version of the LSIB metadata (in ISO 19139 format) is here: https://geodata.state.gov/geonetwork/srv/eng/catalog.search#/metadata/3bdb81a0-c1b9-439a-a0b1-85dac30c59b2 Direct inquiries to internationalboundaries@state.govOverviewThe Office of the Geographer and Global Issues at the U.S. Department of State produces the Large Scale International Boundaries (LSIB) dataset. The current edition is version 11.3 (published 19 December 2023). The 11.3 release contains updates to boundary lines and data refinements enabling reuse of the dataset. These data and generalized derivatives are the only international boundary lines approved for U.S. Government use. The contents of this dataset reflect U.S. Government policy on international boundary alignment, political recognition, and dispute status. They do not necessarily reflect de facto limits of control.National Geospatial Data AssetThis dataset is a National Geospatial Data Asset managed by the Department of State on behalf of the Federal Geographic Data Committee's International Boundaries Theme.DetailsSources for these data include treaties, relevant maps, and data from boundary commissions and national mapping agencies. Where available and applicable, the dataset incorporates information from courts, tribunals, and international arbitrations. The research and recovery process involves analysis of satellite imagery and elevation data. Due to the limitations of source materials and processing techniques, most lines are within 100 meters of their true position on the ground.Attribute StructureThe dataset uses thefollowing attributes:Attribute NameCC1COUNTRY1CC2COUNTRY2RANKSTATUSLABELNOTES These attributes are logically linked:Linked AttributesCC1COUNTRY1CC2COUNTRY2RANKSTATUS These attributes have external sources:Attribute NameExternal Data SourceCC1GENCCOUNTRY1DoS ListsCC2GENCCOUNTRY2DoS ListsThe eight attributes listed above describe the boundary lines contained within the LSIB dataset in both a human and machine-readable fashion. Other attributes in the release include "FID", "Shape", and "Shape_Leng" are components of the shapefile format and do not form an intrinsic part of the LSIB."CC1" and "CC2" fields are machine readable fields which contain political entity codes. These codes are derived from the Geopolitical Entities, Names, and Codes Standard (GENC) Edition 3 Update 18. The dataset uses the GENC two-character codes. The code ‘Q2’, which is not in GENC, denotes a line in the LSIB representing a boundary associated with an area not contained within the GENC standard.The "COUNTRY1" and "COUNTRY2" fields contain human-readable text corresponding to the name of the political entity. These names are names approved by the U.S. Board on Geographic Names (BGN) as incorporated in the list of Independent States in the World and the list of Dependencies and Areas of Special Sovereignty maintained by the Department of State. To ensure the greatest compatibility, names are presented without diacritics and certain names are rendered using commonly accepted cartographic abbreviations. Names for lines associated with the code ‘Q2’ are descriptive and are not necessarily BGN-approved. Names rendered in all CAPITAL LETTERS are names of independent states. Other names are those associated with dependencies, areas of special sovereignty, or are otherwise presented for the convenience of the user.The following fields are an intrinsic part of the LSIB dataset and do not rely on external sources:Attribute NameMandatoryContains NullsRANKYesNoSTATUSYesNoLABELNoYesNOTESNoYesNeither the "RANK" nor "STATUS" field contains null values; the "LABEL" and "NOTES" fields do.The "RANK" field is a numeric, machine-readable expression of the "STATUS" field. Collectively, these fields encode the views of the United States Government on the political status of the boundary line.Attribute NameValueRANK123STATUSInternational BoundaryOther Line of International Separation Special Line A value of "1" in the "RANK" field corresponds to an "International Boundary" value in the "STATUS" field. Values of "2" and "3" correspond to "Other Line of International Separation" and "Special Line", respectively.The "LABEL" field contains required text necessarily to describe the line segment. The "LABEL" field is used when the line segment is displayed on maps or other forms of cartographic visualizations. This includes most interactive products. The requirement to incorporate the contents of the "LABEL" field on these products is scale dependent. If a label is legible at the scale of a given static product a proper use of this dataset would encourage the application of that label. Using the contents of the "COUNTRY1" and "COUNTRY2" fields in the generation of a line segment label is not required. The "STATUS" field is not a line labeling field but does contain the preferred description for the three LSIB line types when lines are incorporated into a map legend. Using the "CC1", "CC2", or "RANK" fields for labeling purposes is prohibited.The "NOTES" field contains an explanation of any applicable special circumstances modifying the lines. This information can pertain to the origins of the boundary lines, any limitations regarding the purpose of the lines, or the original source of the line. Use of the "NOTES" field for labeling purposes is prohibited.External Data SourcesGeopolitical Entities, Names, and Codes Registry: https://nsgreg.nga.mil/GENC-overview.jspU.S. Department of State List of Independent States in the World: https://www.state.gov/independent-states-in-the-world/U.S. Department of State List of Dependencies and Areas of Special Sovereignty: https://www.state.gov/dependencies-and-areas-of-special-sovereignty/The source for the U.S.—Canada international boundary (NGDAID97) is the International Boundary Commission: https://www.internationalboundarycommission.org/en/maps-coordinates/coordinates.phpThe source for the “International Boundary between the United States of America and the United States of Mexico” (NGDAID82) is the International Boundary and Water Commission: https://catalog.data.gov/dataset?q=usibwcCartographic UsageCartographic usage of the LSIB requires a visual differentiation between the three categories of boundaries. Specifically, this differentiation must be between:- International Boundaries (Rank 1);- Other Lines of International Separation (Rank 2); and- Special Lines (Rank 3).Rank 1 lines must be the most visually prominent. Rank 2 lines must be less visually prominent than Rank 1 lines. Rank 3 lines must be shown in a manner visually subordinate to Ranks 1 and 2. Where scale permits, Rank 2 and 3 lines must be labeled in accordance with the “Label” field. Data marked with a Rank 2 or 3 designation does not necessarily correspond to a disputed boundary.Additional cartographic information can be found in Guidance Bulletins (https://hiu.state.gov/data/cartographic_guidance_bulletins/) published by the Office of the Geographer and Global Issues.ContactDirect inquiries to internationalboundaries@state.gov.CreditsThe lines in the LSIB dataset are the product of decades of collaboration between geographers at the Department of State and the National Geospatial-Intelligence Agency with contributions from the Central Intelligence Agency and the UK Defence Geographic Centre.Attribution is welcome: U.S. Department of State, Office of the Geographer and Global Issues.Changes from Prior ReleaseThe 11.3 release is the third update in the version 11 series.This version of the LSIB contains changes and accuracy refinements for the following line segments. These changes reflect improvements in spatial accuracy derived from newly available source materials, an ongoing review process, or the publication of new treaties or agreements. Notable changes to lines include:• AFGHANISTAN / IRAN• ALBANIA / GREECE• ALBANIA / KOSOVO• ALBANIA/MONTENEGRO• ALBANIA / NORTH MACEDONIA• ALGERIA / MOROCCO• ARGENTINA / BOLIVIA• ARGENTINA / CHILE• BELARUS / POLAND• BOLIVIA / PARAGUAY• BRAZIL / GUYANA• BRAZIL / VENEZUELA• BRAZIL / French Guiana (FR.)• BRAZIL / SURINAME• CAMBODIA / LAOS• CAMBODIA / VIETNAM• CAMEROON / CHAD• CAMEROON / NIGERIA• CHINA / INDIA• CHINA / NORTH KOREA• CHINA / Aksai Chin• COLOMBIA / VENEZUELA• CONGO, DEM. REP. OF THE / UGANDA• CZECHIA / GERMANY• EGYPT / LIBYA• ESTONIA / RUSSIA• French Guiana (FR.) / SURINAME• GREECE / NORTH MACEDONIA• GUYANA / VENEZUELA• INDIA / Aksai Chin• KAZAKHSTAN / RUSSIA• KOSOVO / MONTENEGRO• KOSOVO / SERBIA• LAOS / VIETNAM• LATVIA / LITHUANIA• MEXICO / UNITED STATES• MONTENEGRO / SERBIA• MOROCCO / SPAIN• POLAND / RUSSIA• ROMANIA / UKRAINEVersions 11.0 and 11.1 were updates to boundary lines. Like this version, they also contained topology fixes, land boundary terminus refinements, and tripoint adjustments. Version 11.2 corrected a few errors in the attribute data and ensured that CC1 and CC2 attributes are in alignment with an updated version of the Geopolitical Entities, Names, and Codes (GENC) Standard, specifically Edition 3 Update 17.LayersLarge_Scale_International_BoundariesTerms of

Seattle Parks and Recreation ARCGIS park feature map layer web services are hosted on Seattle Public Utilities' ARCGIS server. This web services URL provides a live read only data connection to the Seattle Parks and Recreations Track Field dataset.

Contents: This is an ArcGIS Pro zip file that you can download and use for creating map books based on United States National Grid (USNG). It contains a geodatabase, layouts, and tasks designed to teach you how to create a basic map book.Version 1.0.0 Uploaded on May 24th and created with ArcGIS Pro 2.1.3 - Please see the README below before getting started!Updated to 1.1.0 on August 20thUpdated to 1.2.0 on September 7thUpdated to 2.0.0 on October 12thUpdate to 2.1.0 on December 29thBack to 1.2.0 due to breaking changes in the templateBack to 1.0.0 due to breaking changes in the template as of June 11th 2019Updated to 2.1.1 on October 8th 2019Audience: GIS Professionals and new users of ArcGIS Pro who support Public Safety agencies with map books. If you are looking for apps that can be used by any public safety professional, see the USNG Lookup Viewer.Purpose: To teach you how to make a map book with critical infrastructure and a basemap, based on USNG. You NEED to follow the steps in the task and not try to take shortcuts the first time you use this task in order to receive the full benefits. Background: This ArcGIS Pro template is meant to be a starting point for your map book projects and is based on best practices by the USNG National Implementation Center (TUNIC) at Delta State University and is hosted by the NAPSG Foundation. This does not replace previous templates created in ArcMap, but is a new experimental approach to making map books. We will continue to refine this template and work with other organizations to make improvements over time. So please send us your feedback admin@publicsafetygis.org and comments below. Instructions: Download the zip file by clicking on the thumbnail or the Download button.Unzip the file to an appropriate location on your computer (C:\Users\YourUsername\Documents\ArcGIS\Projects is a common location for ArcGIS Pro Projects).Open the USNG Map book Project File (APRX).If the Task is not already open by default, navigate to Catalog > Tasks > and open 'Create a US National Grid Map Book' Follow the instructions! This task will have some automated processes and models that run in the background but you should pay close attention to the instructions so you also learn all of the steps. This will allow you to innovate and customize the template for your own use.FAQsWhat is US National Grid? The US National Grid (USNG) is a point and area reference system that provides for actionable location information in a uniform format. Its use helps achieve consistent situational awareness across all levels of government, disciplines, and threats & hazards – regardless of your role in an incident.One of the key resources NAPSG makes available to support emergency responders is a basic USNG situational awareness application. See the NAPSG Foundation and USNG Center websites for more information.What is an ArcGIS Pro Task? A task is a set of preconfigured steps that guide you and others through a workflow or business process. A task can be used to implement a best-practice workflow, improve the efficiency of a workflow, or create a series of interactive tutorial steps. See "What is a Task?" for more information.Do I need to be proficient in ArcGIS Pro to use this template? We feel that this is a good starting point if you have already taken the ArcGIS Pro QuickStart Tutorials. While the task will automate many steps, you will want to get comfortable with the map layouts and other new features in ArcGIS Pro.Is this template free? This resources is provided at no-cost, but also with no guarantees of quality assurance or support at this time. Can't I just use ArcMap? Ok - here you go. USNG 1:24K Map Template for ArcMapKnown Limitations and BugsZoom To: It appears there may be a bug or limitation with automatically zooming the map to the proper extent, so get comfortable with navigation or zoom to feature via the attribute table.FGDC Compliance: We are seeking feedback from experts in the field to make sure that this meets minimum requirements. At this point in time we do not claim to have any official endorsement of standardization. File Size: Highly detailed basemaps can really add up and contribute to your overall file size, especially over a large area / many pages. Consider making a simple "Basemap" of street centerlines and building footprints.We will do the best we can to address limitations and are very open to feedback!

The global market for GIS Collectors is experiencing robust growth, driven by increasing adoption of location-based services, the expanding need for precise geospatial data across various sectors, and the continuous advancements in mobile technology and data analytics capabilities. The market is segmented by hardware (handheld devices, tablets, drones) and software (field data collection apps, data management software). Key players like Hexagon, Trimble Geospatial, ESRI, Topcon, Handheld, and Wuhan South are actively innovating and expanding their product portfolios to cater to this growing demand. The market's expansion is further fueled by the rising need for efficient asset management, improved infrastructure planning, and precise mapping for various applications such as environmental monitoring, agriculture, and urban planning. Government initiatives promoting digitalization and smart city development are also contributing significantly to the market's growth trajectory. While high initial investment costs for hardware and software can act as a restraint, the long-term benefits in terms of operational efficiency and data accuracy are overcoming this challenge. We project a steady market growth over the forecast period, with a particular emphasis on the increasing penetration of cloud-based solutions and the integration of AI and machine learning for enhanced data processing and analysis. The period between 2019 and 2024 showed significant market expansion, setting a strong foundation for future growth. We estimate the market size in 2025 at $5 billion, based on observed trends and industry reports. This strong base, coupled with a projected Compound Annual Growth Rate (CAGR) of 12%, will drive considerable market expansion throughout the forecast period (2025-2033). The increasing demand across diverse sectors, from precision agriculture to utility management, will continue to be major drivers. Furthermore, the emergence of new technologies such as 5G and IoT will further enhance data collection and processing capabilities, leading to improved efficiencies and a further expansion of the market. The North American and European markets currently hold a significant share, but emerging economies in Asia-Pacific and Latin America are exhibiting accelerated growth potential, making them crucial regions for future expansion.

Overview

This dataset contains all DOMI Street Closure Permit data in the Computronix (CX) system from the date of its adoption (in May 2020) until the present. The data in each record can be used to determine when street closures are occurring, who is requesting these closures, why the closure is being requested, and for mapping the closures themselves. It is updated hourly (as of March 2024).

Preprocessing/Formatting

It is important to distinguish between a permit, a permit's street closure(s), and the roadway segments that are referenced to that closure(s).

• The CX system identifies a street in segments of roadway. (As an example, the CX system could divide Maple Street into multiple segments.)

• A single street closure may span multiple segments of a street.

• The street closure permit refers to all the component line segments.

• A permit may have multiple streets which are closed. Street closure permits often reference many segments of roadway.

The roadway_id field is a unique GIS line segment representing the aforementioned segments of road. The roadway_id values are assigned internally by the CX system and are unlikely to be known by the permit applicant. A section of roadway may have multiple permits issued over its lifespan. Therefore, a given roadway_id value may appear in multiple permits.

The field closure_id represents a unique ID for each closure, and permit_id uniquely identifies each permit. This is in contrast to the aforementioned roadway_id field which, again, is a unique ID only for the roadway segments.

City teams that use this data requested that each segment of each street closure permit be represented as a unique row in the dataset. Thus, a street closure permit that refers to three segments of roadway would be represented as three rows in the table. Aside from the roadway_id field, most other data from that permit pertains equally to those three rows. Thus, the values in most fields of the three records are identical.

Each row has the fields segment_num and total_segments which detail the relationship of each record, and its corresponding permit, according to street segment. The above example produced three records for a single permit. In this case, total_segments would equal 3 for each record. Each of those records would have a unique value between 1 and 3.

The geometry field consists of string values of lat/long coordinates, which can be used to map the street segments.

All string text (most fields) were converted to UPPERCASE data. Most of the data are manually entered and often contain non-uniform formatting. While several solutions for cleaning the data exist, text were transformed to UPPERCASE to provide some degree of regularization. Beyond that, it is recommended that the user carefully think through cleaning any unstructured data, as there are many nuances to consider. Future improvements to this ETL pipeline may approach this problem with a more sophisticated technique.

Known Uses

These data are used by DOMI to track the status of street closures (and associated permits).

Further Documentation and Resources

An archived dataset containing historical street closure records (from before May of 2020) for the City of Pittsburgh may be found here: https://data.wprdc.org/dataset/right-of-way-permits

On shallow rocky reefs in northeastern Aotearoa, New Zealand, urchin barrens are recognised as indicators of the ecosystem effects of overfishing reef predators. Yet, information on their extent and variability is lacking. We use aerial imagery to map the urchin barrens and kelp forests on reefs (<30 m depth) across seven locations, including within two long-established marine reserves and a marine protected area that allows recreational fishing. Urchin barrens were present in all locations and were restricted to reefs <10-16 m deep. This archive contains ArcGIS shapefiles and layer files for all of the maps used in this study. The study area extends from Cape Reinga in the far north of the North Island to Tawharanui in the Hauraki Gulf near Auckland. Regional scale base maps of the prominent marine habitats were included along with the seven fine-scale maps where the kelp forests and urchin barrens were mapped., The GIS shapefiles produced in this study were hand-drawn over layers of low-level aerial photography taken in specific conditions, which maximised the visible depth observable to create polygons to depict the habitat boundaries of the shallow reef. Of particular interest was the mapping of urchin barrens. Ground truthing surveys creating point data and underwater imagery were also brought into the GIS project to assist in drawing the reef habitat polygons. Arc layer files contain a common symbology across the seven study maps to aid the interpretation of the mapping. Further information on the methodology used in the mapping can be found in two published papers and four technical reports corresponding to the maps. The Readme file details where technical reports and published reports can be downloaded from the internet., , # GIS data of urchin barren mapping in Northeastern New Zealand

GIS mapping resources supporting the research article: Kerr, V.C. Grace R.V. (deceased), and Shears N.T., 2004. Estimating the extent of urchin barrens and kelp forest loss in northeastern Aotearoa, New Zealand. Kerr and Associates, Whangarei, New Zealand.

Description of the data and file structure

Four folders in this archive contain ArcGIS shapefiles with the extension (.shp). The shapefiles can be uploaded to ArcGIS or any ArcGIS-compatible software to view and access the files' spatial data and habitat attributes. It is essential to retain the associated files in each folder as these are system files required by ArcGIS to open and use the shapefiles. Each shapefile has six associated files with extensions: .avi, .CPG, .dbf, .prf, .sbn, and .sbx. In this archive are maps based on polygons drawn to depict habitat boundaries of biological and physical habitats in the shallow coastal areas of Northeastern New Zealan...

DOUGLAS COUNTY SURVEY/GISGIS PARCEL MAPPING GUIDELINES FOR PARCEL DISCREPANCIESIt is the intent of the Douglas County GIS Parcel Mapping to accurately identify the areas of land parcels to be valued and taxed 1. Discrepancies in areas• The Auditor/Assessor (tax) acreage areas started with the original US General Land Office (GLO) township plat maps created from the Public Land Survey (PLS) that was done between 1858 and 1871. The recovery of the PLS corners and the accurate location of these corners with GPS obtained coordinates has allowed for accurate section subdivisions, which results in accurate areas for parcels based on legal descriptions, which may be significantly different than the original areas. (See Example 2)• Any parcel bordering a meandered lake and/or a water boundary will likely have a disparity of area between the Auditor/Assessor acreages and the GIS acreages because of the inaccuracy of the original GLO meander lines from which the original areas were determined. Water lines are not able to be drafted to the same accuracy as the normal parcel lines. The water lines are usually just sketched on a survey and their dimensions are not generally given on a land record. The water boundaries of our GIS parcels are located from aerial photography. This is a subjective determination based on the interpretation by the Survey/GIS technician of what is water. Some lakes fluctuate significantly and the areas of all parcels bordering water are subject to constant change. In these cases the ordinary high water line (OHW) is attempted to be identified. Use of 2-foot contours will be made, if available. (See Example 1)• Some land records do not accurately report the area described in the land description and the description area is ignored. (See Example 3)• The parcel mapping has made every attempt to map the parcels based on available survey information as surveyed and located on the ground. This may conflict with some record legal descriptions.Solutions• If an actual survey by a licensed Land Surveyor is available, it will be utilized for the tax acreage.• If the Auditor/Assessor finds a discrepancy between the tax and GIS areas, they will request a review by the County Survey/GIS department.• As a starting guideline, the County Survey/GIS department will identify all parcels that differ in tax area versus GIS parcel area of 10 % or more and a difference of at least 5 acres. (This could be expanded later after the initial review.)• Each of these identified parcels will be reviewed individually by the County Survey/GIS department to determine the reason for the discrepancy and a recommendation will be made by the County Survey/GIS department to the Auditor/Assessor if the change should be made or not.• If a change is to be made to the tax area, a letter will be sent to the taxpayer informing them that their area will be changed during the next tax cycle, which could affect their property valuation. This letter will originate from the Auditor/Assessor with explanation from the County Survey/GIS department. 2. Gaps and Overlaps• Land descriptions for adjoining parcels sometimes overlap or leave a gap between them.o In these instances the Survey/GIS technician has to make a decision where to place this boundary. A number of circumstances are reviewed to facilitate this decision as these dilemmas are usually decided on a case by case basis. All effort will be made to not leave a gap, but sometimes this is not possible and the gap will be shown with “unknown” ownership. (Note: The County does not have the authority to change boundaries!)o Some of the circumstances reviewed are: Which parcel had the initial legal description? Does the physical occupation of the parcel line as shown on the air photo more closely fit one of the described parcels? Interpretation of the intent of the legal description. Is the legal description surveyable?Note: These overlaps will be shown on the GIS map with a dashed “survey line” and accompanying text for the line not used for the parcel boundary. 3. Parcel lines that do not match location of buildings Structures on parcels do not always lie within the boundaries of the parcel. This may be a circumstance of building without the benefit of a survey or of misinterpreting these boundaries. The parcel lines should be shown accurately as surveyed and/or described regardless of the location of structures on the ground. NOTE: The GIS mapping is not a survey, but is an interpretation of parcel boundaries predicated upon resources available to the County Survey/GIS department.Gary Stevenson Page 1 7/21/2017Example 1Example 2A Example 2B Example 3

An ArcGIS Field Maps map used by public works or planning department personnel to inventory public parking and pay stations in the field.

A map of the University of Mississippi Field Station and accompanying GIS data

Seattle Parks and Recreation ARCGIS park feature map layer web services are hosted on Seattle Public Utilities' ARCGIS server. This web services URL provides a live read only data connection to the Seattle Parks and Recreations Football Field Point dataset.

The files linked to this reference are the geospatial data created as part of the completion of the baseline vegetation inventory project for the NPS park unit. Current format is ArcGIS file geodatabase but older formats may exist as shapefiles. GIS Database 2002-2005: Project Size = 1,898 acres Fort Larned National Historic Site (including the Rut Site) = 705 acres 16 Map Classes 11 Vegetated 5 Non-vegetated Minimum Mapping Unit = ½ hectare is the program standard but this was modified at FOLS to ¼ acre. Total Size = 229 Polygons Average Polygon Size = 8.3 acres Overall Thematic Accuracy = 92% To produce the digital map, a combination of 1:8,500-scale (0.75 meter pixels) color infrared digital ortho-imagery acquired on October 26, 2005 by the Kansas Applied Remote Sensing Program and 1:12,000-scale true color ortho-rectified imagery acquired in 2005 by the U.S. Department of Agriculture - Farm Service Agency’s Aerial Photography Field Office, and all of the GPS referenced ground data were used to interpret the complex patterns of vegetation and land-use. In the end, 16 map units (11 vegetated and 5 land-use) were developed and directly cross-walked or matched to corresponding plant associations and land-use classes. All of the interpreted and remotely sensed data were converted to Geographic Information System (GIS) databases using ArcGIS© software. Draft maps were printed, field tested, reviewed and revised. One hundred and six accuracy assessment (AA) data points were collected in 2006 by KNSHI and used to determine the map’s accuracy. After final revisions, the accuracy assessment revealed an overall thematic accuracy of 92%.

Nielsen PrimeLocation Web and Desktop Software Licensed for Internal Use only: Pop-Facts Demographics Database, Geographic Mapping Data Layers, Geo-Coding locations.