doveabi.to

Data and methodology

Understand what the app shows, how it calculates results and what those results cannot tell you.

Data status and limitations

doveabi.to is an experimental project. Ranking prices, air quality, green indicators, scores and highlights are simulated, not current observations or an official ranking. The illustrative landing graphic is not a result for a real area. These suggestions demonstrate a method: do not use them to make a purchase decision.

Real ISTAT boundaries and dated OpenStreetMap park and service pilots are separate datasets. They do not validate or enter the simulated ranking indicators. No OMI, ARPA or OpenAQ measurements are integrated into these rankings. There is no guarantee of accuracy, completeness, suitability or a property's availability; verify current conditions and costs independently.

General score and personal assessment

The general score is a 0–100 reference combining air (45%), price (25%) and green space (30%). It does not use your guided-search preferences or check your budget. Each component uses the normalization below.

The personal assessment is a local, deterministic weighted index, not a match percentage, probability or guarantee. No AI service is used. Balanced priorities give equal weight to the available components; a chosen priority weighs three times each other component. Without a floor area, price is excluded from weighting as well as budget filtering; if price is selected, air and green remain equally weighted.

Incomplete candidates are excluded. Results are ordered by descending personal score; ties use lower price when a floor area is given, then stable ID. Without floor area ties use stable ID only. The shortlist includes three leading choices and genuinely different lower-price or greener alternatives when available. Rankings stay separate: zones within each city and municipalities within each region. Comparing two areas requires the same province.

Normalization conventions

Values beyond these ranges saturate at 0 or 100. These are prototype conventions, not scientific, health or suitability thresholds. The park count and distance used here do not come from the observed park layer.

Score labels are conventional: Excellent from 80, Good from 65 to below 80, Average from 50 to below 65, Poor from 35 to below 50, Critical below 35. They are not certifications of an area's conditions.

Purchase estimates, budget and floor area

The estimate is the area's mean purchase price per square metre multiplied by your requested floor area. Floor area is optional; no size is assumed. Only with both budget and floor area are estimates strictly above the total excluded; the exact limit is included. Without floor area no economic filter or price weight is applied. With floor area but no budget, the estimate is shown without a spending cap.

The estimate is not a property listing, valuation or rental price. Accessory purchase costs are excluded. Input errors, missing-data exclusions and the warning that budget has not been evaluated remain visible in the app where they affect your results.

Territorial coverage

City, Region and Global refer to the available catalog, not complete national coverage. Regional and Global results include the bundled territories, grouped rather than mixed into one ranking. Municipality lists exclude the cities represented by urban subdivisions. Other municipalities in Piemonte, Lombardia and Lazio use municipal boundaries, not neighbourhoods.

Intermediate homogeneous zones are verified only for Torino and Milano. For the other 23 provinces in Piemonte, Lombardia and Lazio, a complete partition with current membership and reuse conditions has not been confirmed; this does not imply that none exists. Every municipality remains selectable. Missing coverage and real-source loading failures are shown in context.

Boundaries — ISTAT and territorial administrations

© ISTAT · CC BY 4.0. Detailed administrative boundaries dated 1 January 2026, checked against the official 21 February 2026 register. Lirio's 31 January incorporation into Montalto Pavese is represented by union of the original boundaries. Sources were checked on 6 September 2026; later unpublished changes are not guaranteed.

Torino homogeneous zones: Metropolitan City of Torino · CSI Piemonte, 11 zones and 312 municipalities, membership reference year 2024 and elaboration year 2026, reconciled with the February 2026 register. Milano: Metropolitan City of Milano · Regione Lombardia, 7 zones plus Milano city and 133 municipalities, 2017 membership reconciled with the 2019 Vermezzo–Zelo Surrigone merger. Both use exact unions of ISTAT 2026 municipal geometry under CC BY 4.0, not new urban-planning boundaries.

Bundled, modified extracts, not live, legal or cadastral boundaries. No source endorses the app. Sources, revisions and transformations are recorded in the geographic files. Each source retains its licence. The Roma download contains the exact map geometry, sources and notices, not tiles or ranking metrics.

Observed park pilot — Torino

OpenStreetMap snapshot: 6 May 2026, 03:25:00 UTC, supplied through the Overpass mirror below. Coverage: the 94 Torino ASC2021 statistical zones, not all of Italy. Zone input: ISTAT ASC2021 · CC BY 4.0.

Offline intersection of leisure=park polygons with the exact selected zone in WGS84. Only positive-area internal portions count, preserving holes and islands; outside parks and boundary-only contacts are excluded. This is a cropped view, not the complete park boundary. Original OSM objects and official zones are unchanged and included in the export. Explicit private/no access and non-polygon records are excluded; other restrictions remain source tags.

Only when no park intersects the zone, the app can show an external recommendation on request: the closest eligible polygon in the dated snapshot, shown in full. Minimum straight-line distance from the exact zone boundary, including holes and islands, is computed in EPSG:32632 before rounding to metres. It is not measured from a home, centroid or entrance; the connector is not a walking route.

The nearest candidate must be closer than the zone-to-query-edge clearance. OSM and the bounded Overpass extract can still omit parks, including polygons without a vertex inside the query. Neither the nearest actual park nor public access or completeness is guaranteed. No municipal endorsement. This layer does not change the ranking score.

© OpenStreetMap contributors · Open Database Licence (ODbL) 1.0.

Observed service pilot — Torino

OpenStreetMap database snapshot: 7 September 2026, 21:14:21 UTC. 201 retained service objects for the 94 Torino ASC2021 zones. Includes bus/tram stops, metro stations/platforms, amenity=hospital and shop=supermarket. Zone geometry: ISTAT ASC2021 · CC BY 4.0.

A point strictly inside each actual ISTAT zone polygon is the distance reference. The minimum unrounded straight-line distance to a node or object bounding-box centre is computed in EPSG:32632, with stable OSM-ID ties and display rounded to metres. No home, route or entrance is assumed. Candidates must be closer than the query-edge clearance. Conservative stop deduplication preserves different refs; duplicates can remain.

Dated, incomplete extract: the buffered query rectangle may omit objects, so nearest means nearest in the retained dataset only. Explicit private/no access and inactive objects are excluded. Emergency status comes only from explicit yes/no tags. No GTT schedules, frequencies, live status or scoring integration.

ODbL database offer: these downloadable JSON archives include original OSM snapshots, full derived databases, indices, source checksums, exclusions, ISTAT zone inputs, licences, notices and reproducible Python transformations. They replace the in-app clipboard exports and do not require JavaScript.

Background map and licences

Background images come from tile.openstreetmap.org. Names and borders printed on them are independent of the app's ISTAT polygons. ODbL covers the OSM database, not the separately distributed CC BY 4.0 ISTAT boundaries, and does not replace the tile service's usage conditions. Geometry and database downloads do not include the background tiles. Mandatory map attribution remains visible in the app.