Activity catalogue (cross-NGO)
Atlas view
Activity catalogue (cross-NGO)
api_v1.activity_catalogOne row per organisation and activity, with its Atlas service category.
First 5 rows ·
api_v1.activity_catalogsnapshot 2026-05-12
| activity_id | ngo_orgnr | canonical_name | service_category_code | service_category_label_no | is_active | chapter_count |
|---|---|---|---|---|---|---|
| redcross-aktiviteter-pa-asylmottak | 864139442 | Aktiviteter på asylmottak | migrant_mentoring | Flyktningguide | true | 35 |
| redcross-aktiviteter-pa-utlendingsinternat | 864139442 | Aktiviteter på utlendingsinternat | migrant_mentoring | Flyktningguide | true | 1 |
| redcross-akuttovernatting-for-bostedslose-tilreisende | 864139442 | Akuttovernatting for bostedsløse tilreisende | housing_outreach | Boligoppsøking | true | 3 |
| redcross-barnas-rode-kors | 864139442 | Barnas Røde Kors | youth_activity_groups | Ungdomsgruppe | true | 107 |
| redcross-beredskap | 864139442 | Beredskap | first_aid_standby | Beredskapsvakt | true | 171 |
Built from
This Atlas view joins data from the following upstream sources. Click through for provenance, methodology, and citation.
Atlas internal model ↗
dim_activity
Activity catalog — one row per (NGO, NGO-canonical activity name).
Atlas internal model ↗
fact_chapter_activities
The supply-side fact: one row per (chapter, activity) for every NGO in dim_ngo.
Showing direct dbt parents. See full lineage in /lineage/ →
Columns
| Column | Description |
|---|---|
| activity_id | Composite slug (e.g. 'redcross-besokstjeneste'). Stable across refreshes. Unique within this view. |
| ngo_orgnr | 9-digit Brreg organisasjonsnummer of the NGO offering the activity. |
| canonical_name | Atlas's canonical Norwegian name for the activity. |
| service_category_code | ICNPO-derived service category code (e.g. 'health', 'social-services'). FK to ref_atlas_service_category. |
| service_category_label_no | Human-readable Norwegian label for service_category_code, joined from ref_atlas_service_category. |
| is_active | Whether this activity is still offered by the NGO. Inactive activities are kept so historical analysis can still resolve activity_id values. |
| chapter_count | Count of distinct active chapters offering this activity. Zero when the activity exists in dim_activity but no active chapter provides it (rare but possible during transitions). |
Sample query
Live PostgREST query that returns the first 5 rows. URL adapts to the current host — local dev shows api-atlas.localhost; the deployed site shows the configured API base.
https://api-atlas.urbalurba.com/activity_catalog?limit=5
About this view
One row per organisation and activity, with its Atlas service category. Empty today.
🔵 EXPECTED EMPTY TODAY, AND THAT IS NOT A DEFECT. Its one row per (NGO, activity), so it is empty until Red Cross activity data is loaded.
Terje's position, 2026-09-21: the Red Cross data is not coming now, it
will be there later. The relation is published and answers so a consumer
can build against its shape before the rows arrive.
⚠️ A consumer cannot tell "empty by design" from "broken" without being
told, and two of these three were asked about on the day someone noticed
(urb-agents #1351). If this relation is still empty and this note is
gone, something regressed.
One row per (NGO, activity) joining dim_activity to the
service-category seed for the human-readable label, plus a count
of active chapters offering each activity. Backs the per-NGO
activity catalogue page (atlas-frontend
/ngo/[slug]/aktiviteter); equivalent to listActivities().
The full table is small (~35 rows for Red Cross alone in v1) and
grows as new NGOs land. PostgREST consumers filter via
?ngo_orgnr=eq.X.