{
 "currentVersion": 10.91,
 "cimVersion": "2.9.0",
 "id": 180,
 "name": "PIPELINE_COMPANY",
 "type": "Table",
 "description": null,
 "hasAttachments": false,
 "htmlPopupType": "esriServerHTMLPopupTypeNone",
 "displayField": "PL_COMPANY_NAME",
 "typeIdField": null,
 "subtypeFieldName": null,
 "subtypeField": null,
 "defaultSubtypeCode": null,
 "fields": [
  {
   "name": "OBJECTID",
   "type": "esriFieldTypeOID",
   "alias": "OBJECTID",
   "domain": null
  },
  {
   "name": "COMMENTS",
   "type": "esriFieldTypeString",
   "alias": "COMMENTS",
   "length": 255,
   "domain": null
  },
  {
   "name": "CREATED_DATE",
   "type": "esriFieldTypeDate",
   "alias": "CREATED_DATE",
   "length": 8,
   "domain": null
  },
  {
   "name": "CREATED_USER",
   "type": "esriFieldTypeString",
   "alias": "CREATED_USER",
   "length": 50,
   "domain": null
  },
  {
   "name": "DESCRIPTION",
   "type": "esriFieldTypeString",
   "alias": "DESCRIPTION",
   "length": 255,
   "domain": null
  },
  {
   "name": "FROM_DATE",
   "type": "esriFieldTypeDate",
   "alias": "FROM_DATE",
   "length": 8,
   "domain": null
  },
  {
   "name": "IS_OPERATOR",
   "type": "esriFieldTypeString",
   "alias": "IS_OPERATOR",
   "length": 50,
   "domain": {
    "type": "codedValue",
    "name": "WS2_YES_NO_NA_CL",
    "description": "A domain used to store logical answers to Boolean attributes. In some situations a Yes/No answer is not appropriate and two other options are provided - Not Applicable and Unknown. This effectively negates the boolean aspect of the field but there are always situations where the answer is not known (Unknown) and there are occasionally situations where a yes/no answer is not appropriate. Utilizing this domain prevents the addition of fields to account for these situations.",
    "codedValues": [
     {
      "name": "No",
      "code": "No"
     },
     {
      "name": "Not Applicable",
      "code": "Not Applicable"
     },
     {
      "name": "Unknown",
      "code": "Unknown"
     },
     {
      "name": "Yes",
      "code": "Yes"
     }
    ],
    "mergePolicy": "esriMPTDefaultValue",
    "splitPolicy": "esriSPTDuplicate"
   }
  },
  {
   "name": "IS_OWNER",
   "type": "esriFieldTypeString",
   "alias": "IS_OWNER",
   "length": 50,
   "domain": {
    "type": "codedValue",
    "name": "WS2_YES_NO_NA_CL",
    "description": "A domain used to store logical answers to Boolean attributes. In some situations a Yes/No answer is not appropriate and two other options are provided - Not Applicable and Unknown. This effectively negates the boolean aspect of the field but there are always situations where the answer is not known (Unknown) and there are occasionally situations where a yes/no answer is not appropriate. Utilizing this domain prevents the addition of fields to account for these situations.",
    "codedValues": [
     {
      "name": "No",
      "code": "No"
     },
     {
      "name": "Not Applicable",
      "code": "Not Applicable"
     },
     {
      "name": "Unknown",
      "code": "Unknown"
     },
     {
      "name": "Yes",
      "code": "Yes"
     }
    ],
    "mergePolicy": "esriMPTDefaultValue",
    "splitPolicy": "esriSPTDuplicate"
   }
  },
  {
   "name": "LAST_EDITED_DATE",
   "type": "esriFieldTypeDate",
   "alias": "LAST_EDITED_DATE",
   "length": 8,
   "domain": null
  },
  {
   "name": "LAST_EDITED_USER",
   "type": "esriFieldTypeString",
   "alias": "LAST_EDITED_USER",
   "length": 50,
   "domain": null
  },
  {
   "name": "NATIONAL_IDENTIFIER",
   "type": "esriFieldTypeString",
   "alias": "NATIONAL_IDENTIFIER",
   "length": 25,
   "domain": null
  },
  {
   "name": "PL_COMPANY_ACRONYM",
   "type": "esriFieldTypeString",
   "alias": "PL_COMPANY_ACRONYM",
   "length": 10,
   "domain": null
  },
  {
   "name": "PL_COMPANY_NAME",
   "type": "esriFieldTypeString",
   "alias": "PL_COMPANY_NAME",
   "length": 75,
   "domain": null
  },
  {
   "name": "PRESERVE_RELATE_IDENTIFIER",
   "type": "esriFieldTypeGUID",
   "alias": "PRESERVE_RELATE_IDENTIFIER",
   "length": 38,
   "domain": null
  },
  {
   "name": "STATE_OR_PROV_IDENTIFIER",
   "type": "esriFieldTypeString",
   "alias": "STATE_OR_PROV_IDENTIFIER",
   "length": 25,
   "domain": null
  },
  {
   "name": "STATUS",
   "type": "esriFieldTypeString",
   "alias": "STATUS",
   "length": 50,
   "domain": {
    "type": "codedValue",
    "name": "WS2_HISTORIC_STATE_CL",
    "description": "Indicates if the record is the most recent version a feature or event representation. Modern GIS systems support the notion of in-line history where current and historic versions of records are managed in a single table. As these features are updated, the attributes defined by including the HISTORY data type are modified for those features. The FROM_DATE and TO_DATE fields show a life-span of each version of the record. The historical records have both the FROM_DATE and TO_DATE fields set and the STATUS field set to Historic. The current record has the FROM_DATE set, but the TO_DATE field is NULL. The STATUS field is set to Current. As new versions of records are added, the previous version TO_DATE is set to the FROM_DATE of the most recent record. \nA good example of this is changing pipe records to reflect a pipe replacement. This example also brings into play how the LAYER_METADATA table can be used to manage gap and overlap situations. A section of pipeline is removed. In the GIS, the existing pipe segment is split into three pieces and the middle PIPE_SEGMENT record attributes are set as follows: TO_DATE is set to Now and STATUS is set to Historic. For the PIPE_SEGMENT table there is a LAYER_METADATA record set with the following attributes: DEFINITION_QUERY= STATUS=Current, ALLOW_GAP=No, ALLOW_OVERLAP=Yes. If a QA routine is run against the PIPE_SEGMENT layer it will return a gap violation because there is a gap between two active PIPE_SEGMENT records (since the middle record has been set to Historic. A new PIPE_SEGMENT record is inserted with different business attributes (wall thickness, grade etc.) and it fills in the gap between the two active records. The FROM_DATE for this new record is set to Now, and the STATUS is set to Current. There are now four PIPE_SEGMENT records for this pipeline. One is Historic, three are Current. Two are completely coincident with each other but one is the Current record and the other is the Historic record. Now when the QA process is re-run looking for errors in the PIPE_SEGMENT table and neither the gap or overlap situations occur because there are now gaps in Current records and there are no overlaps in Current records.",
    "codedValues": [
     {
      "name": "Current",
      "code": "Current"
     },
     {
      "name": "Historic",
      "code": "Historic"
     },
     {
      "name": "Unknown",
      "code": "Unknown"
     },
     {
      "name": "Verified as unknown",
      "code": "Verified as unknown"
     }
    ],
    "mergePolicy": "esriMPTDefaultValue",
    "splitPolicy": "esriSPTDuplicate"
   }
  },
  {
   "name": "TO_DATE",
   "type": "esriFieldTypeDate",
   "alias": "TO_DATE",
   "length": 8,
   "domain": null
  },
  {
   "name": "UNIQUE_ID",
   "type": "esriFieldTypeGUID",
   "alias": "UNIQUE_ID",
   "length": 38,
   "domain": null
  }
 ],
 "indexes": [
  {
   "name": "FDO_OBJECTID",
   "fields": "OBJECTID",
   "isAscending": true,
   "isUnique": true,
   "description": ""
  },
  {
   "name": "G173UNIQUE_ID",
   "fields": "UNIQUE_ID",
   "isAscending": true,
   "isUnique": false,
   "description": ""
  }
 ],
 "subtypes": [],
 "relationships": [
  {
   "id": 38,
   "name": "Matador.SDE.TANK_TEST_POINT",
   "relatedTableId": 48,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 48,
   "name": "pipeline",
   "relatedTableId": 42,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 49,
   "name": "Matador.SDE.PIPELINE",
   "relatedTableId": 42,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 37,
   "name": "Matador.SDE.TANK_BOTTOM_INSPECTION",
   "relatedTableId": 24,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 42,
   "name": "Matador.SDE.TEST_POINT",
   "relatedTableId": 49,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 6,
   "name": "ownership",
   "relatedTableId": 21,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  },
  {
   "id": 45,
   "name": "Matador.SDE.RECTIFIER",
   "relatedTableId": 23,
   "role": "esriRelRoleOrigin",
   "keyField": "UNIQUE_ID",
   "cardinality": "esriRelCardinalityOneToMany",
   "composite": false
  }
 ],
 "capabilities": "Map,Query,Data",
 "maxRecordCount": 2000,
 "supportsStatistics": true,
 "supportsExceedsLimitStatistics": true,
 "supportsAdvancedQueries": true,
 "supportedQueryFormats": "JSON, PBF",
 "isDataVersioned": false,
 "useStandardizedQueries": true,
 "advancedQueryCapabilities": {
  "useStandardizedQueries": true,
  "supportsStatistics": true,
  "supportsPercentileStatistics": true,
  "supportsHavingClause": true,
  "supportsOrderBy": true,
  "supportsDistinct": true,
  "supportsCountDistinct": true,
  "supportsPagination": true,
  "supportsTrueCurve": false,
  "supportsReturningQueryExtent": true,
  "supportsQueryWithDistance": true,
  "supportsSqlExpression": true,
  "supportsTimeRelation": true,
  "supportsSqlFormat": false,
  "supportsQueryAnalytic": false
 },
 "dateFieldsTimeReference": null,
 "preferredTimeReference": null,
 "datesInUnknownTimezone": false,
 "hasMetadata": true,
 "isDataArchived": false,
 "archivingInfo": {
  "supportsQueryWithHistoricMoment": false,
  "startArchivingMoment": -1
 },
 "serviceItemId": "0b6ea39373374d868246e69ee986e7a0"
}