Weekend trip planner: how to read our practical-facts tables

Every listing page on this site is a table of practical facts: fee, parking, water, toilets, access rules, surface, hours, operator, website, description. This guide explains where those facts come from, what it means when a fact is missing, and how the site decides which spots get a full page versus a bare-bones one.

What “richness” means

Each spot on the site gets a richness score from 0 to 10, one point for each practical detail we actually have on file. A spot with a fee amount, parking notes, water availability, toilet info, access rules, surface type, hours, operator name, a working website, and a description scores a 10. A spot where we only know the name and location scores close to 0.

The score isn’t a quality rating. A richness score of 2 doesn’t mean the place is bad, it means we don’t have much documented about it yet. Some of the best swimming holes and gravel-bar campsites in this region are richness 1 or 2, because nobody’s bothered to tag them thoroughly in the source data. Treat richness as a measure of how much you can plan around before you go, not a measure of how good the spot is.

Spots with a richness score of 3 or higher get a full, indexable detail page. Below that threshold, the page still exists and you can click through from a listing page to see whatever we have, but it’s marked so search engines don’t index it, since a page with almost no information isn’t a useful search result on its own. That’s also why the state and category listing pages, things like Waterfalls in North Carolina, carry more of the practical weight: they group everything we know for a state and category into one table you can scan and compare, richness score included as a column.

Where the data comes from

Almost everything on the site is pulled from OpenStreetMap, the same crowdsourced map data that underlies a huge share of the internet’s mapping products. We query OpenStreetMap for the relevant tags in each state, waterfalls, campsites, river access, trailheads, overlooks, and historic sites, then run that raw pull through a cleanup pass: merging duplicate entries mapped twice in roughly the same spot, dropping unnamed features in most categories, and filtering primitive camping down to sites that are actually primitive rather than developed pay campgrounds tagged incorrectly.

Alligator viewing spots are the one exception. Gator habitat isn’t reliably tagged in OpenStreetMap, so our gator listings come from a small, hand-checked editorial list instead of a bulk data pull. It’s a shorter list than the other categories for exactly that reason: we’d rather have fewer, verified spots than a long list built on guesswork.

Full detail on the cleanup rules, including how river access points get merged with boat ramps and how camping gets filtered, lives on the about page.

Why some pages say “unknown”

OpenStreetMap is only as complete as whoever last mapped a place. A boat ramp might be perfectly mapped for location and name but have no fee data attached, because the person who added it to the map didn’t know or didn’t record it. Rather than guess at a fee or a set of hours, we mark that field unknown and leave it to you to check the operator’s own site, or call ahead, before you go.

This applies across every category. If a waterfall’s trail length is unknown, it’s because that data point wasn’t in the source, not because we forgot to look it up. We’d rather show a gap honestly than publish a number that turns out to be wrong once you’re standing at the trailhead.

How the numbering and access-point pages work

A lot of river access listings, especially in Texas, Georgia, Florida, and South Carolina, show up as generic entries like “TX River Access Point #524” instead of a named boat ramp. These are real, mapped access points, they’re just access points OpenStreetMap doesn’t have a proper name for, usually because they’re informal put-ins rather than developed, signed ramps. We generate a placeholder label instead of dropping them from the site, since knowing a spot exists and roughly where it is still has value even without a name.

Update cadence and “last verified”

The full data pipeline runs on a monthly cycle. The date shown on each listing page reflects when that page’s data was last pulled and processed, not when a person physically visited and confirmed it in person. Read it as “this is what the source data said as of this date,” not a guarantee that a gate hasn’t closed, a fee hasn’t changed, or a road hasn’t washed out since. For anything gated behind a reservation system, a seasonal closure, or a capacity limit, like the springs parks covered in our Florida springs guide, check the operator’s own site the week of your trip regardless of what our page says.

How to report a correction

Because almost all of our data comes from OpenStreetMap, the fastest way to fix something wrong on this site is usually to correct it directly in OpenStreetMap itself. We pull from there, and so does most of the rest of the internet’s mapping ecosystem, so a correction made there has a much longer reach than a note sent just to us. If a fee’s gone up, a road’s been gated, or a campsite’s been closed for construction, editing OpenStreetMap gets that fix into our next monthly pull and into everyone else’s data too.

For the gator listings, which run on our own hand-checked list rather than OpenStreetMap, see the contact information on the about page for how to flag a correction directly.

A category tour, briefly

Each category behaves a little differently depending on what kind of place it’s tracking. A few examples, one state each, if you want to see the pattern for yourself:

• Camping in Arkansas, where dispersed forest sites dominate and most entries carry a low richness score by design, since primitive sites rarely have posted fees or hours.
• River access in Louisiana, heavy on boat ramps and bayou put-ins.
• Trailheads in Oklahoma, a mix of formal park trailheads and informal greenway access points.
• Overlooks in Georgia, a shorter list, since scenic overlooks are naturally rarer than river access points.
• Historic sites in Texas, spanning everything from state historic sites to small local markers.
• Gators in Florida, the hand-checked editorial category described above.

Waterfalls are the thinnest category on the site right now; most of the South’s named waterfalls cluster in the mountains, and our current coverage there is strongest in North Carolina, with other states filling in as the data pipeline catches up.

The short version

Richness score tells you how much we know, not how good a place is. Data comes from OpenStreetMap except for gators, which is a curated list. Unknown means genuinely unknown, not zero. The pipeline updates monthly, and the fastest fix for wrong information is usually a direct edit on OpenStreetMap itself. When a page and reality disagree, especially around fees, hours, or closures, trust the operator’s own site over ours.