T.4.6 - Web client


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • -Presentation-Smart cities is a theme of interest due to the continuos expansion of the city and the need to do this in a intelligent and eco friendly way. The ICT can contribute to this develop by means of new and innovative platform that can be used to plan and manage the city evolution. -A standard format to collect all the needed inforamtion about the city and the landscape is mandatory to obtain interoperability campabilities and fast data exchange
  • The main functionality of the Iscope web client is to visualize in a user friendly environment all the needed information.Those can be stored in the central system or calculated in real time, depending on the complexity of the operation and the needs to keep the results stored ( for example to reutilize it)The client we are developing is based on a open source virtual globe and is based on the java web applet tecnology. In this way a user need only a computer and a internet connection to acces the system.Thanks to the client server architecture is possible to abtaina light and fast client, using mostly the processing power of the server.
  • As well know the main functionality of the Iscope proj are : realistic visualization of a 3d city model described in teh cityGml lenguage on top of this we can visualize different informative layers like the solar potential of the roof surfaces, the values of teh noise pollution of the city and some navigation function expecially delivered for diversly able cityzen.
  • All the needed information will be retrieved from the server, both using some standard ogc services and some custom developed services.The client is compatible with some widely used ocg standard like the wms, wfs and also the openLs interface for the routing purpose.To access some functionality some custom service access has been developed: the noise value acquired from the crowd are accessible using a specific API developed for the noiseTube initiative. The central system will answer the client using the Json technology.Also to access and retrieve the cityGml data a custom service is used.As will be shown many different technology exist to access this kind of data, but the custom integration has been chosen to simplify the integration and to obtain a good speed.
  • To provide the CityGml data to the client is possible to use the standard Wfs service. We tested it in some old prj and this kind of service is really powerful, allowing many different operations, but has the drawback of a really slow response.
  • At the state of the art we can find the w3ds service. At the moment this is only a draft proposal and not a standard. We are working to implement and try this kind of services, but at the moment only for testing and comparison purpose. An implementation inside the geoBrowser is really difficult due to the really different system architecture.
  • T.4.6 - Web client

    1. 1. Presented by:Fondazione Graphitech, Italy
    2. 2. 3D web client• The Entry Point to access i-ScopeServices• Based on a Open Source Virtual GlobeSDK• Integrated into webpage as appletcomponent• Client/Server architecture-oriented• User friendlyWeb Client: Overview
    3. 3.  Noise pollution:• punctual noise value as acquired fromthe crowd• averaged value as a noise mapWeb Client: Main Functionality Energetic values as:• Building roof solar potential• Facade energy dissipation (New Castle Pilot) Routing for diversely-able citizen Realistic 3d city model
    4. 4. Connection with some widely used standardservices, such as:• WMS• WFS• WCS• WPS• OpenLs• W3ds ( possible future implementation)Connection with personalized services:• NoiseTube (jSon formatted answer)• personalized CityGml providing serviceWeb Client: data provider services
    5. 5. Web Client: Realistic 3d city modelPossible approaches to send data to the client:• WfsStandardServiceReallycomplicatedimplementationand slowresponse fromthe serverProsCons
    6. 6. Web Client: Realistic 3d city modelPossible approaches to send data to the client:• W3dsPossible futurestandardservice, and 3dorientedOnly a draftdocumentation,really compleximplementationinside the usedOpen SourceGlobe SDKProsCons
    7. 7. Web Client: Realistic 3d city modelPossible approaches to send data to the client:• Custom serviceTotallycustomizableservice, fastserver response,easyimplementationNot a standardserviceProsCons
    8. 8. • The heat loss of the buildings facades can be represented only byapplying textures to the model  cityGml appearance modelWeb Client: building heat loss and roof solarpotential• The roof solar potential can be visualized in some different manner: Using a standard WMS service to stream to the client a layer representing all therequested information Applying textures to the model’s roofs  cityGml appearance model Changing the colour of the roof as a function of a genericAttribute stored inside thecityGml modelCommon problemSending textures to the clientinvolves the transmission of a largeamount of data
    9. 9. Routing service:• Standard communication interfaceOpenLSWeb Client: routing and noise dataNoise data:• Direct connection to the noiseTube service using personalized API to visualize aspecific subset of acquired noise point (json response)• Use of a standard WMS service to retrieve the average noise value as rasterimages
    10. 10. Web Client: architecture
    11. 11. Thank you for your attentionContact detailsMarco SoaveFondazione GraphitechVia Alla Cascata, 56/C 38123Trento ITALYe-mail: marco.soave@graphitech.itWeb page: www.graphitech.it