Wellbore DDMS Data Loader issueshttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues2022-12-13T08:25:26Zhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/1Setup CI automated testing and linting (flake8) and add a simple unit test.2022-12-13T08:25:26ZGreg HarrisSetup CI automated testing and linting (flake8) and add a simple unit test.This story is to setup the basic development infrastructure for the LAS data loader. It includes
- Creating the folder structure within the repository. (eg src and test folders)
- Setting up pipenv.
- Creating a simple unit test.
- Addin...This story is to setup the basic development infrastructure for the LAS data loader. It includes
- Creating the folder structure within the repository. (eg src and test folders)
- Setting up pipenv.
- Creating a simple unit test.
- Adding an automated test pipeline to gitlab that runs the simple unit test.
- Adding static analysis (linting) to the automated build pipeline (flake8)M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/4Wrapper for web client calls to insert data into OSDU storage.2022-12-13T08:25:26ZGreg HarrisWrapper for web client calls to insert data into OSDU storage.The wrapper class is intended to help support execution of the LAS uploader using OSDU cloud storage or writing to a local file system. It should also enable writing end to end unit tests.
This could include a simple write to file syst...The wrapper class is intended to help support execution of the LAS uploader using OSDU cloud storage or writing to a local file system. It should also enable writing end to end unit tests.
This could include a simple write to file system class.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/2Add class that loads and validate LAS file.2022-12-13T08:25:26ZGreg HarrisAdd class that loads and validate LAS file.Add a class that uses the LASIO parser to load the las file.
https://lasio.readthedocs.io/en/latest/
Add basic validation to ensure that the well name is populated.
Add unit tests for the new functionality.Add a class that uses the LASIO parser to load the las file.
https://lasio.readthedocs.io/en/latest/
Add basic validation to ensure that the well name is populated.
Add unit tests for the new functionality.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/5Wrapper for web client class to load file data from an OSDU cloud instance.2022-12-13T08:25:25ZGreg HarrisWrapper for web client class to load file data from an OSDU cloud instance.The wrapper class is intended to help support execution of the LAS uploader using OSDU cloud storage or loading from a local file system. It should also enable writing end to end unit tests.
This could include a simple load LAS from loc...The wrapper class is intended to help support execution of the LAS uploader using OSDU cloud storage or loading from a local file system. It should also enable writing end to end unit tests.
This could include a simple load LAS from local file file system class.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/14Add Class to map LAS data object to Well Log object2022-12-13T08:25:25ZNiall McDaidAdd Class to map LAS data object to Well Log objectAdd a class to covert the LAS data object output by LASIO to one or more OSDU Well Log objects.
Add unit tests for the class.Add a class to covert the LAS data object output by LASIO to one or more OSDU Well Log objects.
Add unit tests for the class.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/6Implement basic command line interface support.2022-12-13T08:25:25ZGreg HarrisImplement basic command line interface support.Implement basic command line interface support, take inspiration from Equinor CLI (https://github.com/equinor/osdu-cli).
At this stage we should be able to wire up the components and create an application that runs on the local file syst...Implement basic command line interface support, take inspiration from Equinor CLI (https://github.com/equinor/osdu-cli).
At this stage we should be able to wire up the components and create an application that runs on the local file system.
- Load local LAS file, output to well log/well bore file.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/3Add Class to map LAS data object to Wellbore object.2022-12-13T08:25:26ZGreg HarrisAdd Class to map LAS data object to Wellbore object.Add a class to covert the LAS data object output by LASIO to a OSDU Well Bore object.
Add unit tests for the class.Add a class to covert the LAS data object output by LASIO to a OSDU Well Bore object.
Add unit tests for the class.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/7Support for file download using OSDU SDK.2022-12-13T08:25:27ZGreg HarrisSupport for file download using OSDU SDK.Implement a class that can retrieve LAS files from OSDU storage using the OSDU SDK.
- Add a command line flag to allow users to access this functionality.
- At this stage we will need to tackle authentication against OSDU.
* This assume...Implement a class that can retrieve LAS files from OSDU storage using the OSDU SDK.
- Add a command line flag to allow users to access this functionality.
- At this stage we will need to tackle authentication against OSDU.
* This assumes we have a valid token we can use to call the OSDU API.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/8Support for well bore and logs upload using OSDU SDK.2022-12-13T08:25:26ZGreg HarrisSupport for well bore and logs upload using OSDU SDK.Write classes that use the OSDU SDK to upload Well Bore and Well log objects to an OSDU cloud instance.
Add a command line option to support this.Write classes that use the OSDU SDK to upload Well Bore and Well log objects to an OSDU cloud instance.
Add a command line option to support this.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/9Add support for well bore/log download from an OSDU cloud instance.2022-12-13T08:25:27ZGreg HarrisAdd support for well bore/log download from an OSDU cloud instance.Write classes that allow Well Bore and Well Logs to be downloaded from OSDU.
- Get well bore
- Get Well log
- Get bulk log data
Add command line options to support this.
Test by writing data to OSDU and pulling it back.Write classes that allow Well Bore and Well Logs to be downloaded from OSDU.
- Get well bore
- Get Well log
- Get bulk log data
Add command line options to support this.
Test by writing data to OSDU and pulling it back.M9 - Release 0.12https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/10Multi file parse/load support.2022-12-13T08:25:26ZGreg HarrisMulti file parse/load support.Add support for loading multiple LAS files into OSDU.
- Determine if input path is file or folder.
- List contents of folder.
- Process file in folder one by one, on error log and continue.
- Add some logging capability the Knack packag...Add support for loading multiple LAS files into OSDU.
- Determine if input path is file or folder.
- List contents of folder.
- Process file in folder one by one, on error log and continue.
- Add some logging capability the Knack package has logging support built in.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/11Support install and deployment of the application2022-12-13T08:25:26ZGreg HarrisSupport install and deployment of the applicationNot sure at this stage whether we will need to compile to an executable or create a python installer.
Plan to duplicate the deployment approach of https://github.com/equinor/osdu-cliNot sure at this stage whether we will need to compile to an executable or create a python installer.
Plan to duplicate the deployment approach of https://github.com/equinor/osdu-cliM9 - Release 0.12https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/12Log family recognition2022-12-13T08:25:25ZChad LeongLog family recognitionAs a user, I to perform some enrichment (e.g. log family recognition) on my well log record.
## Example
1. Fetch well log record with `GET {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{record_id}"`
2. User perform enrichment process...As a user, I to perform some enrichment (e.g. log family recognition) on my well log record.
## Example
1. Fetch well log record with `GET {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{record_id}"`
2. User perform enrichment process with the curve data in the well log ([log recognition](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/master/docs/log_recognition/log-recognition.md))
* `POST {BaseUrl}/api/os-wellbore-ddms/log-recognition/family`
3. Log family in the well log record is updated from the response with they following key:
`curve["LogCurveFamilyID"] = f"{data_partition_id}:reference-data--LogCurveFamily:{family_id}:`
4. Update the well log record with the new family ID.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/15Writing bulk data into wellbore DDMS2022-12-13T08:25:26ZChad LeongWriting bulk data into wellbore DDMSAs a user, I want to be able to write the curve data into the Wellbore DDMS.
This can be done using the following endpoint where `welllog_id` is the record created through parsing of the LAS file or user supplied.
`POST {BaseUrl}/api/o...As a user, I want to be able to write the curve data into the Wellbore DDMS.
This can be done using the following endpoint where `welllog_id` is the record created through parsing of the LAS file or user supplied.
`POST {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{welllog_id}/data`M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/16LAS Output from bulk data ingested in wellbore DDMS2022-12-13T08:25:26ZChad LeongLAS Output from bulk data ingested in wellbore DDMSAs a user, I want to be able to retrieve the ingested bulk data from the wellbore DDMS and write it out as .LAS file.
User will provide an array of curves that he wishes to fetch.
`curves=DEPT,DT,PHI`
This can be done with the followi...As a user, I want to be able to retrieve the ingested bulk data from the wellbore DDMS and write it out as .LAS file.
User will provide an array of curves that he wishes to fetch.
`curves=DEPT,DT,PHI`
This can be done with the following endpoint:
`GET {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{welllog_id}/data?describe=false{curves}`
Once the data is retrieved, the data can be output as a LAS file through lasio.LASFile() method.
Headers information needs to be constructed based on the well log record.M9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/17Get log header info for retrieving bulk data2022-12-13T08:25:25ZChad LeongGet log header info for retrieving bulk dataAs a user, I want to be able to see what curves are available in the ingested well log before retrieving them.
This can be done through this API
`GET {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{welllog_id}/data?describe=true`
The...As a user, I want to be able to see what curves are available in the ingested well log before retrieving them.
This can be done through this API
`GET {BaseUrl}/api/os-wellbore-ddms/ddms/v3/welllogs/{welllog_id}/data?describe=true`
The results will return all the curve data availableM9 - Release 0.12Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/18Acceptance test2022-12-13T08:25:26ZChad LeongAcceptance testTo test the end to end workflow for
1. Data Loading
2. Data retrievalTo test the end to end workflow for
1. Data Loading
2. Data retrievalM9 - Release 0.12Chad LeongChad Leonghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/19Update record mapper to handle reference curve ID2021-10-07T08:38:37ZNiall McDaidUpdate record mapper to handle reference curve ID1) Update the record mapper to pull the reference curve ID from the LAS file (it is the first curve) instead of taking it from the configuration.
2) Remove the reference curve ID from the configuration requirements.1) Update the record mapper to pull the reference curve ID from the LAS file (it is the first curve) instead of taking it from the configuration.
2) Remove the reference curve ID from the configuration requirements.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/20Allow use of environment variable for storing access token2021-11-16T05:06:06ZNiall McDaidAllow use of environment variable for storing access tokenThis Item has been extended.
It is currently not ideal having to provide the API bearer token as an argument in its full form for CLI commands.
Adapt to allow for the token to be set as an environment variable - either use a default to...This Item has been extended.
It is currently not ideal having to provide the API bearer token as an argument in its full form for CLI commands.
Adapt to allow for the token to be set as an environment variable - either use a default token env variable or allow it to be specified on the command line.
**E.g.**
`set token "some_token_string"`
`python -m lascli list curves -c "path/to/config.json" -u "https://osdu-ship.msft-osdu-test.org" --welllog_id "some_welllog_id_string" --verbose -t $token`
There are a number of arguments on the command line that could be consolidated.
- The base URL could go into the config file.
- There could be a default config file path.
- There could be a default token environment variable name.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/21TypeError: 'type' object is not subscriptable2021-11-09T07:43:17ZChad LeongTypeError: 'type' object is not subscriptableThis error is observed when Python 3.8 is used instead of 3.9.
```
(env) C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src>pipenv run python -m lascli fileload -h
Courtesy Notice: Pipenv found itself running wi...This error is observed when Python 3.8 is used instead of 3.9.
```
(env) C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src>pipenv run python -m lascli fileload -h
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
'type' object is not subscriptable
Traceback (most recent call last):
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\invocation.py", line 153, in execute
parsed_args = self.parser.parse_args(args)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\parser.py", line 260, in parse_args
return super().parse_args(args)
File "C:\Python38\lib\argparse.py", line 1768, in parse_args
args, argv = self.parse_known_args(args, namespace)
File "C:\Python38\lib\argparse.py", line 1800, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
File "C:\Python38\lib\argparse.py", line 1988, in _parse_known_args
positionals_end_index = consume_positionals(start_index)
File "C:\Python38\lib\argparse.py", line 1965, in consume_positionals
take_action(action, args)
File "C:\Python38\lib\argparse.py", line 1874, in take_action
action(self, namespace, argument_values, option_string)
File "C:\Python38\lib\argparse.py", line 1159, in __call__
subnamespace, arg_strings = parser.parse_known_args(arg_strings, None)
File "C:\Python38\lib\argparse.py", line 1800, in parse_known_args
namespace, args = self._parse_known_args(args, namespace)
File "C:\Python38\lib\argparse.py", line 2006, in _parse_known_args
start_index = consume_optional(start_index)
File "C:\Python38\lib\argparse.py", line 1946, in consume_optional
take_action(action, args, option_string)
File "C:\Python38\lib\argparse.py", line 1874, in take_action
action(self, namespace, argument_values, option_string)
File "C:\Python38\lib\argparse.py", line 1044, in __call__
parser.print_help()
File "C:\Python38\lib\argparse.py", line 2494, in print_help
self._print_message(self.format_help(), file)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\parser.py", line 247, in format_help
self.cli_help.show_help(self.prog.split()[0],
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\help.py", line 728, in show_help
else self.group_help_cls(self, delimiters, parser)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\help.py", line 253, in __init__
child.load(options)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\help.py", line 198, in load
description = getattr(options, 'description', None)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\parser.py", line 240, in __getattribute__
self.description = self._description() \
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\commands.py", line 261, in description_loader
return extract_full_summary_from_signature(CLICommandsLoader._get_op_handler(operation))
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env\lib\site-packages\knack\commands.py", line 274, in _get_op_handler
op = import_module(mod_to_import)
File "C:\Python38\lib\importlib\__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 783, in exec_module
File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src\lasloader\commands\file_load.py", line 5, in <module>
from lasloader.file_loader import LasParser, LocalFileLoader
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src\lasloader\file_loader.py", line 49, in <module>
class JsonLoader:
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src\lasloader\file_loader.py", line 57, in JsonLoader
def load(self, path: str) -> dict[str, any]:
TypeError: 'type' object is not subscriptable
```Greg HarrisNiall McDaidGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/22Data loading - Allow user to provide welllog ID and writing bulk data to that...2021-10-18T13:30:16ZChad LeongData loading - Allow user to provide welllog ID and writing bulk data to that welllog id### Description
Currently we allow two scenarios for users to create welllog bulk data.
1. User wants to create a new wellbore record, new welllog record and load the bulk data.
2. User already ingested wellbore record, welllog record....### Description
Currently we allow two scenarios for users to create welllog bulk data.
1. User wants to create a new wellbore record, new welllog record and load the bulk data.
2. User already ingested wellbore record, welllog record. User will provide the welllog record id and only want to write bulk data directly to the already ingested welllog record id.
This issue is about the scenario 2.
![image](/uploads/524c595851d392e566cec01d71e6a4ae/image.png)
### Steps
1. User provide welllog id
2. Retrieve the welllog record, and wellbore record and check for available curves.
3. Retrieve well name / UWI from wellbore record.
4. Parse LAS for validation, check if well name or UWI exists, check if curves exist in LAS.
5. If all check passed, write bulk data with the provided welllog id.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/23Search for ingested wellbore ID to avoid duplicate wellbore record ID2021-10-26T09:52:09ZChad LeongSearch for ingested wellbore ID to avoid duplicate wellbore record IDCurrently, user is allowed to create a new wellbore record based on the LAS information.
However, there are cases where the same wellbore contains multiple well log files. In this scenario, we do not want to create multiple wellbores th...Currently, user is allowed to create a new wellbore record based on the LAS information.
However, there are cases where the same wellbore contains multiple well log files. In this scenario, we do not want to create multiple wellbores that are the same.
This issue addresses the scenario described above by using search API prior to creating a new wellbore record.
1) Parse LAS for well name
2) Run search API (api/search/v2/query) to check for ingested Wellbore with a body.
E.g. Searching for Wellbore name NPD-2105.
```json
{
"kind": "*:*:master-data--Wellbore:*",
"query": "data.FacilityName:\"NPD-2105\"",
"limit": 100
}
```
3) If wellbore already exists, uses that existing wellbore record ID for the welllog reference.
4) If search returns null, create a new wellbore record ID.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/24Capability to update an existing welllog with recognized curve families2021-10-25T14:45:47ZGreg HarrisCapability to update an existing welllog with recognized curve familiesAs a user I want to be able to update my existing welllog with recognized curve families.
To do this the id field (welllog id) of the record will need to be populated and sent as part of the post request.
This is an extension of [Issue...As a user I want to be able to update my existing welllog with recognized curve families.
To do this the id field (welllog id) of the record will need to be populated and sent as part of the post request.
This is an extension of [Issue 12](https://community.opengroup.org/osdu/platform/data-flow/data-loading/wellbore-ddms-las-loader/-/issues/12)Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/25TypeError: Object of type WellboreRecord is not JSON serializable2021-10-20T10:01:20ZChad LeongTypeError: Object of type WellboreRecord is not JSON serializableAfter ingesting a LAS file with ```python -m lascli ingest wellbore```
I try to list it with ```python -m lascli list wellbore```.
I got the following error:
```
Getting wellbore ID opendes:master-data--Wellbore:4e34b3136c4d4b09b6609b...After ingesting a LAS file with ```python -m lascli ingest wellbore```
I try to list it with ```python -m lascli list wellbore```.
I got the following error:
```
Getting wellbore ID opendes:master-data--Wellbore:4e34b3136c4d4b09b6609b969c59e9db
Object of type WellboreRecord is not JSON serializable
Traceback (most recent call last):
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env39\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env39\lib\site-packages\knack\invocation.py", line 223, in execute
cmd_result = parsed_args.func(params)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env39\lib\site-packages\knack\commands.py", line 146, in __call__
return self.handler(*args, **kwargs)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\env39\lib\site-packages\knack\commands.py", line 253, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "C:\Users\cleong4\OneDrive - Schlumberger\OSDU\wellbore-ddms-las-loader\src\lasloader\commands\list_osdu.py", line 27, in wellbore
print(json.dumps(wellbore, indent=4, sort_keys=True))
File "C:\Python39\lib\json\__init__.py", line 234, in dumps
return cls(
File "C:\Python39\lib\json\encoder.py", line 201, in encode
chunks = list(chunks)
File "C:\Python39\lib\json\encoder.py", line 438, in _iterencode
o = _default(o)
File "C:\Python39\lib\json\encoder.py", line 179, in default
raise TypeError(f'Object of type {o.__class__.__name__} '
TypeError: Object of type WellboreRecord is not JSON serializable
```Greg HarrisNiall McDaidGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/26Add logging for `fileload convert` command2021-10-21T11:25:39ZNiall McDaidAdd logging for `fileload convert` commandThere is currently no logging for this command so it is unclear when it has finished or what it has done.There is currently no logging for this command so it is unclear when it has finished or what it has done.M9 - Release 0.12Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/27Setup distribution via Package & registries (look left)2021-11-16T11:56:46ZGreg HarrisSetup distribution via Package & registries (look left)Setup distribution via PyPI
- We will need a project
- We will need user accounts.
All this is subject to approval from @chad.
It may be that there are already official OSDU accounts/projects/subscriptions we should use these if we canSetup distribution via PyPI
- We will need a project
- We will need user accounts.
All this is subject to approval from @chad.
It may be that there are already official OSDU accounts/projects/subscriptions we should use these if we canhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/28Improve documentation2022-08-23T15:55:56ZGreg HarrisImprove documentationWe should provide A few worked examples on how to load a LAS file into the the system, list, query its contents. For a case where a wellbore does not exist and the wellbore does existWe should provide A few worked examples on how to load a LAS file into the the system, list, query its contents. For a case where a wellbore does not exist and the wellbore does existhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/32Renaming project title to wellbore-ddms-data-loader2022-08-23T13:29:49ZChad LeongRenaming project title to wellbore-ddms-data-loaderAs we are expanding our loader to support different data types - LAS, WITSML, etc. We should consider renaming the project to reflect that.As we are expanding our loader to support different data types - LAS, WITSML, etc. We should consider renaming the project to reflect that.https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/33No module named 'colorama'. User has to manually install that package separat...2021-12-01T10:28:26ZChad LeongNo module named 'colorama'. User has to manually install that package separately.Issue reported by Stephen Gallant from Katalyst.
After installing lascli, an errored out with: No module named 'colorama'. So I installed that separately, then it worked.
The module should be included as part of the package.Issue reported by Stephen Gallant from Katalyst.
After installing lascli, an errored out with: No module named 'colorama'. So I installed that separately, then it worked.
The module should be included as part of the package.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/34Missing PATH entry2022-08-23T13:29:51ZChad LeongMissing PATH entryReported by Stephen Gallant from Katalyst.
On install, it did give me several warnings on missing PATH entry to:
C:\Users\user\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\S...Reported by Stephen Gallant from Katalyst.
On install, it did give me several warnings on missing PATH entry to:
C:\Users\user\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\Scripts
But runs ok after adding this to PATH.Stephen GallantNiall McDaidStephen Gallanthttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/36Investigate custom schema best way forward2022-08-23T13:29:49ZChad LeongInvestigate custom schema best way forwardInvestigate custom schema best way forward for implementingInvestigate custom schema best way forward for implementingGreg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/38Trajectory data loader from WITSML format2022-12-01T21:17:04ZDebasis ChatterjeeTrajectory data loader from WITSML formatWITSML Parser handles only catalog data.
The "ask" here is to populate station data (depth, md, inclination angle, Azimuth...) into Wellbore DDMS.
Support of V2.0 and V1.4.WITSML Parser handles only catalog data.
The "ask" here is to populate station data (depth, md, inclination angle, Azimuth...) into Wellbore DDMS.
Support of V2.0 and V1.4.https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/40lascli ingest wellbore command errors out when running against a folder conta...2022-08-23T13:29:51ZStephen Gallantlascli ingest wellbore command errors out when running against a folder containing multiple LAS filesFor example:
lascli ingest wellbore -p "C:\folder_containing_many_LAS_files" -c config.json -t token
Will error like:
Type List cannot be instantiated; use list() insteadFor example:
lascli ingest wellbore -p "C:\folder_containing_many_LAS_files" -c config.json -t token
Will error like:
Type List cannot be instantiated; use list() insteadNiall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/41Rename 'lasloader' package and any associated references in repo2022-01-17T11:10:47ZNiall McDaidRename 'lasloader' package and any associated references in repoRelated to #32
Now the repo has been renamed to 'data loader' it would make sense to rename the package from 'lasloader' to something else.
There are lots of other references to specifically LAS throughout the repo ('lasloader' and 'la...Related to #32
Now the repo has been renamed to 'data loader' it would make sense to rename the package from 'lasloader' to something else.
There are lots of other references to specifically LAS throughout the repo ('lasloader' and 'lascli' being the most obvious) - these would also all need to be changed to remain consistent.
Things to do:
* Rename source code folders (packages)
* Rename lascli filename.
* Update the build and publish pipeline
* Fix comments in code.
* Update documentation.
* Test it all still works.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/43Rename 'fileload' command to 'parse' to remove ambiguity2022-08-23T13:29:49ZChad LeongRename 'fileload' command to 'parse' to remove ambiguityThe `lasloader` package has a command line interface called `lascli` which has the general syntax:
* `fileload`: Dry run of the ingest command, instead of uploading data to the OSDU instance it creates json files for the wellbore and we...The `lasloader` package has a command line interface called `lascli` which has the general syntax:
* `fileload`: Dry run of the ingest command, instead of uploading data to the OSDU instance it creates json files for the wellbore and welllog.
The fileload commands parses a LAS file and generates the manifest for users to QC the data.
As a user, this command might imply the action is also loading the data to OSDU instance.
We want to change it to 'parse' for less ambiguity in the action of the command.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/45Soft mapping of Las data to osdu wellbore and welllog objects2022-08-23T13:29:50ZGreg HarrisSoft mapping of Las data to osdu wellbore and welllog objectsCurrently the mapping from las files to osdu objects is hard coded. This needs to be soft coded in order to support custom headers.
Data mappings should be read from file and look something like this:
```
{
"kind": "osdu:wks:work-pro...Currently the mapping from las files to osdu objects is hard coded. This needs to be soft coded in order to support custom headers.
Data mappings should be read from file and look something like this:
```
{
"kind": "osdu:wks:work-product-component--WellLog:1.1.0",
"mapping":
{
"acl.viewers": "CONFIG.data_default_viewers",
"acl.owners": "CONFIG.data_default_owners",
"legal.legaltags": "CONFIG.legal_tags",
"legal.otherRelevantDataCountries": "CONFIG.legal_relevant_data_countries",
"legal.status": "CONFIG.legal_status",
"data.ReferenceCurveID": "las.curves[0].mnemonic",
"data.WellboreID": {
"type": "function",
"function": "get_wellbore_id",
"args": []
},
"data.Curves": {
"type": "array",
"source": "las.curves",
"mapping": {
"CurveID": "mnemonic",
"Mnemonic": "mnemonic",
"CurveUnit": {
"type": "function",
"function": "las2osdu_curve_uom_converter",
"args": [
"CONFIG.data_partition_id",
"mnemonic"
]
}
}
}
}
}
```
This is an example of how a mapping from LAS to a welllog could be achieved.
Reverse mappings from OSDU to LAS will be considered in a future change.Greg HarrisGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/46Write System Maintenance guide2022-08-23T13:29:50ZGreg HarrisWrite System Maintenance guideWrite System Maintenance guide to support handover of DDMS loader.Write System Maintenance guide to support handover of DDMS loader.Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/48Restructure repository folder structure2022-03-21T09:44:42ZNiall McDaidRestructure repository folder structurePlaces modules into better defined folders, representing the layers of the application as defined in the SMGPlaces modules into better defined folders, representing the layers of the application as defined in the SMGM11 - Release 0.14Niall McDaidNiall McDaidhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/49Failed to ingest LAS data when UWI is empty or not present2023-03-15T19:24:31ZDipika KheraFailed to ingest LAS data when UWI is empty or not presentFailed to ingest LAS data using `wbdutil` when Well Name present but UWI is empty.
the one which is not working -
```
WELL. 15/9-F-15 : WELL
UWI. : UNIQUE WELL ID
```
other which is working -
```
WELL . ...Failed to ingest LAS data using `wbdutil` when Well Name present but UWI is empty.
the one which is not working -
```
WELL. 15/9-F-15 : WELL
UWI. : UNIQUE WELL ID
```
other which is working -
```
WELL . NO_15/9-F-5: WELL
UWI . 15/9-F-5: UNIQUE WELL ID
```
**Error Logs:**
![image](/uploads/ac43b2c384455580edfb7bb627ad7a9f/image.png)
FYI: @chadGreg HarrisNiall McDaidGreg Harrishttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/52Add Csp Specific prefix in service Url2022-05-31T15:16:11ZShrikant GargAdd Csp Specific prefix in service UrlThere can be a scenario where CSP's are adding extra prefix to their service URL because of some security concerns or API gateway in front and hence It will wrong to assume same base url for all the services followed by the same api cont...There can be a scenario where CSP's are adding extra prefix to their service URL because of some security concerns or API gateway in front and hence It will wrong to assume same base url for all the services followed by the same api context path.
e.g. normal url for workflow service : https://osdu-cpd-osdu.osdu-og-platform-validati-ba8e38d4c011d627379af1a4280c4e35-0000.sjc03.containers.appdomain.cloud/api/workflow/v1/
urls with csp specific variable : https://osdu-cpd-osdu.osdu-og-platform-validati-ba8e38d4c011d627379af1a4280c4e35-0000.sjc03.containers.appdomain.cloud/csp-variable/api/workflow/v1/
This can be configurable and csp can have variable of their own.
- Current nomenclature : `{{csp-base-url}}/{{api-service-context-path}}`
- New nomenclature : `{{csp-base-url}}/{{csp-svc-prefix}}/{{api-service-context-path}}`
The presence of `{{csp-svc-prefix}}` should be configurable and by default should not be there so that it won't break existing code.M12 - Release 0.15Shrikant GargShrikant Garghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/53Not able to load Welllog Data from LAS file using wbdutil, because of NumberO...2023-01-02T09:32:20ZKamlesh TodaiNot able to load Welllog Data from LAS file using wbdutil, because of NumberOfColumns field for the curve data has been changed to required field while creating the log header.
**wbdutil ingest data --welllog_id "odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561" -p "D:\OSDU\dev\LoadLogData\wellbore-ddms-data-loader-main\test-data\1013_akm11_1978_comp.las" -c %CONFIGPATH% -t %OSDUTOKEN%...
**wbdutil ingest data --welllog_id "odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561" -p "D:\OSDU\dev\LoadLogData\wellbore-ddms-data-loader-main\test-data\1013_akm11_1978_comp.las" -c %CONFIGPATH% -t %OSDUTOKEN%**
HTTP error: 400. Calling: 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/os-wellbore-ddms/ddms/v3/welllogs/odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561/data'. {"detail":"The number of columns for curve(s): {'DEPT': 1, 'GR': 1, 'DT': 1, 'RHOB': 1, 'DRHO': 1, 'NPHI': 1} in the bulk data do(es) not match the 'NumberOfColumns' property value in the WellLog record for CurveID: {'DEPT': None, 'GR': None, 'DT': None, 'RHOB': None, 'DRHO': None, 'NPHI': None} ."}
Traceback (most recent call last):
File "C:\Python38\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "C:\Python38\lib\site-packages\knack\invocation.py", line 223, in execute
cmd_result = parsed_args.func(params)
File "C:\Python38\lib\site-packages\knack\commands.py", line 146, in __call__
return self.handler(*args, **kwargs)
File "C:\Python38\lib\site-packages\knack\commands.py", line 253, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "C:\Python38\lib\site-packages\wbdutil\commands\ingest.py", line 80, in welllog_data
service.ingest_welllog_data(input_path, welllog_id)
File "C:\Python38\lib\site-packages\wbdutil\well_service.py", line 149, in ingest_welllog_data
self._client.add_welllog_data(data, welllog_id)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 112, in add_welllog_data
self._send_request_json_response("POST", url, payload, None, headers=headers)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 181, in _send_request_json_response
res = self._send_request(method, url, content, json, headers)
File "C:\Python38\lib\site-packages\wbdutil\osdu_client.py", line 193, in _send_request
raise DataLoaderWebResponseError(res.status_code, url, res.text)
wbdutil.osdu_client.DataLoaderWebResponseError: HTTP error: 400. Calling: 'https://preship.gcp.gnrg-osdu.projects.epam.com/api/os-wellbore-ddms/ddms/v3/welllogs/odesprod:work-product-component--WellLog:9aab0457b54b44f3b1f0811aab118561/data'. {"detail":"The number of columns for curve(s): {'DEPT': 1, 'GR': 1, 'DT': 1, 'RHOB': 1, 'DRHO': 1, 'NPHI': 1} **in the bulk data do(es) not match the 'NumberOfColumns' property value in the WellLog record for CurveID: {'DEPT': None, 'GR': None, 'DT': None, 'RHOB': None, 'DRHO': None, 'NPHI': None} ."}**
@debasiscChad LeongChad Leonghttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/54No module named 'wbdutil.wrapper' when calling wbdutil2022-11-09T21:25:51ZChad LeongNo module named 'wbdutil.wrapper' when calling wbdutilAs reported by @todaiks and confirmed by @chad .
The 3 folders are not properly bundled into the set up : common, service, wrapper.
```
No module named 'wbdutil.wrapper'
Traceback (most recent call last):
File "D:\osdu\wellbore-ddms-...As reported by @todaiks and confirmed by @chad .
The 3 folders are not properly bundled into the set up : common, service, wrapper.
```
No module named 'wbdutil.wrapper'
Traceback (most recent call last):
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\invocation.py", line 134, in execute
self.commands_loader.load_arguments(command)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\wbdutil.py", line 129, in load_arguments
super(DdmsCommandLoader, self).load_arguments(command)
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 222, in load_arguments
self.command_table[command].load_arguments()
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 104, in load_arguments
cmd_args = self.arguments_loader()
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 257, in arguments_loader
return list(extract_args_from_signature(CLICommandsLoader._get_op_handler(operation),
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 274, in _get_op_handler
op = import_module(mod_to_import)
File "C:\Python39\lib\importlib\__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 790, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "D:\osdu\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\commands\parse.py", line 3, in <module>
from ..wrapper.environment_var_helper import EnvironmentVarHelper
ModuleNotFoundError: No module named 'wbdutil.wrapper'
```Grant MarblestoneGrant Marblestonehttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/55Error in OsduClient arguments: takes 3 positional arguments but 4 were given2022-11-09T21:25:36ZChad LeongError in OsduClient arguments: takes 3 positional arguments but 4 were given```
__init__() takes 3 positional arguments but 4 were given
Traceback (most recent call last):
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.in...```
__init__() takes 3 positional arguments but 4 were given
Traceback (most recent call last):
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\cli.py", line 231, in invoke
cmd_result = self.invocation.execute(args)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\invocation.py", line 223, in execute
cmd_result = parsed_args.func(params)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 146, in __call__
return self.handler(*args, **kwargs)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\knack\commands.py", line 253, in _command_handler
result = op(client, **command_args) if client else op(**command_args)
File "D:\osdu\osdu-preship-test\wellbore-ddms-data-loader\env\lib\site-packages\wbdutil\commands\ingest.py", line 32, in wellbore
client = OsduClient(config.base_url, token, config.data_partition_id)
TypeError: __init__() takes 3 positional arguments but 4 were given
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/56Well log loader from LAS into Wellbore DDMS - please make error message more ...2023-03-15T18:19:02ZDebasis ChatterjeeWell log loader from LAS into Wellbore DDMS - please make error message more verbose to help troubleshootingWhen running, this gave me the following message.
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
D...When running, this gave me the following message.
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested - LAS file validation failed: **Well name associated with well log record does not match well name in LAS file**.
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
C:\TEMP>
It would be helpful if it shows both values.
1. What is obtained from work-product-component WellLog record.
2. What is obtained from LAS header
We also know that there is issue with convention LAS header says "**Well**" whereas in OSDU DP wpc WellLog is linked to parent **Wellbore**.
So, even that part can be clarified in error message.
cc @chad for informationhttps://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/57wbdutil - status message misleading after failure2023-03-15T18:19:01ZDebasis Chatterjeewbdutil - status message misleading after failureSee for example this - The job failed. Yet it says "Ingest complete".
Propose saying "Ingest failed" instead of "Ingest complete".
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a43...See for example this - The job failed. Yet it says "Ingest complete".
Propose saying "Ingest failed" instead of "Ingest complete".
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested - LAS file validation failed: Well name associated with well log record does not match well name in LAS file.
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
```
Another example
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc -p "C:\TEMP\7556_l0102_1984_comp-WDMS.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Data not ingested: HTTP error: 401. Calling: 'https://r3m15.preshiptesting.osdu.aws/api/os-wellbore-ddms/ddms/v3/welllogs/osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc'. {"reason":"Access denied","message":"The user is not authorized to perform this action. Invalid token.","status":401}
Ingest complete: Data written from 7556_l0102_1984_comp-WDMS.las to Well Log (osdu:work-product-component--WellLog:77874e51358347b9a5a8a4309ef50bfc).
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/59LAS loader (Wellbore DDMS) - run time messages2023-06-25T11:24:02ZDebasis ChatterjeeLAS loader (Wellbore DDMS) - run time messages@chad - great improvement with messaging.
I made one pass successfully for existing WellLog WPC record.
A few comments -
1. Fix typo error "Begining" -> :Beginning"
2. Mention rowcount - as read from LAS file for curve data and the same...@chad - great improvement with messaging.
I made one pass successfully for existing WellLog WPC record.
A few comments -
1. Fix typo error "Begining" -> :Beginning"
2. Mention rowcount - as read from LAS file for curve data and the same for output (how many written in Wellbore DDMS).
3. Bonus - this could serve as "unit test". show curve values at certain depth in the file (not the very first or last, somewhere in between) and show equivalent value as seen from Wellbore DDMS.I myself do that spot check when I run this utility as tester.
```
C:\TEMP>wbdutil ingest data --welllog_id osdu:work-product-component--WellLog:b43d82d4b6fa4c7caaf0402f85d9c517 -p "C:\TEMP\7556_l0102_1984_comp.las" -t %OSDUTOKEN% -c %CONFIGPATH%
Begining ingest of LAS file: C:\TEMP\7556_l0102_1984_comp.las
Retrieving well log record and associated information.
Validating LAS file well name and curves against existing well log record.
LAS well name: 7023
Well log record well name: 7023
LAS curves: ['DEPT', 'GR', 'DT', 'RHOB', 'NPHI']
Well log record curves: ['DEPT', 'GR', 'DT', 'RHOB', 'NPHI']
Ingest complete: Data written from 7556_l0102_1984_comp.las to Well Log (osdu:work-product-component--WellLog:b43d82d4b6fa4c7caaf0402f85d9c517).
C:\TEMP>
```https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/60Unable to ingest a LAS file size of 5 MB using wellbore DDMS - Getting error ...2024-01-25T11:16:40ZDurga Prasad Reddy NadavaluriUnable to ingest a LAS file size of 5 MB using wellbore DDMS - Getting error "413 Request Entity Too Large"When I am trying to ingest a welllog LAS file (size of 4-5 MB) using wellbore DDMS API in Azure M14 environment, I am getting error as "413 Request Entity Too Large". In general log las sizes vary from 2-8 MB.
Is there a size limit to i...When I am trying to ingest a welllog LAS file (size of 4-5 MB) using wellbore DDMS API in Azure M14 environment, I am getting error as "413 Request Entity Too Large". In general log las sizes vary from 2-8 MB.
Is there a size limit to ingesting las files and if yes, how can it be extended?
Attached a dummy LAS file to this issue.
[Dummy_LAS.las](/uploads/87f92bb71570c0fac93b0be6e41c3c59/Dummy_LAS.las)https://community.opengroup.org/osdu/ui/data-loading/wellbore-ddms-data-loader/-/issues/61Investigate issue from preshipping GC M182023-06-25T11:24:02ZChad LeongInvestigate issue from preshipping GC M18https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/527https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/527