Web Mapping Systems

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Notes on slide 1

    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.

    14 Favorites

    Web Mapping Systems - Presentation Transcript

    1. Web Mapping Systems James Fee, GISP – TEC Inc
    2. Web Mapping in 1997
    3. Web Mapping in 2003
    4. Web Mapping in 2007
    5. Modern Web Mapping
    6. What is important? Simplicity Speed Stuff
    7. Expectations
    8. What direction to go?
    9. ESRI Server Stack ArcGIS Server 9.2
    10. 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
    11. 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)
    12. Demonstration
      • Web: http://localhost/nola/
      • Clients:
        • ArcGIS Desktop
        • ArcGIS Explorer
        • Google Earth
          • http://tec003418/ArcGIS/kml/NOLA.kmz
    13. MapDotNet Server
    14. 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
    15. 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
    16. MapDotNet Server
      • Demonstration
        • http://demo.ischosting.net/virtualharriscounty/
        • http://www.virtualtallahassee.com/
      • WMS Client Support
        • ArcGIS Desktop
    17. Open Source Servers
      • OSGeo Server + TileCache + OpenLayers
    18. 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
    19. 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
    20. MapServer or GeoServer
      • Demonstration
        • http://tilecache.org/demo.html
        • http://openaerialmap.org/
        • http://www.openstreetmap.org/
    21. So How Do You Choose?
    22. Factors to consider Goals Cost Maintain Work Flows Obsolescence
    23. Concerns
      • Limited staff
      • Need flexibility
      • Dynamic mapping
      • Accessibility
    24. The Way Forward
    25. Questions? Questions & Answers

    + James FeeJames Fee, 2 years ago

    custom

    2831 views, 14 favs, 0 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 2831
      • 2831 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 14
    • Downloads 0
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories