Did you exclude NPS units intentionally?

Feature request: near bike trail.

It would be nice to already see parts of the entire map coloured so you can see (extremely approximately) what's available.

Are you using this for parcel data? Or are you sourcing them directly from every county

https://www.kaggle.com/datasets/landrecordsus/us-parcel-laye...

I know some folks to have a cabin that they use seasonally that borders national forest land. First of all, it's gorgeous and being able to open their back gate and walk out into unspoiled wilderness is awesome. But it does have some drawbacks; their biggest "neighbors" are cattle ranchers who let their cows graze in the forest. The cows will often wander onto their property, and the cowboys are not shy about breaking fences or cutting wire to get their cattle back out. Since they're only there for part of the year, they've also had issues with hunters breaking the locks and using their cabin as a place to hang out while they're not there.

Surprisingly easy to manage, though. You'd think that things like propane delivery and septic system service would be hard to hire when you're miles out of town, up a steep logging trail, and across a home-made bridge, but the local businesses are used to it. I genuinely don't know how they find the place most of the time.

neat :)

Hi HN, I built this. Listings that say "borders state land" can't easily be checked: you open the county's GIS viewer and line up parcel lines against public-land maps by hand. I did that a lot while looking for land of my own, then automated it.

How it works, once a week:

1. About 700,000 active U.S. listings come in from a licensed listings API.

2. Each listing near public land gets its county parcel boundary, from state and county GIS services where they publish them and from a licensed parcel provider elsewhere. With no boundary, the page says so and measures from the listing point, but never claims a shared edge.

3. Public land is USGS PAD-US 4.1, narrowed to land an agency actually owns (Category = Fee, so no conservation easements), that's open to the public, and that's at least 50 acres.

4. Parcel and public land are compared in a local metric projection (shapely/geopandas): within (an inholding), bordering (the boundaries touch, and the shared edge is measured in feet), or adjacent (within 75 m, about a road's width).

Each property also gets the size of the connected public land behind it, its elevation (USGS 3DEP), road access (Census TIGER roads), FEMA flood zone and Forest Service wildfire hazard. The output is about 16,000 static pages with Leaflet maps on Cloudflare Pages, rebuilt every Monday on a Mac mini. ZIP search looks the ZIP up in your browser from Census centroids, so nothing you type is sent anywhere.

Things that were harder than expected:

- Lot sizes sometimes arrive in square feet in the acres field. A Birmingham, AL listing came through at 7,000 acres. Sizes are now checked against price, property type and the parcel itself, and corrected or withheld with a note.

- Condo and subdivision listings often resolve to the association's common tract, so a single town lot can appear to share miles of boundary. Those are flagged as shared parcels.

- PAD-US stores some units as one multipart polygon. My first "connected public land" figure for one Montana property was 69.7 million acres, about three-quarters of the state. Units are now split into pieces and joined only where they actually touch.

- Road centerlines and lot lines come from different agencies and are often tens of meters apart, so "does a road touch this parcel" needs a tolerance, and frontage only counts where the boundary runs along the road.

It's free, with no account and no cookies. There are free weekly email alerts for any search, starting Monday. I'd especially like to hear from anyone who has bought rural land: what should it measure that it doesn't?

[dead]

[dead]

[dead]