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

Does this follow conventional commits spec?

• 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.

changed milestone to %M18 - Release 0.21

requested review from @sacha, @xyan3, and @DiegoMolteni

assigned to @imonteiro

approved this merge request

added no-detached-pipeline label

approved this merge request

mentioned in commit b31f3833

merged