Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Backfill ik_rating (IEC 62262 impact / vandal resistance)

Open
  • Is something wrong?
#162 8 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
data

Research direction

Start by searching cameras/ for features[] entries mentioning “vandal” or “IK” where ik_rating is missing; these are the quick-win targets. Check each manufacturer datasheet and add the stated rating as a top-level ik_rating field, applying the IK10-at-50-J exception noted in the issue. Leave the field undefined when no rating is stated; done means verified ratings are backfilled without guessing.

Written by the indexing model from the issue text.

Description

enhancement good first issue help wanted

Standing data-collection issue for ik_rating (from #137). Same empirical/community lane as SoC #122, Frigate-compat #154, and low-light lux #161.

The field

ik_rating — IEC 62262 mechanical-impact / vandal-resistance rating (IK00–IK11). Its own top-level field (not inside ip_rating).

Current coverage (of 11,421 cameras — 2.17.0 prep)

4,610 (40%) have it — up from 806. The remaining gap is concentrated in vandal-relevant housings: ~2,001 dome/turret cameras still lack an ik_rating (box / bullet / PTZ / consumer often carry no IK rating, legitimately blank).

Quick-win seed (do these first)

~102 cameras mention "vandal" or "IK" in their features[] but have no ik_rating field — the rating just needs extracting from features/datasheet into the structured field. (grep cameras/ for features containing "vandal"/"IK" without an ik_rating key.)

How to help

  • Read the IK rating off the manufacturer datasheet (e.g. "IK10") → set "ik_rating": "IK10".
  • Note: entries rated IK10 @ 50 J qualify as IK11 per the 2021 IEC 62262 Amendment 1.
  • Leave undefined if not stated — never guess.

Good batch targets: vandal-dome / turret families where the whole series shares an IK rating.

Sibling data-backfill lanes: #122 (SoC), #154 (Frigate autotracking), index #163.

Dominant language
JavaScript
Stars
267
Forks
21
Avg merge
4h 18m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ch-bas/cctv-camera-database

All issues in ch-bas/cctv-camera-database

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.