1. Mapping your business Du domaine métier à l'informatique Mapping your business The Model Driven Approach Jeff Konnen FME User Conference September 22nd Vancouver, BC

2. Mapping your business http://ilix.inser.ch The Idea Exchange Data between several GIS Software Packages (e.g. for cadastral data) Impose the data format and model for data exchange Use a Neutral Language to describe the Data Model Let everyone implement the Data Model like he wants Let everyone implement its own interface to the mandatory data exchange format

3. Mapping your business http://ilix.inser.ch INTERLIS – The GeoLanguage INTERLIS is a data exchange format, allowing you: –To DESCRIBE a data model including Tables Constraints Relationships Generalization / Polymorphism in a VENDOR – NEUTRAL language –To EXCHANGE data based on this Model

4. Mapping your business http://ilix.inser.ch INTERLIS - EXAMPLES DATA MODEL –Object Oriented –Text based description –Can be edited visually with the OSS UML Editor objectOriginType=(AV,BFS,DGN_AG,DGN_BE,DGN_LU,DGN_SO,DGN_VD, DGN_ZH,GG25,GN_BL,LK100,LK200,LK25,LK50,LK500,NDB,Photo, GN25,BWG,Kanton,Ausland,GN200,undefined); gebObject=(Z_Gebaeude,Z_Innenhof,Z_Gasthof,Z_Huette,Z_Kirche,Z_Kuehl turm,Z_Lagertank,Z_Perron,Z_Schiessstand,Z_Schloss,Z_Station,Z_ Treibhaus,Z_WBecken,undefined); CLASS geb = ATTRIBUTE ObjectId: MANDATORY INTEGER4; ObjectOrigin: MANDATORY objectOriginType; ObjectVal: MANDATORY gebObject; YearOfChange: MANDATORY Jahr; Geometrie: MANDATORY SURFACE WITH (STRAIGHTS) VERTEX LKoord; END geb; CLASS geb_zentroid = ATTRIBUTE Geometry: MANDATORY LKoord; END geb_zentroid; ASSOCIATION geb_zentroidObjectId = geb_zentroid -- {*} geb_zentroid; ObjectId -- {1} geb; END geb_zentroidObjectId; DATA –XML DATA 8335 12 6 1991 784946.3 153374.2 78494 6.5 153367.9 784950.7 153354.1 784955.7 153345.6 784960.2 153340.1 8336 12 9 1998 785603.9 153327.4 78561 1.4 153340.9 785621.6 153353.1 785639.643 153368.513 8337 12 10 1998 785808.4 153488.7 7857 87.0 153470.5 785766.0 153455.5 785751.0 153448.2 785744.0 153447.0 785735.9 15 3448.1 785686.0 153407.0 785669.5 153391.5 785663.5 153384.5 785658.7 153375.2 785651.5 153361.5 7856 46.0 153349.5 785630.7 153333.2 785615.9 153319.9

5. Mapping your business http://ilix.inser.ch Implementing the Model Driven Approach We implemented the Model Driven Approach for the ESRI Geodatabase: iliX (just as others did for other vendors) What does it mean? –Generate a Geodatabase Schema based on an INTERLIS Data Model Containing all the Constraints, Rules … –Generate an INTERLIS-Model based on an existing Geodatabase –AND: Generate FME Files for data exchange between the Geodatabase and INTERLIS

6. Mapping your business http://ilix.inser.ch The Data Model In the Geodatabase, the INTERLIS Schema looks like this:

7. Mapping your business http://ilix.inser.ch The FME Files FME includes Readers and Writers for the Geodatabase There exists a free FME Plugin for Reading and Writing INTERLIS Data During the creation of the geodatabase schema, 4 simple « mapping – tables » are created from the INTERLIS DATAMODEL. We then programatically generate WORKBENCH-Files based on these mapping-tables allowing the user to exchange data with his geodatabase

8. Mapping your business http://ilix.inser.ch Conclusion The Model Driven Approach allows you to efficiently exchange data FME is the right tool to do the conversion You can generate schemas and scripts automatically to improve the process  A similar approach could be taken with GML! If you got questions regarding INTERLIS or the generating of Workbench-Files, you can send them to fme@inser.ch