3D Portrayal Interoperability Experiment

Transcription

1 3D Portrayal Interoperability Experiment Benjamin Hagedorn Computergraphische Systeme Hasso-Plattner-Institut an der Universität Potsdam Workshop 3D-Stadtmodelle 2011 Bonn, 9. November 2011

2 OGC & 3DIM D Portrayal Interoperability Experiment Benjamin Hagedorn 2

3 What is the Open Geospatial Consortium? The OGC A non-profit, international voluntary consensus standards organization that is leading the development of standards for geospatial services that support interoperable solutions that "geoenable" the Web, wireless and location-based services and mainstream IT. Facilitates a consensus process in which Members from currently 424 organizations collaborate to define and maintain OGC standards. 35 Adopted standards D Portrayal Interoperability Experiment Benjamin Hagedorn 3

4 Open Geospatial Consortium The OGC The Open Geospatial Consortium (OGC) is an international industry consortium of 421 companies, government agencies and universities participating in a consensus process to develop publicly available interface standards. OGC Standards support interoperable solutions that "geo-enable" the Web, wireless and location-based services and mainstream IT. The standards empower technology developers to make complex spatial information and services accessible and useful with all kinds of applications D Portrayal Interoperability Experiment Benjamin Hagedorn 4

5 Open Geospatial Consortium The OGC Vision To achieve the full societal, economic and scientific benefits of integrating electronic location resources into commercial and institutional processes worldwide. The OGC Mission To serve as a global forum for the development, promotion and harmonization of open and freely available geospatial standards Urban Model of Berlin based on OGC CityGML Source: D Portrayal Interoperability Experiment Benjamin Hagedorn 5

6 OGC Domain Working Groups (Aug-8-11) 3D at the OGC An interest or focus in 3D content modeling, sharing, and integration/fusion D Portrayal Interoperability Experiment Benjamin Hagedorn 6

7 3D Information Management DWG The 3DIM Mission A great deal of technical innovation has been accomplished in the areas of CAD, AEC, geospatial and 3D visualization, and urban simulation. A variety of products, information and services abound in each of these environments. This work is of interest to the Geospatial community in that there is a growing need for technologies and information to interoperate flexibly and fluidly between these domains to support a range of vital services and decision support needs. The CAD/GIS WG will focus its efforts on identifying and acting on opportunities to improve interoperability geospatial data and services across these domains D Portrayal Interoperability Experiment Benjamin Hagedorn 7

8 3DIM DWG - Overview 3DIM History Formed in 2005 as the CAD/GIS Working Group Changed name to 3D Information Management Domain Working Group in 2007 to better reflect the diversity of work in the group Initiated CityGML Standards Working Group in 2007 Initiated Oblique Imagery Domain Working Group in D Portrayal Interoperability Experiment started in May 2011 IndoorGML Standardization in preparation Activities Devise/Initiate architecture for open interoperable 3D services Advance Discussion Papers and Best Practices Participate in Testbeds Build on industry partnerships D Portrayal Interoperability Experiment Benjamin Hagedorn 8

9 3DIM DWG - Relationships buildingsmart alliance (MoU) Development of IFC, the major, open standard for Building Information Modeling (BIM) AECOO-1 Testbed: Discussion Paper released BIM-GIS Information Exchange Project Special Interest Group 3D (MoU) German organization responsible for initial CityGML format MoU signed W3C Point of Interest Working Group Mission is to develop a technical spec for the representation of "Points of Interest" information on the Web Web 3D Consortium (MoU) X3D: ISO Graphics Standard for 3D on the Web D Portrayal Interoperability Experiment Benjamin Hagedorn 9

10 Service-based 3D Portrayal D Portrayal Interoperability Experiment Benjamin Hagedorn 10

11 OGC 3D Standards OGC Geography Markup Language (GML) XML-based language for encoding geographic information to be stored and transported over the Internet Defines both the 2D and 3D geometry and properties of objects that comprise geographic information. CityGML Application independent Geospatial Information Model for virtual 3D city models and 3D landscape models Comprises different thematic areas(buildings, vegetation, water, terrain, traffic etc.) KML Encoding Standard XML for geographic visualization on 2D and 3D Earth browsers Features for display: placemarks, images, polygons, 3D models, text, etc D Portrayal Interoperability Experiment Benjamin Hagedorn 11

12 3D Portrayal Services Separation of rendering concerns; examples of services and formats: Google Earth X3D Viewer GML CityGML KML X3D SLD for WMS DP DP WVS WFS W3DS WMS D Portrayal Interoperability Experiment Benjamin Hagedorn 12

13 3D Portrayal Services Missing Link Proprietary 3D portrayal solutions available for Perspective Street Views, Virtual Globes (commercial and open source) However, extensibility and interoperability are limited and projects (e.g. 3D City Models) depend on the business model of existing platforms By opening the 3D portrayal interfaces it becomes possible to exchange servers and clients in a flexible way 3D visualization systems have different requirements than full desktop GIS We need a Map Server for 3D D Portrayal Interoperability Experiment Benjamin Hagedorn 13

14 OGC Candidate 3D Portrayal Standards Web 3D Service and Web View Service D Portrayal Interoperability Experiment Benjamin Hagedorn 14

15 OGC Candidate Standard: Web 3D Service Web-based, Graphics-Based Provision of and Access to Virtual 3D Worlds Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates It can be used for web applications and datasets that are too big for being stored in single files. Streaming allows effective flythroughs. All features supported by web 3D standards (VRML, X3D, COLLADA, KML) can be exploited D Portrayal Interoperability Experiment Benjamin Hagedorn 15

16 OGC Candidate Standard: Web View Service Web-based, Image-Based Provision of and Access to Virtual 3D Worlds Server-side model management and 3D rendering Generation of images of views on the 3D model and transfer to viewer clients Provides visual, thematic, and geometric information Reduces data complexity and rendering complexity for clients WVS is a 3D equivalent of 2D map services D Portrayal Interoperability Experiment Benjamin Hagedorn 16

17 3DPIE - Setting D Portrayal Interoperability Experiment Benjamin Hagedorn 17

18 3D Portrayal Interoperability Experiment Main focus on Web 3D Service and Web View Service 3DPIE tests server-side issues and client-server interaction to test the interoperability along the visualization pipeline: Advance and harmonize developments of Web 3D Service (W3DS) and Web View Service (WVS) candidate standards. Test the applicability of W3DS-based and WVS-based 3D portrayal approaches for different client platforms, including thick clients, web-based clients, and mobile clients. Test the compatibility of 3D portrayal based on W3DS and WVS with standards-based data formats, including, e.g., CityGML. Lower the barriers for the implementation, integration, and usage of 3D portrayal capabilities D Portrayal Interoperability Experiment Benjamin Hagedorn 18

19 3DPIE Context D Portrayal Interoperability Experiment Benjamin Hagedorn 19

20 3DPIE Questions to Answer Questions to Answer 1. Can the draft service candidates of WVS and W3DS adequately support the web-based management, portrayal, and exploration of environmental and urban 3D geodata? 2. Can the W3DS and WVS specifications be further harmonized to provide a more common interface to 3D portrayal capabilities and to support their potential integration and combination? 3. What are best practices for the application of the various 3D portrayal approaches, including graphics-based 3D portrayal (e.g., through W3DS) and image-based 3D portrayal (e.g., through WVS)? 4. What are best practices for the application of the various 3D geodata formats and 3D graphics data formats including CityGML, X3D, KML, COLLADA, and others? 5. How to exploit W3DS and WVS from various client platforms, including thinclients, web-based clients, and mobile clients? D Portrayal Interoperability Experiment Benjamin Hagedorn 20

21 3DPIE Use Case Urban Planning as a major Use Case Examples of using 3D portrayal within the urban planning process: Demand, Conceptualization Constraints Architectual competition Selection of best submission Urban Development Plan, Zoning Subsurface Structures, Geology Public participation Decision Underground Eploration CAD, BIM Engineering Construction D Portrayal Interoperability Experiment Benjamin Hagedorn 21

22 3DPIE Participants Participants (including 3 Web 3D Cons. members) Bitmanagement CACI Fraunhofer IGD GIScience at the University Heidelberg Hasso-Plattner-Institut at the University Potsdam IGG at Technical University Berlin Institute Geographic Nationale (IGN) LSIS at Aix-Marseille University MOVES Institute at the Naval Post Graduate School Virginia Tech Additionally, many OGC Members are observing the 3DPIE D Portrayal Interoperability Experiment Benjamin Hagedorn 22

23 3DPIE Workplan Work Item 1: Data Integration Ex. #1A: Import raw data into W3DS Ex. #1B: Import raw data into WVS Work Item 2: Service Integration Ex. #2A: Integration of W3DS data in WVS client Ex. #2B: Integration of WVS images in W3DS client Ex. #3A: Seamless integration of multiple W3DS in a client Ex. #3B: Overlay images from multiple WVS in a client Work Item 3: Service Delivery Ex. #4A: Web-based portrayal through W3DS Ex. #4B: Web-based portrayal through WVS Ex. #5A: Mobile 3D graphics from W3DS Ex. #5B: Mobile perspective images from WVS D Portrayal Interoperability Experiment Benjamin Hagedorn 23

24 Architecture 3DPIE Architecture Data Integration Service Integration, Service Delivery D Portrayal Interoperability Experiment Benjamin Hagedorn 24

25 Schedule 3DPIE Schedule Kickoff on 26 May 2011 Intended duration: 5 months June July August September October November Work Item 1: Data Integration Work Item 2: Service Integration Demonstration and Report Work Item 3: Service Delivery Planned to have results ready for the OGC TC Meeting in Brussels in November D Portrayal Interoperability Experiment Benjamin Hagedorn 25

26 3DPIE Experiments & Results D Portrayal Interoperability Experiment Benjamin Hagedorn 26

27 Data Integration Data Formats CityGML Keyhole Markup Language Geodata description language OGC Standard since 2008 Collada X3D XML-based open exchange format for data, e.g., 3D geodata D Portrayal Interoperability Experiment Benjamin Hagedorn 27

28 Data Integration X3D Extensible 3D Graphics Format Scenegraph-based 3D graphics data exchange format Successor of VRML Standard Developed by the Web 3D Consortium (MoU with OGC) W3C Standard for 3D content in the Internet Variants X3D/VRML X3D/XML X3DB (binary X3D) Standardized by ISO X3DEarth provides a set of geodata-related Nodes: GeoDoordinate GeoLocation GeoLOD GeoMetadata GeoOrigin GeoPositionInterpolator GeoProximitySensor GeoTouchSensor GeoTransform GeoViewpoint D Portrayal Interoperability Experiment Benjamin Hagedorn 28

29 Data Integration Paris Data (Bati3D data) Extent: ca. 100 sqkm CityGML terrain + LOD2 buildings Fully textured (Texture Atlases) Provided in 446 tiles (500*500 m) D Portrayal Interoperability Experiment Benjamin Hagedorn 29

30 Data Integration Mainz Data Layers Gelaende Gebaeude (LOD1) sewage_duct Mainz data available only through the CityServer3D W3DS Additional planning data Planning data that include additional building that are partially textured buildings LOD2 for Münsterplatz in separate layer "MuensterplatzLOD D Portrayal Interoperability Experiment Benjamin Hagedorn 30

31 Data Integration Berlin/Potsdam Data Sets Three example data sets Gasometer 430 Buildings in LOD2 Textured 24_ Buildings in LOD2 Textured Potsdam 97 Buildings in LOD2 Availale as CityGML D Portrayal Interoperability Experiment Benjamin Hagedorn 31

32 Data Integration OpenStreetMap Data D Portrayal Interoperability Experiment Benjamin Hagedorn 32

33 Data Integration Data and Servers OSM Data Berlin Data (CityGML) OSM-3D W3DS IGG W3DS VRML, X3D, KML KML Mainz Data (CityGML) CityServer3D W3DS KML, Collada, X3D, HTML5 Paris 3D (CityGML) HPI 3D Server WVS Images D Portrayal Interoperability Experiment Benjamin Hagedorn 33

34 Data Integration Viewers / Clients VRML, X3D, KML KML, KMZ/Collada KML, Collada, X3D, HTML5 Images XNavigator Google Earth Instant Reality Player BS Contact Geo HTML5 Browser HPI WVS Client D Portrayal Interoperability Experiment Benjamin Hagedorn 34

35 Data Integration Preprocessing and integration of 3D city models Preprocessing of the large data sets Handling and management of massive 3D city models (large storage required, large file numbers, texture handling) Spatial organization and Generation of graphical elements Rendering of views on large 3D City Models (WVS) D Portrayal Interoperability Experiment Benjamin Hagedorn 35

36 Data Integration IGG W3DS Paris 3D (CityGML) 3DCityDB Importer 3DCityDB IGG W3DS 3DCityDB Exporter KML master file KMZ_collada refers to KMZ files through KML-NetworkLinks KMZ_geometry Tile Cache D Portrayal Interoperability Experiment Benjamin Hagedorn 36

37 Data Integration Paris: Massive Textures Need to split Texture Atlases to import into 3DCityDB Should textures ind raw data be represented and delivered as texture atlases? D Portrayal Interoperability Experiment Benjamin Hagedorn 37

38 Data Integration CityServer3D Fraunhofer updated CityServer3D to implement W3DS Specific operations can be mapped to W3DS operations GetTileDefinition GetScenario Integrated and provided Paris data set Mainz data D Portrayal Interoperability Experiment Benjamin Hagedorn 38

39 Data Integration Data Integration Experiments Importing Paris data set into IGG Web 3D Service Importing Berlin data set into IGG Web 3D Service Importing Mainz data set into CityServer3D Importing Paris data set into CityServer3D Importing Paris data set into HPI WVS Processing OpenStreetMap data and importing into OSM-3D D Portrayal Interoperability Experiment Benjamin Hagedorn 39

40 Service Integration & Delivery Approache for Service Delivery An integrated client consumes one or more service capability documents Capabilities Service Client Capabilities Service File-based integration/combination url Service Viewer Master File url Service url Service D Portrayal Interoperability Experiment Benjamin Hagedorn 40

41 Service Integration & Delivery Example: Portrayal of Paris data from IGG W3DS W3DS export to KML and integration with Google Earth D Portrayal Interoperability Experiment Benjamin Hagedorn 41

42 IGG W3DS Berlin STYLES=geometry STYLES=textured D Portrayal Interoperability Experiment Benjamin Hagedorn 42

43 IGG W3DS Paris small projected region: STYLES=geometry large projected region: STYLES=textured D Portrayal Interoperability Experiment Benjamin Hagedorn 43

44 IGG W3DS D Portrayal Interoperability Experiment Benjamin Hagedorn 44

45 Serving Large City Models Large scale models require Spatial organisation of geodata / graphics data Streaming this data to a consumer Fundamental questions What does a client know about the spatial organisation of a scene? What does a client have to do? Two approaches for dynamic data integration Include knowledge about spatial organization in the data, e.g., as a scene graph Care free package provided to a viewer client Provide a specific data tiling mechanisms through service interface D Portrayal Interoperability Experiment Benjamin Hagedorn 45

46 Serving Large City Models W3DS specific Tiling Mechanism W3DS advertises Tiling in metadata document Master Document with Raster Specification A master document refers geometry tiles directly Problematically for large scene Worldwide coverage would require a very large raster Adaptive, Dynamic Refinement Special scene graph nodes can group child nodes (group nodes and geometry nodes) D Portrayal Interoperability Experiment Benjamin Hagedorn 46

47 Serving Large City Models W3DS Tiling Mechanism W3DS advertises TileSet element in service meta data document Tile are requested via W3DS GetTile operation D Portrayal Interoperability Experiment Benjamin Hagedorn 47

48 Serving Large City Models GetScene-based transparent Tiling in W3DS W3DS KML export via GetScene Handling arbitrary bounding boxes in requests Based on a layers MaxScaleDenominator Client retrieves a valid documents Example MaxScaleDenominator=300 Requested bounding box is 400 * 500 m Results in a quadtree of 4 tiles Requested Area Responsed Tiles D Portrayal Interoperability Experiment Benjamin Hagedorn

49 Serving Large City Models GetTileDefinition point&surface=mainz_stadt D Portrayal Interoperability Experiment Benjamin Hagedorn 49

50 Serving Large City Models GeoLOD nodes in X3D GeoLOD node provides a terrain-specialized form of the regular LOD node rooturl or rootnode are used to define geometry shown at default level child1url... child4url fields define quadtree links to children subscenes geosystem defines geospatial coordinate system D Portrayal Interoperability Experiment Benjamin Hagedorn 50

51 Serving Large City Models <NetworkLink> <Region> <LatLonAltBox> <Lod> <Link>... to W3DS, e.g., to GetScene operation... more NetworkLinks D Portrayal Interoperability Experiment Benjamin Hagedorn 51

52 Serving Large City Models Tile Generation Raster tiles could be created on the fly Raster tiles could be preprocessed and cached Impact on W3DS Service Specification. Make the implementation of W3DS Tiling mechanism optional Use format s tiling mechanisms if available D Portrayal Interoperability Experiment Benjamin Hagedorn 52

53 Height References Dealing with Height References D Portrayal Interoperability Experiment Benjamin Hagedorn 53

54 Height References Dealing with Height References Object locations needs to fit the terrain that is used by a 3D viewer Problematically in a distributed 3D portrayal system with distributed and independently generated 3D data Approaches Deriving the terrain height, e.g., via Google Elevation API Example request: 36, &sensor=false Use language features to position 3D objects relative to a terrain surface KML: Location, e.g., relativetoheight X3D: GeoLocation D Portrayal Interoperability Experiment Benjamin Hagedorn 54

55 Further Discussions Should we talk about data layers in 3D portrayal or do we rather handle FeatureTypes? Features below the terrain are not visible in Google Earth D Portrayal Interoperability Experiment Benjamin Hagedorn 55

56 WVS-based Visualization WVS requires Server-side Rendering Graphics data needs to be highly optimized Fast access to texture data and large memory required for efficient rendering servers WVS-based server-side 3D rendering D Portrayal Interoperability Experiment Benjamin Hagedorn 56

57 WVS-based Visualization Displaying WVS imagery in Google Earth D Portrayal Interoperability Experiment Benjamin Hagedorn 57

58 Web-based 3D Portrayal X3DOM City Viewer im Web Browser D Portrayal Interoperability Experiment Benjamin Hagedorn 58

59 Mobile 3D Portrayal X3DOM City Viewer im Web Browser D Portrayal Interoperability Experiment Benjamin Hagedorn 59

60 Mobile 3D Portrayal BS Contact on IOS D Portrayal Interoperability Experiment Benjamin Hagedorn 60

61 Mobile 3D Portrayal WVS-based mobile client D Portrayal Interoperability Experiment Benjamin Hagedorn 61

62 Conclusions Some of the 3DPIE Results Demonstration and discussion of different approaches for 3D geodata processing, integration, and visualization New implementation of the IGG W3DS CityServer3D was adapted to latest W3DS specification Extension of the Xnavigator client to consume multiple W3DS capability documents Increasing conformance of service implementation Increasing conformance of data format implementations D Portrayal Interoperability Experiment Benjamin Hagedorn 62

63 Conclusions Next Steps / Future Work Tiled WVS? Test and further develop feature data access How should the GetFeatureData operation work? Navigation and Interaction with portrayed data Extension of 3DCityDB to export X3D W3DS / WVS Standardization?! D Portrayal Interoperability Experiment Benjamin Hagedorn 63

64 Contact Benjamin Hagedorn Prof. Jürgen Döllner Computer Graphics Systems Hasso-Plattner-Institut for Software Systems Engineering at University of Potsdam Arne Schilling GIScience, University of Heidelberg Volker Coors University of Applied Sciences, Stuttgart D Portrayal Interoperability Experiment Benjamin Hagedorn 64