• Save
Web Mapping Systems
Upcoming SlideShare
Loading in...5
×
 

Web Mapping Systems

on

  • 7,477 views

 

Statistics

Views

Total Views
7,477
Views on SlideShare
7,440
Embed Views
37

Actions

Likes
17
Downloads
0
Comments
0

5 Embeds 37

http://www.techgig.com 20
http://www.slideshare.net 12
http://www.linkedin.com 2
https://www.linkedin.com 2
http://www.kovair.techgig.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Choosing a web mapping system can be difficult and confusing. It seems like every week, there is a new technology that will be a revolutionary change forward. You can start with the most simple Google Maps based product, to full custom ESRI ArcGIS Server geoprocessing. The goal is to find a system that works with your existing workflows, but still gives your “customers” a product they can use. We will look at what makes a modern mapping system, what systems that are out there and what to consider when looking at these systems.

Web Mapping Systems Web Mapping Systems Presentation Transcript

  • Web Mapping Systems James Fee, GISP – TEC Inc
  • Web Mapping in 1997
  • Web Mapping in 2003
  • Web Mapping in 2007
  • Modern Web Mapping
  • What is important? Simplicity Speed Stuff
  • Expectations
  • What direction to go?
  • ESRI Server Stack ArcGIS Server 9.2
  • ArcGIS Server 9.2
    • Different licensing levels depending on requirements
    • Supports web mapping, KML (Google Earth), Geography Network, tile cache
    • Supports almost every GIS data type
    • Wizard based maintenance
    • Requires Microsoft Windows Server
  • ArcGIS Server 9.2
    • Pros
      • Easy to use, easy to install
      • ArcGIS is the GIS standard
      • ESRI Technical Support (phone, email, forums)
      • .NET or Java based development (REST support at 9.3)
      • Windows based (Linux and UNIX support is limited)
      • Support for ESRI, KML and WMS web services
      • Easy administration
      • Support for Tile Cache
    • Cons
      • Expensive (ArcGIS Server Enterprise “required”)
      • May require ArcGIS Desktop license
      • Windows based (Linux /UNIX support is limited)
  • Demonstration
    • Web: http://localhost/nola/
    • Clients:
      • ArcGIS Desktop
      • ArcGIS Explorer
      • Google Earth
        • http://tec003418/ArcGIS/kml/NOLA.kmz
  • MapDotNet Server
  • MapDotNet Server
    • .NET based spatial application development platform
    • Supports Web 2.0 standards
    • Serve GIS data on top of Microsoft Virtual Earth
      • 2D or 3D views, address search, familiar navigation
    • Support for ESRI Server products, most GIS data formats, .NET API well documented
    • Requires Microsoft Windows Server
  • MapDotNet Server
    • Pros
      • Inexpensive (very reduced price for non-profit groups)
      • Windows based
      • .NET API
      • Support for Tile Cache
      • Support for Virtual Earth API
      • Supports Open Standards (OGC)
      • Supports ESRI Servers (ArcSDE, ArcIMS)
      • Technical Support (email, forums, Wiki)
    • Cons
      • Not as easy to administer as ArcGIS Server
      • Windows and .NET development only
  • MapDotNet Server
    • Demonstration
      • http://demo.ischosting.net/virtualharriscounty/
      • http://www.virtualtallahassee.com/
    • WMS Client Support
      • ArcGIS Desktop
  • Open Source Servers
    • OSGeo Server + TileCache + OpenLayers
  • MapServer or GeoServer
    • Platform independent (Can run on Linux, Macintosh, Windows, UNIX)
    • No installation required (cgi, Java, Javascript or python based)
    • Support for Open Geospatial Consortium (OGC) Standards
    • No licensing fees (software is freely available)
    • Can use Google or Microsoft mapping APIs for imagery
  • MapServer or GeoServer
    • Pros
      • No licensing
      • Support for OGC standards
      • Many development environments (.NET, C++, Java, Python, Perl, Javascript, Ruby, etc)
      • Vibrant community (email, Wiki, forums, IRC)
      • Customization is limitless
      • Server OS independent
    • Cons
      • Difficult to administer
      • No official technical support
  • MapServer or GeoServer
    • Demonstration
      • http://tilecache.org/demo.html
      • http://openaerialmap.org/
      • http://www.openstreetmap.org/
  • So How Do You Choose?
  • Factors to consider Goals Cost Maintain Work Flows Obsolescence
  • Concerns
    • Limited staff
    • Need flexibility
    • Dynamic mapping
    • Accessibility
  • The Way Forward
  • Questions? Questions & Answers