20231102
13161100
1.0
FALSE
NPMS_Pipelines
-158.129812
-65.999092
17.981603
71.305246
1
002
Projected
GCS_North_American_1983
Linear Unit: Foot (0.304800)
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/2.9.0'><WKT>PROJCS["NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",13123359.58005249],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-84.36666666666666],PARAMETER["Standard_Parallel_1",42.1],PARAMETER["Standard_Parallel_2",43.66666666666666],PARAMETER["Latitude_Of_Origin",41.5],UNIT["Foot",0.3048],AUTHORITY["EPSG",2253]]</WKT><XOrigin>-107138600</XOrigin><YOrigin>-97193800</YOrigin><XYScale>3048</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.01</MTolerance><HighPrecision>true</HighPrecision><WKID>2253</WKID><LatestWKID>2253</LatestWKID></ProjectedCoordinateSystem>
NAD_1983_StatePlane_Michigan_South_FIPS_2113_Feet_Intl
FGDC CSDGM Metadata
20231102
13284100
20231102
13284100
150000000
5000
FGDC
Nathaniel Thompson
U.S. Dept. Of Transportation - Pipeline and Hazardous Materials Safety Administration
GIS Coordinator
202-843-3818
1200 New Jersey Ave., S.E.
Washington
DC
20590
US
nathaniel.thompson@dot.gov
20231102
ArcGIS Metadata
1.0
NPMS_Pipelines
2023-02-22T00:00:00
U.S. Dept. of Transportation - Pipeline and Hazardous Materials Safety Administration
vector digital data
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The National Pipeline Mapping System (NPMS) includes a geographic information system (GIS) dataset containing the location and selected attributes of gas transmission and hazardous liquid pipelines, liquefied natural gas (LNG) plants and breakout tanks (BOT) under jurisdiction of the Pipeline and Hazardous Materials Safety Administration (PHMSA). Effective October 1, 2015, pipeline and LNG plant data is collected annually from pipeline operators as required by 49 CFR §§ 191.29 and 195.61. This metadata is for the national pipeline dataset. There is NPMS pipeline data for all 50 states as well as the District of Columbia and Puerto Rico. The NPMS pipeline dataset contains gas transmission and hazardous liquid pipelines subject to regulations from PHMSA. The NPMS pipeline dataset does not contain gas gathering, gas distribution, or hazardous liquid lines not subject to 49 CFR § 195.61 and can never be used in place of contacting a one call center prior to digging. </SPAN></P><P><SPAN>Distribution of NPMS data in GIS format is handled for PHMSA by the National Repository and is limited to pipeline operators and local, state, tribal, and federal government officials and is subject to data access limitations and agreements. Fulfillments of data requests will include data only for the area of jurisdiction of the person requesting the data (data requests are fulfilled per county/counties, state, or the entire U.S.). Instructions for requesting NPMS data in a GIS format are outlined on the NPMS website at www.npms.phmsa.dot.gov.</SPAN></P></DIV></DIV></DIV>
The National Pipeline Mapping System (NPMS) datasets are used to support the assessment of risk associated with the nation's hazardous liquid and gas pipeline infrastructure.
Nathaniel Thompson
U.S. Dept. Of Transportation - Pipeline and Hazardous Materials Safety Administration
GIS Coordinator
202-843-3818
1200 New Jersey Ave., S.E.
Washington
DC
20590
US
nathaniel.thompson@dot.gov
8am - 5pm EST
Leigha Gooding
U.S. Dept. Of Transportation - Pipeline and Hazardous Materials Safety Administration
GIS Manager
202-366-0667
1200 New Jersey Ave., S.E.
Washington
DC
20590
US
leigha.gooding@dot.gov
8:30am - 6pm EST
Gas Transmission
Hazardous Liquid
Pipelines
ISO 19115 Topic Categories
transportation
transportation
Gas Transmission
Hazardous Liquid
Pipelines
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The NPMS pipeline GIS data is Controlled Unclassified Information (CUI). It is available to pipeline operators and local, state, tribal, and federal government officials by request. Requests for GIS data from the NPMS should follow instructions on the NPMS website at www.npms.phmsa.dot.gov. Pipeline operators will only be provided data they contributed, while government officials will be provided data for their area of jurisdiction at a county, state, or federal level. Several considerations govern the display of static maps containing data derived from the NPMS. Static maps that are accessible/distributed outside of your governmental agency are restricted to displaying NPMS data for a single county and at a scale no larger than 1:24,000. Static maps distributed within your agency or displayed on websites with restricted access for government employees may display NPMS data at a scale larger than 1:24,000 and may include data for more than one county; however, such maps must be marked with the text "CUI". NPMS GIS data may not be included on a web, tablet, or mobile application or viewer unless consent is obtained from PHMSA's GIS Manager. U.S. Department of Transportation's Pipeline and Hazardous Materials Safety Administration thanks government officials for exercising good judgment and recognizing that maintaining the security of NPMS data promotes public safety. This NPMS data is confidential and protected from FOIA disclosure due to the security sensitive nature of the data. It is not to be shared with anyone without express permission from U.S. Department of Transportation's Pipeline and Hazardous Materials Safety Administration (PHMSA). By using this data, you agree to the following: I understand that PHMSA's National Pipeline Mapping System (NPMS), established pursuant to 49 U.S.C. 60132, is a Federal information system that contains sensitive information, access to which is restricted by Federal law (44 U.S.C. 3545(f) and FIPS PUB 200, Sec. 3). I understand that the NPMS information system remains under the exclusive control of PHMSA and that PHMSA's granting of conditional access to NPMS does not render the NPMS or any information contained therein Federal or State property or permit it to be integrated into the Federal or State records system. PHMSA may revoke my NPMS privilege at any time and any records or information obtained from NPMS must be returned to PHMSA upon request. I understand that any requests by third parties for access to the NPMS information system or records derived from NPMS must be referred to the PHMSA Associate Administrator for Pipeline Safety. Notwithstanding the above, if any record derived from NPMS should ever be deemed subject to Federal or State public records laws for whatever reason, the record will be protected to the fullest extent permitted by law.</SPAN></P></DIV></DIV></DIV>
Esri ArcGIS 12.9.7.32739
-158.129812
-65.999092
17.981603
71.305246
0.000000
1000000000.000000
The NPMS pipeline dataset represents pipeline data submitted to PHMSA by regulated pipeline operators in order to stay in compliance with 49 CFR §§ 192.29 and 195.61. Operators are required to make an updated data submission every year to account for changes in operational status (date received recorded in Submission Date attribute field), or to review their previous NPMS submission and confirm that it still accurately represents operations as of the previous year (date confirmed recorded in Revision Date attribute field when a new data submission was not necessary). Data submissions acceptable for use in the NPMS are due each year on March 15 for gas transmission pipelines and LNG plants, and June 15 for hazardous liquid pipelines. To align with operator submitted Annual Reports to PHMSA, NPMS submissions always represent operations as of December 31 of the year prior to the data segment’s last update. Always reference the Revision Date field to determine the currentness of that data segment record. For instance, a data segment record with a Revision Date from June 2021 will represent operational status of that pipeline as of 12/31/2020. Operator submission data undergoes significant quality checks and processing prior to incorporation into the NPMS database and these activities are performed continually throughout the year, which means any version of the NPMS pipeline dataset will contain data submissions representing operations during more than one year. PHMSA publishes an updated NPMS pipeline dataset with all recently-processed and incorporated annual data submissions approximately every two-to-three months. The final annual update which incorporates all acceptable NPMS data submissions received during a calendar year is generally available the following March, but outdated pipeline data from non-compliant operators may be retained in the pipeline dataset rather than removed during enforcement procedures; this is why you may see certain pipeline segments with a Revision Date from more than two years ago. You can view the NPMS Submission and Compliance Status for any gas transmission or hazardous liquid pipeline operator from the operator's dashboard by going to the public PHMSA Portal Operator Search at https://portal.phmsa.dot.gov/analytics/saw.dll?Portalpages.
2004-12-03T00:00:00
2023-02-22T00:00:00
0.000000
1000000000.000000
Distribution Liability: Due to security issues, NPMS data can only be released to pipeline operators and certified local, state, tribal, and federal government officials. Use at your own risk. NPMS data have been compiled by the United States Department of Transportation, Pipeline and Hazardous Materials Safety Administration as part of the NPMS. The data is compiled from annual contributions made by the pipeline operators and is processed by private contractors. Neither the United States Government nor any party involved in the creation and compilation of NPMS data guarantees the accuracy or completeness of the product. NPMS data should be considered no more accurate than ±500 feet and must never be used as a substitute for contacting the appropriate local "one-call" center prior to digging.
1
-158.129812
-65.999092
71.305246
17.981603
During the submission processing stage, operator submissions are subject to thorough review to ensure attribute values logically align with pipeline geometries, pipeline operational changes identified since the previous year, and with other records held at and submitted to PHMSA, such as National Registry Notifications, Annual Reports, Accident Reports and Inspection records. Each incoming pipeline segment is matched and compared to its existing counterpart pipeline segment from the previous year to identify and review every change. Every divestiture, acquisition, new pipeline or removal of a pipeline is validated through communication with stakeholders and corroboration though other records. If National Repository GIS analysts identify any logical inconsistencies, they document the discrepancy, provide artifacts and contact the pipeline operator to request clarifications or corrections not only to their NPMS submission data, but also across other PHMSA records as necessary. NPMS Submissions are not accepted by PHMSA and incorporated into the NPMS database, and operators do not meet compliance with the NPMS related federal safety regulations, until they resolve all issues identified by National Repository GIS analysts. The National Repository is also responsible for ensuring that all geospatial data are complete and correctly projected to the proper geodetic datum. Positional accuracy of +/- 500 feet is the maximum permitted per the NPMS National Data Standards. Data users can view the Quality Code attribute to identify the operator reported spatial accuracy for each pipeline segment.
The NPMS includes pipeline data for all 50 US states as well as the District of Columbia and Puerto Rico. The NPMS pipeline dataset contains gas transmission and hazardous liquid pipelines subject to reporting regulations from the Pipeline and Hazardous Materials Safety Administration (PHMSA) per 49 CFR §§ 192.29 and 195.61. The NPMS pipeline dataset does not contain gas gathering, gas distribution, or hazardous liquid lines not subject to 49 CFR § 195.61 and can never be used in place of contacting a one call center prior to digging. National Repository GIS analysts verify each submitted dataset for completeness according to NPMS standards and by validating mileages and certain attributes against separate reporting methods. As well, through change detection processes National Repository GIS analysts identify and seek validation and collaborating records for every new pipeline or a pipeline that an operator tries to remove through their annual NPMS submittal. The repository checks to ensure that all submissions include the required geospatial data, attribute data, metadata and contact information appropriate for use in the NPMS.
The NPMS National Repository checks all entities and their attribute data for compliance with NPMS data standards.
During the submission stage, operator submissions are subject to automated validation ensuring that only valid attribute values and combinations are used. During submission review by NPMS National Repository GIS analysts, attributes are further reviewed to ensure logical compliance with observed pipeline network changes and other PHMSA information collections, including certain elements on Annual Reports to PHMSA.
NPMS pipeline data is submitted to PHMSA’s NPMS National Repository by pipeline operators subject to 49 CFR §§ 192.29 and 195.61. This includes all gas transmission and hazardous liquid pipeline operations, including both interstate and intrastate operations but excluding all gas gathering, gas distribution and non-jurisdictional hazardous liquid operations.
National Pipeline Mapping System Pipelines
NPMS Pipelines
2023-02-22T00:00:00
Various
withheld
The NPMS data compilation process begins when a pipeline operator submits data to the National Repository. In total there are six major steps in the NPMS process that prepares this data file: 1. Operator Submission. The process starts when an operator prepares required NPMS submission components appropriate for use in the NPMS based on the NPMS national standards, and submits them through the Operator Submission and Validation Environment (OSAVE; https://www.npms.phmsa.dot.gov/AboutOSAVE.aspx). OSAVE allows operators to run QC scripts that automatically check data attribute structures, values and relationships against the NPMS national standards and returns a report outlining which fields and records contain errors. OSAVE will not accept an NPMS submission that does not pass all attribute validation checks at this stage. The NPMS national standards accept a range of GIS and non-GIS data formats and OSAVE is designed to assess and reject unacceptable or incomplete files. OSAVE also includes a questionnaire that collects detailed information from the pipeline operator to compile operator submission level metadata, answers to questions and collection of auxiliary data and files to support the National Repository GIS analysts’ quality control and processing activities, such as reporting previous or new operator contacts when sales or acquisitions have taken place to support our validation activities. 2. Submission Review and Processing. National Repository GIS analysts collect and review the components of every incoming submission through OSAVE; store the files together in a dedicated submission folder; log the submission and critical details about the submission into the submission tracking database; and review related notes, submission metadata, operator compliance and error history, and PHMSA inspection and reporting records to build a custom QC routine aimed to identify key changes expected in this operator’s submission. Depending on the incoming data file format, additional processing may be necessary to prepare required GIS data formats, apply correct projections and transformations, integrate the attributes with the spatial features and load the submission into a staging database. In addition to performing the custom QC routines, many standardized QC routines confirm each NPMS pipeline data submission meets all NPMS national standards, logical expectations, and that all changes are validated and corroborated with records. Additional data fields and spatial analysis are performed during these steps. Errors or concerns are thoroughly documented and delivered to the pipeline operator for resolution, often including inspection staff from federal or state level pipeline safety agencies. Once all issues are resolved or clarified the data submission is ready for incorporation activities into the Linearl Referencing System (LRS) database. 3. Change Detection and Other LRS Data Integration and Maintenance Activities. The National Repository GIS analysts use customized change detection and review applications to match every incoming pipeline segment to its appropriate counterpart in the existing NPMS pipeline dataset, or determine when a new segment should be added or a segment removed because it no longer represents a pipeline subject to 49 CFR §§ 192.29 and 195.61. Once the National Repository GIS analyst is satisfied with the change detection result completeness and accuracy the incoming operator data submission is incorporated into the national NPMS LRS database. Many activities are performed at this stage to update the national LRS pipeline centerline, build spatialized history and establish many events in the LRS database, including those for spatializing inspection and accident records. One of our established spatialized views, (called derived layers) in the LRS database is designed to fulfil all NPMS pipeline GIS data requests. Others support various web mapping applications with the same pipeline centerline but different events necessary to meet application requirements. 4. Final Stakeholder Review. Once an NPMS pipeline submission is fully incorporated into the NPMS database the operator is notified so they can use the Data Review functionality within OSAVE to review their final data submission and a variety of attribute and mileage summarizations to help them identify potential errors. In the rare occasion an error is identified in this final review the operator notifies the NPMS National Repository GIS analysts who apply corrected to the NPMS database. 5. Final QC of the Data Request Data Source. Since the database is running through a queue of National Repository GIS analyst approved updates and triggering event creations and building derived layers every night, a copy of the NPMS GIS data request derived layer is pulled from the LRS database approximately every 2-3 months. National Repository GIS analysts apply additional QC measures and review database logs to ensure there were no errors during the data load, event creation or dynamic segmentation activities, and store this derived layer to support all NPMS data requests fulfilled until the next data pull approximately 2-3 months later. This metadata document is updated for each data pull so the user can always identify the exact data pull that supplied their NPMS GIS data request. 6. Fulfilling the NPMS GIS Data Request. Once National Repository GIS analysts receive a complete and verified data request per the instructions available on the NPMS website at www.npms.phmsa.dot.gov, they use attribute selections to extract the pipeline segments that PHMSA can release, based on the requester’s validated area of jurisdiction (for local, state, tribal or federal government applicants) or operations (for pipeline operators). Based on the request, that data is compiled in an ESRI Shapefile or Peronsal Geodatabase format with metadata and documentation regarding data use restrictions. Data is delivered to applicants through a secure FTP sent to their government or pipeline operator email address. While waiting for a data request to be fulfilled, anyone can use the NPMS Public Map Viewer (https://www.npms.phmsa.dot.gov/AboutPublicViewer.aspx) to view the same pipelines on a map showing one county at a time, scales no larger than 1:24,000, and elimination of sensitive attributes (including Diameter and Quality Code). Users cannot download NPMS GIS data from the Public Map Viewer or any NPMS web mapping application.
2023-02-22T00:00:00
U.S. Dept. of Transportation - Pipeline and Hazardous Materials Safety Administration
2023660667
1200 New Jersey Ave., S.E.
Washington
DC
20590
0
NPMS_Pipelines
Polyline of pipeline segments
Pipeline Segment Attribute Table
Feature Class
0
CMDTY_DTL3
Commodity Detail 3. Abbreviation for the primary commodity's third subcategory detail. This is not a required attribute value. This value will only be populated if more than 2 Commodity Details apply to the pipeline segment.
OPERATOR
CRW, CRR, RGS, RFD, RKJ, OTR, ETB, BDB, OBI, NG1, NG2, NG3, NG4
These values are valid ONLY when COMMODITY = “CRD”: CRW = sweet crude; CRR = sour crude. These values are valid ONLY when COMMODITY = PRD: RGS = refined non-ethanol blended gasoline; RFD = refined fuel oil, diesel; RKJ = refined kerosene, jet fuel; OTR = other refined and/or non-HVL petroleum products; ETB = ethanol blended gasoline; BDB = biodiesel blend; OBI = other biofuels. These values are valid ONLY when COMMODITY = “NG”: NG1 = pipeline quality or tariff quality natural gas; NG2 = wet but non-sour natural gas; NG3= sour but non-wet natural gas; NG4 = wet, sour natural gas
NPMS
CMDTY_DTL3
String
3
0
0
COMMODITY
Commodity. Abbreviation for the primary commodity carried by the pipeline
OPERATOR
CRD, PRD, AA, LPG, NGL, OHV, CO2, ETH, EPL, NG, PG, SG, HG, OTG, EPG
CRD = crude oil; PRD = non-HVL product; AA = anhydrous ammonia; LPG = liquefied petroleum gas; NGL = natural gas liquids; OHV = other HVLs; CO2 = carbon dioxide; ETH = fuel grade ethanol; EPL = abandoned pipelines that previously transported a liquid; NG = natural gas; PG = propane gas; SG = synthetic gas; HG = hydrogen gas; OTG = other gas; EPG = abandoned pipelines that previously transported a gas
NPMS
COMMODITY
String
3
0
0
SUB_DATE
Submission Date. Identifies the date in which the NPMS National Repository received the pipeline data submission. A submission received during 2021 reflects operations in the field as of December 31, 2020.
NPMS
Date
N/A
NPMS
SUB_DATE
Date
8
0
0
QUALITY_CD
Quality Code. Operator's estimate of the positional accuracy of the submitted pipeline data
OPERATOR
E, V, G, P, U
E = Excellent (within 50ft), V = Very Good (50-300ft), G = Good (301-500ft), P = Poor (501-1000ft), U = Unknown
NPMS
QUALITY_CD
String
1
0
0
LOW_STRESS
Low Stress. Designator to identify if the hazardous liquid pipeline segment is a low stress pipeline. Value is required for liquid in-service pipelines. If the hazardous liquid pipeline segment operates at 20% or less of SMYS, the segment is a low stress pipeline. Field is empty for gas pipelines or liquid pipelines which are idle, abandoned, or retired.
OPERATOR
N, Y
N = No (pipeline is not low stress), Y = Yes (pipeline is low stress), <NULL> = this attribute does not apply to this line.
NPMS
LOW_STRESS
String
1
0
0
REVIS_DATE
Revision Date. Use this field to determine the currentness of the pipeline segment. For example, if the Revision Date reflects 2021, the pipeline data segment reflects operations in the field as of December 31, 2020. More specifically, the Revision Date identifies the date in which the NPMS National Repository received the pipeline data submission or a confirmation that no changes are necessary to the existing data in order to reflect operations as of December 31 of the previous year (referred to as a no change notification). If the operator submits new data for the year, this date will be the same as the Submission Date value. If an operator submits a notification of no change for the pipeline rather than new data, the date will reflect the receipt of the notification while the Submission Date will reflect the last date the data changed through a data submission.
NPMS
Date
N/A
NPMS
REVIS_DATE
Date
8
0
0
OS_ST_FIPS
Offshore State FIPS Code. Identifies the state by the 2-digit Federal Information Processing Standard (FIPS) code for the state in which the pipeline line segment is located. State FIPS code determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureaus County TIGER/Shapefile. If a pipeline line segment is offshore, the OS_ST_FIPS value will be 99.
NPMS
2-digit text value established by U.S. government
Refer to the internet, such as EPA's Envirofacts, for information regarding specific FIPS code values
NPMS
OS_ST_FIPS
String
2
0
0
CNTY_MIXED
County Name. Identifies the Name of the county in which the pipeline segment is located in a mix of upper and lower case letters. County Name determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureau's County TIGER/Shapefile.
NPMS
Free text
Any string 30 characters in length
NPMS
CNTY_MIXED
String
30
0
0
SUBMIT_ID
Submission ID. Internal tracking value used by NPMS National Repository GIS Analysts to reflect which pipeline data submission included this pipeline data segment. The Submission ID value is a combination of the submitting pipeline operator’s Operator ID value, and a unique identifier for that year's data submission.
NPMS
Free text
Any string 12 characters in length
NPMS
SUBMIT_ID
String
12
0
0
CNTY_FIPS
County FIPS code. Identifies the county by the 5-digit Federal Information Processing Standard (FIPS) code for the county and state in which the pipeline line segment is located. The first two digits represent the state; the last 3 represent the county. County FIPS code determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureau's County TIGER/Shapefile.
NPMS
5-digit text value established by U.S. government
Refer to the internet, such as EPA's Envirofacts, for information regarding specific FIPS code values
NPMS
CNTY_FIPS
String
5
0
0
ST_FIPS
State FIPS Code. Identifies the state by the 2-digit Federal Information Processing Standard (FIPS) code for the state in which the pipeline line segment is located. State FIPS code determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureau's County TIGER/Shapefile.
NPMS
2-digit text value established by U.S. government
Refer to the internet, such as EPA's Envirofacts, for information regarding specific FIPS code values
NPMS
ST_FIPS
String
2
0
0
CMDTY_GEN
General Commodity Type. Specifies whether pipeline segment carries gas or hazardous liquid commodities. Calculated by NPMS National Repository GIS analysts based on COMMODITY field
NPMS
GAS, LIQUID
GAS = gas transmission general commodity (applies to the following COMMODITY values: NG; PG; SG; HG; OTG; EPG) ; LIQUID = hazardous liquid general commodity (applies to the following COMMODITY values: CRD; PRD; AA; LPG; NGL; OHV; CO2; ETH; EPL)
NPMS
CMDTY_GEN
String
16
0
0
MILES
Miles. Length in miles of the line segment calculated in Albers Equal Area Conic North America, NAD83.
NPMS
0.00005 - 999999.99999
Any real 6 characters in length with 5 decimals
NPMS
MILES
Double
8
38
8
OPER_NM
Operator Name. Name of the company that operates the pipeline, as assigned to the Operator ID in PHMSA records.
NPMS
Free text
Any string 40 characters in length
PHMSA
OPER_NM
String
100
0
0
PLINE_ID
Pipeline ID. Unique identifier for a specific pipeline within a pipeline system.
OPERATOR
Free text
Any string 20 characters in length
NPMS
PLINE_ID
String
20
0
0
STATUS_CD
Status Code. Identifies the current operational status of the pipeline segment.
OPERATOR
I, D, B, R
I = in service; D = idle; R = retired; B = permanently abandoned (I, D, and R are all subcategories of an active pipeline as defined by PHMSA)
NPMS
STATUS_CD
String
1
0
0
DIAMETER
Diameter. Nominal diameter of the pipeline, in inches. This is not a required attribute value.
OPERATOR
1 - 99999.99
Any real 5 characters in length with 2 decimals
NPMS
DIAMETER
Double
8
38
8
OS_YN
Offshore. Designator to identify whether a pipeline segment location is estimated as being offshore. Offshore is determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureau’s County TIGER/Shapefile with additional estimates to represent inland waters. The inland water boundaries are not a legal or accurate boundary, they are estimates to support NPMS data comparisons.
NPMS
N, Y
N = No (pipeline segment is estimated as onshore), Y = Yes (pipeline segment is estimated as offshore)
NPMS
OS_YN
String
3
0
0
SUBSYS_NM
Subsystem Name. Name for a smaller sub-section of a pipeline system. A subset of SYS_NM. This is not a required attribute value.
OPERATOR
Free text
Any string 40 characters in length
NPMS
SUBSYS_NM
String
40
0
0
OPID
Operator ID. Accounting number assigned by the PHMSA to the company that operates the pipeline. This value can be used to access other records from the PHMSA website about this pipeline operator.
NPMS
00001 - 99999
Any number 5 characters in length
PHMSA
OPID
Integer
4
10
0
REVIS_CD
Revision Code. Identifies the type of revision that applied to this pipeline segment during submission processing. NPMS National Repository GIS Analysts use this attribute value to verify changes to the national pipeline dataset.
OPERATOR
A, C, J, S, T, B, N
A=addition to the NPMS, C=addition due to construction, J=addition due to mileage which is new to PHMSAs gas transmission or hazardous liquid reporting jurisdiction, S=spatial modification to the previous pipeline data segment, T=attribute modification to the previous pipeline data segment, B=both a spatial and attribute modification to the previous pipeline data segment, N=no change to the previous pipeline data segment.
NPMS
REVIS_CD
String
1
0
0
Shape
Feature geometry.
Esri
Coordinates defining the features.
Shape
Geometry
8
0
0
OBJECTID
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
OBJECTID
OID
4
10
0
CMDTY_DTL1
Commodity Detail 1. Abbreviation for the primary commodity's first subcategory detail. This is not a required attribute value.
OPERATOR
CRW, CRR, RGS, RFD, RKJ, OTR, ETB, BDB, OBI, NG1, NG2, NG3, NG4
These values are valid ONLY when COMMODITY = “CRD”: CRW = sweet crude; CRR = sour crude. These values are valid ONLY when COMMODITY = PRD: RGS = refined non-ethanol blended gasoline; RFD = refined fuel oil, diesel; RKJ = refined kerosene, jet fuel; OTR = other refined and/or non-HVL petroleum products; ETB = ethanol blended gasoline; BDB = biodiesel blend; OBI = other biofuels. These values are valid ONLY when COMMODITY = “NG”: NG1 = pipeline quality or tariff quality natural gas; NG2 = wet but non-sour natural gas; NG3= sour but non-wet natural gas; NG4 = wet, sour natural gas
NPMS
CMDTY_DTL1
String
3
0
0
ST_MIXED
State Name. Identifies the name of the state in which the pipeline segment is located in a mix of upper and lower case letters. State name determined by NPMS National Repository GIS Analysts through an intersection with the US Census Bureau's County TIGER/Shapefile.
NPMS
Free text
Any string 30 characters in length
NPMS
ST_MIXED
String
30
0
0
SYS_NM
System Name. Name of a single pipeline or a grouping of pipelines that function as a whole.
OPERATOR
Free text
Any string 40 characters in length
NPMS
SYS_NM
String
40
0
0
CMDTY_DTL2
Commodity Detail 2. Abbreviation for the primary commodity's second subcategory detail. This is not a required attribute value. This value will only be populated if more than 1 Commodity Detail applies to the pipeline segment.
OPERATOR
CRW, CRR, RGS, RFD, RKJ, OTR, ETB, BDB, OBI, NG1, NG2, NG3, NG4
These values are valid ONLY when COMMODITY = “CRD”: CRW = sweet crude; CRR = sour crude. These values are valid ONLY when COMMODITY = PRD: RGS = refined non-ethanol blended gasoline; RFD = refined fuel oil, diesel; RKJ = refined kerosene, jet fuel; OTR = other refined and/or non-HVL petroleum products; ETB = ethanol blended gasoline; BDB = biodiesel blend; OBI = other biofuels. These values are valid ONLY when COMMODITY = “NG”: NG1 = pipeline quality or tariff quality natural gas; NG2 = wet but non-sour natural gas; NG3= sour but non-wet natural gas; NG4 = wet, sour natural gas
NPMS
CMDTY_DTL2
String
3
0
0
CMDTY_DESC
Commodity Description. Descriptive information of the commodities carried by the pipeline. This is not a required attribute value.
OPERATOR
Free text
Any string 40 characters in length
NPMS
CMDTY_DESC
String
40
0
0
INTERSTATE
Interstate. Designator to identify whether a pipeline is an interstate pipeline according to federal code and regulations.
OPERATOR
N, Y
N = No (pipeline is intrastate), Y = Yes (pipeline is interstate)
NPMS
INTERSTATE
String
1
0
0
Shape.STLength()
Shape.STLength()
Double
0
0
0
Enterprise Geodatabase Feature Class
dataset
EPSG
5.3(9.0.0)
Simple
FALSE
0
TRUE
TRUE