Japan Saijo

An Experiment onSpatial Data Exchange: 

An Experiment on Spatial Data Exchange October 24, 2001 MURAO, Yoshiaki (IBM Japan) Email: mura@yamato.ibm.com ISO/TC211 Workshop on Standards in Action SAIJO, Yuuki (Geographical Survey Institute) Email: saijo@gsi.go.jp

Content: 

Content Structure and Schedule Experiment phase II Experiment phase III Considerations Demonstoration

Structure for ISO 19100 series in Japan: 

Structure for ISO 19100 series in Japan ISO/TC211 ISO/TC211 Domestic Committee Japanese National Standards for Geographic Information (NSGI) Committee Japan side with 5 WGs

Activity in Committee of National Standards for Geographic Information: 

Activity in Committee of National Standards for Geographic Information Development develop NSGI as conformed to ISO 19100 series (mainly focused on exchange, in current) Support applications specify methodologies to apply NSGI to practical operations Experiments on Spatial Data Produces / Exchanges

Schedule of Spatial Data Experiments: 

Schedule of Spatial Data Experiments FY 1999 Spatial Data Exchange Experiment I 　Convert existing spatial data to standard specification data sets 　Load standardized data set into existing GIS FY 2000 FY 2001 Spatial Data Exchange Experiment III (will end on March 2002) Dynamic recognition of the content of Application Schema Implementation of Portrayal Catalog / Specification Spatial Data Exchange Experiment II Merge multiple standardized data sets in existing GIS Exchange update information XML documentation for Application Schema

Results ofSpatial Data Exchange Experiment II: 

Results of Spatial Data Exchange Experiment II

Dataset and file sizes: 

Dataset and file sizes ( Experiment II ) File ID Original Data 19100 Conformed Data Ratio 513242 533606 533607 533616 533617 544001 564033 1,176 KB 3,002 KB 1,966 KB 2,056 KB 1,651 KB 1,266 KB 1,122 KB 7,364 KB 19,790 KB 13,111 KB 13,316 KB 10,752 KB 8,157 KB 6,584 KB 6.26 6.59 6.66 6.48 6.51 6.44 5.87 (Original Data are in CSV style.) Impact of large file size: Hard to transfer files Process time of XML parsing Memory shortage in DOM process Actions to reduce file size: Simplify Application Schema Assign short tag names Use ATTLIST if possible

Exchanging “Update Data”: 

Exchanging “Update Data” GIS - A Base Map (XML) Update operation GIS - B Update Data (XML) Added Deleted Modified Get Update Information ( Experiment II ) Conformed to 19107, 19108, 19109 and 19118

Defining “Application Schema Description File”: 

Defining “Application Schema Description File” Application Schema Description File Class definitions by UML <Class_A> <Data1> …… </Data1> <Data2> …… </Data2> </Class_A> Class_A DataType 1 DataType 2 <Class name=“HighwayNode” tag="HighwayNode“ abstract="NO" stereotype="Feature"> <Property name=“BoundaryType” tag="meshuKyokai" datatype="Boolean" multiplicity="1" value="false"/> <Composition name=“Point” tag="pt“ targetClass="GM_Point" stereotype="geometry" multiplicity="1“ /> <Composition name=“Period” tag="pd“ targetClass="TM_Period“ stereotype="temporal" multiplicity="0..1“ /> Instantiation of classes by XML General Encoding Rule HighwayNode GM_Point TP_Node Class Property Composition Application Schema by UML MetaClass definitions by UML Instantiation of MetaClasses by XML = Definition of Application Schema by XML General Encoding Rule Data2 Data1 Instances of any UML class diagrams can be encoded with XML.

Characteristics of “Application Schema Description File”: 

Characteristics of “Application Schema Description File” All contents of UML class diagrams are described in “Application Schema Description File” as an XML document. Contents of “configuration table” for Encoding are also included. Both of machine and human readable. Independent from commercial UML tools. Information of Application Schema can be stored and interchanged. ( Experiment II )

Overview of on-goingSpatial Data Exchange Experiment III: 

Overview of on-going Spatial Data Exchange Experiment III

Highlights: 

Highlights Base Map + Thematic data (Point data) overlay Dynamic recognition of Application Schema Implementation of Portrayal Catalogs / Specifications ( Experiment III )

Functional Overview: 

Functional Overview GIS ( 6 different systems ) Base Map (XML) Application Schema of Thematic Data (XML) ( Experiment III ) Conformed to 19107, 19108, 19109 and 19118 Thematic Spatial Data (XML) Portrayal Catalogs and Portrayal Specifications (XML) Load Standardized format file of Base Map data. Application Schema of Base Map is statically defined in GIS-A. Load Application Schema Description File of thematic data, and recognize new classes and their attributes dynamically. According to the recognition of Application Schema, load Thematic Data and overlay them on Base Map. Load Portrayal Catalogs / Portrayal Specifications, and change the way to draw each features. Based on 19117 (1) (2) (3) (4)

Schedule and Current Phase: 

Schedule and Current Phase ( Experiment III ) Aug Sep Oct Nov Dec Jan Feb External Design Detail Design / Development Test Documentation External Design has been completed. Now

Considerations: 

Considerations

Considerations around Application Schema: 

Considerations around Application Schema Differences between spatial attribute and thematic attributes. ( Experiment I ~ III ) Open standard format file for Application Schema descriptions. 〒 ABC Post Office PostOffice +name : CharacterString +symbol_pos : GM_Point +name_pos : GM_Point ≪Feature≫ +shape : GM_Surface Essential spatial Attr. for the feature Thematic spatial Attr. to draw additional data No way to distinguish each other. An alternative: => Add stereotypes at the top of attribte statement to identify “spatial” or “thematic”

Considerations around Encoding: 

Considerations around Encoding File size problem with XML Rule for general UML class diagrams. Exchange Configuration table ( Experiment I ~ III )

Demonstrations: 

Demonstrations

Thank you: 

Thank you