The objective of the RICT (Representation Information CiTy) project is to experiment, exchange and share both knowledge and tools dedicated to the concrete handling of urban/city data. RICT focuses on practilities and technical specificities of the full city data flow starting from database integration of raw data and ending in advanced visualizations of their downstream numerical treatments. RICT adopts an open approach and favors:
- the adoption of mainstream standards of the urban modeling field
- the re-use (and possible improvement/evolution) of existing open source software components
In particular RICT focues on the design and realization of
- a backend:
- an infrastructure enabling the storage of city related data,
- an infrastructure for hosting and executing computational models (using the local backend data as well as online open data).
- a frontend:
- a simple interactive visualizer of the backend data
- a computational model treatment handler (configure, trigger, explore results of a treatment)
We believe that in order to succeed with data usage one must not separate data concerns (information models, database infrastructure) from the offered tools, treatment process and the associated methodology. Questions like how to migrate a database when the information model changes (e.g. from CityGML version 2 to version 3), how to deal with information model modularity and extensions, what are the interactions between data and their treatment or how does one handle data storage and computation scale up, must be dealt at first. RICT will try to propose good practices for doing so.
- MAM and games: a joint project with the Gamagora internship program focusing on the Model AugMented (MAM) approach
- MAM as a mediation tool: Model AugMented Model (MAM) approach with the Erasme team
- Model AugMented: MAM 2018 Erasme (proof of concep)t:
We collect use case oriented early descriptions of the needs. Prior to any particular technical choice, this description of needs can help to
- structure/organise the various involved roles
- decompose the processes in atomic tasks and describe assembled processes Eventually this structured description can
- lead to/orient good practices
- influence/structure the main architecture of components
The aimed backend features could be:
- offer some ETL tools starting from standard (or de facto standards used by mainstream crowd sourcing site like OpenStreetMap) of City related data
- distributed logical data (?)
- abstract level data access (i.e. use accessor API that are directly derived out of UML expressed information models
- computational model execution engine
The aimed frontend features could be:
- 3D visualization of a territory
- Use the iTowns JS/WEBGL component (?)