> For the complete documentation index, see [llms.txt](https://mims.oascities.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mims.oascities.org/mims-specification-v9.0/geospatial-data/capabilities-and-requirements.md).

# Capabilities and Requirements

## **C1: Cities and communities can easily transfer geospatial data between internal and external (including IoT-related) IT systems**

**Requirements:**

**R1.1** Geospatial data shall be exposed through a standards-based web service interface.

## **C2: Cities and communities can integrate 2D and 3D geospatial data coming from a variety of sources, for example geodata and building information models, and share that data within and between them in an interoperable way**

**Requirements:**

**R2.1** Geospatial data shall be encoded using open standards. It is recommended to use relevant standards from OGC and BuildingSMART International.

## **C3: Cities and communities can integrate geospatial data with other data that can provide further information about the context**

**Requirements:**

**R3.1** All data sets used to provide further information about the context covered by geospatial data shall comply with MIM1 and MIM2.

## **C4: Cities and communities have a consistent and persistent way of describing individual instances of all features, things or entities included in the geospatial data sources**

**Requirements:**

**R4.1** Unique and persistent identifiers shall be used to identify particular instances of any entity used in data sets. *(See MIM1: Interlinking Data.)*

## **C5: Coordinate Reference Systems (CRS) used in data sharing are easily transformable into a common CRS**

**Requirements:**

**R5.1** Coordinate Reference Systems (CRS) shall comply with standards, and information shall be provided regarding which standard (e.g. EPSG:4326, EPSG:3857) is being used. This includes the EPSG number or WGS number, along with information about any variation based on national systems such as the Latvian LKS-92, so that data can be transformed to a common CRS. *(Note: Within the EU, for geospatial data it is required to use metadata compliant with the INSPIRE Directive, including the metadata needed to describe the CRS information.)*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://mims.oascities.org/mims-specification-v9.0/geospatial-data/capabilities-and-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.