Automated Parcel & Property Boundary Management Workflows
A production-grade engineering reference for the people who wrangle cadastral data for a living.
▶ Visit the site — www.property-boundary.com
Property Boundary is a free, in-depth reference site for building reliable parcel and property-boundary data pipelines. Every page goes straight to the implementation decisions that matter — runnable PostGIS SQL, Shapely and GeoPandas ETL code, failure modes, and the validation gates that keep a statewide parcel fabric trustworthy. No filler, no basic-GIS hand-holding: it assumes you are a working engineer and gets to the point.
The material spans 54 deeply-linked reference pages organized into three connected sections, each pairing reference architecture with copy-ready code you can drop into a real pipeline.
| Section | What you'll find |
|---|---|
| Automated Tax Assessor Ingestion & Data Cleaning | Parsing county CSV/XML feeds, mapping attributes to a canonical schema, normalizing APNs, deduplicating and record-linking parcels, county-specific format adapters, geometry repair, and batch validation with compliance reporting. |
| Core Parcel Data Architecture & Standards | LADM/FGDC/OGC-aligned schema design, CRS and projection management, precision & tolerance standards, legal-description-to-geometry conversion, legacy plat digitization, and spatial CI/CD, testing & reproducibility. |
| Topology Repair & Boundary Sliver Elimination | Gap and overlap detection, sliver elimination, boundary snapping, dynamic tolerance mapping, and shared-edge topology validation across large cadastral datasets. |
- GIS analysts modernizing county and statewide parcel fabrics
- Python ETL engineers building repeatable ingestion and cleaning pipelines
- Local-government technology teams who need legally-defensible, standards-aligned boundary data
- Property-tech developers integrating parcel geometry and ownership data into products
- Implementation-first. Every technique ships with transaction-wrapped PostGIS SQL and a Python/GeoPandas equivalent — with CRS guards, error handling, and logging already in place.
- Decision-oriented. Comparison guides settle the questions engineers actually argue about:
ST_MakeValidvsST_Buffer(0),ST_SnapvsST_SnapToGridvsset_precision, database topology vs application-level validation. - Standards-anchored. Guidance is tied to LADM (ISO 19152), FGDC, OGC Simple Features, USPS Publication 28, and State Plane / EPSG conventions rather than arbitrary rules of thumb.
- Built to be trusted. Original, hand-authored diagrams; accessible, fast, mobile-friendly pages; and a tight internal link graph so the answer you need is a click or two away.
- Eleventy static-site generator with Nunjucks templates and Markdown content
- Hand-authored, theme-aware inline SVG diagrams (light/dark)
- Reference code targeting PostGIS / PostgreSQL, Shapely, GeoPandas, PyProj, and SQLAlchemy
- Deployed as a static site on Cloudflare Pages
git clone https://github.com/property-boundary/property-boundary.git
cd property-boundary
npm install
npm run serve # local dev server with live reload
npm run build # production build to ./_siteAll commits to this repository are authored solely by the property-boundary account (the identity in the deploy token). Contributions are squashed to that single author and no Co-Authored-By trailers or additional co-authors are used on any commit.
Maintained by the Property Boundary project. Explore the full reference at www.property-boundary.com.
© 2026 Property Boundary. All rights reserved.