ºÝºÝߣ

ºÝºÝߣShare a Scribd company logo
3D-Ondergrond Services DINO
Ìý
3D-ondergrondviewer TNO
Visualisatieomgeving en services
VISUAL : nadruk op inzicht bieden via aan elkaar gelinkte visuele aspecten van 3D-modellen
Results TNO super users workshop VISUAL project Combine data e.g. borehole data projected on cross sections Make links to layered documentation Also make use of Google Maps and Google Earth Show uncertainties Reveal all thematic info at once: 1D, 2D and 3D Be open for feedback and user generated content
Context sensitive documentation in a cross section
Context sensitive documentation in MS Excel
Use of ontology for referencing documents documenten DMS CWS Kaarten ONTOLOGY DINOLoket Nomenclator 3DModelServices Modellen DinoMap

More Related Content

Tn oservices

Editor's Notes

  1. Of this sheet we have most applications running. DINO WEB SHOP only uses the cross section capability, Heat and Cold Storage TOOL TAUW uses the properties per depth interval capability, and HASKONINGs ArcGIS Explorer consumes the virtual borehole capability form the SOAP/WSDL web service. BRO WEB SHOP is our new general web site for data and model dissemination under development. The cross section on Google Earth still has its own service based on a Collada data file.
  2. This is what TNO has running extended with CityGML and BIM/IFC for the building industry. This sector is in need of spatial information from the neighbourhood (?) or surroundings (?) of building works under design or under construction integrated in the Building Information Models (BIM). As long as the BIMs cannot cope with INSPIRE compliant meta data and data services, we have to improvise with a separate portal for the building sector.
  3. The visualisation should cover all aspects of the 3D world
  4. So the visualisation framework (as we call it at TNO) should have the capability to deal with several formats offered by the various servers.
  5. After an inventory of visual aspects of 3D models (1D, 2D, 3D, etc.) 130 possible interactions have been identified. Together with the users a selection of most wanted interactions will be determined. Implementation will take place within the selected web platform FLEX. Objects should be selectable for various operations: invoke interactions with other objects (maybe in other views), order object data and download, or for request of underlying information about the object, the context, the model or basic notions from the domain ontology.
  6. The possibility to request additional information of various levels, here 3: member, formation and model.
  7. Context sensitive information in an Excel sheet that uses the depth-interval-capability of the the web service.
  8. The position of the domain ontolog as central facility for requesting underlying information and disclosure of documents