Frequently asked questions.

An independent collection of reported search and rescue incidents in Colorado. Each record brings together a summary, location, and available source reports. It is a historical reference, not a live rescue service or an official count of all incidents.

Coverage varies by year, place, and responding agency. A place with more records is not necessarily more dangerous, and a year with fewer records does not necessarily mean fewer rescues. Some dates, outcomes, and other details may be approximate or inferred; read the notes and original sources.

Entries collect reported Colorado search and rescue incidents from public sources. Contributors provide source links and document uncertainty; the maintainer reviews submissions and duplicate candidates before promotion. Inclusion is not independent verification of every reported fact. Check the original reports and notes.

Follow the contribution guide. Submit one JSON file per new incident, or propose a correction to the existing record with supporting sources and its stable ID. You can also open an issue; please do not include private medical or contact information.

Yes. Both the project code and incident dataset, including JSON and SQLite downloads, are covered by the MIT license. You may use, copy, modify, and redistribute them, including commercially, provided you retain the copyright and license notice. Linked third-party reporting and images remain subject to their owners' rights and are not covered by this license.

Daniel (@dgriff03) maintains this independent archive. It is not an official SAR agency service. Contributions are reviewed through the public repository.

Email Daniel at dgriff@typetwo.dev with questions about the archive.

Google Analytics collection is currently paused while automatic URL tracking is disabled. The replacement configuration allows only coarse page names, without search queries, incident IDs, titles, hashes or referrers. It respects Do Not Track and Global Privacy Control. Search filters remain in shareable URLs, so avoid entering private information.

Two reports about the same rescue should count as one incident. Share both stable IDs in an issue or follow the merge instructions. Reviewed merges combine sources and preserve uncertainty; the old incident link resolves to the surviving record.

Yes. Open a minimal removal request with the incident ID or source domain and a brief explanation. Please do not post sensitive personal or medical information. The maintainer reviews requests and can exclude individual incidents, specific source URLs, or a full domain and its subdomains. An exclusion withholds the entire matching incident, including merged copies, from future website, database and MCP builds. See the removal process. Live removal requires deployment; repository history and previously downloaded copies require separate handling.

Yes. Contributions may not cite 14ers.com or its subdomains. Validation and promotion reject such submissions, including submissions that also cite other sources. Published snapshots also omit accepted records matching the domain restrictions or removal exclusions. Review the source rules. Do not substitute a shortlink or copied version to bypass a restriction.

Domain and URL hashes let the build recognize excluded sources without listing their full addresses in that registry. They are lookup fingerprints, not encryption or guaranteed anonymity: a known domain can be guessed and hashed. Incident IDs are stored directly. The configuration and normalization rules are documented for contributors.