Turn a buyer’s priorities into an explainable address comparison
Compare two Richmond homes against buyer priorities, with visible thresholds and the proximity measures behind each result.
Two homes can sit in the same suburb and suit the same buyer very differently. Yet a generic location score often hides the reason. For a PropTech product helping a buyer compare a shortlist, the more useful question is simple: which address meets the priorities the buyer selected?
An explainable comparison keeps those priorities visible. Each home receives one point for every selected criterion it meets, with the underlying distance or score alongside the result. A buyer can see why the comparison changes when they choose a different profile.
View the demo screenshot
Illustrative comparison of two real Richmond houses using a fixed HtAG snapshot captured 13 September 2026. Property records were sourced 29 August 2026.
Compare complete homes before comparing location fit
The shortlist contains two houses in Richmond, Victoria. 10 Mary Street is recorded with three bedrooms, two bathrooms, one car space and 176.22 m² of land. 8 Bendigo Street has three bedrooms, one bathroom, one car space and 265 m² of land. Both property records carry a source date of 29 August 2026.
After matching each entered address, the product can attach the six location measures needed for this example: proximity to a tram stop, supermarket, park, train station and cafe, plus the 0–10 walkability score. The proximity figures are reported in metres. They are not walking distance or travel time.
Let the selected priorities explain the result
The demo offers two fixed, illustrative profiles through tabs. Everyday errands checks whether a tram stop is within 250 metres, a supermarket within 400 metres and a park within 250 metres. Mary Street meets all three: tram 99.90 m, supermarket 367.50 m and park 198.53 m. Bendigo Street meets one: its park is 232.84 m away, while the tram stop is 385.85 m and supermarket 413.62 m away.
Switch to Rail and cafe and the result reverses. This profile checks for a train station within 750 metres, walkability of at least 8/10 and a cafe within 150 metres. Bendigo Street meets all three, with train proximity of 555.30 m, walkability 8/10 and cafe proximity of 115.90 m. Mary Street meets the cafe criterion at 136.45 m, while its train proximity is 891.06 m and walkability is 7/10.
Interactive visual
Choose a buyer-priority profile
Select a declared profile to compare criteria met. The counts are transparent checks, not a liveability score.
Loading interactive visual…
View exact data
| Date / label | 10 Mary · criteria met | 8 Bendigo · criteria met |
|---|---|---|
| Everyday errands | 3 of 3 | 1 of 3 |
| Rail and cafe | 1 of 3 | 3 of 3 |
Interactive visual
Compare the underlying proximity distances
Switch metrics to inspect the observed distance behind each profile check.
Loading interactive visual…
View exact data
| Date / label | Nearest train station | Nearest tram stop | Nearest supermarket | Nearest park | Nearest cafe |
|---|---|---|---|---|---|
| 10 Mary Street | 891.06 m | 99.90 m | 367.50 m | 198.53 m | 136.45 m |
| 8 Bendigo Street | 555.30 m | 385.85 m | 413.62 m | 232.84 m | 115.90 m |
The calculation is deliberately plain:
preference fit = selected criteria met ÷ selected criteria
For Everyday errands, Mary Street is 3/3 and Bendigo Street 1/3. For Rail and cafe, Mary Street is 1/3 and Bendigo Street 3/3. The numerator counts criteria met; the denominator is the three criteria selected for that profile. Every criterion counts equally. These thresholds were chosen for the illustration, so the result is not a universal address ranking.
Keep the comparison useful in the buyer’s workflow
The card can sit inside an existing shortlist: match the address, retrieve the property summary, then request only the feature themes used by the selected profiles. Cache the accepted address key and fixed feature snapshot so changing tabs does not trigger another data request. Use current API pricing to plan the requests your product needs.
The comparison helps a buyer decide what to inspect next. Venue quality, opening hours, the walking route, accessibility and personal suitability still need practical verification. The snapshot records what the feature data reported on 13 September 2026; that capture date is not the date the underlying feature was updated. Address features are derived from OpenStreetMap.
Implementation appendix
The native HtAG API documentation covers the seven operations used:
GET /address/geocode— match entered text to an address record and return its address key.GET /property/summary— retrieve the property details used to present a complete shortlist card.GET /address/walkability— retrieve the walkability score.GET /address/transport— retrieve train and tram proximity.GET /address/essentials— retrieve supermarket proximity.GET /address/green-space— retrieve park proximity.GET /address/amenities— retrieve cafe proximity.
Explore HtAG API access and current pricing to add an explainable preference comparison to your product.