vamseeachanta / energydata

MIT License
0 stars 0 forks source link

BSEE | Additional Data #12

Open vamseeachanta opened 3 weeks ago

vamseeachanta commented 3 weeks ago

a/ Get platform structure. Search by using the Area codes or get all the data in one go. Area codes are given by default in the link below. https://www.data.bsee.gov/Platform/PlatformStructures/Default.aspx

b/ pipeline data. Enter segment 100, 17200 etc. https://www.data.bsee.gov/Pipeline/PipelineLocation/Default.aspx

c/ Lease data and trends by date https://www.data.bsee.gov/Leasing/LeaseAreaBlock/Default.aspx

d/ If data is not too big (define < 10 MB?) , can we read it directly from url.

raw data links: https://www.data.bsee.gov/Main/RawData.aspx

Example code: The library can directly read zip files from github repo?

https://stackoverflow.com/questions/19371860/python-open-file-in-zip-without-temporarily-extracting-it

vamseeachanta commented 3 weeks ago

@samdansk2, please finish d first. a/ Code b/ ZipFile Size (?) Read live and know how much time it takes.

Update the bsee_data_status file accordingly. Send email to below Roy

Dear Roy,

Wanted to give bsee data status update. We have written simple python code to get following data by Well API12 Number. well data, production data, . For a given API12, the code runs in 1 min to get all data. A brief overview is also given in link below: https://github.com/vamseeachanta/energydata/blob/bseedata/docs/bsee_data_status.svg

samdansk2 commented 3 weeks ago

@vamseeachanta you didn't pushed the code from your side sir , please push it, i have to update the bsee_data_status file

vamseeachanta commented 3 weeks ago

Just completed pushing the code. Please update and feel free to send the email update to Roy.

samdansk2 commented 3 weeks ago

Already the status file is good sir , no need to change anything. But the svg diagram has to be updated. Thankyou

vamseeachanta commented 2 weeks ago

Dear All,

The application gets well data the details of which is summarized in below schematic: https://github.com/vamseeachanta/energydata/blob/bseedata/docs/bsee_data_status.png

The sample data (i.e. top 100 rows) is given in below folder: https://github.com/vamseeachanta/energydata/blob/bseedata/src/energydata/tests/test_data/bsee/results/Data

For example, Wellbore Zipfile data: https://github.com/vamseeachanta/energydata/blob/bseedata/src/energydata/tests/test_data/bsee/results/Data/by_zip/BoreholeRawData.csv

Way Forward: a/ SMEs (Subject Matter Experts) to review above data and comment/suggest improvements. b/ SMEs to review any gaps found c/ Vamsee to map the data to previous data analysis scripts to provide insights previously provided d/ Any other?

Thank you

vamseeachanta commented 2 weeks ago
samdansk2 commented 2 weeks ago

@vamseeachanta Extracted all zipfile data sir - BSEE

vamseeachanta commented 2 weeks ago

Roy,

Agree with your approach. We target to get there at the earliest. We will provide an update in a week.

Thank you, Vamsee

On Wed, Nov 6, 2024 at 1:53 PM [roy.shilling@frontierdeepwater.com](mailto:roy.shilling@frontierdeepwater.com) wrote: Guys,

In browsing the data files, it looks like an excellent start. I am wondering if it might be productive in terms of our focus to run the scripts on just one of the developments of interest to us and I am thinking of Jack St Malo since it has been out there so long.

The Jack and St. Malo fields are located in the Walker Ridge area of the Gulf of Mexico. Specifically, the Jack field encompasses Walker Ridge blocks 758 and 759, while the St. Malo field is situated in Walker Ridge block 678.

Offshore Technology

This might give us a good way to focus in our end deliverables as it includes all phases of drilling, completion production, recompletion and adding wells. Also, it will help us figure out how to put the output into a more easily readable and usable format. What do you think?

Roy

vamseeachanta commented 2 weeks ago

@samdansk2 , Target inputs: Main file C:\github\energydata\docs\legacy_bsee\code\ong_field_development\BSEE_analysis.yml

Target Output: energydata\docs\legacy_bsee\results\bseedata\data\app_ong_field_development_Jack.xlsx energydata\docs\legacy_bsee\results\bseedata\data\app_ong_field_development_StMalo.xlsx or refer to JSON files energydata\docs\legacy_bsee\results\bseedata\data\Jack.json

Proposed Architecture: Block -> Get all API12 -> Get detailed data for each API12

samdansk2 commented 1 week ago

@vamseeachanta Hello sir , i have read the input and output files thoroughly please explain briefly next time we meet how to start the above one !

samdansk2 commented 1 week ago

@vamseeachanta Hi sir ,

please see below: https://github.com/vamseeachanta/energydata/tree/f32519dca9c246f13215c4aeeb373a1effb0dfa0/src/energydata/tests/test_data/bsee/results/Data

vamseeachanta commented 1 week ago

Utilize the below process to get APIs for all wells by block. See PUML below. SO, please add test to get API data using the bottom area and bottom block data as shown by this process. https://github.com/vamseeachanta/energydata/blob/bseedata/docs/_lib/bsee_data/bsee_data_by_block.puml

Example 2 input files are: https://github.com/vamseeachanta/energydata/blob/bseedata/src/energydata/tests/test_data/bsee/stmalo_by_block.yml https://github.com/vamseeachanta/energydata/blob/bseedata/src/energydata/tests/test_data/bsee/jack_by_block.yml

samdansk2 commented 1 week ago

@vamseeachanta evrything is going good sir , but you have gave me only 2 block no's and bottom area for Jack and 1 block for Stmalo is it enough ? if not , can i take from wellapi data ?

samdansk2 commented 1 week ago

@vamseeachanta Hello sir ,