Map Viewer  |  Live Demos

Connecting the Map Viewer to your GISThe EKO-System Map Viewer supports several open GIS standards and can be used in conjunction with your organization's GIS infrastructure. The Map Viewer can be configured to view spatial data from multiple sources including ESRI shape files and OGC (Open Geospatial Consortium) web services. Integration with ESRI ArcGIS Server is also supported. This option offers the greatest level of flexibility for your organization.

The latest release of the Portal Map Viewer supports direct integration with your ESRI ArcGIS Server through the ArcGIS Server REST API. The ESRI supported API is used by the ESRI Flex API and Silverlight web components and is a proven mechanism for integrating spatial data across the web.  How does it work? In general, the  Map Viewer makes  requests to your ArcGIS REST service(s); requests are processed on your ArcGIS Server; your server then returns either a JSON formatted or map image response to the user's Map Viewer for display.

The diagram below illustrates how the Portal Map Viewer can interact with your ArcGIS server.
Map Viewer GIS Integration Diagram File-Based Integration The file based approach requires your organization to provide shape files for use in the Map Viewer. These shape files are converted to WFS compliant XML, stored on EKO-System servers, and are used as the source of your feature layers. This approach works very well for layers who's content is not in a constant state of change.

Pros
 Offers the best performance (no external service request/response is required)
 No ArcGIS Server is needed
 Best option for layers that don't change often
 Has zero imact on your organization's GIS

Cons
 Layer files must be updated when layers and/or metadata changes
 Display attributes  (i.e. colors, symbology, etc.) are maintained within the Map Viewer configuration

Web Service Integration The web service approach uses your ArcGIS Server as the source for feature layers. When users turn on or off service-bound layers, requests are made to your ArcGIS Server for new data (or image). Web service feature layers can return JSON (JavaScript Object Notation) data or an image layer. The Map Viewer can accommodate both types of layers. When features are selected, additional requests can be made to retrieve meta data for the selected feature. This approach provides the greatest level of integration with your GIS and enables your organization to have full control over the GIS data presented in the Map Viewer.

Pros
 Your organization maintains layers, metadata and display characteristics (image layers only)
 The most up-to-date layer and meta data are retrieved "on demand" from your ArcGIS Server(s)
 EKO-System project data is viewed together with your GIS layers

Cons
 Your Organization must host ArcGIS services on the Web
 External service requests will impact your organizations ArcGIS Server performance
 End user map performance is dependent upon the bandwith and loading of your hosted ArcGIS Server environment
 Slower performance can impact end-user map experience


A Hybrid ApproachIn most scenarios, you will have layers that remain static and will offer the best performance as File-Based layers. You may also have layers that are a constant state of change (i.e. County Parcels, Fish Distribution, etc.). These layers will most likely be implemented as Web Services. The Map Viewer handles each layer type automatically behind the scenes. Users simply turn each layer on/off as needed.

Accessing EKO-System Spatial DataEKO-System users have the ability to download project spatial data in ESRI Shape File format while signed in to the EKO-System back office application. Paladin is currently developing spatial data services to allow users to access this spatial data directly via REST web service.
Powered by EKO-System ®
Copyright © 2005-2010 Paladin Data Systems. All rights reserved