T3.1 CityGML core standard extension

424 views
335 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
424
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

T3.1 CityGML core standard extension

  1. 1. Presented by: Carsten Rönsdorf
  2. 2. CityGML overview plus core standard extension
  3. 3. http://www.financialpost.com/executive/smart-shift/story.html?id=2146219Smart cities theme
  4. 4. What is CityGML?CityGML is an open data model and XML-based format forthe storage and exchange of virtual 3D city models. It is anapplication schema for the Geography Markup Languageversion 3.1.1 (GML3), the extendible internationalstandard for spatial data exchange issued by the OpenGeospatial Consortium (OGC) and the ISO TC211.
  5. 5. CityGML overview... Covered by Martin Ford’s presentation (through Mark Stileman)
  6. 6. Copyright © 2012 Open Geospatial ConsortiumWeb 3D Service and Web View Service
  7. 7. Copyright © 2012 Open Geospatial ConsortiumIGG‘s W3DS serves Paris data (from CityGML) to Google Earth
  8. 8. Fraunhofer’s X3DOM City Viewer in the Web browser and on mobile device
  9. 9. HPI‘s WVS serves Paris city model to a web and mobile client
  10. 10. Features of CityGML Geospatial information model (ontology) forurban landscapes based on the ISO 191xxfamily GML3 representation of 3D geometries, basedon the ISO 19107 model Representation of object surface characteristics(e.g. textures, materials) An out of the box data model that should cover80-90% of your requirements and can easily beextended
  11. 11. Modularisation...CityGML CoreOGC GML 3.1.1AppearanceGenericsApplication Domain Extensions (ADE)BuildingCityFurnitureCityObjectGroupLandUseReliefTransportationVegetationWaterBodyTunnelBridge…
  12. 12. ModularisationVery powerful concept to add an a lot:- attributes- features- relationships- themesAt what point do we need to extend the corestandard?
  13. 13. How long does standardisation take?• Proposal– 4 weeks in ETSI if in scope of existing work programme, 3 months ormore if not• Drafting– Months, years• Approval– Depends on standard type but from 8 weeks to 18 months• Publication– Depends on publisher but about 4 weeks is normal• Maintenance– Depends on publisher but for essential corrections corregenda maybe published at any time, major review generally every 3-5 years______ _ __ __ _________ __ _Standardisation timeframes (from Scott Cadzow)
  14. 14. OGC timeframes Standard process 9-18 months Fast track process 3 months, only applicable for wellresearched and established, not controversial items Need to submit RfC Prioritisation and scheduling will be evaluated by OGC Alignment with other requirement and potential publicationschedule 30 day public comment process for draft final version(similar to Committee Draft at ISO) 60 days IPR review and OGC voting process
  15. 15. The big sticky IPR point For any outcomes of iSCOPE (or any other project/input) tobe included into the published CityGML standard, theconsortium needs to transfer IPR to OGC. OGC will make make CityGML available on a RAND androyalty free basis We might want to think about an MoU between iSCOPE andOGC to formalise the relationship and allow iSCOPEmembers to fully participate in OGC processes
  16. 16. CityGML timeframes Version 2.0 was published in April 2012 Potential work on version 3.0 has been discussed in March First RfCs have been submitted Work on CityGML 3.0 will start at OGC meeting in Exeternext week Move to GML 3.2.1, authoritative UML model and GMLencoding rules Rethink some of the core concepts Draft spec expected by end of 2013 Published CityGML 3.0 spec by mid/end of 2014
  17. 17. Additional activities in context of extension• 3DIM registry sub-group: Objective:To provide useful specification resources to the usercommunity, complementary to the CityGML specification.• Set of user guides focussing on explicit target communities,probably aligned to the 3 iSCOPE use cases (lead by MartinFord, CEN)
  18. 18. OGC ADE lifecycle/graduation process1. Link to external resource2. Schema validated by 3DIM registry-sub group3. Content reviewed by 3DIM and comments published4. OGC Discussion paper agreed by TC5. OGC BP paper agreed by TC6. OGC standard agreed by TC (CityGML or separate OGCstandard)7. Deprecated (Don’t create any new data using this ADEany more!)Add user experience as additional attribute
  19. 19. iSCOPE requirements• based on D1.2 Data, Metadata and ModellingRequirements• use cases Energy and Noise can be dealt with 100% byADEs• Transport is more challenging and requires a deeper lookinto core principles and concept of CityGML• Number of complementary extension activities that sitoutside the actual specification
  20. 20. Extensions of core CityGML Master UML model based on GML 3.2.1 CityGML as an Inspire BU data encoding Registries (ADE, feature concept, feature catalogue)Particular concepts Storeys, floors and stairs Indoor LoDs FloorplansFor the Mobility use case examine and discuss multi-graphconcepts such as in Indoor ML in the iSCOPE consortium andin OGC

×