Data source
Data from US Bureau of Safety and Environmental Enforcement (BSEE), delivered clean.
1 dataset pulled from US Bureau of Safety and Environmental Enforcement (BSEE)'s releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.
- 1 dataset
- 1 industry
- Real rows on request
What Datadory delivers from US Bureau of Safety and Environmental Enforcement (BSEE)
1BSEE Well API (multiregional online query)
Pick a catch, see the rows.
Name any US Bureau of Safety and Environmental Enforcement (BSEE) dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.
Get a sampleAPI, files, or your warehouse. Daily, weekly, or hourly.
Straight answers about US Bureau of Safety and Environmental Enforcement (BSEE) data
How far back does the history run?
Spud dates reach back to the early 1950s and the earliest completions in the file are dated 1966. That span is what makes lifecycle work possible - Arena Offshore's E006 was spudded in December 1963, reached total depth in February 1964 and was plugged and abandoned in April 1997, all on one row.
Why does location appear twice on every row?
Because offshore, the surface location and the bottomhole location are different facts. Area, block and lease codes come in both flavors - SURF_ and BOTM_ prefixed - with BOTM_FLD_NAME_CD naming the containing field. Directional wells make the distinction load-bearing.
Are there schema quirks worth knowing before modeling?
One, and it is documented up front: BH_TOTAL_MD is typed as text even though its values are numeric strings such as 10930. Datadory casts it correctly in every delivery and names the type in the field dictionary, so your depth histograms do not sort alphabetically.