##### About ##### Overview ---------- Urban datasets come in many forms. Every municipality and organization uses different formats, standards, and file structures to represent their buildings and related data, such as energy consumption and space occupancy. Various components of the **TOOLS**\4CITIES ecosystem consume urban datasets, both from closed and open sources, but that means each tool needs code to read, parse, and clean data for its own purposes, which may lead them to become incosistent, redundant, and hard to maintain. To ensure quick, flexible, and consistent access to urban datasets, we developed `CITYdata `_, a middleware that abstracts away these complexities and allows users to work with diverse urban data sources through a unified, extensible interface. Rather than reimplementing data handling logic across each tool, CITY\ **data** provides a standardized approach to data integration through the following abstractions: - **Producer**: connects to data sources and fetches data. - **Operation**: describes transformations to be performed on producer outputs (data). - **Runner**: calls a series of producers, executes a series of operations on the producer's outputs, and then outputs the resulting data. .. figure:: ../images/CITYdata-simplified-architecture.png :width: 1000 :alt: CITY\ **data** detailed subsystem view :align: center CITY\ **data** exposes Producers and Operations through a REST API, making it easy to use as a standalone tool or integrate with existing tools. We are working towards making CITY\ **data** a unified data access tool to serve the entire **TOOLS**\4CITIES ecosystem. If you would like to know more about CITY\ **data** architecture and the research work behind it, please check the :doc:`/citydata/architecture/index` and :doc:`/citydata/references/index` pages. Current state of the project ----------------------------- CITY\ **data** is currently being developed by the `Ptidej Team `__, under the supervision of Dr. Yann-Gaël Guéhéneuc.