fix: Bingrid returns the X,Y as closed polygon
Type of change
-
Bug Fix -
Feature -
Pipeline -
Test
Does this introduce a change in the core logic?
-
No -
Yes
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
conventional commits spec?
Does this follow-
No -
Yes
Have you set the target Milestone?
-
No -
Yes
Have you set the no-detached-pipeline label?
-
No -
Yes
Updates description?
Filemetadata/openzgy/bingrid endpoint was returning annotations when it was supposed to return world coordinates in the P6Bin.BinGridLocalCoordinates. Additionally, the coordinates were not defined as a closed polygon.