Data sources used by ARDH

ARDH separates source data from AI interpretation. Below are sources actually used in the product stack.

User-provided data

Addresses, coordinates, listing text/URLs, surfaces, prices, and analysis profile. Limitation: ARDH does not independently verify seller claims.

OpenStreetMap — Nominatim

Geocoding and reverse geocoding. Limitation: address quality varies by country and neighborhood.

OpenStreetMap — Overpass API

Nearby amenities and POIs. Limitation: features can be missing or outdated.

GeoPAU — Tunisia PAU zoning (Layer 138)

Official public PAU zoning polygons. Use: click-to-zone and architect zoning sections when a point intersects a digitized plan. Limitation: not all Tunisian land is covered.

Local Tunisia planning knowledge

Curated zone explanations for architect assistance—not a substitute for the full municipal PAU or certificat d’urbanisme.

Morocco listing comps (when configured)

Optional public Mubawab Morocco listings. Limitation: asking vs closing prices; Tunisia comps are not guaranteed from a live scrape.

AI synthesis — OpenRouter

LLMs draft report narrative from the enriched fact pack. Limitation: treat prose as analysis, not a certified appraisal.

Source data vs AI interpretation

Coordinates, OSM amenities, and PAU codes are source or derived facts. Valuation commentary and SWOT wording are AI interpretation.