How developers and data-product builders use oil & gas storage & transportation data

What you pay instead is engineering attention. The flagship collection is a single 3.08 GB GeoPackage; the time-series source ships as newline-delimited records inside ZIP archives described by a Frictionless manifest; and one product, TankTerminals.com — Global Tank Terminal Directory, publishes its fact sheets only through its own web application with no bulk export. Plan the build around coverage first, plumbing second.

Three of them return current-state geometry on demand:

• TGS US Pipelines ArcGIS Feature Layer — 731,388 US line segments (server-side count run 2026-08-21) carrying roughly 44 fields: operator, system name, commodity code, nominal diameter, liquid and gas capacity, flow direction and an ABANDONED flag, served as ArcGIS JSON, GeoJSON or PBF.
• OpenStreetMap — Pipeline & Storage Facility Features — community-maintained and tag-rich: 867,272 man_made=storage_tank nodes and ways worldwide, 418,492 pipeline-family ways and 99,029 pipeline=* node features (42,777 substations, 31,306 valves, 15,740 markers), returned as JSON, XML, CSV or GeoJSON.
• ENTSOG Transparency Platform — European interconnection-point flows, nominations and technical/available/booked capacity as JSON, CSV or XML, with histories dating back to 2007 — useful when a European gas-storage dashboard needs day-ahead numbers beside its map.

Three collections cover the static map:

• OGIM — Oil and Gas Infrastructure Mapping database (EDF) — the v2.7 release ships as one 3.08 GB GeoPackage (exactly 3,083,259,040 bytes) flanked by two companion PDFs: the README (509 KB) holds the full attribute schema in Supplements 1 and 2, and the source-reference PDF (477 KB) lists all 188 upstream datasets behind the figures.
• HIFLD Petroleum Terminals (POL Terminals) — the authoritative US terminal map: 2,302 operable POL terminals, 50 attributes each. A CONUS clip runs just 39 KB compressed, while the full layer extends to the US Virgin Islands, Puerto Rico, Guam and the Northern Mariana Islands. The current edition revalidated 658 records in August 2025.
• PUDL Raw EIA Bulk API Data (archived snapshots) — v81.0.0 bundles ~1.6 GB across 30 files, led by the 57.5 MB petroleum zip. Its datapackage.json lists byte sizes and md5 hashes for every resource, so your CI can fail loudly on truncated pulls.

Every format here opens with tooling you already run: QGIS, GDAL/OGR, geopandas and plain sqlite3 all read OGIM's GeoPackage natively, and its 16 layers split cleanly by grain — 4,537,369 wells, 1,858,109 LineString pipeline segments totalling more than 1.2 million kilometres, plus three dedicated midstream point layers: Petroleum Terminals (3,661), Crude Oil Refineries (692) and LNG Facilities (547). Common columns (OGIM_ID, CATEGORY, REGION, COUNTRY, STATE_PROV, ON_OFFSHORE) make cross-layer joins a one-line operation,, and the Data_Catalog table flags each upstream source Public or Proprietary.

HIFLD rows behave like address-level facility objects: a TERM_ID following the pattern ANLTK + state FIPS + sequence, a CAPACITY field reporting shell storage in barrels (Pennsylvania samples run from 95,748 barrels at Sunoco Partners' Altoona terminal to 1,440,000 at Gulf Oil's), twelve YES/NO transport-mode flags covering TRUCK, PIPE, MARINE and RAIL in both directions, fourteen product-handling flags from gasoline and distillate to propane, ethanol and avgas, plus SOURCE/VAL_DATE provenance and NAICS 424710 on essentially every row.

TGS's ~44 fields reward a different index: CMDTY_DES decodes commodity codes (CRD maps to CRUDE OIL), DIA_IN carries nominal diameter, CAP_MBBLD and CAP_MMCFD hold liquid and gas capacity, FLOW_DIR distinguishes bidirectional trunk lines, and even ABANDONED segments keep operator, system name and a MOD_DATE stamp formatted YYYYMMDDHHMMSS.

PUDL Raw EIA Bulk API Data is the only deep time-series source in the slice, and its design flatters reproducible pipelines. Weekly lower-48, PADD and state petroleum stocks carry observation histories back to April 2004, and the separate petroleum-imports zip (5.5 MB) details imports at national, PADD, state, city, port and refinery level by crude grade and country of origin. Everything arrives as newline-delimited JSON inside ZIP archives — one line per series with its full history, so a streaming reader ingests without pagination logic.

Four shipping patterns dominate. Market dashboards join OGIM's refinery and LNG point layers with PUDL's weekly stocks so a lower-48 inventory chart sits beside the infrastructure that moves it. Logistics and pricing tools lean on HIFLD's terminal attributes — barrel capacity, twelve transport-mode flags, fourteen product-handling flags — to answer which Gulf Coast terminals can receive a given grade by barge rather than pipe. Monitoring products watch TGS's segment layer and Overpass for change along named corridors, using the operator and MOD_DATE fields to surface new construction. And risk models fold TankTerminals.com's berth and throughput fact sheets for 13,000+ facilities across 2,420 ports into port-level congestion scoring.

Ranked by what a shipping product gets per unit of integration effort, using Datadory's quality scores and delivery formats:

A workable reference stack, using only sources named above:

Start with the oil gas storage transportation data guide, which scores all 8 pooled datasets by quality, coverage and delivery format. Then take the builder view further: the developers builders use cases page ranks this slice by relevance to engineering work, the oil-gas-storage-transportation data hub holds per-source metadata in one table, and the best oil-gas-storage-transportation datasets list shortlists where to start. For the deepest head-to-head in the slice, see how OGIM — Oil and Gas Infrastructure Mapping database (EDF) stacks up against the PUDL archive on coverage and granularity.