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

Source: https://datamodels.jp/en/models/common/Geometry/ · Text CC BY 4.0

Geometry draft value type ​

A GeoJSON geometry (RFC 7946) as the value of a GeoProperty such as location: Point, LineString, Polygon, their multi forms (MultiPoint, MultiLineString, MultiPolygon), or a GeometryCollection of these. Positions are longitude, latitude and optional altitude, in WGS 84. A model may narrow the allowed types, for example to Point only.

Kindvalue type: used inside an attribute, not as an entity of its own
IRIhttps://datamodels.jp/ns/common/Geometry
@contexthttps://datamodels.jp/context/common/v1.jsonld
JSON Schema/schema/common/Geometry/v1.json
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 relationshipslocationlocationlocationlocationlocationlocationlocationlocationlocationGeometryGeometryDesignatedShelterDesignated shelter3 more links →EvacuationSiteDesignated emergency evacuation site3 more links →AEDLocationAED location4 more links →FacilityFacility6 more links →MedicalInstitutionMedical institution4 more links →PublicToiletPublic toilet4 more links →ProjectProject3 more links →TaskTask5 more links →RoadRestrictionRoad restriction1 more link →

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

Using this model ​

Other models use this value type as the value of an attribute. Checking data that has such an attribute reads this schema too (Validate 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
{
  "type": "Polygon",
  "coordinates": [
    [
      [
        139.7515,
        35.693
      ],
      [
        139.755,
        35.693
      ],
      [
        139.755,
        35.6955
      ],
      [
        139.7515,
        35.6955
      ],
      [
        139.7515,
        35.693
      ]
    ]
  ]
}

Files: example.json

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.

Municipal standard open dataset, data item definition sheet A (2026-08-01), latitude and longitude (Digital Agency)1 of 3 fields

Datasets 01–03, 05 and 07–15 of definition sheet A give the location as two columns, 緯度 (latitude) and 経度 (longitude), written by the rules of GIF's core data part 地理座標 as decimal degrees in a string (e.g. 43.064310). This becomes a Geometry of type Point. GeoJSON puts longitude first.

This modelMaps toNote
typeno counterpartalways Point
coordinates経度 (longitude), 緯度 (latitude)numbers in the order [longitude, latitude] (converted from the strings)
coordinates[2]no counterpart高度の種別 / 高度の値 (heightType, height) are a floor number, an elevation above mean sea level or a height above ground, not the third GeoJSON coordinate; leave them out of the coordinates

Mapping file (YAML) for converting data from this standard: jichitai-opendata-location.yaml (see Mapping files)

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

Notes ​

  • A value type, not an entity type. Use it as the value of the core location GeoProperty (or another GeoProperty) and reference the schema with $ref from an entity schema. The member names (type, coordinates, bbox) and the geometry types (Point, Polygon and so on) are terms of the NGSI-LD core context and expand to the GeoJSON-LD vocabulary; the catalog mints only the class for any of these geometries.
  • Stricter than RFC 7946 alone: a position has two or three numbers, and a multi-geometry, a Polygon or a GeometryCollection has at least one member. A model narrows the allowed types with a type constraint next to the $ref, as DesignatedShelter does for Point.
  • RFC 7946 §3.1.6 requires every linear ring to close (first and last position identical). JSON Schema cannot express this; the catalog's validator checks the rings of every example in the catalog, and consumers should check instances with a GeoJSON-aware library.
  • The class is minted (https://datamodels.jp/ns/common/Geometry) because the GeoJSON-LD vocabulary (https://purl.org/geojson/vocab#) defines the individual geometry types but no class for a geometry in general. OGC's Simple Features vocabulary (http://www.opengis.net/ont/sf#Geometry) has such a class, but GeoJSON values in NGSI-LD expand to the GeoJSON-LD types, not to Simple Features.
  • Upstream considered (2026-09-25): the GeoJSON schemas at geojson.org (JSON Schema draft-07 while this catalog uses 2020-12; GeometryCollection in a separate file; unversioned URLs; empty coordinate arrays accepted) and Smart Data Models Location-Commons in common-schema.json (six types without GeometryCollection; defines a whole location property rather than a reusable geometry; published on master only). Neither can be referenced as it is; this schema follows the same RFC 7946 structure.
  • The NGSI-LD core context (v1.8) defines coordinates and bbox but not geometries, so in JSON-LD processing a GeometryCollection's geometries expand to the core context's default vocabulary, and a collection with a single member compacts back to an object instead of an array. Brokers that store GeoJSON as it is are not affected.