Docs / Data sources / Recreation.gov

Recreation.gov

Government

Built when you ask for it

Sync Recreation.gov federal recreation data into your warehouse. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.

The Recreation.gov connector syncs your federal recreation data into analytics-ready tables in your data warehouse. Pull facilities, campsites, permits, and activities from the Recreation Information Database (RIDB) API, with Ingest handling auth, pagination, and retries so the tables stay current.

What you would get

Each of these arrives as its own table, kept current on the schedule you choose:

  • Facilities
  • Campsites
  • Permits
  • Activities

How it gets built

  1. Choose Recreation.gov when you set up a pipeline, with the warehouse it goes to and a schedule.
  2. Ingest reads Recreation.gov's documentation, and you choose the tables you want.
  3. Ingest builds the connector and tests it against Recreation.gov itself.
  4. A person at Ingest reviews and publishes it, and your pipeline starts on its own.

What you will need

API key. Request a free RIDB API key from your Recreation.gov profile.

You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.

Questions

Does Ingest have a Recreation.gov connector?
Not as a finished connector yet. Ingest builds it from Recreation.gov's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
Which warehouses can Recreation.gov data go to?
Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
Do I need to write code?
No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Recreation.gov API documentation: https://ridb.recreation.gov/docs

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.

Request Recreation.gov