Kadaster parcels: is it worth wiring in? #189
No reviewers
Labels
No labels
agent
agent:ci
agent:done
agent:failed
agent:needs-input
agent:refined
agent:refining
agent:running
agent:shipped
agent:skip
autonomous
autopilot
driven
local
plan
proposal
qa
qa-gap
research
retro
ship
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jeroen/cartopolis!189
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/187-kadaster-parcels-not-taken"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #187
Merged by the autopilot (docs/direction.md) after every Actions job passed on the branch head.
The frontier row promised "plot boundaries -- the gardens between the buildings". Both halves are wrong, and the check that shows it is worth keeping so nobody repeats it. The interface and the licence were both fine. WFS 2.0 at service.pdok.nl/kadaster/kadastralekaart/wfs/v5_0 with five feature types and a daily bulk download beside it; CC0 1.0 and no fees, read off the service's own ows:AccessConstraints rather than a wiki. As with NWB, this lost on content. Value 1, "Measured beats plausible", is what settles it. A cadastral boundary is a legal line, not a physical object, and the physical ones -- fences, walls, hedges -- are already surveyed by the BGT and already drawn as LineKind::{Fence,Wall,Hedge}. Over the Groningen box: 312.4 km of cadastral boundary against 21.9 km of surveyed boundary. Drawing the cadastre would stand ~290 km of invented fence per cell where the register says nothing at all, which is the exact inversion of that value. The gardens the row wanted are the BGT's begroeidterreindeel, i.e. the "BGT, the remaining layers" row, which keeps its own place unjudged. Volume seals it independently: Perceel alone is 8,855 features and 14.0 MB per cell, 3.7x the paving layer's densest cell. The note also records four paging traps -- a cumulative numberMatched, a short page that is not the last page, resultType=hits as the only honest total, and PagingIsTransactionSafe=FALSE returning 8,855 features of which 8,638 are unique -- because anyone reaching for this service will meet them, and they are worse than the BAG WFS truncation CLAUDE.md warns about. Docs only; no crate is touched. Refs #187