Open Test Data issueshttps://community.opengroup.org/osdu/data/open-test-data/-/issues2024-01-18T12:52:20Zhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/95WorkProduct manifests generation fails while validating Manifest.1.0.0.json2024-01-18T12:52:20ZZhubin SalehiWorkProduct manifests generation fails while validating Manifest.1.0.0.jsonWorkProduct manifests generation fails with the following error each time Manifest.1.0.0.json is validated:
```
2024-01-10 09:46:53 ERROR Unable to process document file: 69_D_CH_11
Traceback (most recent call last):
File "/home/zhubi...WorkProduct manifests generation fails with the following error each time Manifest.1.0.0.json is validated:
```
2024-01-10 09:46:53 ERROR Unable to process document file: 69_D_CH_11
Traceback (most recent call last):
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1098, in resolve_from_url
document = self.store[url]
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/_utils.py", line 20, in __getitem__
return self.store[self.normalize(uri)]
KeyError: 'https://schema.osdu.opengroup.org/json/abstract/GenericWorkProductComponent.1.0.0.json'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connection.py", line 159, in _new_conn
conn = connection.create_connection(
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/util/connection.py", line 61, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.10/socket.py", line 955, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 670, in urlopen
httplib_response = self._make_request(
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 381, in _make_request
self._validate_conn(conn)
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 978, in _validate_conn
conn.connect()
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connection.py", line 309, in connect
conn = self._new_conn()
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connection.py", line 171, in _new_conn
raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f67bb1e4e80>: Failed to establish a new connection: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/adapters.py", line 439, in send
resp = conn.urlopen(
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 726, in urlopen
retries = retries.increment(
File "/home/zhubin/.local/lib/python3.10/site-packages/urllib3/util/retry.py", line 446, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='schema.osdu.opengroup.org', port=443): Max retries exceeded with url: /json/abstract/GenericWorkProductComponent.1.0.0.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f67bb1e4e80>: Failed to establish a new connection: [Errno -2] Name or service not known'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1101, in resolve_from_url
document = self.resolve_remote(url)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1202, in resolve_remote
result = requests.get(uri).json()
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/api.py", line 76, in get
return request('get', url, params=params, **kwargs)
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/api.py", line 61, in request
return session.request(method=method, url=url, **kwargs)
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/sessions.py", line 530, in request
resp = self.send(prep, **send_kwargs)
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/sessions.py", line 643, in send
r = adapter.send(request, **kwargs)
File "/home/zhubin/.local/lib/python3.10/site-packages/requests/adapters.py", line 516, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='schema.osdu.opengroup.org', port=443): Max retries exceeded with url: /json/abstract/GenericWorkProductComponent.1.0.0.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f67bb1e4e80>: Failed to establish a new connection: [Errno -2] Name or service not known'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/zhubin/open-test-data/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/osdu_document_manifest.py", line 155, in create_document_manifest_from_path
obj=create_document_manifest(
File "/home/zhubin/open-test-data/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/osdu_document_manifest.py", line 75, in create_document_manifest
document = cm.create_loading_manifest(
File "/home/zhubin/open-test-data/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/common_manifest.py", line 272, in create_loading_manifest
validate_schema(lm_group, schema_id_lm, dict_schemas)
File "/home/zhubin/open-test-data/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/common_manifest.py", line 661, in validate_schema
jsonschema.validate(lm, schema, resolver=resolver)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1306, in validate
error = exceptions.best_match(validator.iter_errors(instance))
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/exceptions.py", line 456, in best_match
best = next(errors, None)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 368, in iter_errors
for error in errors:
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/_keywords.py", line 295, in properties
yield from validator.descend(
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 416, in descend
for error in errors:
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/_keywords.py", line 295, in properties
yield from validator.descend(
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 416, in descend
for error in errors:
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/_legacy_keywords.py", line 135, in items_draft6_draft7_draft201909
yield from validator.descend(item, items, path=index)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 416, in descend
for error in errors:
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/_keywords.py", line 274, in ref
yield from validator._validate_reference(ref=ref, instance=instance)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 461, in _validate_reference
scope, resolved = resolve(ref)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1087, in resolve
return url, self._remote_cache(url)
File "/home/zhubin/.local/lib/python3.10/site-packages/jsonschema/validators.py", line 1103, in resolve_from_url
raise exceptions._RefResolutionError(exc)
jsonschema.exceptions._RefResolutionError: HTTPSConnectionPool(host='schema.osdu.opengroup.org', port=443): Max retries exceeded with url: /json/abstract/GenericWorkProductComponent.1.0.0.json (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f67bb1e4e80>: Failed to establish a new connection: [Errno -2] Name or service not known'))
```
After discussion with @deepapathak she found out that changing the version of `jsonschema` to `3.2.0` in `open-test-data/rc--3.0.0/2-scripts/load_manifest_scripts/requirements.txt` fixes the issue:Chad LeongDeepa KumariChad Leonghttps://community.opengroup.org/osdu/data/open-test-data/-/issues/86Sample data integrity issue, missing Basin id in Well record2022-12-13T00:15:32ZB Ravi KumarSample data integrity issue, missing Basin id in Well recordIn all Well records BasinID and FieldID values are null. Due to this missing data, we are unable to map a Well under a Basin.
Issue Priority (Use Critical/High/Medium/Low): Medium
OSDU Major Release: R3
OSDU Minor Release: M11
Steps ...In all Well records BasinID and FieldID values are null. Due to this missing data, we are unable to map a Well under a Basin.
Issue Priority (Use Critical/High/Medium/Low): Medium
OSDU Major Release: R3
OSDU Minor Release: M11
Steps to Reproduce:
Search for data with kind “osdu:wks
![image_2_](/uploads/b9d0ab616185ee9742a6abcfbdeb1e8d/image_2_.png)[RE+Sample+data+integrity+issue+missing+Basin+id+in+Well+record_1_.msg](/uploads/334b6c213a506095f9618adaf3298328/RE+Sample+data+integrity+issue+missing+Basin+id+in+Well+record_1_.msg)https://community.opengroup.org/osdu/data/open-test-data/-/issues/85Process manifest task of Osdu_ingest DAG calls the Storage Service for the Da...2022-09-05T11:00:45ZMeghnath SahaProcess manifest task of Osdu_ingest DAG calls the Storage Service for the Dataset Id in WorkProductComponent irrespective of the outcome of validate referential integrity, resulting in creation of new record versionIt has been observed that the process manifest task of Osdu_ingest DAG calls the Storage Service for the DatasetId in WorkProductComponent irrespective of the outcome of validate referential integrity, resulting in creation of new record...It has been observed that the process manifest task of Osdu_ingest DAG calls the Storage Service for the DatasetId in WorkProductComponent irrespective of the outcome of validate referential integrity, resulting in creation of new record version. Also, in dataload_r3.py the FileId updated in WorkProductComponent is **file_id:file_version**. As result following the challenges are encountered.
1. If WorkProuct and WorkProuctComponent are not processed by Airflow Manifest Ingestion DAG due to failure in referential integrity validation then the file source information used in first attempt cannot be used for reprocessing the manifest because the file version in the file source json is not the latest anymore and validation of referential integrity fails when reused. As a result ingestion of WPC is tightly coupled with upload of Datasets which generates File Source information used to replace the surrogate key in the WPC manifest by the dataload_r3.py script.
2. open-test-data/rc--3.0.0/4-instances/TNO/work-products/markers/*.json and open-test-data/rc--3.0.0/4-instances/TNO/work-products/markers_1_1_0/*.json are using same dataset. Similarly, open-test-data/rc--3.0.0/4-instances/TNO/work-products/'well logs'/*.json and open-test-data/rc--3.0.0/4-instances/TNO/work-products/'well logs_1_1_0'/*.json. Same is the case with the manifests for Volve. Because of the current behavior of DAG and dataload_r3.py described above, same File Source information generated from the upload of Datasets cannot be reused. As a workaround, the dataset files s3://osdu-seismic-test-data/r1/data/provided/markers/ are copied into two different directories markers and markers_1_1_0 so that the files are uploaded separately generating unique FileId. Similarly for well logs.
@anujgupta @shrikgar @sukanta.bhattacharjee @aparial FYIhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/84Job Failed #13280772022-09-30T17:19:55ZShrikant GargJob Failed #1328077Job [#1328077](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/jobs/1328077) failed for 695474b13b1e39964dd1b17e56927ad4abe63c00:
@chad @divido We are creating pipeline for loading master tno data. ...Job [#1328077](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/jobs/1328077) failed for 695474b13b1e39964dd1b17e56927ad4abe63c00:
@chad @divido We are creating pipeline for loading master tno data. As data load takes time , pipeline is getting timed out after 60mins. Is it possible to increase timeout for this repo to 180 mins.
@BdasIBM @anujguptaM14 - Release 0.17David Diederichd.diederich@opengroup.orgShrikant GargDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/data/open-test-data/-/issues/83Error while creating trajectory manifests2022-09-30T16:44:09ZErnesto GutierrezError while creating trajectory manifestsI faced a couple issues while creating trajectories 1.1.0.
- One in common code, related to a [expected json file](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/2-scripts/loa...I faced a couple issues while creating trajectories 1.1.0.
- One in common code, related to a [expected json file](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/main_swps.py#L211) which I think should be in Title case as the one present in folder [Trajectory_Other_Property.json](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/2-scripts/load_manifest_scripts/src/loading_manifest/Trajectory_Other_Property.json)
- Other in azure scripts, it's needed to update the bash scripts to account for new Trajectory_1_1_0 data and properties.M14 - Release 0.17Ernesto GutierrezErnesto Gutierrezhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/82PreloadFilePath casing issue2023-06-15T11:25:52ZMorris EstepaPreloadFilePath casing issueThe data loaded into preshipping uses "PreloadFilePath" attribute. However, some services expect that this attribute be spelled as "PreLoadFilePath". The schema declares that the spelling be the former (PreloadFilePath). We need to chang...The data loaded into preshipping uses "PreloadFilePath" attribute. However, some services expect that this attribute be spelled as "PreLoadFilePath". The schema declares that the spelling be the former (PreloadFilePath). We need to change all services to line up with the schema definition.M13 - Release 0.16https://community.opengroup.org/osdu/data/open-test-data/-/issues/81The file collection records generated in the Volve Open test data do not cont...2022-07-13T12:30:38ZOkoun-Ola Fabien HouetoThe file collection records generated in the Volve Open test data do not contain a FileCollectionPath in the DatasetPropertiesThe file collection records generated in the dataload do not contain a FileCollectionPath in the DatasetProperties. This will make the DMS fail on getting retrieval instructions as it looks at that path. Additionally, the FileSource insi...The file collection records generated in the dataload do not contain a FileCollectionPath in the DatasetProperties. This will make the DMS fail on getting retrieval instructions as it looks at that path. Additionally, the FileSource inside the FileSourceInfos array is not being generated. Lastly, the capitalization of the file name is incorrect for file ST0202R08_PS_PSDM_RAW_PP_TIME.MIG_RAW.POST_STACK.3D.JS-017534.segy. The "STACK" is "Stack" but the files in S3 are "STACK".
Specific asks from build team include:
1. Check that all file collections have a FileCollectionPath property
2. Fill out all FileSource and not just PreloadFileSource (as some services check one or the other)
3. Check all file names/paths match exactly between the record and S3M13 - Release 0.16Debasis ChatterjeeChad LeongDebasis Chatterjeehttps://community.opengroup.org/osdu/data/open-test-data/-/issues/79Add spatial information for TNO WellboreTrajectory Records2022-07-12T20:56:33ZMichaelAdd spatial information for TNO WellboreTrajectory RecordsThe manifest records for the TNO work-product-component--WellboreTrajectory lack any Spatial fields. This prevents any spatialFilter queries from being done on the trajectories. The location information should be provided for the traject...The manifest records for the TNO work-product-component--WellboreTrajectory lack any Spatial fields. This prevents any spatialFilter queries from being done on the trajectories. The location information should be provided for the trajectories when available because this allows users to filter trajectories by location on a large scale without having to link a trajectory to its parent Wellbore or Well.Keith WallKeith Wallhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/78Error retrieving TNS / Volve dataset mentioned in README.md2022-07-12T20:04:02ZLH Hon [ExxonMobil]Error retrieving TNS / Volve dataset mentioned in README.mdWhile attempting to download the dataset mentioned in README.md, I get the following error. Is there an updated location for the dataset?
```
C:\Users\hon>aws configure
AWS Access Key ID [****************OYPV]: AKIAS4UKBKGJRZVFOYPV
AWS ...While attempting to download the dataset mentioned in README.md, I get the following error. Is there an updated location for the dataset?
```
C:\Users\hon>aws configure
AWS Access Key ID [****************OYPV]: AKIAS4UKBKGJRZVFOYPV
AWS Secret Access Key [****************IgE+]: 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
Default region name [us-east-1]: us-east-1
Default output format [None]:
C:\Users\hon>aws s3 ls s3://osdu-seismic-test-data/
An error occurred (InvalidAccessKeyId) when calling the ListObjectsV2 operation: The AWS Access Key Id you provided does not exist in our records.
```https://community.opengroup.org/osdu/data/open-test-data/-/issues/77Lack of documentation of WITSML parser2022-08-09T08:17:33ZAha!Lack of documentation of WITSML parserAdding documentation
Created from Aha! https://osdu.aha.io/features/TICKETS-11Adding documentation
Created from Aha! https://osdu.aha.io/features/TICKETS-11https://community.opengroup.org/osdu/data/open-test-data/-/issues/76generate-manifest does not generate the Reference Data for Type ResourceSecur...2022-08-09T08:21:02ZChris Smithgenerate-manifest does not generate the Reference Data for Type ResourceSecurityClassificationWhen attempting to load the test generated data, the reference data failed to load because the schema integrity check failed because the ReferenceSecurityClassification Data did not exist.
I was able to work around this by using [this f...When attempting to load the test generated data, the reference data failed to load because the schema integrity check failed because the ReferenceSecurityClassification Data did not exist.
I was able to work around this by using [this file](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/ReferenceValues/Manifests/reference-data/LOCAL/ResourceSecurityClassification.1.0.0.json) as a reference and updating the variables for my cluster. After I modified the file and uploaded it to the environment, the rest of the data was able to be injected.
I would expect this classification type to be generated as part of the test data.https://community.opengroup.org/osdu/data/open-test-data/-/issues/75generate-manifest and data-loader reference different reference manifests fol...2022-08-09T08:25:36ZChris Smithgenerate-manifest and data-loader reference different reference manifests folders.When generating manifest data, the reference data is output to the `generated-manifests/reference-data` folder, per this [line of code](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc-...When generating manifest data, the reference data is output to the `generated-manifests/reference-data` folder, per this [line of code](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/6-data-load-scripts/scripts/generate-manifests.sh#L16-17).
However, the [ingestion_sequence file](https://community.opengroup.org/osdu/platform/data-flow/data-loading/open-test-data/-/blob/master/rc--3.0.0/6-data-load-scripts/scripts/config/ingestion_sequence.json#L3) configures the `data-loader.sh` script to read the reference data from the `generated-manifests/reference-data-manifest` folder, which does not exist.
I am running the scripts off the master branch.
This is the directory structure after I generated my data.
```
generated-manifests git:(master) ✗ tree -d .
.
├── master-well-data-manifests
├── master-wellbore-data-manifests
├── misc-master-data-manifests
├── reference-manifests
├── welllogs-cgg-manifests
└── welllogs-manifests
6 directories
```https://community.opengroup.org/osdu/data/open-test-data/-/issues/74Creating wellbore entity2021-09-15T17:29:18ZChad LeongCreating wellbore entityCreating a wellbore entity with LASIOCreating a wellbore entity with LASIO2021-09-10https://community.opengroup.org/osdu/data/open-test-data/-/issues/72Missing Reference and Misc Master data2021-11-05T22:23:23ZShrikant GargMissing Reference and Misc Master dataGenerate Manifest files from CSV files for reference, misc master data, well and wellbore data for TNO/Volve data.
https://community.opengroup.org/osdu/platform/open-test-data/-/blob/master/rc--3.0.0/4-instances/TNO/master-data/Well/lo...Generate Manifest files from CSV files for reference, misc master data, well and wellbore data for TNO/Volve data.
https://community.opengroup.org/osdu/platform/open-test-data/-/blob/master/rc--3.0.0/4-instances/TNO/master-data/Well/load_Well.1.0.0_1011.json
-----------------------------------------------------------------------------------------------------------
After Loading This TNO Well data through Manifest Ingestion , if failed because of missing Ids
Ex-- Missing ids '{'opendes:master-data--GeoPoliticalEntity:F:', 'opendes:reference-data--CoordinateReferenceSystem:NAP:', 'opendes:reference-data--UnitOfMeasure:M:', 'opendes:master-data--GeoPoliticalEntity:Friesland:', 'opendes:reference-data--VerticalMeasurementPath:ELEV:'}'
These Missing ID or data are not present in opengroup Gitlab. Missing data needs to be made available.Keith WallDadong ZhouKeith Wallhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/71WellboreMarkerSet manifest in TNO test data should specify meaurement units v...2022-08-09T08:51:53ZSteven ReynoldsWellboreMarkerSet manifest in TNO test data should specify meaurement units via the optional meta fieldWellboreMarkerSet manifest in TNO test data should specify the meaurement units via the optional meta field. Right now, the top measurement is given in the manifest, but the units have been left out because the meta field is optional. Se...WellboreMarkerSet manifest in TNO test data should specify the meaurement units via the optional meta field. Right now, the top measurement is given in the manifest, but the units have been left out because the meta field is optional. See https://gitlab.opengroup.org/osdu/subcommittees/data-def/work-products/schema/-/issues/210 for more background discussion.Keith WallKeith Wallhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/70Volve manifests have "Data" as an array, TNO manifests have "Data" as a map2021-03-08T17:29:16ZSpencer Suttonsuttonsp@amazon.comVolve manifests have "Data" as an array, TNO manifests have "Data" as a mapThis issue is strictly about the difference between Volve manifests and TNO manifests. Volve manifests have the "Data" field as an array like so:
"Data": []
While TNO manifests have "Data" field as a map:
"Data": {}
I'm not sure whic...This issue is strictly about the difference between Volve manifests and TNO manifests. Volve manifests have the "Data" field as an array like so:
"Data": []
While TNO manifests have "Data" field as a map:
"Data": {}
I'm not sure which is right, seems like it should be a map. The real issue is that they are different which will be a problem.
**Possible resolution**
Update Volve manifests "Data" field to be a map.
![image](/uploads/56d0ce2d5b0d2a29328fdf10d006a830/image.png)
![image](/uploads/bbb03174739231e83d594b0473a1aa3a/image.png)Keith WallDadong ZhouKeith Wallhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/69Create a script to load in reference data2021-08-18T15:24:34ZAndy GroheCreate a script to load in reference dataPer @rajk on Slack, creating this issue to track script to load reference data.
@ChrisZhang @alan.hensonPer @rajk on Slack, creating this issue to track script to load reference data.
@ChrisZhang @alan.hensonhttps://community.opengroup.org/osdu/data/open-test-data/-/issues/68Access request to Test environment - Define Process2021-06-16T22:20:37ZMeena RathinavelAccess request to Test environment - Define ProcessWell defined plan for access request to dev / test environment to be producedWell defined plan for access request to dev / test environment to be producedM1 - Release 0.1David Diederichd.diederich@opengroup.orgStephen Whitley (Invited Expert)David Diederichd.diederich@opengroup.org2020-07-30https://community.opengroup.org/osdu/data/open-test-data/-/issues/67[Open Test Data] OpenID Connect frontchannel logout does not work reliably2021-06-16T22:20:38ZSteven Reynolds[Open Test Data] OpenID Connect frontchannel logout does not work reliablyAfter experience supporting OSDU R1, we can see that OpenID Connect frontchannel logout does not work reliably. All of the service providers send an HTML header X-Frame-Options deny. However, the OpenID specifications recommend to use an...After experience supporting OSDU R1, we can see that OpenID Connect frontchannel logout does not work reliably. All of the service providers send an HTML header X-Frame-Options deny. However, the OpenID specifications recommend to use an iFrame when implementing the frontchannel logout.
So unfortunately, this is a conflict. The X-Frame-Options header of deny is meant to prevent code from using an iFrame.
For some cases this mostly works but with sporadic errors. In other cases this never works.https://community.opengroup.org/osdu/data/open-test-data/-/issues/39Inconsistency and repetition in formatting of wellbore Location information2020-01-21T14:40:01ZAaronInconsistency and repetition in formatting of wellbore Location informationThe agreed geojson standard is not implemented anywhere except for GeoLocation field. The rest are all over the place.
Example from "WellCommonName": "AME-102",
```json
"GeoCentroid": [
[
5...The agreed geojson standard is not implemented anywhere except for GeoLocation field. The rest are all over the place.
Example from "WellCommonName": "AME-102",
```json
"GeoCentroid": [
[
5.92039522,
53.4651278
]
],
"GeoLocation": {
"coordinates": [
5.92039522,
53.4651278
],
"type": "point"
},
"ProjectedBottomHoleLocation": {
"Coordinates": [
{
"x": 693694.0,
"y": 5928280.0
}
],
"HorizontalCRSID": "srn:reference-data/HorizontalCRS:UTM31_ED50:"
},
"SpatialLocation": [
{
"Coordinates": [
{
"x": 5.92039522,
"y": 53.4651278
}
],
"HeightAboveGroundLevelUOMID": "srn:reference-data/UnitOfMeasure:M:",
"HorizontalCRSID": "srn:reference-data/HorizontalCRS:WGS84:",
"VerticalCRSID": "srn:reference-data/VerticalCRS:NAP:"
},
{
"Coordinates": [
{
"x": 693943.0,
"y": 5928197.0
}
],
"HorizontalCRSID": "srn:reference-data/HorizontalCRS:UTM31_ED50:"
}
],
```