1) Use the search tool to find where you go to school or work2) Measure the distance you travel to school or work

Information Lookup is a configurable web application template that can be used to provide the general public, internal staff and other interested parties with information about a location. If no features are found at that location, a general message is displayed. Optionally, the location entered can be stored in a point layer.Configurable OptionsThe template can be configured using the following options:Lookup Layers: One or more polygon layers queried by the location specified. The pop-up defined in these layers combined into a single pop-up and displayed to the user. The layers can either be a feature service layer or a layer that is part of a dynamic map service. Use a vertical bar or pipe (|) to separate this list of layers. It is recommended that these layers visibility is turned off.Pop-up Title: The title of the pop-up when results are returned from one or more of the Lookup Layers.Pop-up Width: The width of the pop-up. pop-up Max Height: The maximum height title of the pop-up.Unavailable pop-up Title: The title of the pop-up when no results are returned from the Lookup Layers.Unavailable pop-up Message: The message to display in the pop-up when no results are returned from the Lookup Layers.Zoom Level for Location: The scale to set the map at when a location is specified.Store Location: Option to store the location specified in a point layer, if checked on, fill out the remaining parameters.Application Title: Enter a custom title for the application.Storage Layer Name: Name of the point feature service layer in the map to store the location. Editing must be enabled on this layer.Storage Layer Field: Field in the Storage Layer to store a value if a result was returned from the Lookup Layers.Yes Value: The value to store in the Storage Layer Field specified above when a result is returned from the Lookup Layers.No Value: The value to store in the Storage Layer Field specified above when no results are returned from the Lookup Layers.Display Splash Screen on Startup: Option to show a splash screen when the app loads.Splash Screen message: The message to display in the splash screen.Splash Screen Theme: The color scheme for the splash screen.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Geoform is a configurable app template for form based data editing of a Feature Service. This application allows users to enter data through a form instead of a map's pop-up while leveraging the power of the Web Map and editable Feature Services. This app geo-enables data and workflows by lowering the barrier of entry for completing simple tasks. Use CasesProvides a form-based experience for entering data through a form instead of a map pop-up. This is a good choice for users who find forms a more intuitive format than pop-ups for entering data.Useful to collect new point data from a large audience of non technical staff or members of the community.Configurable OptionsGeoform has an interactive builder used to configure the app in a step-by-step process. Use Geoform to collect new point data and configure it using the following options:Choose a web map and the editable layer(s) to be used for collection.Provide a title, logo image, and form instructions/details.Control and choose what attribute fields will be present in the form. Customize how they appear in the form, the order they appear in, and add hint text.Select from over 15 different layout themes.Choose the display field that will be used for sorting when viewing submitted entries.Enable offline support, social media sharing, default map extent, locate on load, and a basemap toggle button.Choose which locate methods are available in the form, including: current location, search, latitude and longitude, USNG coordinates, MGRS coordinates, and UTM coordinates.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Basic Viewer is a configurable app template that can be used as a general purpose app for displaying a web map and configuring a variety of tools. This app offers a clean, simple interface that accentuates the web map and includes a toolbar and floating panel.Use CasesDisplays a set of commonly used tools within a floating pane. This is a good choice for balancing the need for a collection of tools while still maximizing the amount of screen real estate dedicated to the map. The app includes the ability to toggle layer visibility, print a map, and show pop-ups in the floating pane.Provides editing capabilities in the context of a general-purpose mapping app. This is a good choice when your audience needs additional tools or information about the map to support their editing activities.Configurable OptionsUse Basic Viewer to present content from a web map and configure it using the following options:Choose a title, sub title, logo, description, and color scheme.Configure a custom splash screen that will display when the app loads.Use custom CSS to customize the look and feel of the app.Enable tools on a toolbar including a basemap gallery, bookmarks, layer list, opacity slider, legend, measure, overview map, etc.Enable an editor tool and an editor toolbar giving users editing capabilities on editable feature layers.Configure a printing tool that can utilize all available print layouts configured in the hosting organization.Configure the ability for feature and location search.Set up custom URL parameters that define how the app and web map appear on load.Supported DevicesThis application is responsively designed to support use in browsers on desktops, mobile phones, and tablets.Data RequirementsThis web app includes the capability to edit a hosted feature service or an ArcGIS Server feature service. Creating hosted feature services requires an ArcGIS Online organizational subscription or an ArcGIS Developer account. Get Started This application can be created in the following ways:Click the Create a Web App button on this pageShare a map and choose to Create a Web AppOn the Content page, click Create - App - From Template Click the Download button to access the source code. Do this if you want to host the app on your own server and optionally customize it to add features or change styling.

Footprint outlines of buildings in New York City. Please see the following link for additional documentation: https://github.com/CityOfNewYork/nyc-geo-metadata/blob/master/Metadata/Metadata_BuildingFootprints.md P Layers are the centroid layers for the Building and Building Historic layers. They contain the same data as those layers but are represented as points instead of polygons. For additional resources, please refer to https://nycmaps-nyc.hub.arcgis.com/search?tags=building&type=feature%2520service%2Cfeature%2520layer

This resources contains PDF files and Python notebook files that demonstrate how to create geospatial resources in HydroShare and how to use these resources through web services provided by the built-in HydroShare GeoServer instance. Geospatial resources can be consumed directly into ArcMap, ArcGIS, Story Maps, Quantum GIS (QGIS), Leaflet, and many other mapping environments. This provides HydroShare users with the ability to store data and retrieve it via services without needing to set up new data services. All tutorials cover how to add WMS and WFS connections. WCS connections are available for QGIS and are covered in the QGIS tutorial. The tutorials and examples provided here are intended to get the novice user up-to-speed with WMS and GeoServer, though we encourage users to read further on these topic using internet searches and other resources. Also included in this resource is a tutorial designed to that walk users through the process of creating a GeoServer connected resource.

The current list of available tutorials: - Creating a Resource - ArcGIS Pro - ArcMap - ArcGIS Story Maps - QGIS - IpyLeaflet - Folium

Vegetative Difference Image gives an easy to interpret visual representation of vegetative increase/decrease across 2 time periods.This raster function template is used to generate a visual product. The results cannot be used for analysis. This templates generates an NDVI in the backend, hence it requires your imagery to have the red and near infrared bands. In the resulting image, greens indicate increase in vegetation, while the magenta indicates decrease in vegetationReferences:Raster functionsWhen to use this raster function templateThis template is particularly useful when trying to intuitively visualize the increase or decrease in vegetation over two time periods. How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. This index supports many satellite sensors, such as Landsat-8, Sentinel-2, Quickbird, IKONOS, Geoeye-1, and Pleiades-1.Applicable geographiesThe template uses a standard vegetation which is designed to work globally.

This mapping tool provides a representation of the general watershed boundaries for stream systems declared fully appropriated by the State Water Board. The boundaries were created by Division of Water Rights staff by delineating FASS critical reaches and consolidating HUC 12 sub-watersheds to form FASS Watershed boundaries. As such, the boundaries are in most cases conservative with respect to the associated stream system. However, users should check neighboring FASS Watersheds to ensure the stream system of interest is not restricted by other FASS listings. For more information regarding the Declaration of Fully Appropriated Stream Systems, visit the Division of Water Rights’ Fully Appropriated Streams webpage. How to Use the Interactive Mapping Tool: If it is your first time viewing the map, you will need to click the “OK” box on the splash screen and agree to the disclaimer before continuing. Navigate to your point of interest by either using the search bar or by zooming in on the map. You may enter a stream name, street address, or watershed ID in the search bar. Click on the map to identify the location of interest and one or more pop-up boxes may appear with information about the fully appropriated stream systems within the general watershed boundaries of the identified location. The information provided in the pop-up box may include: (a) stream name, (b) tributary, (c) season declared fully appropriated, (d) Board Decisions/Water Right Orders, and/or (e) court references/adjudications. You may toggle the FAS Streams reference layer on and off to find representative critical reaches associated with the FASS Watershed layer. Please note that this layer is for general reference purposes only and ultimately the critical reach listed in Appendix A of Water Rights Order 98-08 and Appendix A together with any associated footnotes controls. Note: A separate FAS Watershed boundary layer was created for the Bay-Delta Watershed. The Bay-Delta Watershed layer should be toggled on to check if the area of interest is fully appropriated under State Water Board Decision 1594.

This application is designed to replace website search mechanisms utilizing the County GIS layers and databases in a non-map centric style application. Standalone Parcel Search tool.

The Terrain Ruggedness Index (TRI) is used to express the amount of elevation difference between adjacent cells of a DEM. This raster function template is used to generate a visual representation of the TRI with your elevation data. The results are interpreted as follows:0-80m is considered to represent a level terrain surface81-116m represents a nearly level surface117-161m represents a slightly rugged surface162-239m represents an intermediately rugged surface240-497m represents a moderately rugged surface498-958m represents a highly rugged surface959-4367m represents an extremely rugged surfaceWhen to use this raster function templateThe main value of this measurement is that it gives a relatively accurate view of the vertical change taking place in the terrain model from cell to cell. The TRI provides data on the relative change in height of the hillslope (rise), such as the side of a canyon.How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. The output is a visual TRI representation of your imagery. This index supports elevation data.References:Raster functionsApplicable geographiesThe index is a standard index which is designed to work globally.

Purpose: This is an ArcGIS Pro template that GIS Specialists can use to identify vulnerable populations and special needs infrastructure most at risk to flooding events.How does it work?Determine and understand the Place Vulnerability (based on Cutter et al. 1997) and the Special Needs Infrastructure for an area of interest based on Special Flood Hazard Zones, Social Vulnerability Index, and the distribution of its Population and Housing units. The final product will be charts of the data distribution and a Hosted Feature Layer. See this Story Map example for a more detailed explanation.This uses the FEMA National Flood Hazard Layer as an input (although you can substitute your own flood hazard data), check availability for your County before beginning the Task: FEMA NFHL ViewerThe solution consists of several tasks that allow you to:Select an area of interest for your Place Vulnerability Analysis. Select a Hazard that may occur within your area of interest.Select the Social Vulnerability Index (SVI) features contained within your area of interest using the CDC’s Social Vulnerability Index (SVI) – 2016 overall SVI layer at the census tract level in the map.Determine and understand the Social Vulnerability Index for the hazard zones identified within you area of interest.Identify the Special Needs Infrastructure features located within the hazard zones identified within you area of interest.Share your data to ArcGIS Online as a Hosted Feature Layer.FIRST STEPS:Create a folder C:\GIS\ if you do not already have this folder created. (This is a suggested step as the ArcGIS Pro Tasks does not appear to keep relative paths)Download the ZIP file.Extract the ZIP file and save it to the C:\GIS\ location on your computer. Open the PlaceVulnerabilityAnalysis.aprx file.Once the Project file (.aprx) opens, we suggest the following setup to easily view the Tasks instructions, the Map and its Contents, and the Databases (.gdb) from the Catalog pane.The following public web map is included as a Template in the ArcGIS Pro solution file: Place Vulnerability Template Web MapNote 1:As this is a beta version, please take note of some pain points:Data input and output locations may need to be manually populated from the related workspaces (.gdb) or the tools may fail to run. Make sure to unzip/extract the file to the C:\GIS\ location on your computer to avoid issues.Switching from one step to the next may not be totally seamless yet.If you are experiencing any issues with the Flood Hazard Zones service provided, or if the data is not available for your area of interest, you can also download your Flood Hazard Zones data from the FEMA Flood Map Service Center. In the search, use the FEMA ID. Once downloaded, save the data in your project folder and use it as an input.Note 2:In this task, the default hazard being used are the National Flood Hazard Zones. If you would like to use a different hazard, you will need to add the new hazard layer to the map and update all query expressions accordingly.For questions, bug reports, or new requirements contact pdoherty@publicsafetygis.org

This StoryMap series contains a collection of four Dashboards used to display active project data on the Connecticut road network. Dashboards are used to display Capital Projects, Maintenance Resurfacing Program (MRP) projects, and Local Transportation Capital Improvement Program (LOTCIP) projects, as well as a dashboard to display all data together.Dashboards are listed by tabs at the top of the display. Each dashboard has similar capabilities. Projects are displayed in a zoomable GIS interface and a Project List. As the map is zoomed and the extent changes, the Project List will update to only display projects on the map. Projects selected from the Map or Project List will display a Project Details popup. Additional components of each dashboard include dynamic project counts, a Map Zoom By Town function and a Project Number Search.Capital Project data is sourced from the CTDOT Project Work Areas feature layer. The data is filtered to display active projects only, and categorized as "Pre-Construction" or "Construction." Pre-Construction is defined as projects with a CurrentSchedulePhase value of Planning, Pre-Design, Final Design, or Contract Processing.Maintenance Project data is sourced from the MRP Active feature layer. Central Maintenance personnel coordinate with the four districts to develop an annual statewide resurfacing program based upon a variety of factors (age, condition, etc.) that prioritize paving locations. Active MRP projects are incomplete projects for the current year.LOTCIP Project data is sourced from the CTDOT LOTCIP Projects feature layer. The data updates from LOTCIP database nightly. The geometry of the LOTCIP projects represent the approximate outline of the projects limits and does not represent the actual limits of the projects.

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

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

The Planning and Land Development web experience provides a variety of property-related information such as lot boundaries, subdivisions, zoning district, and land use in East Baton Rouge Parish, Louisiana. Users have the options to turn on other various layers such as overlay districts, council districts, addresses and the tax parcel layer which is provided courtesy of the EBRP Assessor's Office.This application features three web maps including:Planning Cadastral Map at https://ebrgis.maps.arcgis.com/home/item.html?id=43e518581406442990aa676044796418Land Development Application Search Tool at https://ebrgis.maps.arcgis.com/home/item.html?id=c53a5bf66b994005a08978e84fc435d3Planning Reference Map at https://ebrgis.maps.arcgis.com/home/item.html?id=66ed92bfbe7446cabe0129009f8d3848

SearchAreaTheoretical

GIS polylines for Scottish marine protected area search feature species from survey undertaken by Cefas and JNCC in January 2013 at the three Fladen Grounds pMPAs. This was a Scottish Marine Protected Areas (SMPA) site identification survey. The main aims were to confirm the presence of the Priority Marine Features and MPA Search Features recommended for protection within the pMPAs and to gather groundtruth data to compare benthic assemblages between, and within/outside, the sites.

Use the Zone Lookup template to allow users to search for an address or use their current location to identify locations that are within a zone or region. With apps created with this template, users can learn more about a location and features of interest in the surrounding area. Grouping results by layer provides an organized view of search results. You can also include the export tool to capture images of the map with the search results. Examples: Facilitate finding hurricane evacuation zones by address in an emergency. Build an app where users can identify schools within a school district, based on a searched address or location. Provide city planning information by zone or area. Data requirements The Zone Lookup template requires a feature layer to use all of its capabilities. Key app capabilities Results - Customize result panel location information with feature attributes from a configured pop-up. Show selected result only - Display the selected result feature in the map while hiding the other features. Attribute filter - Configure map filter options that are available to or added by app users. Sketch a zone - Enable app users to draw a search zone with sketch tools, including buffer capabilities. Export - Print or export the search results or selected features as a .pdf, .jpg, or .png file that includes the pop-up content of returned features and an option to include the map. Additionally, download the search results as a .csv file. 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.

This index is developed to estimate the chlorophyll content of leaves, using the ratio of reflectivity in the near-infrared (NIR) and red-edge bands. Chlorophyll is a good indicator of the plant’s production potential. It can be also used to understand the plant’s nutrient status, stress due to water, disease outbreak, and more. This raster function template is used to generate a visual representation using CIRE with your data. The results cannot be used for analysis. To use this index, your imagery must have bands that collect data at wavelengths between 710nm and 805nm.References:Chlorophyll Index - Red Edge (CIRE)Raster functionsWhen to use this raster function templateCIRE is useful when working with imagery to determine general health of plants and productions potential. How to use this raster function templateIn ArcGIS Pro, search ArcGIS Living Atlas for raster function templates to apply them to your imagery layer. You can also download the raster function template, attach it to a mosaic dataset, and publish it as an image service. The output is a visual CIRE representation of your imagery. This index supports many satellite sensors, such as Landsat-8, Sentinel-2, and RapidEye.Applicable geographiesThe index is a standard vegetation index which is designed to work globally.