bringing “it” all together !? dean djokic, esri david maidment

36
Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Upload: andra-dawson

Post on 02-Jan-2016

220 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Bringing “it” all Together !?

Dean Djokic, ESRI

David Maidment

Page 2: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

What is “it” ?

• Integration of data, data models, and analyses in a functional system

GIS

MIKE 21HMS

SWAT

WRAP

MIKE 11

RAS

Other …

Page 3: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Hugh Bender, TNRIS

Page 4: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

• Data providers• Data consumers

– (often both)

• Unspecified at the beginning of the integration exercise

• Proprietary

• Independence from integration platform

• Development out of “control”

• Maintenance “curse”• Complexity increase

(multiplicative)

Integration Issues

Page 5: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Integration Issues(direct interfacing)

GIS

MIKE 21 HMS

SWAT

WRAP

MIKE 11

RAS

Other …

N

N * (N - 1)Bi-directional

Page 6: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Integration Issues(intermediary interfacing)

GIS

MIKE 21 HMS

SWAT

WRAP

MIKE 11

RAS

Other …

N

2 * NBi-directional

XML

Page 7: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Integration Issues(number of required interfaces)

Number of models

Direct integration

Intermediary integration

2 2 4

3 6 6

4 12 8

5 20 10

N N * (N-1) 2 * N

Page 8: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

An XML-Based Generic System for Spatial

Data Exchange

Extension of GOODES approach

Dean Djokic, Zhumei Qian, Xinnong Zhou

Environmental System Research Institute

Redlands, CA

Page 9: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Why XML-Based Spatial Data Exchange

• Semantic tags for spatial data are user specified

• Easy customization of data structure for different systems

• Data structure is extensible

• Good for data distribution on Internet (multi-platform)

• Existing technologies for XML management (parsers, editors, viewers, components, checkers, converters, …) – economy of development

Page 10: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

System Design of the XML-Based Exchange System

• Architecture– A central exchange mechanism accompanied by

customizable XML structures

• Three components– Central data exchange mechanism embedded in GIS

(ArcMap-based)

– Customizable control XML structure for import

– Customizable control XML structure for export

Page 11: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

GIS

External Data Analysis Package

Customizable ExportXML Structure

Customizable ImportXML Structure

Import Data as XML Document

Export GIS Data as XML Document

Import Engine

Export Engine

Import

Export

Central Exchange Mechanism

Page 12: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Central XML-Driven Spatial Data Exchange Mechanism

• GIS Import Engine– Transform data from various XML data exchange

structures into spatial data in a user-defined data model• An intermediate XML to XML conversion might be required

– Input data exchange structure and geodatabase design are managed by import control XML

• GIS Export Engine– Transform spatial data from a user-defined data model

into various XML data exchange structures– Output data exchange structure and geodatabase design

are managed by export control XML

Page 13: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Anatomy of an Interface (1)

Page 14: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Anatomy of an Interface (2)

Page 15: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Anatomy of an Interface (3)

Page 16: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Anatomy of an Interface (4)

Page 17: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Anatomy of an Interface (5)

Page 18: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Data Export Process

• Read XML structure

• Determine what needs to be exported

• Determine output data structure

• Generate output data

Export XML Structure I

Export Data I as XML Document

Export Engine

GIS

Export XML Structure II

Export Data II as XML Document

Spatial Data II

Spatial Data I

Page 19: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

A Close Look of Export Process

DetermineData Structure

Output Data

XML Structure

ExportGIS Data

• System reads export control XML• Determines output data structure• Generates output

Page 20: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Customization of Data Export

• Customization is via node attributes in control XML structure

• Node attributes fall into two categories– Describe data model customization

• SourceType, DataLocation, Identity, IdentityValue, and DataFrame

• Follow the logic of spatial database (ESRI geodatabase in this prototype)

– Describe data representation style• Name, Entries, and Target • Completely user defined

Page 21: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Control XML in Export Process

Sample Control XML

Sample Output Data

<StreamNetwork>

<Stream StreamID=“1” />

<Stream StreamID=“2” />

</StreamNetwork>

<Node1 Name=“StreamNetwork” SourceType=“FeatureLayer” Identity=“LayerName” IdentityValue=“Reaches” >

<Node2 Name=“Stream” SourceType=“Feature” Entries=“Multiple” >

<Node3 Name=“StreamID” SourceType=“FeatureTable” Identity=“FieldName” IdentityValue=“Reach_ID” Target=“Attribute” />

</Node2>

</Node1>

Page 22: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Export WorkflowExport Workflow

Page 23: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Data Import Process

• Read in data

• Read control XML structure

• Validate import data structure against the control structure

• Generate spatial data

• Store spatial data in a geodatabase

Import XML Structure I

Import Data as XML Document

Import Engine

GIS

Import XML Structure II

Import Data as XML Document

Spatial Data II

Spatial Data I

Page 24: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Model Connections to ArcHydro

Tim WhiteakerCenter for Research In Water Resources

August, 2002

TIWSSTexas Integrated Water Simulation System

Page 25: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Variety of Models & Input Formats

• Record-Parameter List

• Modify Particular Records

RecordID Parameter1 Parameter2 …RecordID Parameter1 Parameter2 …RecordID Parameter1 Parameter2 …

Update Curve Number

Page 26: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

WRAP Inputs (-SIM, -HYD, CON-SIM)

• Brazos.DAT – basic input file

• Brazos.INF – naturalized streamflows

• Brazos.EVA – net evaporation-precipitation

• Brazos.DIS – flow distribution and watershed parameters

Page 27: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Input Records in GIS

• Brazos.DAT– CP Records

NextDownID

• Brazos.DIS– WP Records Control Point Identifier

Drainage AreaCurve NumberMean Precipitation

Page 28: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

A Central GeoDatabase

~3,316 Control Points

Page 29: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

XMLThe Extensible Markup Language

A meta-markup language for text documents

XML documents with data in strings of text surrounded by text markup that describes the data

Users can define the elements they need. In Water Resources elements like Control Points can be defined

An XML document can be used as a config file for any program to take action based on it

Due to its extensibility & platform independent character XML is being recognized as “The new standard for data exchange”

Page 30: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

From GIS to XMLApplications to extract GIS data and format it as a XML document, are being develop by ESRI (XML-Based Converters)

Page 31: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Control XML Structure

The application extracts the data based on a Control XML file thatspecifies the data to be extracted and the XML structure in which will be organized

Page 32: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

GIS Data with XML StructureAfter running the application, the extracted data is placed in a XML document from which data can be exchanged with any modeling system by parsing the XML structure

Page 33: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

The Document Object ModelDOM

•To parse a XML document

•To readily manipulate the Data XML document file and retrieve all the needed GIS values

•A Visual Basic Application that takes advantage of DOM to retrieve the data and write it back following any format prescribed by any modeling system, e.g., WRAP, SWAT, etc.

Page 34: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

From XML to WRAP

Exporting Geospatial and Time Series Data into WRAP

Page 35: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Generic Data Exchange XML-Based Structure

NewRoot.dis

NewRoot.dat

XML 2 WRAP(DOM)

Data XML

ControlXML

WRAP

Root.dis Root.dat

GISXML

Converter

Page 36: Bringing “it” all Together !? Dean Djokic, ESRI David Maidment

Example of Input FilesExisting Brazos.dat File Existing Brazos.dis File

Updated Brazos.dat FileUpdated Brazos.dis File