Pre-Plans: Managing ArcGIS Layers

Pre-Plans: Managing ArcGIS Layers

Purpose Statement

  1. The ArcGIS layer management feature within the Web Responder module allows authorized users to add, configure, and manage various types of ArcGIS mapping layers to enhance situational awareness and operational capabilities. This functionality enables integration of public resources, shared organizational data, and protected third-party mapping services to provide comprehensive geographic information for emergency response operations.

Background Information

  1. ArcGIS layer management is essential for fire departments and EMS agencies that require specialized mapping data beyond standard base maps. Common use cases include adding weather overlays, hazmat facility locations, hydrant systems, utility infrastructure, traffic cameras, and jurisdictional boundaries. The system supports four distinct layer types to accommodate various data sources and security requirements, from publicly available resources to protected organizational data requiring authentication credentials.

Required Permissions

  • ArcGIS Layers: Allows user to Setup, Manage & Configure which REST service layers can be used with ArcGIS Maps within First Due.

Video



Step-by-Step Guide

1.  After logging in to your First Due account, select the ArcGIS button in the lower left section of the page. The map layer will switch from Google Maps to ArcGIS.







2.  Next, select the Layers  icon.  Then scroll down to the bottom of the list and select Manage Layers.






3. The list of previously added ArcGIS layers will appear. Select New Layer.






Alert
There are four (4) options for adding ArcGIS layers:
  1. Is a public resource
  2. Is a shared resource with the ArcGIS Online portal FDSU account
  3. Is a protected resource hosted on ArcGIS portal
  4. Is a protected resource hosted on a third-party organization's serve


4.  "Is a public resource". This layer type requires the following:
  1. The public URL for the layer (must be exact URL).
  2. The Display Name (the name you'd like to give the layer).





5.  "Is a shared resource with the ArcGIS Online portal FDSU account". This layer type requires the following elements:
  1. The URL for the layer (must be exact URL).
  2. The Display Name (the name you'd like to give the layer).
Notes
This layer type is used whenever an an agency wishes to share a non-public layer in their ArcGIS account with First Due's ArcGIS Online account. The agency wishing to share a layer will need to create a "group" in their ArcGIS account. The agency will then add layer(s) to that group.  Then the agency will share that group with the First Due ArcGIS Online Account using the information proved below.
Alert
IMPORTANT: The agency sharing their ArcGIS layer(s) will need the names of the First Due's ArcGIS accounts:
fdsustartup
appdev_fdsu




6.  "Is a protected resource hosted on ArcGIS portal". This layer is used whenever a client wishes to add a protected resource hosted on the ArcGIS portal. This layer type requires the following elements:
  1. The URL for the layer  (must be exact URL).
  2. The Display Name (the name you'd like to give the layer).
  3. The ArcGIS Online User Name.
  4. The ArcGIS Online Password.






7.  Is a protected resource hosted on a third-party organization's server. This layer is used whenever a client wishes to add a protected resource hosted on third party's organization's server. This layer type requires the following elements:
  1. The URL for the layer (must be exact URL).
  2. The Display Name (the name you'd like to give the layer).
  3. The ArcGIS Enterprise User Name.
  4. The ArcGIS Enterprise Password.
  5. Endpoint to Authenticate (this may not be required; confirm with the third-part organization).
  6. Select "No referer". If you have any authentication issues, and then please contact your Client Success Manager.






8.  When finished adding a layer, select Save.






9.  When finished managing layers, select Finish.





Best Practices

Do's

  • Verify URLs are exact and complete before saving layer configurations
  • Test new layers immediately after adding them to confirm functionality
  • Document layer sources and purposes for future reference and troubleshooting
  • Coordinate properly with sharing agencies for shared resource setup
  • Keep authentication credentials secure and up-to-date
  • Contact your Client Success Manager when experiencing persistent issues

Don'ts

  • Don't assume URLs will work without testing - always verify exact formatting
  • Don't share authentication credentials unnecessarily or store them insecurely
  • Don't add duplicate layers that might cause confusion or performance issues
  • Don't forget to complete prerequisite steps for shared resources
  • Don't ignore authentication issues - use "No Referer" option when needed

Tips

  • Work closely with third-party organizations to understand their specific authentication requirements
  • Keep a record of layer URLs and credentials in a secure location for future updates
  • Test layers during different operational scenarios to ensure consistent performance
  • Consider the impact of multiple layers on system performance and user interface clarity
  • Establish a regular review process to ensure layers remain current and functional

Troubleshooting & FAQs

Q: My layer URL isn't working even though it looks correct. What should I check?
A: Ensure the URL is the exact, complete URL including all parameters. Even small differences can prevent proper layer loading.

Q: How do I know if a layer requires authentication?
A: If the layer is not publicly accessible and requires login credentials when accessed directly, it will need authentication setup in First Due.

Q: The shared resource setup seems complex. Can you simplify the process?
A: The sharing agency must: 1) Create a group, 2) Add layers to the group, 3) Share the group with First Due's ArcGIS account. Contact your Client Success Manager for detailed coordination assistance.

Q: I'm getting authentication errors with a third-party resource. What should I try?
A: First, verify all credentials are correct. Then try selecting "No Referer" option. If issues persist, contact both the third-party organization and your Client Success Manager.

Q: Can I edit or remove layers after adding them?
A: Layer management capabilities may vary. Check the manage layers interface for edit/remove options, or contact your system administrator.

Q: How many layers can I add to the system?
A: While there may not be a strict limit, consider system performance and user interface clarity when adding multiple layers.


Related Articles

  1. Web Responder: ArcGIS Features
  2. Pre-Plans: Map Overview


    • Related Articles

    • Pre-Plans: Map Overview

      Purpose Statement The Pre-Plans Map section within the Pre-Plans module provides users with a comprehensive geographic view of occupancies and related emergency response resources. This feature combines mapping capabilities with pre-plan data to ...
    • Pre-Plans: Managing Attachments

      Purpose Demonstrate how to manage, add and delete attachments to a Pre-Plan. Video Managing Attachments to a Pre-Plan. 1. Access the desired Pre-plan to edit. 2. Once in edit mode for a Pre-Plan, select the Attachments Tab. 3. The attachments can be ...
    • Web Responder: ArcGIS Features

      Purpose To give an overview of using the ArcGIS map in the Responder view. Video Overview 1. Navigate to the Responder Module and select the Responder view. 2. The responder view may default to Google Maps. To Ensure that you are in the ArcGIS map ...
    • Pre-Plans 201

      First Due Academy: Pre-Plans 201 This training session dives into the features and functionality within First Due's Pre-Incident Planning Module. In 201 level sessions we review advanced features of First Due modules including data gathering, ...
    • Pre-Plans 101

      First Due Academy: Pre-Plans 101 This training session dives into the features and functionality within First Due's Pre-Incident Planning Module. In 101 level sessions we review fundamental module navigation, demonstrate common use cases, offer ...