PODS for ArcGIS Enterprise

At its most basic level, an ArcGIS geodatabase is a collection of geographic datasets of various types held in a common file system folder, or a multiuser relational database management system such as IBM Db2, Microsoft SQL Server, Oracle, PostgreSQL, or SAP HANA. Geodatabases come in many sizes; have varying numbers of users; and can scale from small, single-user databases built on files up to larger workgroup, department, and enterprise geodatabases accessed by many users.

There are currently three geodatabase implementations for PODS for ArcGIS Enterprise

1.  PODS for ArcGIS Enterprise Standard

The out of the box PODS for ArcGIS solution, this implementation requires only ArcGIS Pro Standard.  ArcGIS Enterprise is not required, nor are any ESRI software extensions.  Pipeline location is managed via an M-aware centerline and events are located by stationing attributes on top of the centerline (as ‘route events’).

Learn more about ESRI linear referencing and route events here.

2.  PODS for ArcGIS Enterprise + ArcGIS Pipeline Referencing (APR)

An expansion of PODS for ArcGIS Enterprise Standard, users can implement PODS with the ESRI ArcGIS Pipeline Referencing extension.  This extension will allow the ESRI platform to manage all centerline and event editing processes.  This version requires ArcGIS Enterprise and the ArcGIS Pipeline Referencing extension.

Learn more about ESRI ArcGIS Pipeline Referencing extension here.

3.  PODS for ArcGIS Enterprise + ArcGIS Pipeline Referencing (APR)/Utility Network

Set for release in 2022, the PODS APR/UN release will combine the centerline and feature management components of the ArcGIS Pipeline Referencing extension with traceability, containers and data integrity management features of the ArcGIS Utility Network extension.  This version requires ArcGIS Enterprise, the ArcGIS Pipeline Referencing extension and the Utility Network extension.

Learn more about ESRI Utility Network extension here.

PODS Relational

The PODS Relational data model requires only out-of-the-box RDMBS technologies for database management environments, such as SQL Server or Oracle.  This non-spatial version of PODS utilized traditional database functions to manage the interrelated entities within PODS, such as primary/foreign keys, database trigger and stored procedures.  Centerline spatial locations are managed through XY coordinate attributes within the model and stationing of features along pipeline routes.

Looking for a previous version of PODS? Please contact us at info@pods.org