Background

The Tall Timbers (TT) Web GIS is a collection of systems that allows Tall Timbers staff and collaborators to share data; create interactive maps; configure apps; and, conduct common geospatial workflows such as such as basic data collection, editing and reporting.  The two systems that participate in the TT Web GIS are the Tall Timbers Geospatial Data Infrastructure (GDI) and the Tall Timbers ArcGIS Online Organization (AGOL).

 

Though there are numerous methods to create and interact with geospatial content and capabilities within the TT Web GIS, there are only three distinct ways to share the content.  The three ways to share are essentially paths that describe the system(s) where the content originates.  The paths are discussed and explained in the paragraphs below.  Reviewing the descriptions below with an understanding of the project goals and user audience will help determine the most appropriate path to choose.  

 

Access Paths

Depending on the goals and needs of a project and its user audience, content can be shared from AGOL Only; from the GDI Only; or, as a Hybrid solution that uses resources from both AGOL and the GDI.  Each path determines a varying set of characteristics that should be considered when choosing the best way to share content.  These characteristics include: Access to the content (membership/visibility); Functionality (features/capabilities); Scale, Capacity and Reliability.  

 

For example, choosing AGOL Only means the content will have to be shared with Everyone (Public) or, the user audience will have to be members of the Organization’s AGOL account.  Understanding the pros and cons of these access paths are important for anyone planning to share content and interact on the TT Web GIS.  Consult with the IT/GIS Group if you have questions.

AGOL Only https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/31018379406/original/VcDo2C6oFt2nE_lsNtcRQHydzgZ2m37VKw.png?1578595317

  • Access – Membership: Staff must request membership in the Organization’s AGOL account in order to share content.  Contact the Geospatial Database Administrator to request membership.
  • Access - Visibility: If public access to the content is needed, sharing must be set to Everyone.  Otherwise, the audience must belong to an ESRI ArcGIS Online Organization.
  • Functionality: This path provides the richest capabilities as ESRI’s ArcGIS Online environment affords the most up-to-date set of software features.  Options of use are limited by the Organization’s current licensing agreement with ESRI.  Please check with IT/GIS if you have questions.
  • Scale, Capacity and Reliability: ArcGIS Online is a vast cloud-based environment built to support ESRI’s entire client-base and potentially the general public.  
  • Licensing: ESRI’s license agreement caps Tall Timbers to a limited number of role-based users (Viewers, Data Editors, Users, Publishers, and Administrators).  Basic privileges such as viewing data or maps shared as a public resource do not expend any of the Organizations’ licenses, but advanced functionality such as field data collection and editing do require a license. Therefore, in order to share and interact with data that has not been made public, a license is required.
  • Pros and Cons: This path works well for internal or collaborative projects that need a solution for disconnected, mobile data creation and editing.  It also works well for quick web maps and/or basic configurable apps that include public data resources. The cons can include the consumption of limited licenses (credits) depending on the visibility or sharing of the content and the functionality or capability enabled with the content.  Another potential con is the requirement that an ESRI Organizational account is required for any non-public interaction.

 

GDI Only   https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/31018379620/original/GlxL8xGrx-HlGF8rl9rlBlFshwTTBTBoDw.png?1578595827

  • Access – Membership: Staff must request membership in the TT GDI, which is the Organization’s on-premise implementation of ESRI’s ArcGIS Enterprise software.  Contact the Geospatial Database Administrator to request membership.
  • Access - Visibility: If public access to the content is needed, sharing must be set to Everyone.  Otherwise, the audience must also be a member of the GDI.  
  • Functionality: This access path does not provide as rich a set of features as the GDI has been designed as a lean implementation focused on the Organization’s present needs.  However, it still allows for sharing data, creating maps and geospatial apps.  The software is not as current as AGOL, nor are all the possible extensions installed.  ESRI continually improves the features in their AGOL environment before releasing software upgrades to its user base.  Please check with IT/GIS if you have questions.
  • Scale, Capacity and Reliability: The GDI consists of a set of virtualized servers hosted onsite.  The primary server is configured with a base deployment of ESRI’s ArcGIS Enterprise software.  A dedicated data server and web server facilitate development of services and apps.  As mentioned it had been designed to handle TT’s current needs.  As the Organization grows and as grants and collaborations dictate, potentially more resources can be applied to improve its scale, capacity and reliability
  • Licensing: As mentioned before, since ESRI’s license agreement caps Tall Timbers to a limited number of role-based users (Viewers, Data Editors, Users, Publishers, and Administrators) who can interact with either AGOL or the GDI, requests for access must be balanced first against internal staff needs, as the number of staff employees currently outnumbers the number of licenses.
  • Pros and Cons: This path works well for internal projects that need a solution for basic geospatial interaction, such as web maps and apps.  It also works well for quick web maps and/or basic configurable apps that include public data resources.  The Experience Builder component that is built into the GDI provides easy to use configurable apps that can be downloaded and placed on the Organization’s web site.  The cons include concerns about scale, capacity and reliability as the GDI’s resources are limited when compared with commercial implementations that include redundant, high-availability systems.  Another potential con is the requirement that a GDI account is required for any non-public interaction.

 

Hybrid  https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/31018379406/original/VcDo2C6oFt2nE_lsNtcRQHydzgZ2m37VKw.png?1578595317https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/31018379620/original/GlxL8xGrx-HlGF8rl9rlBlFshwTTBTBoDw.png?1578595827

  • Access – Membership: Staff must request membership in both the TT GDI and in the Organization’s AGOL account in order to share content that requires resources from both systems.  Contact the Geospatial Database Administrator to request membership.
  • Access - Visibility: As mentioned for either AGOL Only or GDI Only, if public access to the content is needed, sharing must be set to Everyone.  Otherwise, the conditions of membership for the audience will depend on access restrictions of the content and where it is hosted.  For example, an AGOL web map that includes a web layer from the GDI may require that the audience is also part of the TT AGOL account.  
  • Functionality: This path provides the best of both worlds as any feature not found implemented in the GDI, may potentially be used from AGOL.  There may be limits, however, due to ESRI’s licensing agreement, so check with IT/GIS if you have questions.  
  • Scale, Capacity and Reliability: This path provides the option to leverage AGOL’s vast cloud-based environment when it makes sense.  For example, if a collaborative project requires joint access to data or web maps, these can be hosted from AGOL.  Then, upon completion of the project, final deliverables can be shared from the GDI for use in other internal projects. 
  • Licensing: As mentioned previously, ESRI’s license agreement caps Tall Timbers to a limited number of role-based users (Viewers, Data Editors, Users, Publishers, and Administrators) on both AGOL and the GDI.  Basic privileges such as viewing data or maps shared as a public resource do not expend any of the Organizations’ licenses, but advanced functionality such as field data collection and editing do require a license.  Therefore, in order to share and interact with data that has not been made public, a license is required.  
  • Pros and Cons: This path works well for collaborative projects that involve staff who already belong to an ESRI ArcGIS Online organization.  This path also works well for internal or collaborative projects that need a solution for disconnected, mobile data creation and editing.  It also works well for quick web maps and/or basic configurable apps that include public data resources. The cons can include an increased level of complexity due to the fact that multiple systems are involved in hosting and sharing content.  Documentation and testing are recommended during all phases of the project to make sure all who require access to the content can get to it and interact with it as planned.  As always, the consumption of limited licenses (credits) depending on the visibility or sharing of the content and the functionality or capability enabled with the content may play a part.  Another potential con is the requirement that an ESRI Organizational account is required for any non-public interaction.