Pre-release. Until the official launch, content may change, including published files.
Skip to content

Source: https://datamodels.jp/en/models/disaster/EvacuationShelter/ · Text CC BY 4.0

EvacuationShelter draft ​

Evacuation shelter operation

Operational overlay for one evacuation shelter. The shelter master data (name, location) is not included: the designated shelter is referenced by shelter (DesignatedShelter) or by externalShelterId / nationalShelterId, and one of the three is required. Only opening status and evacuee counts live here. When the shelter is also a designated emergency evacuation site, site links to its EvacuationSite. 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).

Kindentity
Type IRIhttps://datamodels.jp/ns/disaster/EvacuationShelter
@contexthttps://datamodels.jp/context/disaster/v1.jsonld
JSON Schema/schema/disaster/EvacuationShelter/v1.json
DownloadCSV template Table Schema Structured output for AI PostgreSQL / PostGIS table About these files
LicenceCC0 1.0: the files (@context, JSON Schema, examples) can be used without conditions

These @context and JSON Schema URLs (version aliases) always point to the latest compatible version.
For URLs that never change, see Versions. More in URLs and versions.

Types and relationships ​

Types and their relationshipssheltersiteDesignatedShelterDesignated shelter3 more links →EvacuationShelterEvacuation shelter operationEvacuationSiteDesignated emergency evacuation site3 more links →

Relationship (attribute name)N more links: continued on that type's page

Attributes ​

AttributeDescriptionValue
externalShelterIdThe shelter's ID in the municipality's own shelter list (unique within it). Together with localGovernmentCode it is unique nationwide; the same ID as DesignatedShelter's externalShelterId. One of shelter, externalShelterId and nationalShelterId is required
https://datamodels.jp/ns/disaster/externalShelterId
Property, string
nationalShelterIdThe nationwide common shelter/evacuation-site ID (14 characters, the '共通ID' of GSI's data). Only type codes 11 (general designated shelter) and 12 (welfare shelter) are valid on this model. When none is assigned, leave the property out rather than send an empty string. Its structure and source are described once, in EvacuationShelter's mapping 'nationwide common shelter/evacuation-site ID' (gsi-national-shelter-id). One of shelter, externalShelterId and nationalShelterId is required
https://datamodels.jp/ns/disaster/nationalShelterId
Property, string
localGovernmentCode*Local government code of the municipality that publishes the shelter list (全国地方公共団体コード per MIC's "全国地方公共団体コード仕様", 2007-04-01; 6 digits including the check digit)
https://datamodels.jp/ns/common/localGovernmentCode
Property, string
shelterThe designated shelter (DesignatedShelter) this operation record is for. One of shelter, externalShelterId and nationalShelterId is required
https://datamodels.jp/ns/disaster/shelter
Relationship → DesignatedShelter
siteThe designated emergency evacuation site (EvacuationSite) at the same place, when the shelter is also one
https://datamodels.jp/ns/disaster/site
Relationship → EvacuationSite
openingStatusNormalised 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
https://datamodels.jp/ns/disaster/openingStatus
Property, string: open | closed | full | requested
statusLabelThe opening status in the local or source system's wording (e.g. 未開設, 開設中, 満員, 依頼中). Required when openingStatus is left out
https://datamodels.jp/ns/task/statusLabel
Property, string
evacueeHouseholdsNumber of evacuated households
https://datamodels.jp/ns/disaster/evacueeHouseholds
Property, integer, ≥ 0
evacueeTotalTotal number of evacuees
https://datamodels.jp/ns/disaster/evacueeTotal
Property, integer, ≥ 0
evacueeFemaleNumber of female evacuees
https://datamodels.jp/ns/disaster/evacueeFemale
Property, integer, ≥ 0
evacueeMaleNumber of male evacuees
https://datamodels.jp/ns/disaster/evacueeMale
Property, integer, ≥ 0
descriptionFree-text memo
http://purl.org/dc/terms/description
Property, string
openedAtTime the shelter opened
https://datamodels.jp/ns/disaster/openedAt
Property, string (date-time)
closedAtTime the shelter closed
https://datamodels.jp/ns/disaster/closedAt
Property, string (date-time)

* required

Using this model ​

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

  • To add attributes of your own to this model, the extension builder writes the @context and JSON Schema.

  • Extended this model? If you publish it on a site made with the toolkit, it shows on this page once your site is on the list of sites. Without a site, list your extension so others can reuse your names (how it works).

  • Files that particular brokers and tools can load as they are, made from this model: Adapters

  • The Link header, for sending data without @context in the body:

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

Example ​

Most examples are a fictional scenario (heavy rain in Chiyoda, Tokyo). Place names and codes are real; the events, people and teams are invented. Some examples copy a real row of a published list instead; their notes name the source. See writing examples.

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

Files: example.json · example-normalized.jsonld · Open in the JSON-LD Playground: see the full IRI behind every attribute (expanded form).

Something missing or wrong?

Open an issue, or propose new attributes or models with the proposal form. How it works: Contributing. The source files (notes, mapping tables) are on GitHub.

Referenced standards ​

The standards this model corresponds to, field by field. Open one to see its table.

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

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 modelMaps toNote
openingStatus開設状況(チェックリスト項目 1-3, 2-1)the enum values are not quoted from a public code list
statusLabelno counterpartno corresponding item in the guideline; this catalog's own escape hatch so local wording is never dropped
evacueeHouseholdsno counterpart
evacueeTotal避難者人数の定期報告(チェックリスト項目 5-2)
evacueeFemaleno counterpart
evacueeMaleno counterpart

Mapping file (YAML) for this standard: cao-hinanjo-guideline.yaml (see Mapping files)

Essential Elements of Information (EEI, 災害対応基本共有情報) version 1.1 (Cabinet Office, June 2025), item 21 避難所等: 避難所 (shelters), the attributes collected during a disaster (災害時取得)9 of 14 fields

For what EEI is and its 基本 (basic) and 特定 (specific) classes, see the EvacuationSite table. The attributes kept in normal times (name, address, shelter type) are in DesignatedShelter, reached through shelter. The basic attributes 開設状況 and 避難者数(総数) have fields here. Specific attributes with no field: 開設理由 (reason for opening), occupancy against capacity, needed staff support, drinking water, toilet counts, needed supplies, infection-control supplies (shortage and number needed) and living conditions (space, beds, bathing, laundry, blankets). 避難所開設情報(都道府県別集計) is a total, counted from the individual shelters.

This modelMaps toNote
nationalShelterId全国共通避難所・避難場所ID(基本)
localGovernmentCode地方公共団体コード(基本)
openingStatus開設状況(基本)EEI's values are 未開設 (not open yet), 開設 (open), 閉鎖 (closed), 不明 (unknown), 常設 (permanent) and the like. open → 開設 (a permanent shelter is open too, with 常設 in statusLabel); closed → 未開設 if it never opened or 閉鎖 if it closed after opening, as statusLabel and openedAt tell; full → 開設 (open and at capacity; EEI's 定員状況, specific, has no field here); requested → 未開設. For 不明, leave openingStatus out and put 不明 in statusLabel
statusLabel開設状況(基本)the local wording; send it when no EEI value fits
evacueeTotal避難者数(総数)(基本)in EEI the sum of men and women, including people who came on their own
evacueeMale避難者数(男)(特定)
evacueeFemale避難者数(女)(特定)
shelterno counterpartEEI joins the two sets of attributes by the same 全国共通避難所・避難場所ID
siteno counterpart
externalShelterIdno counterpart
evacueeHouseholdsno counterpart
openedAt開設日時(特定)
closedAt閉鎖日時(特定)
descriptionno counterpart

Mapping file (YAML) for this standard: eei.yaml (see Mapping files)

Licence of this standard: Public Data License (Version 1.0) (PDL1.0) under the Cabinet Office website terms of use (内閣府ホームページ利用規約), compatible with CC BY 4.0

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)1 of 1 fields

A 14-character 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.

14 characters = 1-character fixed identifier 'E' + 5-digit municipality code (serial number of the municipal code) + 5-digit facility code (serial per municipality) + 1-digit major type code (1 = designated shelter, 2 = designated emergency evacuation site) + 1-digit minor type code (meaningful only when major = designated shelter -- 1 = general shelter, 2 = welfare shelter; 0 when major = emergency evacuation site) + 1-character sequence number (count of same-type facilities at the same address; 1-9 then A-Z, a-z)

This modelMaps toNote
nationalShelterId共通IDoptional 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

Mapping file (YAML) for this standard: gsi-national-shelter-id.yaml (see Mapping files)

Municipal standard open dataset, data item definition sheet A (2026-08-01), sheet '03. designated emergency evacuation sites' (Digital Agency)3 of 13 fields

The master of designated emergency evacuation sites a municipality publishes. This sheet defines 指定緊急避難場所 (designated emergency evacuation site, Basic Act on Disaster Management Art. 49-4), a legally distinct concept from the 指定避難所 (designated shelter, Art. 49-7) this model is about. A row of the sheet is an EvacuationSite, which this operation record links with site when the shelter is also a site. The shelter itself is a DesignatedShelter, referenced by shelter or nationalShelterId (mapping/gsi-national-shelter-id.yaml). Evacuee counts are not in the master.

This modelMaps toNote
externalShelterIdno counterpartthe ID of item No. 2 identifies the emergency evacuation site, EvacuationSite's externalSiteId (see the site row); externalShelterId is the ID in the municipality's shelter list
siteID (項目No.2)find the EvacuationSite by this ID (its externalSiteId) and localGovernmentCode, and link it
nationalShelterIdno counterpartnot 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)
openingStatusno counterpart
statusLabelno counterpart
evacueeHouseholdsno counterpart
evacueeTotalno counterpartmaxCapacity is on the master side (EvacuationSite's maxCapacity)
evacueeFemaleno counterpart
evacueeMaleno counterpart
description備考 (remarks)different meaning: master remarks vs operational memo
openedAtno counterpart
closedAtno counterpart

Mapping file (YAML) for this standard: jichitai-opendata-shelter.yaml (see Mapping files)

Licence of this standard: Public Data License (Version 1.0) (PDL1.0), compatible with CC BY 4.0

Notes ​

  • Derived from the Custom Data Models of a municipal disaster-response application (September 2026; its source is not public). Type names generalised by removing a tenant-specific 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). The shelter itself is a DesignatedShelter; an operation record names it by shelter, by externalShelterId (the municipality's own ID for the shelter, as on DesignatedShelter) or by nationalShelterId, and one of the three is required (#118). List 03 of the Digital Agency 自治体標準オープンデータセット (successor of the 推奨データセット since 2023-03-31) covers only 指定緊急避難場所: its ID identifies an EvacuationSite (externalSiteId), which site links. 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 一般避難所 / 福祉避難所 type and the capacity belong to the shelter, not to this operational overlay: they are shelterType and maxCapacity on DesignatedShelter.
  • 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.
  • site links to the EvacuationSite at the same place (the 指定緊急避難場所 a municipality publishes). shelter links to the DesignatedShelter, the 指定避難所 itself, from GSI's designated shelter data.
Change history (3)
  • 2026-09-25 (#66): the project relationship (to a task subject Project) was removed. 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.
  • 2026-09-28 (#85): site added, now that the catalog had a type for the 指定緊急避難場所 a municipality publishes. The 指定避難所 itself got a type with #105: DesignatedShelter.
  • 2026-09-30 (#118): one of shelter, externalShelterId and nationalShelterId is required. Before, externalShelterId was required and meant the ID of list 03.