Our number of storeys value is algorithmic, based on eave heights and ground height (both of which can sometimes be incorrectly measured) combined with a floor height for the property.
Floor height is a data point we can access for the property however there can sometimes be issues. The floor height is sometimes specifically provided, but incorrectly measured and therefore affects the algorithm in a way that the result is incorrect. Alternatively, sometimes floor height is not an available data point, in which instance we have a temporal and spatial average system that provides the best estimate for floor height. The algorithm then uses this estimated floor height which again can lead to an incorrect value.
We are always looking at ways of improving but with any automatic/algorithmic system there will be issues.
If the user knows the correct no. of storeys and can see that the value displayed is incorrect they can edit it in the 'Edit Data' window for a more accurate valuation.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article