Evolution of Web GIS Maps

Instant Cache from Mapmobility

Combine the benefits of both externally and internally hosted map services. Configure desired data layers in MXD and publish with support for closed, behind-the-firewall installations. Online mapping has finally changed. Here is how it has evolved.

History of GIS Maps on the Web

MapsPhase 1: (beginning 1994)

Dynamic Map Services– Sacrificed style and cartography for performance– Data access on every request meant increased infrastructure load

Advantages	Disadvantages
Direct access to current data	Extremely slow Extreme infrastructure load Terrible cartography

MapsPhase 2 : (beginning 1999)

Externally Hosted Map Services– Access to static, pre-cached maps (Google, Bing, ArcGIS Online)– Fast and virtually no load on internal infrastructure

Advantages	Disadvantages
High performance Well designed cartography Zero production time Fast (assuming bandwidth is good)	Maps can be out-of-date No update cycle control No symbology or design choice Fixed data choice No option for closed firewall implementations

MapsPhase 3: (beginning 2005)

Internally Hosted Cached Maps– Pre-cache maps and host internally on file system– Fast performance and fully integrated with data lifecycle– Same capabilities as dynamic (Query, identity etc.)

Advantages	Disadvantages
Choice of data set Control over data updates Fast Full ArcGIS Server capabilities REST Endpoint Interaction	Time-consuming to produce Requires in-house expertise on high-end cartographic design Additional workflow to manage (keeping cache in sync with data) Additional cache generation hardware and licenses

Now - With Mapmobility

• Combine the benefits of both externally and
  internally hosted map services
• Configure desired data layers in MXD and publish
• Supports closed, behind-the-firewall installations

 

 

---