Official facts and visual context are separate
Project facts come from a dated static snapshot linked to HDB, OneMap, and agency datasets. The 3D city is orientation context built from processed URA and OpenStreetMap geometry; it does not alter project facts.
Missing information stays missing
If HDB has not published a project name, classification, coordinate, flat mix, price, or waiting time, the field remains empty and the page says “Not published by HDB yet.” The matching result for that criterion is neutral rather than pass or miss.
Four criteria, equal visual treatment
Commute, budget, nearby amenities, and waiting time are evaluated independently. Every confirmed miss reduces the project opacity by exactly 23 percentage points: 100%, 77%, 54%, 31%, then 8%. Selection adds an outline but never restores opacity.
Workplace proximity is straight-line only
Users may select up to two workplace anchors or place one custom pin. A project passes the screen when its available coordinate is within 5 km straight-line distance of the selected point or points. This is not travel time or routing.
Amenity context is approximate
The selected project displays an approximate 1 km straight-line context. A chosen amenity group passes when at least one curated record in that group is attached to the project snapshot. The list is not a complete commercial or civic directory.
Results are grouped, never ranked
Projects are shown as fits, awaiting published data, or trade-offs. There is no winner, composite score, probability, or hidden weighting. Snapshot order is preserved inside each group.
Media never affects matching
Open-licence amenity photographs are stored in a separate manifest with creator, licence, and source. When no defensible licensed image was found, the detail view shows an explicit no-photo state.