EvacuationShelter draft

Evacuation shelter operation

Operational overlay for one evacuation shelter. The shelter master data (name, location) is not included; it is referenced by externalShelterId / nationalShelterId. Only opening status and evacuee counts live here. Models the operation of a 指定避難所 (designated shelter, Basic Act on Disaster Management Art. 49-7), a distinct legal concept from the 指定緊急避難場所 (designated emergency evacuation site, Art. 49-4).

Japanese name	避難所運用状況
Type IRI	https://datamodels.jp/ns/disaster/EvacuationShelter
@context	https://datamodels.jp/context/disaster/v1.jsonld (alias, latest compatible version) https://datamodels.jp/context/disaster/v1.0.0.jsonld (this version, immutable)
JSON Schema	/schema/disaster/EvacuationShelter/v1.json /schema/disaster/EvacuationShelter/v1.0.0.json
Examples	key-values · normalized
Source	github.com/geolonia/datamodels

Attributes

externalShelterId

required

The shelter's ID in the municipality's 指定緊急避難場所一覧 (自治体標準オープンデータセット, the Digital Agency's municipal standard open dataset; unique within the municipality, e.g. CC0100022200). Together with localGovernmentCode it identifies the shelter nationwide. That dataset has no item definition for 指定避難所 itself, so this ID borrows the emergency-evacuation-site list's numbering (see nationalShelterId below)

• Value: Property, string
• IRI: https://datamodels.jp/ns/disaster/externalShelterId

nationalShelterId

The nationwide common shelter/evacuation-site ID (assigned by the Cabinet Office's new comprehensive disaster information system, SOBO-WEB, via GSI's shelter-data maintenance web system). 14 characters: fixed 'E' + 5-digit municipality code + 5-digit facility code + major type code ('1' = designated shelter, the only value valid on this model) + minor type code ('1' = general shelter, '2' = welfare shelter) + a 1-character sequence starting at 1 (never 0). Also published as the '共通ID' column of GSI's designated-shelter CSV data. Optional: omit the property entirely, rather than send an empty string, when no ID is assigned yet

• Value: Property, string
• IRI: https://datamodels.jp/ns/disaster/nationalShelterId

localGovernmentCode

required

Local government code of the municipality that publishes the shelter list (全国地方公共団体コード per MIC's "全国地方公共団体コード仕様", 2007-04-01; 6 digits including the check digit)

• Value: Property, string
• IRI: https://datamodels.jp/ns/common/localGovernmentCode

openingStatus

Normalised opening state: open, closed, full (open but at capacity), requested (opening has been requested/instructed but not yet confirmed open; no public controlled vocabulary defines this state). The local wording always also goes in statusLabel. When no value fits, leave it out and send only statusLabel

• Value: Property, string: open | closed | full | requested
• IRI: https://datamodels.jp/ns/disaster/openingStatus

statusLabel

The opening status in the local or source system's wording (e.g. 未開設, 開設中, 満員, 依頼中). Required when openingStatus is left out

• Value: Property, string
• IRI: https://datamodels.jp/ns/task/statusLabel

evacueeHouseholds

Number of evacuated households

• Value: Property, integer, ≥ 0
• IRI: https://datamodels.jp/ns/disaster/evacueeHouseholds

evacueeTotal

Total number of evacuees

• Value: Property, integer, ≥ 0
• IRI: https://datamodels.jp/ns/disaster/evacueeTotal

evacueeFemale

Number of female evacuees

• Value: Property, integer, ≥ 0
• IRI: https://datamodels.jp/ns/disaster/evacueeFemale

evacueeMale

Number of male evacuees

• Value: Property, integer, ≥ 0
• IRI: https://datamodels.jp/ns/disaster/evacueeMale

description

Free-text memo

• Value: Property, string
• IRI: https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.8.jsonld#description

openedAt

Time the shelter opened

• Value: Property, string (date-time)
• IRI: https://datamodels.jp/ns/disaster/openedAt

closedAt

Time the shelter closed

• Value: Property, string (date-time)
• IRI: https://datamodels.jp/ns/disaster/closedAt

Example (key-values)

The examples are a fictional scenario (heavy rain in Chiyoda, Tokyo). Place names and codes are real; the events, people and teams are invented. See writing examples.

{
  "id": "urn:ngsi-ld:EvacuationShelter:0012",
  "type": "EvacuationShelter",
  "externalShelterId": "13101-0012",
  "nationalShelterId": "E1310100012111",
  "localGovernmentCode": "131016",
  "openingStatus": "open",
  "statusLabel": "開設中",
  "evacueeHouseholds": 12,
  "evacueeTotal": 30,
  "evacueeFemale": 16,
  "evacueeMale": 14,
  "description": "物資不足",
  "openedAt": "2026-07-08T09:00:00+09:00"
}

Example (normalized)

{
  "@context": [
    "https://datamodels.jp/context/disaster/v1.0.0.jsonld",
    "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.8.jsonld"
  ],
  "id": "urn:ngsi-ld:EvacuationShelter:0012",
  "type": "EvacuationShelter",
  "externalShelterId": {
    "type": "Property",
    "value": "13101-0012"
  },
  "nationalShelterId": {
    "type": "Property",
    "value": "E1310100012111"
  },
  "localGovernmentCode": {
    "type": "Property",
    "value": "131016"
  },
  "openingStatus": {
    "type": "Property",
    "value": "open"
  },
  "statusLabel": {
    "type": "Property",
    "value": "開設中"
  },
  "evacueeHouseholds": {
    "type": "Property",
    "value": 12
  },
  "evacueeTotal": {
    "type": "Property",
    "value": 30
  },
  "evacueeFemale": {
    "type": "Property",
    "value": 16
  },
  "evacueeMale": {
    "type": "Property",
    "value": 14
  },
  "description": {
    "type": "Property",
    "value": "物資不足"
  },
  "openedAt": {
    "type": "Property",
    "value": {
      "@type": "DateTime",
      "@value": "2026-07-08T09:00:00+09:00"
    }
  }
}

Link header

Link: <https://datamodels.jp/context/disaster/v1.jsonld>; rel="http://www.w3.org/ns/json-ld#context"; type="application/ld+json"

How to validate data and send it to a broker: Using the models.

Corresponding standards: Guideline (checklist) for shelter operation and evacuation-life support, April 2016 (revised December 2024), Cabinet Office (Disaster Management)

Guideline (checklist) for shelter operation and evacuation-life support, April 2016 (revised December 2024), Cabinet Office (Disaster Management)

This checklist backs the claim that openingStatus and the evacueeTotal-family attributes are officially recognised operational tracking concepts. Checklist items 1-3 "confirm the shelter's opening status" (p.25), 2-1 "publicise the shelter's opening status" (p.28), 5-2 "report evacuee headcount periodically" (p.26). However, no controlled vocabulary for the specific opening-status values was found here or in the Digital Agency dataset. openingStatus's enum (open/closed/full/requested) is this catalog's own normalisation, not a copy of a public code list; the local wording must always also be kept in statusLabel.

This model	Maps to	Note
openingStatus	開設状況（チェックリスト項目 1-3, 2-1）	the enum values are not quoted from a public code list
statusLabel	no counterpart	no corresponding item in the guideline; this catalog's own escape hatch so local wording is never dropped
evacueeHouseholds	no counterpart
evacueeTotal	避難者人数の定期報告（チェックリスト項目 5-2）
evacueeFemale	no counterpart
evacueeMale	no counterpart

Corresponding standards: The nationwide common shelter/evacuation-site ID (assigned via the Cabinet Office's new comprehensive disaster information system, SOBO-WEB, and GSI's shelter-data maintenance web system; also published as the '共通ID' column of GSI's designated-shelter/evacuation-site CSV data)

The nationwide common shelter/evacuation-site ID (assigned via the Cabinet Office's new comprehensive disaster information system, SOBO-WEB, and GSI's shelter-data maintenance web system; also published as the '共通ID' column of GSI's designated-shelter/evacuation-site CSV data)

A 14-digit nationwide common ID whose structure was published in the Cabinet Office's 2024-11-07 slide deck (slides 6-7). GSI's designated-shelter/evacuation-site download site (https://hinanmap.gsi.go.jp/hinanjocp/hinanbasho/koukaidate.html, confirmed 2026-09-24) carries it as the '共通ID' column of both the nationwide 指定緊急避難場所 and 指定避難所 CSVs. SOBO-WEB is designed to join the dynamic '開閉情報' (opening/closing) and '避難者数' (evacuee count) layers on this ID (same slide deck, slide 7) -- the same overlay pattern this model uses. No licence statement was found on the download page.

This model	Maps to	Note
nationalShelterId	共通ID	optional in this model, and restricted to major-category=1 (designated shelter) IDs only (enforced by schema.json's pattern); for shelters not yet assigned an ID, omit the property entirely rather than send an empty string

Corresponding standards: Municipal standard open dataset, data item definition sheet A (2026-08-01), sheet '03. designated emergency evacuation sites' (Digital Agency)

Municipal standard open dataset, data item definition sheet A (2026-08-01), sheet '03. designated emergency evacuation sites' (Digital Agency) · 公共データ利用規約（第1.0版）(PDL1.0), compatible with CC BY 4.0

The shelter master a municipality publishes. This type is the operational overlay and references a master row by externalShelterId and localGovernmentCode; evacuee counts are not in the master. Caveat: this sheet defines 指定緊急避難場所 (designated emergency evacuation site, Basic Act on Disaster Management Art. 49-4), a legally distinct concept from 指定避難所 (designated shelter, Art. 49-7) that this model is actually about. The Digital Agency dataset has no item-definition sheet for 指定避難所, so externalShelterId borrows the emergency-evacuation-site list's ID scheme as a practical fallback. Prefer nationalShelterId (see mapping/gsi-national-shelter-id.yaml) to reference the shelter itself.

This model	Maps to	Note
externalShelterId	ID (項目No.2)	unique within the municipality
nationalShelterId	no counterpart	not present in this dataset; carried as the '共通ID' column of GSI's designated-shelter data instead (see mapping/gsi-national-shelter-id.yaml)
localGovernmentCode	全国地方公共団体コード (項目No.1, localGovernmentCode)
openingStatus	no counterpart
statusLabel	no counterpart
evacueeHouseholds	no counterpart
evacueeTotal	no counterpart	maxCapacity is on the master side
evacueeFemale	no counterpart
evacueeMale	no counterpart
description	備考 (remarks)	different meaning: master remarks vs operational memo
openedAt	no counterpart
closedAt	no counterpart

Notes

• Derived from the Custom Data Models of the Takamatsu City flood-prevention headquarters application (geolonia/geonicdb-datamodels, September 2026). Type names generalised from the tenant-specific "Saitai" prefix; attribute names aligned with the task subject.
• From the source application: status → openingStatus, normalised to open | closed | full | requested, with the local wording in statusLabel; evacuee counts are integers (strings in the source); memo → description. requested covers the application's 依頼中 (opening requested or instructed, not yet confirmed).
• This model is the operation of a 指定避難所 (designated shelter, Basic Act on Disaster Management Art. 49-7), which the law distinguishes from a 指定緊急避難場所 (designated emergency evacuation site, Art. 49-4). List 03 of the Digital Agency 自治体標準オープンデータセット (successor of the 推奨データセット since 2023-03-31) covers only the latter; its ID is what externalShelterId holds, together with localGovernmentCode. The GSI publishes separate nationwide lists for both kinds, each with a 共通ID column.
• nationalShelterId is that 共通ID: the 14-character nationwide shelter ID of the Cabinet Office's SOBO-WEB system (slides of 2024-11-07). The Cabinet Office uses the same ID to join opening status and evacuee counts to the shelter, which is the overlay this model describes.
• The Cabinet Office shelter-operation guideline (April 2016, revised December 2024) names confirming and publishing the opening status and reporting evacuee counts as operational tasks, but defines no code list for the status. The openingStatus values are this catalog's normalisation; statusLabel keeps the local wording.
• localGovernmentCode follows the MIC specification of the 全国地方公共団体コード (2007-04-01): 5-digit JIS X 0401/X 0402 code plus a check digit.
• Upstream considered: Smart Data Models has no shelter type. Deferred: a day and night split of evacuee counts (Cabinet Office daily shelter report form, 2020), the 一般避難所 / 福祉避難所 subtype and maxCapacity; the last two belong to the shelter master, not to this operational overlay.
• The project relationship (to a task subject Project) was removed on 2026-09-25 (#66): it came from the source application, where every entity belonged to one disaster event, and neither the shelter guidelines nor the municipal dataset has it. Grouping shelters by operation is left to the application: a task subject Task points at a shelter with refersTo, or an extended model adds its own relationship.

Model content on this page is licensed under CC BY 4.0. LICENSE-CONTENT