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

Source: https://datamodels.jp/en/models/transportation/RoadRestriction/ · Text CC BY 4.0

RoadRestriction draft ​

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

Kindentity
Type IRIhttps://datamodels.jp/ns/transportation/RoadRestriction
@contexthttps://datamodels.jp/context/transportation/v1.jsonld
JSON Schema/schema/transportation/RoadRestriction/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 relationshipsaddresslocationGeometryGeometry8 more links →JapaneseAddressJapanese address6 more links →RoadRestrictionRoad restriction

used as a value typeother subjectN more links: continued on that type's page

Attributes ​

AttributeDescriptionValue
roadNameRoad name
https://smartdatamodels.org/dataModel.Transportation/roadName
Property, string
roadTypeRoad class by the Road Act (Art. 3): expressway, nationalRoad, prefecturalRoad, municipalRoad, or other for a road outside the Act (farm, forest or private road). A motorway designation (自動車専用道路) is not a class: give the class of the road it is on
https://datamodels.jp/ns/transportation/roadType
Property, string: expressway | nationalRoad | prefecturalRoad | municipalRoad | other
addressAddress, as a JapaneseAddress value from the common subject
https://schema.org/address
Property, object: JapaneseAddress
location*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
https://uri.etsi.org/ngsi-ld/location
GeoProperty (Geometry)
restrictionLengthLength of the regulated section in metres, for a line. The NPA format's 距離・延長 (item 133) and EEI's 距離・延長; known even when the geometry is simplified
https://datamodels.jp/ns/transportation/restrictionLength
Property, number, ≥ 0
maximumAllowedWeightWeight limit in kilograms: vehicles heavier than this may not pass (for example 4000 when the source limit is 4 t). The same term as Smart Data Models RoadSegment; the NPA format gives it in tonnes (制限重量, item 135). Whether it is gross weight or payload follows the source; keep its wording in statusLabel
https://smartdatamodels.org/dataModel.Transportation/maximumAllowedWeight
Property, number, ≥ 0
restrictionStatusNormalised 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
https://datamodels.jp/ns/transportation/restrictionStatus
Property, string: closed | limited | open
regulationCategoryRegulation category, from the legend of MLIT's Road Information Provision System: closedWeather, closedConstruction, closedHeavyVehicle, closedWinter, laneRestriction, alternatingOneWay, mobileRestriction, chainRestriction, chainGuidance, other. closedWeather also covers closures after a disaster, such as a landslide or a collapsed road shoulder. Optional
https://datamodels.jp/ns/transportation/regulationCategory
Property, string: closedWeather | closedConstruction | closedHeavyVehicle | closedWinter | laneRestriction | alternatingOneWay | mobileRestriction | chainRestriction | chainGuidance | other
statusLabelThe restriction status in the local or source system's wording (e.g. 依頼中, 通行止め中, 解除済み). Required when restrictionStatus is left out
https://datamodels.jp/ns/task/statusLabel
Property, string
validFromWhen the restriction takes effect
https://smartdatamodels.org/validFrom
Property, string (date-time)
validToWhen the restriction is lifted
https://smartdatamodels.org/dataModel.Alert/validTo
Property, string (date-time)
descriptionFree-text memo
http://purl.org/dc/terms/description
Property, string

* 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/transportation/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: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
      ]
    ]
  },
  "restrictionLength": 150,
  "restrictionStatus": "closed",
  "regulationCategory": "closedWeather",
  "statusLabel": "通行止め中",
  "validFrom": "2026-07-08T10:45:00+09:00",
  "description": "アンダーパス冠水のため通行止め"
}

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.

Essential Elements of Information (EEI, 災害対応基本共有情報) version 1.1 (Cabinet Office, June 2025), item 05 道路関連: 通行止め情報(規制情報) (road closures and restrictions)8 of 12 fields

EEI lists the disaster information that response bodies share through the Cabinet Office's disaster information system (SOBO-WEB). It names the data attributes and marks each as 基本共有データ属性 (basic: required when exchanging, may be empty) or 特定データ属性 (specific: recommended), with no data types or code lists. All attributes of 通行止め情報 are basic. EEI splits date and time into separate attributes, so validFrom and validTo each correspond to two.

This modelMaps toNote
roadType道路種別(基本)EEI defines no values (its examples: 高速自動車国道, 自動車専用道路)
roadName路線名(基本)
location規制場所始点、規制場所終点(基本)the first and last points of the line (LineString); a point gives only the start; an area has no counterpart
restrictionLength距離・延長(基本)both in metres
regulationCategory規制種別(基本)EEI defines no values (the content of the regulation)
description規制理由(基本)both are free text
validFrom規制開始日、規制開始時間(基本)
validTo規制終了日、規制終了時間(基本)
restrictionStatusno counterpartEEI has no status attribute; a lifted restriction has its end date and time
statusLabelno counterpart
maximumAllowedWeightno counterpart
addressno 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

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

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 modelMaps toNote
regulationCategory凡例(通行規制の種別)1:1 mapping: 通行止(異常気象等)→closedWeather, 通行止(工事)→closedConstruction, 大型通行止→closedHeavyVehicle, 冬期通行止→closedWinter, 車線規制→laneRestriction, 片側交互通行→alternatingOneWay, 移動規制→mobileRestriction, チェーン規制→chainRestriction, チェーン指導→chainGuidance, その他規制→other
restrictionStatusno counterpart
locationno counterpartthe 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)

Mapping file (YAML) for this standard: mlit-road-info-prvs.yaml (see Mapping files)

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

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 modelMaps toNote
location規制場所の経度緯度 / 点規制・線規制・面規制borrows the point/line/area classification, not the raw coordinate columns
regulationCategoryno counterpartnot 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)
restrictionLength距離・延長(項目133)both in metres; the length of a line regulation's section
maximumAllowedWeight制限重量(項目135)tonnes in this standard, kilograms here (multiply by 1000); vehicles above this value are restricted; whether it is payload or gross weight depends on the regulation type
description規制理由both are free text; no coded vocabulary exists in either
validFrom意思決定日(新規)
validTo意思決定廃止日

Mapping file (YAML) for this standard: npa-traffic-regulation-format.yaml (see Mapping files)

Smart Data Models RoadSegment (dataModel.Transportation)5 of 11 fields

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 modelMaps toNote
roadNameroadNamesame IRI
addressno counterpart
locationlocationRoadSegment's location is a LineString for the whole segment; here it can be a point, line or area regulated section
restrictionStatusstatussame value space closed / limited / open
regulationCategoryno counterpartnot in RoadSegment; comes from MLIT's Road Information Provision System (see mlit-road-info-prvs.yaml)
statusLabelstatusDescription
restrictionLengthno counterpartRoadSegment's length is the whole segment's length in kilometres, not the length of the restricted part
maximumAllowedWeightmaximumAllowedWeightsame IRI, both in kilograms
validFromno counterpart
validTono counterpart
descriptionno counterpart

Mapping file (YAML) for this standard: sdm-roadsegment.yaml (see Mapping files)

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 → 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.
  • With the national restriction categories it covers road restrictions in general (roadworks, winter closures, lane and chain restrictions), not only closures caused by disasters.
  • 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).
  • restrictionLength (length of the regulated section, metres) and maximumAllowedWeight (weight limit, kilograms): Wakayama Prefecture's road restriction data (34 real records, #85) has them, and so do other standards: the length is in the NPA format (item 133) and EEI, the weight limit in the NPA format (item 135, tonnes) and Smart Data Models RoadSegment (same IRI). Direction (上り/下り), detour and contact are only in Wakayama's data, so they are not added and go into description; the NPA format gives direction as coordinates. Smart Data Models' roadWork (causes such as LANDSLIDE, FLOOD) was considered but not adopted: no Japanese source has matching categories.
Change history (2)
  • 2026-09-25 (#55, during the pre-release): moved from the disaster subject to transportation and renamed from RoadClosure. 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.
  • 2026-10-02 (#149, during the pre-release): restrictionLength and maximumAllowedWeight added.