kentbis Kavramsal Model Tasarımı

Transkript

1 COĞRAFİ BİLGİ SİSTEMLERİ GENEL MÜDÜRLÜĞÜ TÜRKİYE KENT BİLGİ SİSTEMİ STANDARTLARININ BELİRLENMESİ PROJESİ kentbis Kavramsal Model Tasarımı Doç. Dr. Arif Çağdaş AYDINOĞLU İTÜ kentbis Kapsam- Uygulama Alanı Kavramsal Modeli Standart Hiyerarşi TUCBS veri modeli; - temel / ortak veri modeli olarak kabul edilebilir, - farklı kullanıcıların ve sektörlerin paylaşım ihlyacı duyduğu verileri içerir.

2 kentbis Kapsam- Uygulama Alanı Kavramsal Modeli Standart Hiyerarşi HI BI TUCBS AD Dere Göl Bina Bağımsız Bölüm Dışkapı Adres Ruhsat kentbis MAKS PROJE KAPSAMI TEMEL VERİ AD Adres Adres Yer İsimleri Numarataj BI Bina Bina Kamu/Tarım/Endüstri Tes. Ticari Hizmet Tes. TK Tapu/Kadastro Tapu/Kadastro IB İdari Birim İdari Birimler Sorumluluk Bölgeleri UL Ulaşım Karayolu Havayolu Demiryolu Denizyolu Ulaşım Tesisleri HI Hidrografya Göl/Göletler Nehir/Dere Oşinografik Detaylar Deniz / Bölgeleri AR Arazi Örtüsü Arazi Örtüsü/Kullanım OR Ortofoto Ortofoto Görüntü Uydu Görüntüsü TO Topografya Fizyografya/Hipsografya Sayısal Yükseklik Verileri BaLmetri Kıyı Kenar Çizgisi JD Jeodezi Coğrafi Referans Sisteml. Coğrafi Grid Sistemleri Temel/SıklaşYrma Ağları TEMATİK VERİ YA Yasak/Koruma Tarihi- Doğal Özel Çevre Koruma Bölg. Askeri Yasak Bölg. Kentsel Koruma Bölg. Havza Bölg. SO Sosyal/Kültür Kentsel ve Kırsal Yerleşim Nüfus Dağılımı /Demografi Turizm Varlıkları Kültür Varlıkları İnsan Sağlığı ve Güvenliği AL Altyapı İçmesuyu Kanalizasyon Haberleşme Doğalgaz Petrol Boru Elektrik Jeo Termal Y PL Plan Bölgeleri A P Bölge Planı ilkeler ve esaslar, A Çevre Düzeni Planı Y İl Çevre Düzeni referans Planı modeli, İmar Planı ölçek- çözünürlük ve genelleşlrme yaklaşımları, genel detay modeli, detay kataloğu, HA Hava/İklim Meteorolojik uygulama şeması Hava ve kuralları, atmosferik durum BI Biyoçeşitlilik geometri, İklim Bölgeleri Bitki Örtüsü topoloji, Biyocografik Bölgeler DO Doğal Kaynaklar D Habitat Bölgeleri coğrafi nesnenin Ekosistem tanımlanması, Kaynakları O Türlerin Dağılımı (Bitki/ Su Kaynakları Ğ Hayvan) zamansal yönelmi, Tarımsal/ A L metaveri, ToprakKaynaklarıOrman JF Jeofizik/Çevre Kaynakları Jeoloji veri kalitesi ve Balıkçılık veri Kaynakları paylaşımı Jeo- morfoloji Jeolojik Kaynaklar Toprak Yenil. Enerji Kaynakları 2

3 OGC 2-09 CityGML is used together with GeoTIFF as the only exchange formats between web services and noise calculaogc 2-09 tion software (Fig. 96 -Fig. 98). For the special requirements of the noise directive, a CityGML noise application schema has been developed by the Institute of Geodesy and Geoinformation University of Bonn and the Special Interest Group SIG 3D of GDI NRW. It is based on the ADE mechanism (see chapter 6.2 and 0.3). This chapter 0.; XML schema definition see annex A.6). A group may be assigned oneand or more names and may(e.g. be buildings) by thematic mechanism allows the supplementation of existing classes objects in CityGML further classified by specific attributes, example, " escape route roomattributes no. 43 in is house no. 22 in CityGML a fire attributes. The for quantity as well as the typefroofmthese selectable. The schema can also be scenario" as a name andcomplemented " escape route "byasnew type.classes. Each member of the group can optionally assigned role (e.g. segmentation of Hence, the noise application schema be contains newa objects name, which specifies the role this particular member plays in the group. This role name may, for example, roads according to noise requirements - NoiseRoadSegment, Fig. 99) as well as noise attributes attached to describe the sequence number of objects this object an escapeofroute, or in Fig. the case a building complex, the are derived from regulaexisting (e.g.inreflection buildings, 00).ofThese additional noisedenote attributes main building. tions issued by the Federal Government of Germany realising the obligations of the Environmental Noise Directive of theaseuropean Union (cf. BImSchV 2006, VBUS 2006, VBUSch 2006). A group may contain other groups members, allowing nested grouping of arbitrary depth. The grouping concept is delivered by the thematic extension module CityObjectGroup of demonstrate CityGML (cf.achapter 0.). The interoperability techniques of this project remarkable innovation, as for the first time 7/9/2 statewide 3D geodata are provided via common standards and web services (cf. Czerwinski et al. 2006b). Therethe Spatial Data Infrastructure for noise calculation in North Rhine-Westphalia provides an application example for the INSPIRE directive of the European Union 2007/2/EC (Infrastructure for Spatial Information in,qirupdwlrq DERXW D VXUIDFH V DSSHDUDQFH L H REVHUYDEOH SURSHUWLHV RI WKH VXUIDFH LV FRQVLGHUHG DQ LQWHJUDO SDUW Europe) (cf. Czerwinski et al. 2007). of virtual 3D city models in addition to semantics and geometry. Appearance relates to any surface-based theme, e.g. infrared radiation or noise pollution, not just visual properties. Consequently, data provided by appearances can be used as input for both presentation of and analysis in virtual 3D city models. 6.9! Appearances fore, kentbis_nesne "#! $%!&'()!*%,--'./! CityGML supports feature appearances for an arbitrary number of themes per city model. Each LOD of a feature can have an individual appearance. Appearances can represent ± among others ± textures and georeferenced #$%&'&()!*!*)!,$))*-./!$!0/&/!23!0*(!4$'/.)!&!&!/&)$5&-./!0$)!'6/!$!7/!&,*'! WH[WXUHV &LW\*0/ V DSSHDUDQFH PRGHO LV SDFNDJHG ZLWKLQ LWV RZQ H[WHQVLRQ PRGXOH Appearance (cf. chapter 9). '/8/.$,4/5! $9! 0$4,6/! 7&'%&/:! &5'!,$))*-*.*(! $9! '&&! &0;6*)**$5! 9$4! )//$! 6.0 &,,.*0&*$5! Prototypic objects &/*&.! *4&</)=! >7*)! '/8/.$,4/5! 7&)! *50/&)/'! )/8/&.! $9! 7//! / scene graph concepts '*4/5)*$5&.! ),&*&.! *59$4&*$5! *5! &! 8&*/(! $9! 9*/.')! *50.6'*5<!6-&5!,.&55*5<:! In CityGML, objects of equal shape like trees and other vegetation objects, traffic lights and traffic signs can be /./0$4465*0&*$5):!/0$.$<(:!$6*)4!&5'!/5/&*54/5!?@A=!! represented as prototypes which are instantiated multiple times at different locations (Fig. 7). The geometry of prototypes is defined in local coordinate systems. Every instance is represented by a reference to the prototype, a B!0$44$5!65'/)&5'*5<!*)!7&!/8/(!23!0*(!4$'/.!0$5)*))!$9!&!'*<*&.!/./8&*$5! base point in the world coordinate reference system and a transformation matrix that facilitates scaling, rotation, 4$'/.!%*7!<$65'!7/*<7!&5'!23!-6*.'*5<!'&&!%*7!-6*.'*5<!7/*<7)=!C)6&..(!&!23! and translation of the prototype. The principle is adopted from the concept of scene graphs used in computer 0*(!4$'/.!/,/)/5)!&5!/D*)*5<!0*(!-6!*5!)$4/!&,,.*0&*$5):!/),/0*&..(!*5!<&4*5<! graphics standards like VRML and X3D. As the GML3 geometry model does not provide support for scene graph concepts, it is implemented as an extension to the GML3 geometry model (for further description cf. &5'!/5/&*54/5:!*!4&(!7&8/!5$!0$65/,&!*5!7/!/&.!%$.'!?@A=!E$!*5)&50/:!*5! chapter 8.2). 7/!8*6&.!23!F*(!G$'/.!$9!H/.*5!IE*<=J=KL!)/8/&.!'&&!)$60/)!7&)!-//5!6)/'!)607! BitkiOrtusu KentMobilyasi SuYapilari AraziKullanim &)! 0&'&)&.! '&&:! '*<*&.! /&*5! 4$'/.:! &/*&.! *4&</:! -6*.'*5<! 4$'/.)! &5'! '*99//5! Fig. 97: 3D geodata in CityGML for the calculation of the noise map in Fig. 94: Derived contour lines for the generation of CityGML breaklines, 3D block model in CityGML, 3D road and railway data in CityGML, state road data for higher-level roads in CityGML (source: 8&*&5)!$9!0*(!$-M/0!0$./0*$5)!?NA=!! Surveying and Mapping Agency NRW, State Road Enterprise NRW, Stapelfeldt GmbH, Institute of Geodesy and Geoinformation Uni Bonn).! Fig. 7: Examples of prototypic shapes (source: Rheinmetall Defence Electronics) !"#6!7 B!8*/%!9$4!23!F*(!G$'/.!$9!H/.*5!?NA=! Fig. 98: Extract from Fig. 97 shows the integration of 3D block models in the DTM by appropriate A. Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 CityGML modelling (lowest point of 6.! GmbH, Institute of Geodesy and Geoinformation Uni Bonn).!! Generic city objects andpolygon attributes ALK building is taken as measure to generate the building bottom side) (source: Surveying and Mapping Agency NRW, Stapelfeldt " CityGML is being designed as a universal topographic information model that defines object types and attributes which are useful for a broad range of applications. In practical applications the objects within specific 3D city models will most likely contain attributes which are not explicitly modelled in CityGML. Moreover, there might be 3D objects which are not covered by the thematic classes of CityGML. CityGML provides two different 307 Copyright 202 Open Geospatial Consortium. Ölçek- Çözünürlük 5ve GenelleşLrme Yaklaşımı Copyright 202 Open Geospatial Consortium. kentbis Kapsam- Uygulama Alanı Veri Veri Veri Düzeyi Temel Ölçek Kullanım Çözünürlüğü (vektör) Düzeyi (raster) Ülke < 00,00 m 0 > :.000b 0 Bölge (Küçük Ölçek) < 2,50 m 2 > : 25b 2 (Orta Ölçek) İlçe < 0,50 m 3 Harita 500b Harita 250b Harita 00b Harita 25b Harita 0b Harita 5b Harita b Harita > : 250b < 25,00 m İl 000b > : 5b 3 (Büyük Ölçek) Konumsal 4 > : b Hiyerarşi Mahalle < 0,05 m b= 000 Yaklaşımı A. Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202, 3

4 kentbis Kapsam- Uygulama Alanı Ölçek- Çözünürlük ve GenelleşLrme Yaklaşımı kentbis Teknik Kavramsal Model Coğrafi veri yönelminde yeni yaklaşım Teknolojik gereksinimlerden ve yazılımlardan bağımsız, coğrafi verilerin birlikte çalışabilirliğini sağlayacak yaklaşımları ve prensipleri içermektedir. ISO/TC 2 standartlarına, INSPIRE Veri Standartları beklenllerine, TUCBS eylemlerine uyumludur. Nesne- ilişkisel veri modeli- coğrafi veri ve ilişkili öznitelikler tek bir coğrafi veritabanında depolanabilir. SemanLk Model- kavramsal modeldeki ortak tanımlamalara göre ürellmişlr. Model Bazlı Yaklaşım ile UML kullanılarak gelişlrilmişlr. 4

5 kentbis Teknik Kavramsal Model class Schema BI TUCBS kentbis Uygulama Şemaları OF... «import» TUCBS Kavramsal Model TUCBS Kavramsal Model ISO/TC2 ve diğer u.arası öngörülere göre Kavramsal Modeli gelişlrilmekte, bu kapsamda da coğrafi veri temalarına ait birlikte çalışabilir veri standartları gelişlrikmektedir. «import» Foundation Şema ISO 9000 Diger Semalar kentbis Teknik Kavramsal Model Referans ISO Standartları ISO 90 Referans Model ISO 903 Kavramsal Şema Dili ISO 907 Uzaysal Şema ISO 908 Zamansal Şema ISO 909 Uygulama Şema Kuralları ISO 90 Detay Kataloglama Metadolijisi ISO 9 Koordinatlarla Uzaysal Referanslama ISO 92 Coğrafi Tanımlayıcılarla Konumsal Referanslama ISO 95 Metaveri ISO 923 Kapsama Alanı Geometrisi ve İşlevi ISO 926 Detay Kavram Sözlüğü ve Kayıtlar ISO 93 Veri Ürünü Özellikleri ISO 935 Coğrafi Bilgi Elemanları Kayıt Prosedürleri ISO 936 Coğrafi İşaretleme Dili ISo 939 Metaveri XML Şema Uygulaması 5

6 kentbis Teknik Kavramsal Model Genel Detay Modeli (ISO 909) GF_InheritanceRelation GF_AggregationType <<metaclass>> GF_FeatureType <<metaclass>> GF_SpatialAssociationType GF_AssociationType 0..* Generalization Gerçek " dünya varlıklarının..* supertype -subtype sınıflandırılması için kavramları belirler../02'" memberof Sp ecializatio n 0..* 0..* linkbetween 0..*!"!""!" GF_TemporalAssociationType 0..* constrainedby DependsOn,-./$'0.2345'/567895'$::5;;'<' ' <<Abstract>> 0..* carrierofcharacteristics 0..* GF_Constraint <<Abstract>> GF_PropertyType 0..* constrainedby "..* observesvaluesof 0..* <<metaclass>> <<metaclass>> <<metaclass>> characterizedby GF_AssociationRole GF_Operation 0..* GF_AttributeType 0..* (3" triggeredbyvaluesof 0..* characterize 0.. affectsvaluesof At tributeofattribute 2'"45678"9 :*;<=5057":.>.2.?@."* " kentbis Teknik Kavramsal Model " A."2.>.25?B"05678BC"DE)"B.F"G.8H.02I."50"=28J./BI8?"D;K-"%"4#L-"MC2'" Geometri (OGC Simple Features, ISO 907, 923) (3" " " " "!" " #$%&#'!#$"%"$&'(" ")*,()*"%"(&'&-((" " 6

7 kentbis Teknik Kavramsal Model Nesne Tanımlayıcı Her bir coğrafi nesne ulusal olarak tek/benzersiz zorunlu tucbsno özniteliğine sahiplr. ID Verinin TemaLk Yapısına göre Tanımlama İdari Birim Kodu (IDBK) IB Aksular Köyü TR Numarataj Kodu (NUKO) AD Aksular Köyü A Sok. (T.N.:32) No:4 TR A032/04 Mülkiyet Kodu (MUKO) MB Aksular Köyü 50 Ada 9 parsel TR M50/009 Veri Sağlayıcısına Göre Tanımlama {TR.BBBBBB.CC.DDDDDDDD} Veri sağlayıcısını ifade eden tanımlama Verinin tematik grubu Veri sağlayıcısının kendi veri tabanındaki tanımlama UUID / GUID: Evrensel Tek/benzersiz Tanımlayıcı (ISO 56) {6a54f dc c9a66} kentbis Teknik Kavramsal Model Nesne Tanımlayıcı!"#$%&' %$%(&) *"&,-.' ) /!"#$%" &!'( ) &!'( * &!'(,-" -"./0 /"/234/5/"2/ 67458%9%""/ ': ;('<' '=-6 8%9%""30-2%>/"/> Trabzon İli Akçaabat ilçesi Akçakale Beldesi X Mahallesi 7

8 kentbis Teknik Kavramsal Model Zamansal Veri YöneLmi Nesneye zamansal değişimi zamansal özniteliklerle tanımlanmışyr. tucbsno / kbsno versiyonno versiyonbaslangictarihi versiyonbitistarihi Coğrafi Nesnenin yaşam süreç kuralları kentbis Metaveri Uygulama Esasları TUCBS Metaveri Coğrafi veri hakkındaki tanımlayıcı bilgilerdir ve coğrafi veriye erişimde amacına uygunluğu hakkında bilgi verir. () Coğrafi Veri Servisleri (2) Coğrafi Veri Setleri (3) Detay (Nesne Tanımlayıcı, Versiyonu) Taslak TUCBS- Metaveri kapsamında 9 bölümde 25 i zorunlu 6 metaveri elemanı tanımlanmaktadır. () Veri Kimliği (2) Sınıflandırma (3) Anahtar Kelime (4) Coğrafi Konum (5) Veri Standardı ve Referans Bilgileri (6) Zamansal Referans (7) Coğrafi Veri Kalitesi ve Geçerlilik (8) Veri Kullanım Hakkı / DağıYmı (9) Metaveri Referans Bilgileri 8

9 kentbis Metaveri Uygulama Esasları TUCBS Metaveri 9

10 kentbis Metaveri Uygulama Esasları TUCBS Portalı TUCBS kullanıcısı; yazılım/donanım bağımsız olarak, ihlyacı olan veriye elektronik ilelşim ağları üzerinden erişebilmeli ve kullanabilmelidir. TUCBS portalındaki kullanıcı Veri paylaşımı ve değişimi altyapısı Kamu kurumları ve yerel yönelmlerin verisi Adres, Bina, vb. 0

11 kentbis Kavramsal Model Uygulama Şeması Kuralları Her bir veri teması için nesneye yönelik- ilişkisel UML uygulama şemeları ve detay katalogları ürellmektedir. Stereotype Uygulama Şeması (ApplicaLon Schema) Detay Tipi (Feature Type) Veri Tipi (Data Type) Kod Listesi (Code List) Öznitelik Değeri (EnumeraLon) Kullanılan Standart ISO 909 ve TUCBS Kavramsal Modele göre ISO 936 ve TUCBS Geometri ye göre ISO 903 ISO 936 ISO 936. kentbis Kavramsal Model Örnek UML Uygulama Şeması

12 KBS Standart GelişLrme Metodolojisi İP. Mevzuat Analizi İP.3 İş ve Veri Gereksinim Analizi İP.3 Mevcut Veri Analizi; BÖHHBÜY, KBS uygulamaları... İP.4 Uluslararası Standart Analizi KBS temaları; AD, BI, TK, UL, HI, AR, OR, TO, JD için veri modelleri gelişlrilmektedir. TUCBS Standart GelişLrme Metodolojisi Kullanıcı Gereksinim Analizi için; İP.3 saha çalışması ile tüm TUCBS paydaşlarının coğrafi veriye ihlyaç duyduğu uygulamalar ve veri gereksinimi belirlenmişlr. Uygulama/Servis Listesi Her bir uygulama için; İş- Veri Gereksinim Analizi 2

13 Implementation Rules (e.g. Data Specifications) Mechanisms for sharing and exchange Memberstates Data (e.g. Addresses) (This is a very generic diagram!) 7/9/2 GSDI Workshop.3 INSPIRE DS Addresses 7 TUCBS Standart GelişLrme Metodolojisi The Balance Challenge TUCBS ve KBS veri temaları için oplmum içerik belirlenmelidir. Which level of interoperability is just right? Simple Basit Too simple: Uygulaması kolay Yetersiz uyum Kullanıcı için beklenen Few benefits faydayı sağlamaması Identified requirements can not be supported Insufficient harmonisation Too complex: Karmaşık Complex Uygulaması zor Difficult to implement Beklenen Substantial faydaların benefits available belirli kullanıcılara only to few users yönelik olması High costs Yüksek bedeller (Kaynak: INSPIRE) GSDI Workshop.3 INSPIRE DS Addresses 8 4 TUCBS:BI Bina Veri Modeli Temalardaki detay sınıflarına ait öznitelik ve değerleri tanımlanmışyr. Sınıflar arasında; - İlişki (AssociaLon) - KalıYm / Genelleme (Inheritance) - Bütünleme (AggregaLon) - Oluşum (ComposiLon) - Bağımlılık (Dependency) ilişki Lpleri tanımlanmışyr. 3

14 7/9/2 TUCBS:AD Adres ve ilişkili temalar class Capraz Iliski Adres DisKapi eski Kapi No: Integer geom etri : GM _Poi nt kapi No: CharacterStri ng kapi T uru: Num arataj T i pi uavtno: Integer yerl esi m Aci si : Real Num arataj AdresDi skapi 0.. konum : Cografi Konum [..*] {ordered} konum l ayi ci : AdresKonum l ayi ci [..*] {ordered} tucbsno: NesneT ani m l ayi ci «voi dabl e, l i fecycl einfo» versi yonbasl angi ct ari hi : DateT i m e versi yonbi ti st ari hi : DateT i m e [0..] versi yonno: CharacterStri ng bi l esen Detay «voi dabl e» * AdresBilesenleri tucbsno: NesneT ani m l ayi ci «voi dabl e, l i fecycl einfo» versi yonbasl angi ct ari hi : DateT i m e versi yonbi ti st ari hi : DateT i m e [0..] CSBM csbm Adi : CharacterStri ng csbm Kodu: Integer csbm T uru: CharacterStri ng {ordered} «voi dabl e» sabi tt ani ti m Num arasi : CharacterStri ng [0..] IdariBirimAdi i l : CharacterStri ng i l ce: CharacterStri ng Kod: Idari Bi ri m Kodu m ahal l e/koy: CharacterStri ng KapiNo di skapi No i ckapi No: CharacterStri ng [0..] turu: Num arataj T i pi..*..* TUCBS:UL UL::YolTanitimi TUCBS:ID ID::M ahallekoy..* TUCBS:TK TUCBS:BI TK::Parsel BI::Bina 0..* * UL::YolHatti A. Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 kbs.gml ile verilerin birlikte çalışabilirliği UML Uygulama Şemaları ile coğrafi verilere yazılım/donanım bağımsız açık erişimi sağlayan GML3.X uyumlu veri değişim formay ürellmektedir. TUCBS:UL XMI XML Uygulama Şeması Detay Sınıfı Geometri Tanımlamalar Öznitelikler İlişkiler Değer Kümesi A. Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202, 4

15 )$* $%,$% )$* $%,$% )$* $%,$% "5'E# (4/?03 F903 7/9/2!"#$% &'()*$,--$./00/2/$.03/45$*67849/0 % :;<-:<,::=!" >$,::;%,::=$9734/?79@3$9A746B37A$!BCD kbs.gml ile verilerin birlikte çalışabilirliği &#%2&34"&5.!&#4&*"&67%83#&'$#%9#&('&*"& 8"(4:#*7#6&;"0 GML Standart '7/I/4I923I$ kodlama J?8I9K 3/0 Standartlaşmış '7/I/4I923I$ servis '34@9?3$&734L/?3A arayüzü!"#$%"$#&'&!"#%("$# StandartlaşNrılmış Veri Değişim dili )$*&$(#2%$ $%,$% )$*&$(#2%$ $%,$% )$*&$(#2%$ $%,$% )$*&444 $%,$%!&'$GH (4/?03 F !"#$% &'()*$,--$./00/2/$.03/45$*67849/0 % :;<-:<,::=!! >$,::;%,::=$9734/?79@3$9A746B37A$!BCD!! Bütünleşik ulaşım ağı 5

16 7/9/2 0.7 Transportation objects The transportation model of CityGML is a multi-functional, multi-scale model focusing on thematic and functional as well as on geometrical/topological aspects. Transportation features are represented as a linear network in LOD0. Starting from LOD, all transportation features are geometrically described by 3D surfaces. The areal modelling of transportation features allows for the application of geometric route planning algorithms. This can be useful to determine andofmanoeuvres required alongand a transportation route. This information can TransportationCo mplexrestrictions is a subclass _TransportationObject of the root class _CityObject. The geometalso be employed foroftrajectory planning of mobile the realthe world or thelevels automatic placement avatars rical representation the TransportationCo mplexrobots variesin through different of detail. SinceofTransporta(virtualmplex people) vehicleofmodels in 3D and visualisations and training simulators. The gtransportation tionco is aor subclass _ CityObject hence a feature, it inherits the attribute ml:na me. Themodel street of name CityGML is provided by the thematic extension module Transportation (cf. chapter 7). is also stored within the gml:na me property of the Road feature. The main class is TransportationComplex, which represents, for example, a road, a track, a railway, or a square. In the LOD0 the transportation complexes are modelled by line objects establishing a linear network. Yol coarsest nesneleri Fig. 57 illustrates the four different thematic classes. On this abstract level, path finding algorithms or similar analyses can be executed. It also can be used to generate schematic drawings and visualisations of the transport network. Since this abstract definition of transportation network does not contain explicit descriptions of the transportation objects, it may be task of the viewer application to generate the graphical visualisation, for example by using a library with style-definitions (width, color resp. texture) for each transportation object. Starting from LOD a TransportationComplex provides an explicit surface geometry, reflecting the actual shape of the object, not just its centerline. In LOD2 to LOD4, it is further subdivided thematically into TrafficAreas, which are used by transportation, such as cars, trains, public transport, airplanes, bicycles or pedestrians and in AuxiliaryTrafficAreas, which are of minor importance for transportation purposes, for example road markings, green spaces or flower tubs. The different representations of a TransportationComplex for each LOD are illustrated in Fig. 60. «««OGC 2-09 Kaynak: CityGML Fig. 57: Representations of TransportationComplex (from left to right: examples of road, track, rail, and square) (source: Rheinmetall Defence Electronics). A TransportationComplex is composed of the parts TrafficArea and AuxiliaryTrafficArea. Fig. 58 depicts an a LOD2 TransportationComplex configuration within a virtual 3D city model. The Road consists of 0.9example Cityforfurniture several TrafficAreas for the sidewalks, road lanes, parking lots, and of AuxiliaryTrafficAreas below the raised flower beds. City furniture objects are immovable objects like lanterns, traffic lights, traffic signs, flower buckets, advertising OGC 2-09 columns, benches, delimitation stakes, or bus stops (Fig. 67, Fig. 68). City furniture objects can be found in traffic areas, residential areas, on squares or in built-up areas. The modelling of city furniture objects is used for visualisation of, for example city traffic, but also for analysing local structural conditions. The recognition of special locations in a city model is improved by the use of these detailed city furniture objects, and the city 0.9 City furniture model itself becomes more alive and animated. The city furniture model of CityGML is defined by the thematic extension module CityFurniture (cf. chapter 7).like A. objects Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 City furniture are immovable objects lanterns, traffic lights, traffic signs, flower buckets, advertising columns,objects benches, delimitation or businfluence stops (Fig.on67,simulations Fig. 68). City objects city can be found situations. in City furniture can have an stakes, important of,furniture for example traffic traffic areas, residential areas, on squares or in built-up areas. The modelling of city furniture objects is used for Navigation systems can be realised, for example for visually handicapped people using a traffic light as routing visualisation of, for example city traffic, but also for analysing local structural conditions. The recognition of target. Likewise, city furniture objects are important to plan a heavytraffic vehicle transportation, where the exact special locations in a city model is improved by the use of these detailed areacity furniture objects, and the city Auxiliary Traffic position model and further conditions of obstacles must be known. itself becomes more alive and animated. The city furniture model of CityGML is defined by the thematic traffic area extension module CityFurniture (cf. chapter 7). areas Fig. 60: TransportationComplex in LOD0,, and 2-4 (example shows part of a motorway) (source: Rheinmetall Defence Electronics). City furniture objects can have an important influence on simulations of, for example city traffic situations. Traffic area Navigation systems can be realised, for example for visually handicapped people using a traffic light as routing In LOD0 transportation objects in the same way where as in the GDF, the ISO target. areal Likewise, city furniture objectslike are squares importantshould to planbea modelled heavy vehicle transportation, exact standard for and transportation networks, which must is used in most car navigation systems. In GDF a square is typically position further conditions of obstacles be known. 3B kent ve kent obilyaları represented asnaesneleri ring surrounding themplace and to which Road the incident roads connect. CityGML does not cover further functional aspectsfor ofthe transportation modelsm(e.g. as aitroad, is intended Fig. 58: Example representation ofnetwork a TransportationCo plex inspeed LOD2 inlimits) CityGML: which is theto complement aggregation of TrafficAreas AuxiliaryTrafficAreas (source: City of Solingen, IGG Unihave Bonn). and not replace existing standards like and GDF. However, if specific functional aspects to be associated with CityGML transportation objects, generic attributes SURYLGHG E\ &LW\*0/ V Generics module (cf. chapter 0.2) Fig. 59 depicts the UML diagram of the transportation model, for the XML schema definition see annex A.0. can be used. Moreover, further objects of interest can be added from other information systems by the use of ExternalReferences (see chapter 6.). For example, GDF datasets, which provide additional information for car navigation, can be used for simulation and visualisation of traffic flows. The values of the object attributes can be augmented or replaced using the concept of dictionaries (see chapter 6.6). These directories may be countryor user-specific (especially for country-specific road signs and signals). Copyright 202 Open Geospatial Consortium. 24 Fig. 67: Real situation showing a bus stop (left). The advertising billboard and the refuge are modelled as CityFurniture objects in the right image (source: 3D city model of Barkenberg). Fig. 67: Real situation showing a bus stop (left). The advertising billboard and the refuge are modelled as CityFurniture objects in the right image (source: 3D city model of Barkenberg). 26 Copyright 202 Open Geospatial Consortium. A. Ç. AYDINOĞLU, Kent Bilgi Sistemi Standartlarının Belirlenmesi Çalıştayı, 09- Temmuz 202 Fig. 68: Real situation showing lanterns and delimitation stakes (left). In the right image they are modelled as CityFurniture obfig. 68: Real situation showing lanterns and delimitation stakes (left). In the right image they are modelled as CityFurniture objects with mplicitgeo metry representations (source:3d3d city model of Barkenberg). jects Iwith ImplicitGeo metry representations (source: city model of Barkenberg). Thediagram UML diagram the city furniture modelisisdepicted depicted in thethe XML schema definition see below The UML of theofcity furniture model in Fig. Fig.69, 69,forfor XML schema definition see below anda.5. annex A.5. and annex Kent Bilgi Sistemi Standartlarının class CityFurniture attributesclass, class, function function and. Their possible valuesvalues can be can specified The classthe CityFurniture may may havehave the the attributes andusage usage. Their possible be specified in corresponding code 2 lists (chapter and annex C.4). The class attribute allows an object classification like Belirlenmesi Çalıştayı, in0corresponding 9- T emmuz 02, code lists (chapter and annex C.4). The class attribute allows an object classification like traffic light, traffic sign, delimitation stake, or garbage can, and can occur only once. The function attribute traffic light, traffic sign, delimitation stake, garbage can,belongs and can occur only once. traffic The function describes, to which thematic area the cityor furniture object to (e.g. transportation, regulation,attribute describes, to which thematic area the city furniture object belongs to (e.g. transportation, traffic regulation, architecture), and can occur multiple times. The attribute usage denotes the real purpose of the object. architecture), and can occur multiple times. The attribute usage denotes the real purpose of the object. Copyright 202 Open Geospatial Consortium. Copyright 202 Open Geospatial Consortium

17 2 L. van den Brink et al. (a) 3B kent modeli örnekleri International Journal of Geographical Information Science Downloaded by [Istanbul Technical University] at 6:53 June 202 Figure 2. Triangulated terrain integrated with IMGeo objects (Emgård and Zlatanova 2008). Figure ). Downloaded by [Istanbul Technical University] at 6:53 June 202 (b) Figure 4. Examples of 2.5D topographic data provided by Province of Noord Brabant (a) and Rijkswaterstaat (b). Rijksdriehoeksmeting) (EPSG:28992)andz coordinates in the national height system (called Nieuw Amsterdams Peil) (EPSG:5709).Theexperiencesinthepilotshowedthat this reference system should be explicitly stated in the CityGML files. Example of the employed 2.5D topological principle (Oude Elberink and Vosselman 4. Experiments with the model Another Dutch data set, that is, the 2.5D topographical data set of This Rijkswaterstaat section illustrates how the model works in practice by showing how the IMGeo (DTB), already supports a similar 2.5D topological structure of topography. classexamples Wegdeel are (TrafficArea) (i.e. road part; road segments that constitute a road) is modelled thatinsuch CityGML IMGeo 2.5D and by applying Teşekkürler the model to real data at the end of this shown in Figure 4 (Rijkswaterstaat 20). Although this data set shows data structures are already in existence and therefore feasible, it doesection. not yet contain height information within the polygon surfaces, in contrast to the LOD0 representations of CityGML IMGeo Define the reference system CityGML IMGeo uses the Spatial Reference System (SRS) EPSG:745. This is a combined SRS of x, y coordinates in the national reference system (called Doç. Dr. Arif Cagdas AYDINOGLU İTÜ Geomatik Mühendisliği Maslak- aaydinoglu@itu.edu.tr Istanbul - Turkey 7