Virtual Cities of the Future and Past. Paul Cote Geographic Information Systems Specialist Harvard University Graduate School of Design

Transcription

1 Virtual Cities of the Future and Past Paul Cote Geographic Information Systems Specialist

2 Harvard University Graduate School of Design

3 500 Design Students 250 Architecture 50 Urban Planning 100 Urban Design 100 Landscape

4 A Knowledge Engine GSD Studio Culture: 75% of Student effort focused on one studio problem 100 Studios per year at the GSD Focus on representing, understanding, modifying and evaluating places: Appearance & performance Many Many Models are Made!!! An intense replica of the greater world of design

5 Studio Information Lifecycle Start Semester Finish Collect Information: Site Photos GIS Data CAD Data Documents Process Understanding End of Term Synthesis / Study: Maps Digital 3D Models Physical 3D Models Simulation Models Presentation Materials: Maps 3D Models Animations Document ation Sources / Bibliography Small Fraction Suited for Re-Use Bulk of Knowledge is Lost Many Mysterious Presentation Documents

6 Discover, Obtain, Transform, Organize Ideas & Information Information & Ideas About Places & Processes (In-House or Internet) Paul Cote, 2008 Compile Data / Create Schema: Information Infrastructure Information Lifecycle in Site Studies Author / Modify Regulation Groundplan Landform Circulation Buildings Vegetation Visualize / Study Programmatic Capacity Streetscape, Shadows Views Coherence with Context Finance, Phasing Exchange: between specialized tools Exchange: Individuals & Enterprises to Shared Infrastructure Evaluate: Alternatives: Performance & Impacts Communicate: Narrative, Graphics, Video Collaborate / Share: Resources, Understanding, Procedures

7 It Takes a Village of Specialized Tools Compile Data / Create Schema: Author / Modify Synthesize / Study Evaluate / Share ArcGIS Public GIS Agency/Firm Knowledge Base AutoCAD Rhino RevIt Tree Pro Maya, 3D Studio, V-Ray Master CAM Revit Adobe Ecotect Agency/Firm Knowledge Base Many Specialized Tools Paul Cote November 13, 2008 One-Way, Lossy Exchanges 7

8 GSD Handbook for Site Modeling in Context Paul Cote NOMA Boston October 7

9 Virtual Cities as a Mirror with Memory Paul Cote NOMA Boston October 7

10 Collaboration of Administrative Domains Public Works Photogrammetry Tax Assessor Planning & Design Review State / Federal Permitting and Inspection Emergency Planning and Response The most authoritative information about an urban situation are collected and maintained by a host of administrative departments that employ a variety of data models and tools 10 Paul Cote,

11 Collaboration of Administrative Domains Understanding 11

12 Collaboration of Territorial Domains 1/29/

13 Collaboration of Territorial Domains Understanding Town A Town / Campus B 13

14 Memory and Intelligence Past Situation Current Situation Possible Scenarios Planned Scenario If these alternate views of the city are expressed in common terms, much might be learned about urban mechanics and the probable consequences of decisions. 14 Paul Cote,

15 Necessity for Shared Semantic Models Paul Cote NOMA Boston October 7

16 One-Way, Lossy Exchanges Inputs Outputs Domain / Tool A (e.g. GIS, RDBMS) Outputs!&$@# Inputs Domain / Tool B (e.g. CAD / BIM) Semantic Trash Bin 16

17 Coherent Spatial / Semantic Models Real World Concepts: Critical Entities Conceptual Information Model Kolbe & Groeger CityGML Relationships The building meets the terrain along this line. e.g. Observations, Prescriptions, Rules Kolbe & Groeger CityGML e.g. UML (Unified Modeling Language) 17 Paul Cote,

18 Coherent Conceptual & Data Models Conceptual Information Model Technical Implementation Binary Data Storage Programs & Business Logic Outputs Inputs Business Processes Kolbe & Groeger CityGML e.g. Software tools: Proprietary or Open 18 Paul Cote,

19 Shared Conceptual Models & Exchanges Round Trip with Coherent Semantics Outputs Inputs Domain Tool A Inputs Outputs Domain Tool B Kolebe and Groeger: CityGML See: Stadler & Kolbe: Spatio-Semantic Coherence in the Integration of 3D City Models 19

20 Community Based Standards Development Communities Industry Consortium International Standards Organization Engineers Tool Makers Understanding Consensus Foundation Standards Information Structure Service Protocols Content Creators Service Providers Application Standards Application Standards Users Participation Assured Stable Environment Lots of Interoperable Content! 20

21 Community Based Standards Development Standards Organizations Encodings Service Protocols SQL structured query language HTTP hypertext transfer protocol WMS web map service GML WFS web feature service WCS web coverage service Paul Cote,

22 Some KML, KMZ Collada Examples Paul Cote NOMA Boston October 7

23 The Virtual City Collective: A Forum on the Web Paul Cote NOMA Boston October 7

24 The Google Earth Train Set Paul Cote NOMA Boston October 7

25 The Greenline Station Workshop Paul Cote NOMA Boston October 7

26 Executive Office of Transportation: College Avenue Station Plan Paul Cote NOMA Boston October 7

27 Executive Office of Transportation College Avenue Station Plan Paul Cote NOMA Boston October 7

28 Executive Office of Transportation College Avenue Station Elevation Paul Cote NOMA Boston October 7

29 GSD6447: Virtual Cities as Public Infrastructure Paul Cote,

30 Seaport Sandbox: A Cybernetic View of Studio Paul Cote,

31 Toward Deeper Semantic Coherence Paul Cote,

32 CityGML: Shared, Open, Coherent Real World Concepts: Conceptual Information Model Exchange Encoding Images from CityGML Spec Kolbe & Groeger CityGML UML (Unified Modeling Language) GML3 32 Paul Cote,

33 CityGML: Objects May Honor Specific Levels of Detail Image from OGC CityGML Discussion paper, Kolbe, Groeger, Czerwinski Paul Cote, 33

34 First Component Sub-Models of City GML Image from OGC CityGML Discussion paper, Kolbe, Groeger, Czerwinski Paul Cote, NCFMT

35 The GSD Metropolitan Model Repository: A Simple Relational Schema For Temporally Deep City Models Paul Cote,

36 Scalable Infrastructure for 3d Cities Paul Cote,

37 Granularity and Identifiers Goals: Provide a way of uniquely identifying parts of buildings at multiple levels of detail across diverse territorial domains Provide for retrieval of past, present and future views of the city through simple SQL queries on a simple relational database schema Support check-out and off-line modification of parts of the model without possibility of ID conflicts on check-in. 1/29/

38 Existing GIS Layers: Parcels Each town in the metro area has a parcels layer that forms a decent source of information about buildings. We alter the parcel ID by appending a 3 character territory code and an _P so that the parcel IDs are assured to be unique within a multi_town schema. Parcel Attributes Shape Territory Parcel_ID Polygon Brookline Brk_P * Owner Mobil Oil Co Year Built 1971 Address 333 Boylston St Stories 1 Paul Cote,

39 Existing Layers: Building Footprints Each town has a building footprints layer established from a photogrammetric survey Footprint Attributes Shape Polygon Unique ID * Paul Cote,

40 New Table: Abstract Buildings The Parcels table can form a table of information about buildings. Unique Building IDs are created from Parcel IDs. This table has no geometry associated with it. Any building associated with a parcel are designated Building 0. This lumping is inaccurate, but sufficient for an initial buildings table. Abstract Buildings Cam_P Territory Building Owner Cambridge Cam_P364234_B0 Harvard B0 Built Date 1870 Demo Date Address Null 49 Quincy St Stories 5 1/29/

41 New Layer: Building Massing Parts Where individual building parts vary in terms of their attributes, they may be distinguished with unique IDs and individual build and demo dates, etc. The Building Massing Part IDs are formed by appending a Massing Part ID to the Building ID. Building Massing Parts Part_ID Cam_P364234_B0_M1 B0_M1 Cam_P B0_M0 Owner Built Date Demo Date Address Null 1998 Null Null Stories 2 1/29/

42 3d Building Massing Parts Table The Massing Parts Layer forms a complete model of every building in the metro area at a low level of detail (CityGML LOD2). Building parts may have more specific attributes from their parent Abstract Buildings. Building Massing Parts B0_M0 Part_ID Cam_P364234_B0_M1 B0_M1 Owner Built Date Demo Date Address Built Null 1998 Null Null Yes *CityGML LOD 1 Buildings Stories 2 1/29/

43 3d Building Skin Models Using a 3D authoring tool, models of building exterior skins can be encapsulated as sketchup or collada models and placed into relational tables as georeferenced objects. Like Massing Parts, Skin Parts have unique IDs linking them to abstract buildings and may have more specific attributes. Building Skin Parts Cam_P B0_S0 *CityGML Generic City Object or External Link Shape Model Part_ID Owner Build Date Demo Date Built 1/29/ Multipatch / COLADa Sketchup or Collada Blob Cam_P364234_B0_S0 Null 1870 Null Yes 43

44 3d Building Skin Parts Skin parts and massing parts for a given building may have independent dates. The Model field holds a Binary Large Object that can be downloaded to a 3d authoring tool for editing. B0_S1 Building Skin Parts Shape Multipatch / COLLADA Model Part_ID Owner Sketchup or Collada Blob Cam_P364234_B0_S1 Null Cam_P Buid Date Demo Date Built 2001 Null Yes 1/29/

45 Relational Queries Create Views Based on Dates or Scenarios Abstract Buildings 1 Territory Building Cambridge Cam_P364234_B0 1 Owner Harvard Year Built Year Building Skin Parts Demo Shape Multipatch Address Model Sketchup or Collada Blob Stories Part_ID Owner Cam_P364234_B0_S1 Null Built 2001 Demo Null Null Building Massing Parts 49 Quincy Part_ID St Cam_P364234_B0_M1 5 Owner Null Built 1998 Demo Null Address Null n Built Yes Stories 2 1/29/

46 Current Built View 1/29/

47 1998 Historic View 1/29/

48 Handling Fictitious Future Urban Design Schemes 1/29/

49 Built and Unbuilt Schemes The Built attribute is set to Yes for buildings that were actually built. Unbuilt buildings can be represented in the schema to allow experimentation with proposed scenarios. Building Skin Parts Shape Multipatch Cam_P364223_B0_S0 Model Part_ID Owner Built Date Demo Date Built Sketchup or Collada Blob Cam_P364223_B0_S0 Null 2001 Null Yes 1/29/

50 Built and Unbuilt Schemes The Built attribute is set to Yes for buildings that were actually built. Unbuilt buildings can be represented in the schema to allow experimentation with proposed scenarios. Building Skin Parts Shape Multipatch Cam_P364223_B0_S1 Model Part_ID Owner Built Date Demo Date Built Sketchup or Collada Blob Cam_P364223_B0_S1 Null 2001 Null No 1/29/

51 Design Scenario Tables In order to create custom scenarios you must be able to turn on unbuilt buildings and to turn off other buildings that would otherwise render. This is accomplished by creating Schemes and entering part-specific rendering instructions in the Scheme_Parts table. Because the Part IDs are distinct for Massing and Skin part models, the Scheme Parts table can refer to either type of part. Scheme Parts Schemes 1 Part_ID Render Scheme- ID Cam_P364223_B0_S1 Yes 1 Cam_P364223_B0_S0 No 1 n 0 Sheme- ID Name 1 Flipped Gund Hall 2 Tank Building Skin Parts Building Massing Parts Part_ID Name Built Part_ID Name n Cam_P364223_B0_S1 Flipped Unbuilt Cam_P364223_B0_S0 Gund Hall built n Cam_P364223_B0_M0 Brk_P _B0_M1 Gund Hall 1/29/

52 Building Model Management Schema 1 Abstract Buildings Building ID Attributes 1 Schemes Scheme ID Name 1 n 1 Scheme Parts Scheme_ID Part ID Render 1 Skin Parts n Building ID Part ID n Attributes n Massing Parts Building ID Part ID n Attributes 1/29/

53 Unbuilt Scheme: Turn Gund Hall Around 1/29/

54 View From Proposed Design Scheme 1/29/

55 References City Geography Markup Language Kolbe and Groger, 2008 SPATIO-SEMANTIC COHERENCE IN THE INTEGRATION OF 3D CITY MODELS Stadler and Kolbe Collada: 3D Asset Exchange Schema Khronos Group Town of Brookline Model Management System Cote, 2007 Public Infrastructure for Virtual Cities Cote, 2006 Integration of CAD, GIS, and Building Information Models in Open Web Services Cote, 2007 Building Interior Spaces Data Model for GIS Penobscott Bay Media, BISDM.org 1/29/

56 Lets Get it Together! Understand Open Exchange Specifications Target our conceptual and data models for open exchange Participate in standards development Demand open exchange capabilities in our tools 56 Understanding 1/29/2011

57 Credits and References Find these links at City Geography Markup Language Kolbe and Groger, 2008 SPATIO-SEMANTIC COHERENCE IN THE INTEGRATION OF 3D CITY MODELS Stadler and Kolbe Collada: 3D Asset Exchange Schema Khronos Group Town of Brookline Model Management System Cote, 2007 Public Infrastructure for Virtual Cities Cote, 2006 Integration of CAD, GIS, and Building Information Models in Open Web Services Cote, 2007 Building Interior Spaces Data Model for GIS Penobscott Bay Media, BISDM.org 1/29/

58 Efforts to Develop Web Standards for Encoding and Exchanging City Mo Building Information Modeling Community: International Alliance for Interoperability -- BuildingSmart (Consortium of Owners, Engineers & Architects) IFC (Semantic and Exchange Standard for Building Information Models) National BIM Standard (social and institutional construction of BIM) Open Floor Plan Toward a simple standard for exchanging georeferenced floorplans OASIS Geospatial Information Infrastructure Community: Open Geospatial Consortium (Architecture for Interoperable Web Services spanning diverse semantic schema) CityGML: Semantic and Exchange Standard for City & Landscape Models Web Services Architecture for CAD, GIS and BIM (edited by Yours Truly) Game Development Community Khronos Group (Gaming Community Consortium) COLLADA (exchange standard for high-quality digital objects, includes materiality, lighting, physical behavior) Paul Cote NOMA Boston October 7