How we keep it true
A wrong confident answer
ends the product.
landfeed exists to be the source of truth for everything geo and działka in Poland, reachable from anyone's own agent with one API call. These are the rules that keep the "truth" part honest. They are not business rules; they come first.
Every field is sourced
Every field carries its source, its as-of date and one of four coverage states. Where the state does not publish something, we say so rather than guess.
Four coverage states
An affirmative negative is not the same as missing data, and neither is the same as "not computed yet". The API keeps them apart, and each comes with a plain-language note.
Never "safe"
The tools tell the agent never to call a parcel safe. It reports what each source says and what it does not cover.
Never "no plan"
The agent names which plan (plan ogólny or MPZP), its status (draft, adopted, in force or none), its effective date and the source. Drafts are shown and labelled.
No KW, no owners
No land registry (KW) numbers, no owner or holder data, no investor names, no address-level transaction prices; aggregates need at least 5 transactions. Tests fail on leakage.
Licence before serving
Every layer has a written licence position and an attribution string before it is served. Official sources first, or feeds with written terms; no spoofed headers.
Freshness is an endpoint
A layer with no refresh job and no status row is not in the API. The API exposes its own freshness per source, for free.
Checked against a fact oracle
Every layer refresh is checked against verified facts on a sampled set of parcels. A miss is a defect, fixed before the next refresh.
An example where we were wrong.
When an outside source disagreed with us about one parcel, the rule was to resolve it before shipping, not to pick the friendlier number.
Stepnica, distance to a cemetery
For parcel 320407_4.0001.232/18 our earlier figure was 203.3 m; another provider said 60.3 m. Measured edge to edge on the official BDOT10k polygon, the distance is 61.3 m. Our old adapter measured to the centre point of the cemetery's bounding box, which always overstates the distance.
The definition landfeed uses
Minimum distance between the parcel polygon and the cemetery polygon, 0 if they touch; BDOT10k first, the full OSM polygon as fallback, never a centre point; the source and geometry basis published with the answer. It is a sanitary-distance indicator, not a building ban.
How we decide.
When two options differ, we prefer the one that makes an agent's answer more correct, more sourced, or more complete, in that order. Products, prices, brand and hosting follow from this.
A null with a note beats a plausible guess.
Every fact can be traced to a publisher, a licence and a date.
Breadth grows layer by layer, each with a refresh job and a status row.
Sources,
not adjectives.
See what each layer is, where it comes from and how fresh it is.