Hey! Came across OpenCamp while researching the recreation.gov API landscape. Great tool, the polling + email notification flow is exactly what the permit grind calls for.
I'm building Outdex (outdex.dev), a developer API that aggregates and normalizes federal outdoor recreation data. One of the endpoints is a permit/availability layer over recreation.gov, similar territory to what you're doing here, but exposed as a REST API rather than a CLI. I'm also pulling in USFS trail data, SNOTEL snowpack, USGS streamflow, and avalanche hazards, so developers can get conditions alongside availability in a single interface.
One thought on potential overlap: if you ever want to layer in trail conditions or snowpack data alongside campground availability, Outdex could be a clean way to do that without wiring up multiple APIs yourself.
No ask here really, just wanted to connect. Would love to hear what you're thinking about for where OpenCamp goes next.
Hey! Came across OpenCamp while researching the recreation.gov API landscape. Great tool, the polling + email notification flow is exactly what the permit grind calls for.
I'm building Outdex (outdex.dev), a developer API that aggregates and normalizes federal outdoor recreation data. One of the endpoints is a permit/availability layer over recreation.gov, similar territory to what you're doing here, but exposed as a REST API rather than a CLI. I'm also pulling in USFS trail data, SNOTEL snowpack, USGS streamflow, and avalanche hazards, so developers can get conditions alongside availability in a single interface.
One thought on potential overlap: if you ever want to layer in trail conditions or snowpack data alongside campground availability, Outdex could be a clean way to do that without wiring up multiple APIs yourself.
No ask here really, just wanted to connect. Would love to hear what you're thinking about for where OpenCamp goes next.