Show HN: Unfenced – Land for sale that borders public land
- ID
- 36200
- Status
- summarized
- Published
- 15 Oct 2026, 7:38 PM
- Fetched
- 16 Oct 2026, 2:35 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://unfenced.land/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.0
- Created
- 16 Oct 2026, 2:36 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Unfenced is a Show HN project that lists land for sale which physically borders public land, matching 695,439 active listings against official boundary data to surface 13,626 properties across 49 regions (as of Oct 12, 2026, refreshed roughly weekly). It measures real shared boundaries — e.g. a 120-acre parcel in Grants Pass, OR at $90,000 with 5,240 ft of measured boundary — using USGS PAD-US 4.1 rather than trusting listing descriptions, with parcel data supplied by Realie. Colorado has the most matches (1,396), then California (836), Utah (645); there are currently no properties in DC or North Dakota, and the site states it is 'not a survey, and not a listing service' and is a project of a design studio in Philadelphia.
Why it matters
This is a concrete pattern for a niche data product: join an authoritative public dataset (PAD-US 4.1 boundaries) against a commercial feed (Realie parcel/listing data), recompute weekly, and sell the derived match — not the raw data. If you are building anything similar, note the two things Unfenced ships alongside the product: a provenance line for every number ('checked against official boundary maps, not listing descriptions') and an explicit 'not a survey' disclaimer, because the product's whole value is an assertion about physical reality that a user may act on. The same join-and-disclaim approach is what any local land, forestry, or licensing dataset product would need before users rely on it.
Discussion angle
The 191-comment thread is worth mining for the boundary-measurement arguments: what happens when your computed boundary disagrees with what a buyer's own surveyor finds, and how much of that liability does a 'not a survey' disclaimer actually absorb?