FAQ
Transparent answers about how Plekia works
Clear, user-friendly information about what Plekia measures, where the data comes from, what freshness means, and how to interpret each report.
How Plekia works
What does Plekia actually analyse?
Plekia analyses a location around the address you enter and turns that into a practical report on transit, green space, safety, amenities, noise, and housing context. The goal is to help you understand the neighbourhood before you commit time or money.
What does the score mean?
The score is a decision-support summary, not a property valuation. It combines multiple measured inputs into a single number so you can compare locations more easily. Different lifestyle profiles change how those inputs are weighted.
What are the lifestyle pillars?
Plekia groups the analysis into a few clear decision areas: mobility, safety, green and calm, daily convenience, and affordability. These pillars help you see where a location is strong, where it is weaker, and what trade-offs you are making.
What is the 800 metre radius?
Nearby places are counted within roughly 800 metres of the analysed point. That gives a walkable-area view of the neighbourhood instead of a city-wide summary.
Data and sources
Where do nearby places come from?
Nearby places and map context come from OpenStreetMap data. That includes categories like transit, grocery, parks, bars, restaurants, gyms, and other mapped amenities.
Where do schools come from?
School context combines OpenStreetMap with DUO-backed school data where available, so the report can reflect both mapped nearby schools and official education context.
Where do income and housing numbers come from?
Income and housing context comes from CBS, Statistics Netherlands. Depending on the address and available data, Plekia may use neighbourhood-level context or municipality-level averages.
Where does safety data come from?
Safety context is derived from area-level police crime data together with CBS neighbourhood matching. The safety label is a simplified interpretation of the stored area context and recorded crime totals.
Where does noise information come from?
Noise and environmental context combines mapped infrastructure with imported environmental noise data. Plekia uses that to estimate transport exposure and local street-activity pressure around the address.
What about commute fit?
Commute fit is currently a practical estimate, not a live route calculation. It uses the chosen destination together with distance and local mobility context to give a useful directional read, but it is not a substitute for checking a real route in a navigation app.
Freshness and transparency
How fresh is the data in my report?
Each report is a snapshot of the data available at the moment that analysis was generated. Different sources update on different schedules, so freshness is best understood as the app’s latest imported context at analysis time, not a single universal timestamp across every source.
Why does Plekia show a generated date?
The generated date tells you when that specific report snapshot was created. If a source dataset changes later, a newly generated report may differ slightly from an older saved one.
Why can a public location page be lighter than a fresh dashboard analysis?
Public location pages use cached balanced reports so they stay fast and stable. Your own dashboard analysis is generated for the exact address or listing you enter, so it can be more specific or fresher than a generic public area page.
Is the AI text fully custom?
The verdict, summary, strengths, and trade-offs are generated from the measured inputs in your report. The structure of the report is consistent, but the outcome and commentary are shaped by the actual data for that location.
Limits and interpretation
Is this a valuation, legal opinion, or guarantee?
No. Plekia is a decision-support tool. It is designed to help you understand a location more quickly, but it is not legal, financial, mortgage, or valuation advice.
Why can a score feel different from my personal impression?
Some things are measurable and some are subjective. Plekia can measure mapped places, area-level housing context, crime totals, and noise-related signals, but it cannot fully capture building quality, neighbour behaviour, route comfort, or every personal preference.
Why do lifestyle profiles matter?
A family, a remote worker, and a nightlife-focused user may want very different things from the same address. Profiles help Plekia reflect those priorities instead of pretending every user evaluates a location the same way.
What do custom priorities do?
Custom priorities let you change how strongly Plekia weighs transit, safety, green space, and amenities. This helps the report reflect your own lifestyle better than a one-size-fits-all profile.