090°Données ouvertes
Jeux de données ouverts, entièrement documentés — interrogeables ici, et lisibles par n’importe quel LLM.
Les titres et les descriptions proviennent des sources de données, en anglais.
2 jeux de données
Baker Hughes
Weekly rig-count momentum for 26 US states, Canadian provinces and NL Offshore from Baker Hughes' North America Rotary Rig Count report (keyless XLSX, 2024-01-05 -> present), aggregated from the workbook's county x basin x trajectory detail rows. Per state-week: total/oil/gas/misc rigs, week-over-week / 4-week / 52-week changes and YoY percent, a trailing-52-week z-score, a documented 5-state activity_regime classifier, and a documented 0-100 activity_score composite. Who joins this: a sales team joins week_ending + region_code to rep quotas and pipeline to weight energy-region territories (TX, NM, ND, AB) by drilling momentum; a subscription business selling into oilfield services joins churn/expansion to region_code for demand-regime features. Source: Baker Hughes.
Weekly drilling-activity momentum for the USA and Canada from Baker Hughes' North America Rotary Rig Count report (keyless XLSX, 2024-01-05 -> present; ~27k county x basin x trajectory detail rows per vintage aggregated by summation). Per country-week: total/oil/gas/misc rigs, land/offshore/horizontal splits, oil and horizontal shares, week-over-week / 4-week / 52-week changes and YoY percent, a trailing-52-week z-score, a documented 5-state activity_regime classifier, and a documented 0-100 activity_score composite (high = hot and accelerating drilling: a demand tailwind for energy-region businesses). Who joins this: a sales team selling industrial equipment joins weekly rig momentum to territory quotas because the rig count leads oilfield-services demand; an online shop serving energy regions joins week_ending + country_code to weekly demand to model drilling-driven swings. Source: Baker Hughes.
Une fois l’allocation gratuite du jour épuisée, les fonctions d’IA peuvent passer par votre propre compte fournisseur.
Conservée uniquement dans cet onglet (effacée à sa fermeture) et envoyée avec chaque requête d’IA. Nos serveurs l’utilisent pour cette requête et ne la stockent ni ne la journalisent jamais.