In the User Guide, the Matching Price is described as follows:
The estimated price of the property given by the average of the property's lowest ASK price and highest BID price.
This however, does not fully describe the full behaviour.
While Ask and Bid prices are explicitly stated to be calculated in integer thousands of dollars,
This is not explicitly stated for Matching Price in the user Guide.
However Matching Pricedoes follow the same behaviour.
Example:
Given the following property,
Using the command: filterproperties gte/1 lte/1 returns:
One would expect that since Matching Price was not described to follow this integer behaviour, its average would be calculated to $1.5k, and hence this property should have not been a result of this search query.
Description
In the User Guide, the Matching Price is described as follows:
This however, does not fully describe the full behaviour.
While Ask and Bid prices are explicitly stated to be calculated in integer thousands of dollars,
This is not explicitly stated for Matching Price in the user Guide.
However Matching Price does follow the same behaviour.
Example:
Given the following property,
Using the command:
filterproperties gte/1 lte/1
returns:One would expect that since Matching Price was not described to follow this integer behaviour, its average would be calculated to $1.5k, and hence this property should have not been a result of this search query.
[original: nus-cs2103-AY2425S1/pe-interim#2931] [original labels: severity.Low type.DocumentationBug]