esri euc 2008 - developing hydrologycgis server 9.3 mashups with ar

Developing Hydrology Mashups with ArcGIS

Server 9.3

by Alper DinçerM.Sc. Civil EngineerGeo Web Developer

State Hydraulic Works (DSI)TURKEY

E-mail : gis@dincer.tc

Outline DSI in Brief Infrastructure of GIS in DSI Mashups Conclusion Discussions

DSI in Brief

State Hydraulic Works (DSI) is a legal entity included in general budget, and is the primary executive state agency responsible for planning, management, development and operation of the nation’s overall water resources.

It is founded in 1953 as a public agency.

DSI in Brief

DSI is responsible for four major tasks namely;• Irrigated agriculture enhancement• Hydroelectric energy generation• Water supply to large cities• Flood prevention measures

DSI in Brief

DSI is responsible for dam projects, surface water and groundwater.

DSI in Brief – GIS UsageLayers used in DSİ are :• National and City Boundaries• Sea Boundaries• Lakes and Ponds• Dams• Rivers and streams• Hill shade and DEM• Areas due to usage, ex: residential areas • Monitoring Stations

DSI in Brief – GIS Usage• River Basins• DSI districts• Wells• Irrigation Areas• Soil Classification Areas• Geological Areas

DSI in Brief – GIS Usage

Some of Layers used in DSI in Action

Infrastructure of Software

Infrastructure is based on ESRI Products ArcGIS Server 9.2 / SDE ArcGIS Server 9.3 / SDE (Still for testing

purposes) Oracle 10g PostgreSQL with PostGIS Extension Windows Server 2003

Infrastructure of Hardware

Infrastructure of Internal Apps

DSI Statistics Bulletin on Map-Based on ASP.NET Web ADF onArcGIS Server 9.2

Infrastructure of Internal Apps

DSI Base maps on ArcGIS Server 9.2 Default Template

Infrastructure of Internal AppsMashup Example:Flow Monitoring Stations App.- Based on ASP.NET, Oracle Spatial, Google Maps API

Infrastructure of Internal AppsMashup Example:Energy and DamsApp.- Based on ArcGIS Server 9.3, Google Maps API

Infrastructure of Internal AppsMashup Example:Monitoring Stations App.- Based on ArcGIS Server 9.3, Google Earth

External Apps - Mashups

Mashups are used for testing purposes inside DSI, but the main target of mashups is the external users. There are approximately 500 users inside DSI, but internet is not as small as inside, so we have to think about :

Performance (ArcGIS Server 9.3 & GAE) User Interface (YUI) Security (Token based – still working on)

Mashups – What is mashup? In web development, a mashup is a web

application that combines data from more than one source into a single integrated tool; thereby creating a new and distinct web service that was not originally provided by either source. (Wikipedia)

Mashups – What is ingredients? Google Maps API with YUI / DOJO JS

Framework ArcGIS Server 9.3 with REST Services Arc2Earth on ArcMap (for static tiles) Google App Engine (for storing static tiles) Little knowledge of Python and Javascript Aptana Studio Community Edition or notepad

Mashups – Why Google Maps API?

Coverage of both Street Maps and Satellite Maps in Turkey (Main Reason)

Support for dynamic “Ground Overlays” Better community support Open source extensions

Mashups – Which JS Framework?DOJO vs YUI

Depends on your personal chooseBoth frameworks are powerful and have a good

documentation.For me : DOJO for ArcGIS Javascript API YUI for ArcGIS Javascript Extension for the

Google Maps API

Mashups – Why Arc2Earth for Static Tiles?

I used to develop mashups Arc2Earth before ArcGIS Server 9.3 and accessing static tiles via direct connection is a bit faster than accessing via ArcGIS Server Services. (don’t ask for scientific proof, because there isn’t any )

Mashups – Why Google App Engine?

It is only used for storing tiles for now, but it can be used for GIS queries and analysis in the future.

Google App Engine’s advantages are: No need for hardware and software Scalable (Same app. for 1 to 1 Million user) Free (Up to some limitations)

Mashups – Anatomy of a mashup

Mashups – Current Situation

There is a conflict about security issues on which layers and how much data to be available for the public. When the issue will be solved, our mashup will completely opened to the public.

DEMO

Conclusion

This presentation covers the new era in GIS development : “mashups”

As it is seen from the slides, it is much more easy than before to develop web based GIS applications with the service based architectures and mash them up.

THANKS FOR ATTENTION!

Discussions

Questions & Answers