... | @@ -62,7 +62,6 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
... | @@ -62,7 +62,6 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
|
- Handle EDS [incremental fetch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/252 "Handle EDS incremental fetch scenario") scenario
|
|
- Handle EDS [incremental fetch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/252 "Handle EDS incremental fetch scenario") scenario
|
|
- Provide [default date and time](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/253 "Provide default date and time to LastSuccessfulRunDateUTC and CreateTimeMax in ConnectedSourceDataJob (CSDJ))") to LastSuccessfulRunDateUTC in ConnectedSourceDataRegistry
|
|
- Provide [default date and time](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/253 "Provide default date and time to LastSuccessfulRunDateUTC and CreateTimeMax in ConnectedSourceDataJob (CSDJ))") to LastSuccessfulRunDateUTC in ConnectedSourceDataRegistry
|
|
- [EDS DMS](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/52 "EDS DMS - Options for Consumer to manage bulk data files (ex: LAS, DLIS, SegY) from Data Provider") - Options for Consumer to manage bulk data files (ex: LAS, DLIS, SegY) from Data Provider
|
|
- [EDS DMS](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/52 "EDS DMS - Options for Consumer to manage bulk data files (ex: LAS, DLIS, SegY) from Data Provider") - Options for Consumer to manage bulk data files (ex: LAS, DLIS, SegY) from Data Provider
|
|
[Known Issue] In the current version EDS DMS can manage bulk data files from one Data Provider only. It will not support a combination of dataset IDs from different data providers.Also, testing can be done using eds-DMS API and not from data set API.
|
|
|
|
|
|
|
|
### GCZ (Geospatial Consumption Zone)
|
|
### GCZ (Geospatial Consumption Zone)
|
|
|
|
|
... | @@ -202,6 +201,11 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
... | @@ -202,6 +201,11 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
|
|
|
|
|
* WellLog support / Spatialization will only pull geometries from the `SpatialArea.Wgs84Coordinates` or `SpatialLocation.Wgs84Coordinates` properties from a record gathered via the Search API. By default, this is typically where Well records store their surface locations, and as such, Well Logs can only currently be displayed via the Surface Location of a Well, and **not** via the bottomhole or midpoint location.
|
|
* WellLog support / Spatialization will only pull geometries from the `SpatialArea.Wgs84Coordinates` or `SpatialLocation.Wgs84Coordinates` properties from a record gathered via the Search API. By default, this is typically where Well records store their surface locations, and as such, Well Logs can only currently be displayed via the Surface Location of a Well, and **not** via the bottomhole or midpoint location.
|
|
|
|
|
|
|
|
### External Data Service
|
|
|
|
|
|
|
|
EDS DMS - In the current version EDS DMS can manage bulk data files from one Data Provider only. It will not support a combination of dataset IDs from different data providers.Also, testing can be done using eds-DMS API and not from data set API.
|
|
|
|
|
|
|
|
|
|
## Supporting Information
|
|
## Supporting Information
|
|
|
|
|
|
## OSDU Community utilities |
|
## OSDU Community utilities |
|
|
|
\ No newline at end of file |