Parcel-level technical evidence
Istanbul property intelligence, joined at its official grains.
One locally accepted index connects cadastral parcels, YAPIKN buildings, KAPIKN exterior doors, and planning controls across all 39 districts. It is a technical evaluation asset—not a public dataset or production-serving claim.
Accepted local snapshot
Coverage is counted. Availability is not implied.
These are aggregate rows verified in the accepted local database generation. They do not authorize record republication or make Istanbul searchable in the production portal.
- Parcel profiles
- 1,346,745 with matching geometries
- Buildings
- 1,167,491 official building grain
- Addresses
- 2,554,500 exterior-door identities
- Zoning controls
- 405,232 joined without flattening
- Parcel-zoning links
- 3,877,903 one-to-many retained
- Listing observations
- 0 no marketplace rows accepted
Entity model
Parcel is not building. Building is not address.
The model keeps each official identity at its native grain, then records the accepted links between them.
Parcel
The cadastral grain for area, geometry, district, neighbourhood, block and parcel references.
Building
A building identity linked to its parcel only where the accepted relationship is explicit.
Exterior door
An address-level identity retained separately from the parcel and building grains.
Zoning control
Plan controls and overlays joined to parcels while preserving one-to-many relationships.
Listing observation
A time-bounded marketplace observation. No accepted listing rows are present in this snapshot.
A bounded screening example
Hotel terms narrow Fatih. They do not grant permission.
The accepted query looked for otel, turizm, konaklama in zoning controls. It demonstrates candidate discovery while preserving the gap between a plan signal and legal operating status.
A zoning-term match is a candidate signal, not proof of hotel permission or an operating licence.
Access methodology
Resolve, link, layer, review.
Institutional filtering is useful only when identity uncertainty and unavailable facts survive the query.
- 01
Resolve the parcel
Start from official address or cadastral references and keep ambiguous matches visible.
- 02
Link accepted identities
Attach YAPIKN and KAPIKN only through explicit links, one-building parcels, or a unique exact exterior door.
- 03
Layer planning controls
Retain every matching zoning control and overlay instead of collapsing conflicting or overlapping records.
- 04
Screen, then review
Use institutional filters to produce candidates; permissions, licences, ownership and valuation require separate diligence.
Supported screening dimensions
- District, neighbourhood, block and parcel
- Parcel area and geometry
- Building identity and footprint
- Exterior-door address identity
- Zoning controls and plan overlays
- Active listing observations when separately accepted
Fail-closed boundary
What this evidence cannot answer.
No absent fact is converted into a commercial assertion. Ambiguity stays visible, and production gates stay off.
- Registered ownership requires authorization and is not included.
- Building permits and occupancy records are not published in this accepted scope.
- Hotel and business licences have no accepted exact join to these parcel records.
- The accepted snapshot contains zero marketplace listing observations.
- Asking prices, completed sales, mortgages and valuations are not inferred.
- The accepted database retained three colliding source address identifiers instead of silently merging them.
- An exact Haseki address remained ambiguous across two official building-parcel identities.
- Units are not asserted from listing text without a separately accepted unit identity.
Technical evidence, not customer availability
The next gate is authorization—not a larger claim.
Technical evaluation only; production reuse is not cleared. Aggregate evidence is derived from the immutable Istanbul institutional-search local acceptance receipt. No underlying records are published on this page.