Skip to content

Commit 127e906

Browse files
docs(charter): add copy-as-is conversion rule + eo-dat/VAP examples
- Document the Charter→Monty conversion principle: source items are carried over as-is (geometry, assets, eo/sar/sat/view/proj/processing, disaster: fields), with only STAC-consistency fixes and the Montandon specifics added. - Add two worked Response examples converted from the S3 fixtures (Act-1019 / Call-1166): - charter-response-1166-phr1a-0907-00777.json — eo-dat calibrated Pléiades acquisition (call-keyed id; imagery extensions + assets preserved). - charter-response-1019-1166-19.json — Act-1019 VAP (eo-gra), with a related/response sibling link to the eo-dat item. - Wire both into the charter-response collection; clarify its title/description and refresh extent/summaries; update examples/index.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1 parent fe9e94a commit 127e906

5 files changed

Lines changed: 5461 additions & 9 deletions

File tree

docs/model/sources/Charter/README.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,27 @@ to Monty STAC items.
2222
- **License**: partner access (Terradue-granted, IP-allowlisted)
2323
- **Temporal coverage**: 2000-11-05 onwards (Charter formation)
2424

25+
## Conversion principle — copy-as-is + Montandon specifics
26+
27+
> The Charter Mapper already publishes valid STAC, so the conversion is a
28+
> **pass-through**: each source item is carried over **as-is** — geometry, `bbox`,
29+
> assets, the imagery extensions (`eo:` / `sar:` / `sat:` / `view:` / `proj:` /
30+
> `processing:`), `providers`, and the Charter-native `disaster:` fields are all
31+
> **preserved**. The ETL only does two things on top:
32+
>
33+
> 1. **Fix STAC-level consistency issues** — normalise the legacy Terradue
34+
> `disaster:` v1.0.0 declaration to
35+
> [v1.1.0](#the-terradue-disaster-extension) (lowercase `disaster:class`,
36+
> plural `disaster:types` / `disaster:regions`), set `stac_version`, drop
37+
> null/internal bookkeeping fields, and repair anything that fails STAC validation.
38+
> 2. **Add the Montandon specifics** — the `monty` extension plus `monty:corr_id`,
39+
> `monty:country_codes`, `monty:hazard_codes`, `monty:response_detail`, the
40+
> `event` / `hazard` / `response` `roles`, the Monty `id` and `collection`, and
41+
> the typed `related` / `derived_from` links.
42+
>
43+
> Everything else in the source item is left untouched. The mapping tables below
44+
> describe only these two deltas — assume every other field rides along unchanged.
45+
2546
## Object model
2647

2748
### The process flow (Call → Activation → Areas/VAPs, Call → Acquisitions)
Lines changed: 142 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,142 @@
1+
{
2+
"stac_version": "1.1.0",
3+
"stac_extensions": [
4+
"https://ifrcgo.org/monty-stac-extension/v1.3.0/schema.json",
5+
"https://stac-extensions.github.io/file/v1.0.0/schema.json",
6+
"https://stac-extensions.github.io/version/v1.0.0/schema.json",
7+
"https://terradue.github.io/stac-extensions-disaster/v1.1.0/schema.json"
8+
],
9+
"type": "Feature",
10+
"id": "charter-response-1019-1166-19",
11+
"geometry": {
12+
"type": "Polygon",
13+
"coordinates": [
14+
[
15+
[
16+
-43.347,
17+
-21.771
18+
],
19+
[
20+
-43.323,
21+
-21.771
22+
],
23+
[
24+
-43.323,
25+
-21.728
26+
],
27+
[
28+
-43.347,
29+
-21.728
30+
],
31+
[
32+
-43.347,
33+
-21.771
34+
]
35+
]
36+
]
37+
},
38+
"properties": {
39+
"disaster:class": "vap",
40+
"updated": "2026-07-06T07:21:00.1512695Z",
41+
"disaster:activation_id": 1019,
42+
"datetime": "2026-03-10T19:47:05Z",
43+
"created": "2026-03-10T20:08:21Z",
44+
"title": "Geological Risk/Landslides Vitorino Braga, São Benedito, Vila Alpina Neighborhoods and Others, Juiz de Fora, Brazil [03/10/2026 19:47:05]",
45+
"copyright": "Includes Pleiades material © CNES (2026), Distribution Airbus DS.;INPE",
46+
"additional_information": "Map featuring a post-event Pléiades 1A HiRI image, overlaid with geological risk classifications and landslide polygons. The risk assessment was conducted by the National Secretariat for Civil Protection and Defense (SEDEC).",
47+
"vap_status": "ACCEPTED",
48+
"version": "2",
49+
"disaster:call_ids": [
50+
1166
51+
],
52+
"disaster:country": "BRA",
53+
"disaster:types": [
54+
"landslide"
55+
],
56+
"disaster:activation_status": "archived",
57+
"disaster:resolution_class": "VHR",
58+
"roles": [
59+
"response",
60+
"source"
61+
],
62+
"monty:country_codes": [
63+
"BRA"
64+
],
65+
"monty:hazard_codes": [
66+
"MH0901",
67+
"LS",
68+
"nat-geo-mmd-lan"
69+
],
70+
"monty:corr_id": "20260224-BRA-616285-MH0600-1-GCDB",
71+
"monty:response_detail": {
72+
"type": "eo-gra",
73+
"source_id": "1166-19",
74+
"producer": "INPE",
75+
"methodology": "human_interpreted",
76+
"sendai_targets": [
77+
"C",
78+
"D"
79+
]
80+
}
81+
},
82+
"bbox": [
83+
-43.347,
84+
-21.771,
85+
-43.323,
86+
-21.728
87+
],
88+
"assets": {
89+
"overview": {
90+
"type": "image/png",
91+
"roles": [
92+
"overview"
93+
],
94+
"title": "Value Added Product Overview",
95+
"href": "https://supervisor.disasterscharter.org/assets/activations/act-1019/vaps/act-1019-vap-1166-19/act-1019-vap-1166-19.json?key=overview",
96+
"file:size": 2284641
97+
}
98+
},
99+
"links": [
100+
{
101+
"rel": "related",
102+
"href": "../charter-events/charter-event-1019.json",
103+
"type": "application/geo+json",
104+
"roles": [
105+
"event"
106+
]
107+
},
108+
{
109+
"rel": "related",
110+
"href": "../charter-hazards/charter-hazard-1019-juiz_de_fora-qvwjejdb0iznzao3svgtow__-landslide.json",
111+
"type": "application/geo+json",
112+
"roles": [
113+
"hazard"
114+
]
115+
},
116+
{
117+
"rel": "related",
118+
"href": "./charter-response-1166-phr1a-0907-00777.json",
119+
"type": "application/geo+json",
120+
"roles": [
121+
"response"
122+
]
123+
},
124+
{
125+
"rel": "derived_from",
126+
"href": "https://disasterscharter.org/activations/flood-in-brazil-activation-1019-",
127+
"type": "text/html",
128+
"title": "International Charter activation Act-1019"
129+
},
130+
{
131+
"rel": "self",
132+
"href": "https://ifrcgo.org/monty-stac-extension/examples/charter-response/charter-response-1019-1166-19.json",
133+
"type": "application/json"
134+
},
135+
{
136+
"rel": "collection",
137+
"href": "https://ifrcgo.org/monty-stac-extension/examples/charter-response/charter-response.json",
138+
"type": "application/json"
139+
}
140+
],
141+
"collection": "charter-response"
142+
}

0 commit comments

Comments
 (0)