Update M23 Release Notes authored by Brian's avatar Brian
...@@ -396,7 +396,21 @@ TBA ...@@ -396,7 +396,21 @@ TBA
### Geospatial Consumption Zone (GCZ) ### Geospatial Consumption Zone (GCZ)
- TBA * Upgrade Transformer codebase to JDK17 to comply with [OSDU Java 17 Migration](https://community.opengroup.org/groups/osdu/platform/-/epics/17 "Java 17 migration") - [!182](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/182 "Update jdk17")
* Added `.bat` and `.sh` scripts to simplify running the GCZ's transformer in a local installation
* [Docs updated with new steps here](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/docs/deployment/deployment_procedure.md#running-the-gcz##transformer)
* Enable custom configuration of GCZ Transformer port for cases where default (8080) is already in use - [!189](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/189 "331 port for spring boot app")
* Can be adjusted via environment variable `GCZ_TRANSFORMER_PORT`
* Support the display of Well Log as Bottomhole when data is available - [!188](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/188 "Well Log as Bottomhole")
* Uses `spatialSourceKind`, `spatialSourceID` and the [new](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/gcz-transformer-core/config/application.yml?ref_type=heads#:\~:text=spatialSourceGeometryLocation) `spatialSourceGeometryLocation` to define relationship between WellLog and the associated Wellbore's bottomhole (if it exists)
* Enable configurable `authInfo` (see [ArcGIS Server Info sample](https://developers.arcgis.com/rest/services-reference/enterprise/server-info.htm)) for GCZ Service to support scenarios where the `tokenServicesUrl` is different than default - [!193](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/193 "Support configurable auth-info enhancement")
* Supports ArcGIS Online compatibility during use of simple/direct [GCZ Provider Security](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/docs/security/gcz-provider-auth.md)
* Enhance GCZ Provider's where-clause parsing logic - [!202](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/202 "Update GCZ Provider Where Clause Parsing Logic")
* Upgrade Node v16 to v18 - [!204](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/204 "Update node to 18.19.1")
* Update Transformer API to use common OSDU patterns for auth and responses - [!206](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/206 "Update Transformer API to use common OSDU patterns for auth and responses")
* Add Ambassador Service endpoint which displays all `kinds` and their associated `recordCount` for a connected OSDU instance - [!208](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/merge_requests/208 "Ambassdor service 338 return all kind")
* Part of a new suite of upcoming Ambassador endpoints which support and streamline GCZ Configuration tasks
* [Service detailed here](https://community.opengroup.org/osdu/platform/consumption/geospatial/-/blob/master/docs/deployment/pre_deployment_config.md#ambassador-configuration-utility)
## Known Issues/Gaps ## Known Issues/Gaps
... ...
......