Your cross-market price chart is nearly ready to publish, and matching minSize and maxSize inputs look like evidence that you're comparing similarly sized homes.

Then you check the units.

Search size bounds use square feet in Singapore and Malaysia, but square metres in Thailand. The returned floorAreaSqft and floorAreaSqm fields standardise the units after selection; they can't recover homes excluded by the original search.

The filter has already chosen your sample

The tempting assumption is that matching numeric inputs produce comparable cohorts, provided you normalise the output afterwards.

The selection happens earlier:

physical interval → local-unit search bounds → selected listings ↓ converted area fields

Enter fullscreen mode

Exit fullscreen mode

If the local-unit translation is wrong, the converted fields can describe the wrong cohort perfectly well.

Bad selection can have excellent formatting.

That matters before you calculate asking-price differences, because changing the floor-area…