We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Digital Twins: Metropolitan Cooperation Platform and Underground Network

00:00

Formal Metadata

Title
Digital Twins: Metropolitan Cooperation Platform and Underground Network
Title of Series
Number of Parts
156
Author
Contributors
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Digital twins and 3D are becoming increasingly important for planning, data diffusion and decision-making. Several projects are currently underway at Camptocamp, in collaboration with Virtual City Systems and Cesium. We will present two very different use cases: developments around Rennes Métropole and the underground network for the SUEZ project. Rennes Métropole In a context of digital transition and the increasing availability of urban data, Rennes Métropole wishes to better equip its decisions and public policies on the basis of data and cooperation. Ultimately, the goal is to promote cooperation and the contribution of the different actors and "enlighten" public decisions and policies, in particular the democratic, ecological and energy transition projects. Issues of transparency, public service efficiency and cost control are also sought. The platform is developed partly on VC Map which is an Open-Source JavaScript framework and API for building dynamic and interactive maps on the web. It can display 2D data, oblique imagery and massive 3D data including terrain data, vector data, mesh models, and point clouds making it easy for users to explore and interact with the data in an integrated and high-performance map application. VC Map is built upon open, proven, and reliable GIS and web technologies such as OpenLayers and Cesium for the visualization of 2D and 3D geo-data. A particular effort was made on the design in order to offer users, mainly citizens, a pleasant user experience that allows an exploration of the development projects of the metropole in 2D and 3D. We will present the cooperation platform through three use cases of interest for Rennes Metropole : simulation of the photovoltaic production potential, linear transport systems and exposure to electromagnetic waves. SUEZ As part of its work in the field of water management, SUEZ has a number of requirements for 3D data visualization, particularly for underground data. The project focuses on two main areas: the visualizer and data preparation. The visualizer is designed to be integrated into an application developed by SUEZ. It is based on Cesium, to which specific functionalities have been added. One of the major challenges was to integrate two types of navigation into the same application: * Constrained navigation. Possibility of positioning oneself in an underground pipe and moving through it without passing through the walls, with video game-style controls * Free navigation. More traditional 3D controls with floor transparency The other aspect of the project is data preparation. A processing chain was set up to construct the pipe tubes, whose data was initially in 2D. Other objects in IFC format, such as pumping stations, were merged and added to the model, while allowing them to be queried via Cesium. Finally, a textured 3D mesh was used to realistically reproduce the interior of the pipes. The challenge was to ensure consistency between these heterogeneous data sources provided by SUEZ.
Keywords
127
Computer networkComputing platformUsabilityMetropolitan area networkContext awarenessPersonal digital assistantCollaborationismOpen sourceSoftwareEnterprise architecturePlanningData managementSystem programmingInformationOffice suiteModel theoryFinite element methodLocal GroupVirtual realityDigital electronicsTwin primeSoftware maintenanceDecision theoryMilitary operationGroup actionSound effectVisualization (computer graphics)Latent heatImplementationWaveLevel (video gaming)AudiovisualisierungSimulationVector potentialEmulatorMaxima and minimaCommercial Orbital Transportation ServicesPole (complex analysis)Lie groupStack (abstract data type)Plug-in (computing)Interface (computing)Core dumpLibrary (computing)AbstractionFile viewerParametrische ErregungConfiguration spaceStructural loadData managementProjective planeDigital electronicsTwin primePoint cloudCommercial Orbital Transportation ServicesFisher informationFeedbackComputer simulationCubeWordAreaVisualization (computer graphics)Electronic visual displayLine (geometry)Green's functionMereologyReliefService (economics)Finite element methodBuildingAbstractionBitCASE <Informatik>MappingPhysical systemSimulationMultiplication signPlug-in (computing)Slide ruleCollaborationismLibrary (computing)Model theorySoftware developerInterface (computing)Core dumpInformationFocus (optics)TouchscreenWindowTransportation theory (mathematics)Cartesian coordinate systemProduct (business)SummierbarkeitOpen sourceGroup actionGoodness of fitRepresentation (politics)Electromagnetic radiationDecision theoryReal numberSoftware maintenanceConstructor (object-oriented programming)VirtualizationConfiguration spaceLecture/ConferenceComputer animation
AbstractionFile viewerConfiguration spaceModel theoryParametrische ErregungLibrary (computing)Structural loadCore dumpComputer networkMetropolitan area networkComputing platformSoftware frameworkComponent-based software engineeringPlug-in (computing)GUI widgetContent management systemInterface (computing)DisintegrationMarkov chainContext awarenessInteractive televisionRepresentation (politics)FreewareConstraint (mathematics)Structural equation modelingVideoconferencingSimilarity (geometry)Game theoryCalculationMathematical optimizationOrientation (vector space)Control flowData conversionTheoryObject (grammar)Workstation <Musikinstrument>Cylinder (geometry)Stochastic processHybrid computerStandard ModelComputer fileServer (computing)Extension (kinesiology)CuboidDebuggerVideo gameIntegrated development environmentProjective planeSoftwareGame controllerStochastic processMarkov chainTesselationSoftware repositoryData managementView (database)Multiplication signInteractive televisionSpherical capWeb 2.0Context awarenessOrientation (vector space)InformationBitDifferent (Kate Ryan album)Model theoryHybrid computerContent (media)Motion captureData conversionSoftware frameworkCartesian coordinate systemCASE <Informatik>Functional (mathematics)Representation (politics)Type theoryInstance (computer science)Plug-in (computing)Proof theoryComponent-based software engineeringUniform resource locatorInterface (computing)Position operatorWordLibrary (computing)Electronic program guideTemplate (C++)Constraint (mathematics)MereologyWater vaporGroup actionAsynchronous Transfer ModeConfiguration spaceLevel (video gaming)Fuzzy logicDemosceneOpen sourceText editorCoordinate systemComputer animationLecture/Conference
Dot productSpecial unitary groupLeast squaresComputer animation
Transcript: English(auto-generated)
So, hello, I'm Yves, I'm project manager at Cam2Camp, and we'll talk about digital twins with Ben here from Virtual City Systems. So yes, we'll have two parts of the talk. First we will talk about the Rennes Metro Project, so Rennes is a city in France.
Then I will have a word about Suez Project, that is quite a different one. It's two digital twins, but quite different, you will see. So first, maybe a word about Cam2Camp. So we are a company, a service company, founded in 2001.
Now I guess we are 200 now, it's growing. We're based in France, Germany, and Switzerland, and active in three areas, but always open source. First department about ERPs, so business solutions,
infrastructure solutions, more cloud management, and of course, Joe's special, and that's my department. Yeah, hello from me, my name is Ben. I work at Virtual City Systems in Berlin, Germany. We are not as many as Cam2Camp, we're just about 25 people.
And we focus on 3D city models, I think that's the core of the company. We do a lot of development, and we do some project work. And the project work mainly revolves around urban planning and digital twins.
But also urban simulations, so we're a member of the COTFEM group, we're big on finite element simulation. And we have a lot of colleagues in Krafing, which is close to Munich, that do fancy stuff with your 3D data to simulate wind, climate, detonations,
as you can see in the picture here. Detonations, well. Okay, so now about this project here at WEN. So what is a digital twin? First, a digital twin is a virtual representation of some reality.
When we speak about this digital twin, maybe we think about cities and 3D, but it could be anything and even 2D, if it's a virtual representation of some reality. And so in the case of REMetropol, the goals of the project was those five goals.
It sees, there are general goals for digital twins, I guess, manage public policies, cooperate with citizens, also work with professionals, and of course support decisions. So by modelization, simulation.
And at the end, one goal also is to follow the project, so from design to maintenance. In the case of this project, REMetropol, the main focus was the cooperation with citizens.
So the goal of the project in one sentence, it's a participative portal, so collaboration with citizens. Based on a 2D and 3D visualization, it's a digital twin, of course, and what was very important for the customer, open source.
And WEN is here. There. Okay, we had three use cases in this project. First is the solar cadastro, so it's a simulation of solar panels on roofs.
About transportation, so it was to display new lines, new transport lines, and to have feedbacks from citizens. And the last one is about visualization of electromagnetic waves, so antennas, where they are, and technical stuff about those antennas.
Three main challenges in the project. First, it was co-construction, so we did work with virtual city systems, but also with designers, because of the fact that the general public is the end user. It was very important to work with designers,
and the designers did work with some citizens to have feedback and to have a very good UI and user experience. And of course, performance and reliability, because WEN is quite a big city, and so we will have a lot of users,
we hope to have a lot of users using the application. And I guess that's the case. So now some screenshots. The first use case about simulation of photovoltaic production.
So this is an example of the digital twin we have with the solar radiation on buildings. Then on the next screen, you can have an automatic,
it's automatic that they put the solar panels on the roof that you selected, and then you can remove some solar panels if they are windows or chimneys, et cetera. And so you can remove them. And then you have here 36, I guess, yes,
36 solar panels, and it is displayed on the roof. And at the end, the user can see a simulation of the electric production during the year with nice crafts, et cetera.
Second one is about public transportation. So here we have the display of a future new line in the WEN city. And the goal here is to have some kind of mediation
with the citizen, and the citizen can also give feedback if they're happy with the new transportation line. The third one is about only visualization in this case, so that we can see the antennas where they are,
have information, technical information, and know about the electromagnetic waves emissions. Yep. Thank you. So I'm gonna be talking a bit about what you just saw
and how we participated. As it said, it was a co-production. And then Metropol was lucky to have designers work directly with the end user, which is tricky and very expensive, time-consuming to do. So what you saw in the slides, what we provided
is basically just this geospatial stack that we use. So we use open layers, we use cesium in the background, we use PostGIS, or we use 3D CityDB, which is also maintained by us most of the time, and we combine it into a library.
And this was the first thing that we put open source was this library, so it's just, we call it CORE, it's just a GIS library, and after the project and also the things we did with then, we realized we need more on top, because not everybody has the money or the time for designers and these long discussions.
So on top of the CORE, we also built a UI, which is just a basic UI, and most of the time, you have very special use cases, like we had with Renn Metropol, so we started implementing a plugin interface, and then we started developing a lot of plugins ourselves,
which we then also put open source. And I'm gonna quickly talk about this. So first of all, we have this CORE library, which we've used in the Renn Metropol project, and this is basically all the mapping you saw was done using this library. It has an abstraction, so that was one
of the important bits with Renn Metropol, so you can seamlessly move from 2D to 3D, and even if you have oblique imagery, you can move to that as well, which makes it easier for users that aren't that versed in GIS to kind of navigate, and it also makes for nice models, which is also important for city planning,
is that you can have semi-3D data visualized, so you know this is gonna be a building, and you know how high it's gonna be, maybe, but you don't have an architectural model yet. This is what you see here. You can do these little green cubes, or blue cubes, or whatever, and just kind of say, okay, this is where I wanna build. And we made it in a way that
you can save these configuration files somewhere, and put it onto a server, and then the end user can just reload this configuration. That makes it easier to deploy, so you don't need a backend component. You can just configure the front end using a JSON file, and push it onto a server, and that's that.
And then we started building a UI framework, which kind of just helps with basic map navigation, and content management. It's based off of Vodify and Vue. For those of you who know it. And it just provides basic components that you would need,
and some components that you would need in a GIS environment, like coordinate input, or an extent, bounding box editor, things that you don't have in a typical UI framework. And then we just started developing functionality, and we thought, previously we had the functionality
just as part of the library, but with all these specialized use cases, and we don't know what use cases are to come, we decided to only have a minimal functionality in the library, in the UI itself, and push everything into plugins that we develop ourselves, but we opened the plugin interface as much as possible,
so that anyone could develop a plugin. And right now we have about 20-ish plugins that we've placed open source. You can find them on GitHub. Mainly used for those functionalities that you typically need, search, draw, analyze.
There's some scene handling things that are nice, so you can change the view mode to first person, so that you can walk around your city. You can generate camera flights, these things. But if you don't need that, you can just not include it into your application, and you don't have the fuzz of all these many buttons and functionalities,
which was also something that was important in REN, is that they said the end user just wants to do one thing. They don't want to do anything else. So we kind of tried to implement that in that way, that you can do just the one thing if you want to. And then we created a tool to help you easily do this yourself.
And this is basically how we run our own research projects, but this could work for any research project. It's all open source, and it kind of guides you through a setup step. Kind of try to display this here. It guides you through what you want to do. You can choose from a template you want to start out with.
Start it, and you have your Web GIS application running, and can start adding your own functionality. And this has proved to be very speedy, and it's also fairly easy to learn, so junior developers can start pretty fast. And as of last year, or this year, it's also completely typed in TypeScript,
which was important to us as well. Thank you. So now about this Suez project, it's quite different. The context, so Suez is a company
that works for water and waste management, and the goal was here to have a POC, to proof of concept, to know about this network they built, and have detailed technical information
about the network of pipes, et cetera. So the main goal here is to develop a web component with two types of models. First, a visitable network,
you will see afterwards with some screenshots, and also non-visited, non-visitable networks. So the fact that some models are here only virtual, and other are captured, and you will see the difference afterwards.
One challenge here was the fact that we have two types of navigation. One is the classic navigation for any cesium model, and the second one is indoor mode,
so the goal is to navigate inside the pipes, and to be able to see if there are problems in the pipes, et cetera. And the challenge was to have a smooth transitions between the two modes.
So we used cesium, cesium with advanced features to be able to go underground. The goal was to have a complete and detailed representation of the reality, and to have a better experience for user,
interactive, and engaging. So yes, now you understand what I meant by indoor navigation. It's not very indoor, but it's in pipes. So yeah, this is a constrained navigation.
This is quite challenging to do, to be able to have a precise control of the camera position. Also the ability to recenter the camera, because if you go a bit too close to the sides of the pipes, you have to come back to the center.
Also about orientation, of course. And to have an intuitive way of walking inside the pipe, we changed the navigation to have a navigation similar to video games. So a word about the data.
We have three kind of sources. The first one, it was about the location of the pipes. So the source was 2D. And so it was possible then to decide
where to put the pipes. And we had also information like the depth of the pipes, the size of it, et cetera. Then we had some information for the models that were not the pipes. So for instance, pumps, et cetera.
And it was some standard models and not so captured data like you saw for the pipes. And for this we used FME. And the last one is, yeah, thank you. The last one is, yeah, the pipes themselves.
So the captured data for the inside of the pipes. And this was a bit more complex with a hybrid processing chain. And it came from the capture of the 3D data. Yeah, so thank you for your attention, I guess.
Thank you for inspiring talk. And thank you for your questions. I hope there are some. I believe there are some. Give me some questions.
Is the conversion process that you had to 3D tiles through Postgres and the other forms, that's also in the GitHub repo that you're open sourcing for the pipeline processing?
You mean this, yeah? Yeah, not the FME, but the OBJ and the. I have to check with, I was not the project manager of this, I have to check, but I could. I think it was quite specific to the project. Come back to me, I will have the answer.
Yeah, I have only a question about the solar cluster. Which data did you use to calculate it? Like a leader or? The data was provided by the customer, actually. So also here I have to check for, to answer exactly that.
We don't provide the data in most of our projects that come to camp, the data is provided by the customer. So yeah, if you want to have the answer, I have to check further.
Thank you. Maybe someone here and backwards when I'm here. Someone in the middle. So many thanks, one more time. Thank you.