RoadRestriction draft

One road restriction, including closures: road name, regulated section (point, line or area), status, category and period.


Japanese name	通行規制
Type IRI	`https://datamodels.jp/ns/transportation/RoadRestriction`
@context	`https://datamodels.jp/context/transportation/v1.jsonld` (alias, latest compatible version) `https://datamodels.jp/context/transportation/v1.0.0.jsonld` (this version, immutable)
JSON Schema	`/schema/transportation/RoadRestriction/v1.json` `/schema/transportation/RoadRestriction/v1.0.0.json`
Examples	key-values · normalized
Source	github.com/geolonia/datamodels

Attributes

roadName

Road name

Value: Property, string
IRI: https://smartdatamodels.org/dataModel.Transportation/roadName

address

Address, as a JapaneseAddress value from the common subject

Value: Property, object: JapaneseAddress
IRI: https://schema.org/address

location

required

The regulated section, as a GeoJSON geometry (point, line or area), matching the point/line/area regulation forms of the NPA's traffic regulation data format

Value: GeoProperty (Geometry)
IRI: https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.8.jsonld#location

restrictionStatus

Normalised restriction state, the value space of Smart Data Models RoadSegment.status: closed (no traffic), limited (traffic possible but not in full capacity), open (restriction lifted or not yet in place). The local wording goes in statusLabel; a finer public-sector category goes in regulationCategory. When no value fits, leave it out and send only statusLabel

Value: Property, string: closed | limited | open
IRI: https://datamodels.jp/ns/transportation/restrictionStatus

regulationCategory

Regulation category, from the legend of MLIT's Road Information Provision System: closedWeather, closedConstruction, closedHeavyVehicle, closedWinter, laneRestriction, alternatingOneWay, mobileRestriction, chainRestriction, chainGuidance, other. Optional

Value: Property, string: closedWeather | closedConstruction | closedHeavyVehicle | closedWinter | laneRestriction | alternatingOneWay | mobileRestriction | chainRestriction | chainGuidance | other
IRI: https://datamodels.jp/ns/transportation/regulationCategory

statusLabel

The restriction status in the local or source system's wording (e.g. 依頼中, 通行止め中, 解除済み). Required when restrictionStatus is left out

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

validFrom

When the restriction takes effect

Value: Property, string (date-time)
IRI: https://smartdatamodels.org/validFrom

validTo

When the restriction is lifted

Value: Property, string (date-time)
IRI: https://smartdatamodels.org/dataModel.Alert/validTo

description

Free-text memo

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

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.

json

{
  "id": "urn:ngsi-ld:RoadRestriction:0001",
  "type": "RoadRestriction",
  "roadName": "靖国通り",
  "address": {
    "addressRegion": "東京都",
    "addressLocality": "千代田区",
    "machiaza": "九段南",
    "chome": "1",
    "jisMunicipalityCode": "13101",
    "addressText": "東京都千代田区九段南1丁目"
  },
  "location": {
    "type": "LineString",
    "coordinates": [
      [
        139.7505,
        35.695
      ],
      [
        139.752,
        35.6956
      ]
    ]
  },
  "restrictionStatus": "closed",
  "regulationCategory": "closedWeather",
  "statusLabel": "通行止め中",
  "validFrom": "2026-07-08T10:45:00+09:00",
  "description": "アンダーパス冠水のため通行止め"
}

Example (normalized)

json

{
  "@context": [
    "https://datamodels.jp/context/transportation/v1.0.0.jsonld",
    "https://uri.etsi.org/ngsi-ld/v1/ngsi-ld-core-context-v1.8.jsonld"
  ],
  "id": "urn:ngsi-ld:RoadRestriction:0001",
  "type": "RoadRestriction",
  "roadName": {
    "type": "Property",
    "value": "靖国通り"
  },
  "address": {
    "type": "Property",
    "value": {
      "addressRegion": "東京都",
      "addressLocality": "千代田区",
      "machiaza": "九段南",
      "chome": "1",
      "jisMunicipalityCode": "13101",
      "addressText": "東京都千代田区九段南1丁目"
    }
  },
  "location": {
    "type": "GeoProperty",
    "value": {
      "type": "LineString",
      "coordinates": [
        [
          139.7505,
          35.695
        ],
        [
          139.752,
          35.6956
        ]
      ]
    }
  },
  "restrictionStatus": {
    "type": "Property",
    "value": "closed"
  },
  "regulationCategory": {
    "type": "Property",
    "value": "closedWeather"
  },
  "statusLabel": {
    "type": "Property",
    "value": "通行止め中"
  },
  "validFrom": {
    "type": "Property",
    "value": {
      "@type": "DateTime",
      "@value": "2026-07-08T10:45:00+09:00"
    }
  },
  "description": {
    "type": "Property",
    "value": "アンダーパス冠水のため通行止め"
  }
}

Link header

http

Link: <https://datamodels.jp/context/transportation/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: Road Information Provision System, traffic regulation information (MLIT Road Bureau, road-info-prvs.mlit.go.jp, verified 2026-09-24)

Road Information Provision System, traffic regulation information (MLIT Road Bureau, road-info-prvs.mlit.go.jp, verified 2026-09-24)

The system that aggregates driver-facing road-regulation information from road administrators nationwide (regional bureaus, national highway offices) across Japan. Its legend's 10 categories were adopted verbatim as the value space of regulationCategory. No separate specification PDF could be found; the live system page's legend was used as the primary source. The GSI-hosted "road closure" dataset (geospatial.jp/ckan/dataset/1101, MLIT Road Bureau Disaster Prevention Division, last updated 2024-10-05) was checked as a related resource from the same system but adds no further item definitions beyond the legend.

This model	Maps to	Note
`regulationCategory`	`凡例（通行規制の種別）`	1:1 mapping: 通行止(異常気象等)→closedWeather, 通行止(工事)→closedConstruction, 大型通行止→closedHeavyVehicle, 冬期通行止→closedWinter, 車線規制→laneRestriction, 片側交互通行→alternatingOneWay, 移動規制→mobileRestriction, チェーン規制→chainRestriction, チェーン指導→chainGuidance, その他規制→other
`restrictionStatus`	no counterpart
`location`	no counterpart	the legend has no coordinate specification of its own (map-icon display only); the geometry taxonomy instead comes from the NPA format (see npa-traffic-regulation-format.yaml)

Corresponding standards: Traffic Regulation Information (Extended Standard Format) manual, Ver: k_2.1 (National Police Agency; published by JARTIC, first edition 2024-04-22, revised 2025-01-20)

Traffic Regulation Information (Extended Standard Format) manual, Ver: k_2.1 (National Police Agency; published by JARTIC, first edition 2024-04-22, revised 2025-01-20)

A nationwide common CSV format the National Police Agency defined (SIP phase 2 research) for prefectural police traffic-regulation databases to publish. It defines the location of a regulation as one of three forms, point/line/area regulation (点規制・線規制・面規制, section 3.5); this model's location (Point/LineString/Polygon) borrows that geometry taxonomy directly. Its regulation-type code table (73 types) centres on traffic-law regulations (one-way streets, no-parking, etc.), not disaster closures, so the codes themselves were not adopted. Its regulation-reason field (item 169) is 600-byte free text, not coded; this model's description follows the same practice.

This model	Maps to	Note
`location`	`規制場所の経度緯度 / 点規制・線規制・面規制`	borrows the point/line/area classification, not the raw coordinate columns
`regulationCategory`	no counterpart	not adopted; this standard's regulation-type codes are traffic-law codes with no disaster-closure category. regulationCategory instead comes from MLIT's Road Information Provision System (see mlit-road-info-prvs.yaml)
`description`	`規制理由`	both are free text; no coded vocabulary exists in either
`validFrom`	`意思決定日（新規）`
`validTo`	`意思決定廃止日`

Corresponding standards: Smart Data Models RoadSegment (dataModel.Transportation)

Smart Data Models RoadSegment (dataModel.Transportation)

RoadSegment is a road-network master; a closure corresponds to the status of a segment. This type borrows the status value space and the roadName IRI, and models the closure itself for municipalities that have no segment master.

This model	Maps to	Note
`roadName`	`roadName`	same IRI
`address`	no counterpart
`location`	`location`	RoadSegment's location is a LineString for the whole segment; here it can be a point, line or area regulated section
`restrictionStatus`	`status`	same value space closed / limited / open
`regulationCategory`	no counterpart	not in RoadSegment; comes from MLIT's Road Information Provision System (see mlit-road-info-prvs.yaml)
`statusLabel`	`statusDescription`
`validFrom`	no counterpart
`validTo`	no counterpart
`description`	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 → restrictionStatus, normalised to the RoadSegment value space closed | limited | open, with the local wording in statusLabel (依頼中 is open with the label 依頼中: the road is still passable); area → location (core term; the closed section is the location of the closure); memo → description; the flat town and block fields → address (JapaneseAddress).
Upstream considered (2026-09-18): Smart Data Models RoadSegment (a network master; a closure is a state of a segment the city does not have), RestrictedTrafficArea (regulation, not an incident) and Alert (a broadcast notice with roadClosed but no road name, alertSource required). None fits as a type. Borrowed: the RoadSegment status value space for restrictionStatus and the Transportation roadName IRI; validFrom/validTo from Smart Data Models.
Public-sector guidelines reviewed (2026-09-24). Adopted: (1) National Police Agency, 交通規制情報（拡張版標準フォーマット）説明書 Ver: k_2.1 (published by JARTIC, first edition 2024-04-22, revised 2025-01-20, https://www.jartic.or.jp/d/opendata/typeD_kisei_73_k_2.1.pdf) — its point/line/area regulation-form taxonomy (点規制・線規制・面規制, section 3.5) is the basis for widening location from LineString-only to Point/LineString/Polygon (see mapping/npa-traffic-regulation-format.yaml); its 経度緯度 field is 必須 (mandatory) for every regulation record, which is why location is now required. (2) MLIT Road Information Provision System, traffic regulation legend (road-info-prvs.mlit.go.jp, verified 2026-09-24) — its 10-category legend (通行止(異常気象等)/通行止(工事)/大型通行止/冬期通行止/車線規制/片側交互通行/移動規制/チェーン規制/チェーン指導/その他規制 — the site's own labels, verbatim) is the value space of the new regulationCategory attribute (see mapping/mlit-road-info-prvs.yaml).
Checked but not adopted: (1) Ministry of Internal Affairs and Communications, Fire and Disaster Management Agency (総務省消防庁) 災害報告取扱要領 (昭和45年4月10日消防防第246号, last amended 平成31年4月消防応第28号, https://www.fdma.go.jp/laws/laws/items/h3104_houkoku_youryou.pdf) does define 道路 (road, excluding bridges) as an official disaster-damage category in its 第1号様式, but only as an aggregate count of 箇所 (sites) for prefecture-level statistical reporting — a different granularity from a per-closure NGSI-LD entity, so no attribute was borrowed from it. (2) Digital Agency 自治体標準オープンデータセット (31 items, confirmed via https://www.digital.go.jp/resources/open_data/municipal-standard-data-set-test on 2026-09-24) has no road-closure or road-regulation item. (3) SIP4D-ZIP (JSA-S1016:2023, Japanese Standards Association) is a real, cited national data-sharing framework for disaster information, but its full text sits behind the JSA webdesk paywall; its road-closure field definitions could not be verified from freely available sources, so nothing was adopted from it; it remains open for review.
No public controlled vocabulary for closure cause (landslide/flooding/fallen tree, etc.) was found anywhere reviewed above; the NPA format itself keeps its own 規制理由 (regulation reason) as 600-byte free text, uncoded. description therefore stays free text for the cause, unchanged from before.
Moved from the disaster subject to transportation and renamed from RoadClosure on 2026-09-25, during the pre-release (#55): with the national restriction categories it covers road restrictions in general (roadworks, winter closures, lane and chain restrictions), not only closures caused by disasters. closureStatus became restrictionStatus with the same values. The project relationship (to a task subject Project) was removed at the same time: it came from the source application, where every entity belonged to one disaster event, and no national standard has it.
Grouping restrictions, for example by disaster-response operation, is left to the application: a task subject Task points at a restriction with refersTo, or an extended model adds its own relationship (see the extension pattern in the GeonicDB guide).

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

RoadRestriction draft ​

Attributes ​

roadName ​

address ​

location ​

restrictionStatus ​

regulationCategory ​

statusLabel ​

validFrom ​

validTo ​

description ​

Example (key-values) ​

Example (normalized) ​

Link header ​

Corresponding standards: Road Information Provision System, traffic regulation information (MLIT Road Bureau, road-info-prvs.mlit.go.jp, verified 2026-09-24) ​

Corresponding standards: Traffic Regulation Information (Extended Standard Format) manual, Ver: k_2.1 (National Police Agency; published by JARTIC, first edition 2024-04-22, revised 2025-01-20) ​

Corresponding standards: Smart Data Models RoadSegment (dataModel.Transportation) ​

Notes ​