Contributing

OpenHunt's code is a working platform, but its coverage is a community project by design. There is no national open parcel dataset — there are ~3,100 counties, and the plan for reaching them is the same one OpenAddresses proved: a registry where each source is one reviewable config file.

Add your county or state

The most valuable thing you can contribute needs GIS curiosity, not Rust:

1. Find your county assessor's parcel data (most counties have ArcGIS Hub or Socrata open-data portals; ~20 states publish statewide cadastral data).
2. Check the license. Record the exact terms. Sources that prohibit redistribution get redistributable: false and stay out of published tiles — see licensing rules.
3. Write the source YAML: URL, license, cadence, and the SQL mapping the source's fields onto the common schema.
4. Run the pipeline on it and look at the result in your local map.

Hunt units, walk-in access programs, and trail inventories for uncovered states follow the same pattern.

Code

The stack is Rust (pipeline, API) and TypeScript (web, mobile). The repo is a Cargo workspace plus per-app npm projects; each piece runs locally with what its README documents. CI builds and tests every push, including booting the self-host compose stack.

Code is AGPL-3.0: if you run a modified hosted version, you share your changes. That license choice is load-bearing — it's what keeps the open map from being quietly enclosed.

Where

Source, issues, and contributions: github.com/thull32/openhunt.

What not to contribute

Two standing project rules, so nobody wastes effort:

• No data from commercial hunting apps — not even "just to compare." Original sources only.
• No game-prediction features or "top spots" rankings. Transparent terrain math with published formulas; your compute on your screen — never editorial spot lists that manufacture crowding.