Two related issues have been identified by @aleen95 in the Map block that prevent correct data handling:

1. Override logic rejects values ≤ 0

The override logic in the Map block expects values strictly greater than 0. As a result, any value that is not greater than 0 (i.e., zero, negative values, or null) is rejected and not saved. This causes valid data to be silently dropped.

2. Coordinate data type declared as integer instead of decimal

The data type for coordinates in the Map block is declared as integer (int) rather than a floating-point type (float/decimal). This causes coordinate values with fractional precision (e.g., 16.50, -25.00) to be truncated, leading to significant loss of positional accuracy.

Steps to Reproduce

  1. Attempt to save a map entry with a value of 0 or a negative value via the override logic → value is not persisted.
  2. Attempt to save a coordinate with decimal precision (e.g., 16.50) → value is truncated to 16.

Comments

hexabinaer created an issue. See original summary.

hexabinaer’s picture

@aleen95 provided patches and very helpful field descriptions that will be included in the upcoming release.

tobiasb’s picture

Version: 3.0.x-dev » 2.6.x-dev

Commited to 3.0.x and cherry-picked to 2.6.x.

tobiasb’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.