Your SlideShare is downloading. ×
Getting your Data Out There:An Introduction to Distributed GIS
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Getting your Data Out There: An Introduction to Distributed GIS


Published on

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Getting your Data Out There:An Introduction to Distributed GIS
    John ReiserRowan University
  • 2. Instructor
    John Reiser
    Rowan University
    John is the Campus GIS Specialist for Rowan University. At Rowan, he manages the campus GIS infrastructure, develops GIS applications for campus and project use, guides curriculum and teaches GIS courses. In his spare time, he continues to be a GIS geek, developing web-based GIS projects, GPS software and contributes to the open source GIS community.
  • 3. Workshop Description
    This workshop is designed for those that are looking for an introduction to Internet-enabled GIS and Cloud-based GIS services. Distributed GIS relies on remote services to render maps, convert data formats, or perform geoprocessing tasks. The workshop will begin with an overview of the current options available to those looking to use and implement distributed GIS. We will then explore freely available web services from a multitude of providers. Live demonstrations of the services will be incorporated into the workshop. A discussion of implementing distributed GIS within your organization will conclude the workshop.
  • 4. Workshop Objectives
    Upon completion of the workshop, students will have a greater understanding of:
    The newest GIS file formats and services
    Preparing your data for distribution
    OGC Web Service standards
    Available GIS servers
    GIS-friendly content distribution networks
  • 5. Workshop Outline
    Section 1 – Introducing Distributed GIS
    Section 2 – Is Distributed GIS right for you?
    Section 3 – Delivering your data as KML
    Section 4 – Your first Web Map
    Section 5 – Developing your GIS Server
    Section 6 – Putting the pieces together
    Section 7 – Final Thoughts
  • 6. Workshop Materials
    While the workshop will not give you “hands on” experience, links to demos and code samples will be provided at:
  • 7. Section 1Introducing Distributed GIS
  • 8. What exactly is Distributed GIS?
    Distributed GIS is a system where components of a GIS are distributed amongst computers on a LAN or the Internet.
    For this workshop, we will be exploring D-GIS technology that allows you to offer your GIS data as a public-facing, Internet-based service.
    Distributed GIS services should allow members of the public access to your data without an interruption of your internal workflow.
    Distributed GIS can also provide geoprocessing tasks performed on your data to the public.
  • 9. Open Standards
    For these separate pieces to work together, they must share a common language.
    Several common languages that are open standards supported by the Open Geospatial Consortium.
    You are not limited to the open standards for internal use; many systems allow for exporting or services that produce open formats.
  • 10. Who uses Distributed GIS?
    Today, almost everyone has used a form of Distributed GIS, from generating driving directions from Google Maps to viewing aerial photography from a remote server.
    The days of ordering 15 DVDs of base imagery are nearly gone.
    The Internet has drastically changed the way we manage, process and present data.
  • 11. What types of Distributed GIS are there?
    Using KML to distribute basic data to users through a virtual globe.
    Providing your data in a “slippy” web map.
    Providing web maps, data services and geoprocessing capabilities through a dedicated GIS server or servers.
  • 12. What’s not Distributed GIS?
    Offering data burned to a CD or DVD.
    Providing GIS data for download.
    Don’t fall into this trap with KML data! The real power of KML comes from pulling in many data sources. It shouldn’t act as just another data format.
    Providing PDFs, other static maps on the Web.
    GeoPDF, while useful, is not Distributed GIS.
  • 13. Section 2Is Distributed GIS right for you?
  • 14. Is Distributed GIS right for me?
    Every situation is different. If your project would benefit from any of the following, you should consider Distributed GIS:
    • Your users are spread out across offices.
    • 15. Your data is updated frequently.
    • 16. Your data is often requested by the public.
    • 17. Many of your clients are not familiar with GIS.
    • 18. You currently use or have used ArcIMS or another Internet Mapping Service.
  • Public and Private Distributed GIS
    All of the examples in the workshop today will deal with delivering data and maps to the public.
    You could just as easily cater your system to a specific group, or to only a handful of authorized users.
    We will not be discussing how to restrict access to your Distributed GIS system.
  • 19. What type of Distributed GISis right for me?
    Want users to remix?Deliver it in KML, providing the data in the easiest form to manipulate.
    Need to paint a picture?Develop a web map with your cartographic styling, framing the data as you want it to be seen.
    Recreating a desktop GIS on the web?Deploy services using GIS server software.
  • 20. What’s right for you?
    The correct answer is: depends on the project.
    Use the technology that serves your users best.
    Many alternatives to provide the services you choose, varying in platform, features and cost.
    Let’s take a look at a few of our options.
  • 21. KML – it’s not just Google Earth
    Keyhole Markup Language is the file format developed for the Keyhole Earth Browser, predecessor to Google Earth.
    After purchasing Keyhole in 2004, Google greatly expanded KML’s capabilities.
    In 2008, the OGC declared KML 2.2 to be an open standard for geographic data.
    Many software packages outside of Google Earth support KML data.
  • 22. Working with KML
    Other than Google Earth:
    ArcGIS Explorer
    ArcGIS Desktop/Server
    Google Maps
    Several GPS utilities
    Many open source projects
  • 23. Using KML
    KML is a subset of XML, thus text-editable.
    KML stores vector data along with symbology.
    KML can act as a wrapper for WMS services.
    Network links allow you to push fresh data out to users.
    It’s a lightweight data format for export and distribution. It’s not going to be your native data format.
  • 24. How KML is used
    Because KML is viewed in a virtual globe, your data will be in your users’ control.
    They may not be viewing the same data as others, as other data and base imagery may be in use.
    Complicated or complex data may not be suited for KML that will be presented to a general audience.
  • 25. Web Maps – What’s ArcIMS?
    Many of you might be familiar with ArcIMS. For many years, ArcIMS was the way to deliver interactive maps across the web.
    Google introduced Maps in 2004, completely changing the way we think about mapping on the Web.
    Introduced the “slippy” map interface, where pre-rendered tiles are displayed in a draggable matrix at set zoom levels.
  • 26. The Slippy Map Interface
    Smooth, intuitive panning creates a welcoming user experience.
    Pre-rendered tiles reduce processing overhead, while increasing storage needs.
    Storage is relatively cheap, compared to upgrading the processing power of a server.
    The experience is what is important and long wait times negatively impact that experience.
    It has become the standard for web maps.
  • 27. Creating your own Web Map
    There are several methods for creating Web Maps, however most require your own server and software.
    Arc2Earth allows you to generate the tiles needed from ArcGIS, and then upload them to a server.
  • 28. Using Web Maps
    Providing a slippy style web map can help your organization provide users with a simple, easy-to-use interactive web map.
    Web maps can help acclimate users to your data without requiring a GIS application.
    Users looking for basic maps and information may turn to your map instead of a desktop GIS.
    Greater control over the user experience.
  • 29. How Web Maps will be used
    While the ability to manipulate the data without your knowledge is not as easy as it is with KML, your maps by their very nature will be shared across the Internet.
    Make sure your map is clearly depicting what you want to show and that any explanatory narrative is clear and concise.
    It will be hosted on your website, so it will be treated as a definitive source, on par with the actual GIS data behind the map.
  • 30. Hosting Your Own Server
    Your own GIS server could produce KML and web maps like the previous examples, but it can also do much more.
    Act as a front-end to your GIS database.
    Provide additional web services, such as geocoding and geoprocessing.
    Greater control over your clients’ experience.
    Requires hardware and customization.
  • 31. Your GIS Server
    ArcGIS Server is probably the most robust offering out there today, but very costly.
    Roll your own using Open Source software.
  • 32. Using your GIS Server
    The server can feed data to both your KML files and hosted Web Maps.
    The server can manage your data and provide snapshot “views” to groups of users.
    Geoprocessing can be executed on the server, removing the processing burden on local workstations.
    Can support to complement data offerings and common tasks.
  • 33. How your GIS Server will be used
    Once the server is up and running, people will use it and expect it to be there when needed.
    Conversely, if you don’t make it easy to use, users will reject it and revert back to previous workflows (calling you, begging for maps/info)
    You will want to plan for redundancy, security testing, maintaining quality of service, etc.
    Plan big and plan to scale services as needed.
  • 34. Section 3Delivering your data as KML
  • 35. Your Data in KML
    If you have not yet worked with KML, you will quickly find that it is a great format for distributing data, as it includes symbology, can support raster and vector data, and can be updated over the network.
    There is a small learning curve for your users; many will be familiar with the format already.
    However, there are some issues to consider before you migrate your data to KML.
  • 36. KML – Technical Issues
    While it supports many features, not all features are as robust as in a traditional GIS and support varies among the KML viewers.
    Symbology is limited to outlines and fill for polygon features. Hatching and line styles are not supported.
    Large features (>10K vertices) are not rendered properly.
    Network links do not always behave.
  • 37. KML – Usability Issues
    While a desktop 3D earth browser is impressive, it’s not the right solution for all data types.
    If the 3D browser helps people navigate your data, all the better. If they end up getting lost, it’s not very useful.
    Consider creating camera viewpoints or tours, similar to bookmarks in ArcMap Documents.
    You can also include political boundaries in your document, allowing users to zoom to an area.
  • 38. Exporting your data to KML
    There are many options for converting your existing GIS data to KML:
    ArcGIS Layers to KML: export from ArcMap.
    Online conversion services: upload a shapefile, download a KML file.
    Command line scripts: GDAL/OGR, Python scripts.
    3rd party extensions to ArcGIS
  • 39. Workshop Examples
    For the purpose of this workshop, the examples assume that you have access to ArcGIS 9.3 or later.
    Unless specified otherwise, the examples reflect using a typical Windows XP, ArcView-level GIS configuration.
  • 40. Getting Started with KML
    For this first example, we will be working with the municipalities of Atlantic County.
    We will add the layer to ArcMap, then use the Layer to KML tool to export the data.
    We will view the data in Google Earth to see how the data is modified in the conversion.
  • 41. Atlantic County Municipalities
  • 42. Export Layer to KML
  • 43. Municipality Data in Google Earth
  • 44. Initial Observations
    The exported data appears in Google Earth at the proper location. Note that not all export tools will reproject to WGS84 automatically.
    The symbology is preserved from ArcGIS to Google Earth.
    The exported file is a .KMZ, which is a ZIP-compressed file format.
    Clicking on the individual polygons does not cause anything to occur. Google Earth does allow for clickable polygons.
  • 45. Interactive KML
    Let’s add some basic functionality to our KML data: clicking on a municipality in Google Earth will cause a balloon to pop up with attribute information.
    This is enabled through a Layer Properties tab introduced in ArcGIS 9.3 – HTML popup.
    Along with the hyperlink functionality, the HTML popup will be exported to Google Earth.
  • 46. The HTML Popup Window
  • 47. Configuring the HTML Popup
    We will use the most basic HTML popup, a table with attribute information.
    We can switch field visibility off in the Fields tab if we do not want select fields in the popup.
    Advanced formatting is available through the use of XSLT stylesheets.
  • 48. Popup in Action
  • 49. Popups in Google Earth
  • 50. Symbology Shortcomings
    While configuring the HTML Popup, the symbology was changed to a dashed outline.
    The dashed outline did not get carried over to the KML symbology, although the color and line weight did.
    Keep in mind that complex data may need to be generalized to work with the limited cartographic capabilities of earth browsers.
  • 51. Exporting Raster Data
    Similar to the process used to export the vector municipality data to Google Earth, we can export raster data to KML.
    Define a custom extent to clip the exported raster to a bounding box.
    ArcGIS takes some liberties with resampling, so you may need to tweak settings to get the data to appear as desired.
  • 52. Raster data in Google Earth
  • 53. Export Multiple Layers
    KML supports a mix of geometry types within the same KML file.
    ArcGIS can export multiple layers of mixed type (point, line, polygon, raster, etc) as one KML document.
    We can use the Map to KML tool to export all of the layers to a KML file.
  • 54. Multi-layer KML in Google Earth
  • 55. Using Web Services with KML
    KML has the ability to access web services natively. Most earth browsers support this capability.
    KML can access WMS services and bring in WMS images based on the current extent.
    KML supports network links, automatically downloading remote KML/KMZ files and adding them to the current list of layers.
  • 56. Accessing WMS
    Unfortunately, WMS layers added to ArcGIS do not get exported to KML. Luckily, it’s very easy to add WMS layers within Google Earth.
    Save the Image Overlay (Google’s KML feature for supporting WMS) as its own KML file, so it is easy to add to other KML files.
  • 57. WMS in Google Earth
  • 58. Notes on Image Overlays
    By default, Google specifies that the image overlay only covers 75% of the current view extent. You will likely want to change this to a value between 1 and 1.25.
    The default refresh settings are to wait 4 seconds before requesting new WMS imagery. You may want to alter this for your services.
  • 59. Network Overlays
    “If my users are already downloading the KML from my website, why do I need this?”
    When they download the data, they will then need to redownload to receive any updates.
    The network link will cause their Earth Browser to load the latest data on startup.
    Network link could point to a static KML or to the KML services provided by ArcGIS Server.
  • 60. Simple Network Example
    We will upload our municipalities KML to a website and note the URL.
    Use Google Earth to add a new Network Link to your earth browser.
    Save the Network Link to its own KML file.
    Note the small size of the Network Link file.
    The data will be pulled in as needed.
  • 61. Serving KML Online
    While you could easily post a KML to your website, consider some alternative hosting options.
    GeoCommons, the open web mapping platform, can host your KML and a web map.
    Amazon Web Services can store your KML files, allowing the use of the Amazon network to distribute larger files.
    Depends on costs and service needs.
  • 62. Complex Network Links
    Network links can be configured to load based on the current extent.
    Load balance or use a CDN for larger datasets.
    Remember, your user will need to download the data every time, so generalized or simple data works best.
  • 63. KML Review
    Provides user with an snapshot of your data.
    Open standard, readable by many programs.
    Can mix vector, raster and web services.
    Includes symbology information.
    Network links ensure users have latest data.
    Minimally interactive; view but not explore.
    Easy to produce and distribute.
  • 64. Section 4Your First Web Map
  • 65. Your First Web Map
    Providing a basic web map, similar to Google Maps, has become a simple task.
    The ability to generate tiles, the rendered GIS data presented to end users, is possible through many different software packages.
    The heavy lifting will come as you move your map from a general viewer to a specific data interface.
  • 66. Basis of the Technology
    Previous methods for generating maps on the Internet were in two forms:
    Render requests for any map extent and scale.
    Render a few static maps; provide links between.
    Google Maps changed this dynamic, as it publicized the “slippy map” concept.
    Slippy Maps are composed of square tiles rendered into a seamless map at static scales.
  • 67. Spherical Mercator
    A new projection was developed to make web mapping easier: Spherical Mercator.
    A Mercator project based on a spherical datum.
    Not for high-precision work. Not a problem because no one should be using web maps in place of surveys.
  • 68. Spherical Mercator
    Projection creates a square Earth, which can then be divided into square map tiles.
    Many GIS platforms now support this projection natively.
  • 69. Map Framework
    Creating a Slippy Map requires a map framework, such as OpenLayers (JS) or Yahoo! Maps (Flash)
    Google offers both JS and Flash APIs.
    Your map framework will request the tiles from a GIS server or a tile cache.
    A tile cache is simply a set of static map images in a standard directory structure.
  • 70. Tile Cache
    A tile cache can greatly improve the responsiveness of your web map.
    A GIS Server requires multiple connections to a DB or disk to render a map tile.
    A tile cache does not need active connections to your GIS data. It is “dumb” storage.
    While the disk storage requirements increase, the latency your users experience decreases.
  • 71. Cache Creation
    There are two predominate methods for populating a tile cache with map tiles.
    Direct: using a desktop computer to generate the tiles from a GIS, storing them locally or remotely.
    Intermediary: using middle-man software that passes on requests to a GIS server while creating and managing the cache.
    We will first look at the direct method using Arc2Earth.
  • 72. Arc2Earth
    Initially created in 2006 by SpatialDataLogic, Arc2Earth was a tool for bringing GIS data to Google Earth.
    It has since evolved into a GIS swiss army knife, allowing you to move your GIS data into many new distributed formats.
    Can supplement your KML as well as your map tile production.
  • 73. Getting Started with Arc2Earth
    We will explore Arc2Earth’s tile generating capabilities using Pinelands data for Atlantic County.
    We will prepare our data in ArcMap, then use Arc2Earth to generate the tiles and basic web map based on our ArcMap settings.
  • 74. Atlantic County Pinelands Data
  • 75. Arc2Earth Interface
  • 76. General Web Map Settings
  • 77. Items to Consider
    You may want to experiment with anti-aliasing, as it may improve the legibility and crispness of your maps.
    Transparency can be implemented within the tiles (alpha-channel PNGs) or in Javascript.
    Remember to include metadata for your maps.
  • 78. Generating Zoom Levels
  • 79. Number of Levels
    You want to render only the levels needed for your application.
    Number of tiles quadruple as the zoom level increases.
    Limit the zoom levels of your map to what is appropriate.
    Specify the tile ordering scheme.
  • 80. Storing Your Tiles
    Arc2Earth will generate your tiles, but you must specify how they will be stored.
    Local copy is generated for a local cache.
    Upload to a cloud-based hosting service.
  • 81. Hosting Your Tiles in the Cloud
    Arc2Earth can save your tiles locally, allowing you to manually set up your tile cache.
    Can also export into:
    Amazon S3 &
    Arc2Earth managed cloud-hosting using Google.
  • 82. Benefits of Cloud Hosting
    Relying on a third-party service for hosting frees you from managing a server.
    Cloud hosting providers have a much larger infrastructure and capacity.
    Pre-built viewers remove the need for custom configuration.
  • 83. Our data on
  • 84. Hosted with provides a framework for basic web map functionality.
    Service provides base map data that you would otherwise need to manage or license.
    Framework for desktop and mobile access.
  • 85. Disadvantages of Cloud Hosting
    If you already have some server infrastructure in place and your expected traffic is low, you may want to consider hosting in-house.
    Included frameworks are not as flexible or customizable compared to hosted services.
    Security of data – facilities & infrastructure
    Purchasing outside software/services can be difficult in government.
  • 86. Final Thoughts on Arc2Earth
    Easiest way to build tiles without a dedicated server. No need to manage server infrastructure as you rely on Amazon/Google.
    Very useful for generating KML files that may not export well using ESRI’s built-in tool.
    Can create SLD files for use on your own open source GIS server.
    Costs money for additional features; closed source.
  • 87. Section 5Developing Your GIS Server
  • 88. Developing your GIS Server
    A GIS Server can be relatively simple, providing file or database storage while serving data through the intranet or Web.
    A GIS Server can be run on one workstation or on a cluster of servers.
    Your ultimate configuration depends on your needs, budget, and level of know-how.
  • 89. Assumptions Made
    While we will discuss GIS Servers in general terms, we will focus on a few software offerings.
    The software in this workshop is open source, feature rich, well-documented, and relatively straightforward to install and manage.
    While it may not be the right fit for you, what we discuss today you should be able to try at home with your time being the only cost.
  • 90. Technologies Used
    GeoServerA Java-based OGC-compliant, WFS-T capable GIS Server. Handles data and map rendering.
    TileCache & OpenLayersEnables you to host your own “slippy” maps.
    PostgreSQL & PostGISOpen source GIS database technology. Compatible with ArcSDE.
  • 91. Technologies Used
    GeoServer, TileCache, and PostgreSQL can be switched out for similar software.
    However, this configuration works with minimal tweaking required.
    All are open source and freely available.
    All run on Linux, Mac OS X and Windows.
    Each has their own dedicated support community and options for purchased support.
  • 92. GeoServer
    Based on the GeoTools Java toolkit.
    Standards compliant & arguably the easiest server platform to incorporate into other GIS systems and products.
    Java Servlet technology; can run in a container or standalone.
    Simple to install (binaries available) and manage. Web-based user interface.
  • 93.
  • 94. Open Source Support
    Before we proceed, it should be stated that open source software is not “fix it yourself.”
    Many organization are hesitant to use open source for “enterprise” level applications due to the perceived lack of support.
    OpenGeo is the developer behind Geoserver.
    While open source, OpenGeo provides technical support and custom development to users of GeoServer.
  • 95.
  • 96. GeoServer Configuration
    Most features managed through a web interface.
    GeoServer is undoubtedly one of the easiest GIS servers to deploy.
    Upload data to server, then point-and-click configuration.
    Symbology defined using Styled Layer Descriptors (SLD).
  • 97. GeoServer Installation
    Deploy as WAR from within a servlet container
    Install stand-alone.
    May need to install some dependencies for additional features.
  • 98. Post-Install
    Log in to your server via a web interface.
    If installing on your own Windows desktop, it’s simply http://localhost:8080/geoserver/web
    From there, you can add data to the server, configure layers to serve, access service capabilities and much more.
  • 99. Your Installation Homepage
  • 100. List of Layers Available
  • 101. Styled Layer Descriptors
    SLDs are used to define symbology in GeoServer and in other open source projects.
    Is an OGC open format. Subset of WMS.
    You can define several SLDs to be used with a data layer, and give the option for the user to switch between them.
    Edit SLDs from GeoServer web interface.
  • 102. GeoServer’s Built-in SLD Editor
  • 103. Yes, SLDs are XML
    SLDs are very powerful, but not user-friendly.
    A GUI editor for SLDs within GeoServer is under development.
    Part of the GeoExt project for web GIS interfaces in JavaScript.
  • 104. SLD Cookbook
    GeoServer’s documentation covers frequently-desired cartographic effects implemented with SLDs.
    Also available is an SLD reference, that includes notes on vendor-specific (GeoServer only) features.
  • 105. Now What?
    Now that you have your data in your server, what can you do with it?
    Serve the data to users via WMS or WFS, allowing ArcGIS Desktop users access.
    Serve the data to users through a website.
  • 106. ArcGIS WMS & WFS Access
    ArcGIS allows for direct access to WMS services.
    Under “GIS Servers” select Add New WMS
    Enter the URL to your server. Use the WMS link on the homepage.
    NJ’s aerial photography is available through WMS.
  • 107. WMS Layers in ArcMap
  • 108. Getting Started with Web Maps
    On your organization’s website, you can create a page that uses the OpenLayers JavaScript library to create a slippy map on a page of your choosing.
    You can also install TileCache to speed up the rendering of the slippy map.
    Warning: some programming ahead!
  • 109. OpenLayers
    A JavaScript library for implementing slippy-style web maps.
    Originally developed by MetaCarta, then became an OSGeo project.
    Open source and no cost.
    Can interface with WMS services as well as ArcGIS Server.
  • 110. Why not Google Maps?
    While the Google Maps API seems ubiquitous, there are limitations that may impact your use.
    While free at first, Google will charge for high-traffic sites using its API.
    Version 2 is deprecated and they are going to turn it off eventually.
    Cannot be used on your intranet. All pages using the API must be public.
  • 111. Using OpenLayers
    OpenLayers provides the same basic functionality as Google Maps.
    Additional functionality such as in-map editing of vector features, easy configuration of custom projections, etc.
    If you’re familiar with the Google Maps API, OpenLayers should be an easy transition.
    OpenLayers does not come with base maps; provide your own or use Google, Bing, Yahoo!
  • 112. Entirely Your Own
    While you may want to use Google/Bing as a base map, using their APIs may restrict you from tailoring the application to your users.
    You can host your own copy of OpenLayers and modify it as needed
    From the map functionality through to the user interface, the API is customizable.
  • 113. OpenLayers Examples
  • 114. Starting from Example
    One of the OpenLayers examples is a basic web map using a WMS service for the map tiles.
    We can copy that example to our own website and replace the example WMS URL with our own.
    Change the starting coordinates and zoom level and we’re off!
  • 115. Example from OpenLayers
  • 116. Changing the Example
  • 117. Additional Functionality
    OpenLayers or Google Maps are the frameworks for developing custom interactions with the maps and data.
    OpenLayers even has code for manipulating vector data; modifying vertices in a feature.
    Additional functionality is performed server side, such as spatial or network analysis.
    Your server must be able to support those functions.
  • 118. TileCache
  • 119. TileCache
    Once your web mapping application is nearing release, you should consider taking steps to optimize your users’ experience.
    Caching map tiles will improve overall rendering speeds.
    Increased storage costs, but reduced CPU & DB demands as you are no longer rendering repeatedly from GIS data.
  • 120. Intermediary
    TileCache sits between your interface and your rendering engine.
    It handles WMS requests, so your interface can continue to use the same request methods.
    WMS requests that have not been cached are passed along to the rendering engine, then stored when returned to the interface.
    Caches can be pre-rendered or rendered as needed.
  • 121. Caching On-The-Fly
    Web Map
    GIS Server
    Map Tile does not exist:
    Rendered then stored.
    Web Map
    GIS Server
    Map Tile does exist:
    Pre-rendered tile returned.
  • 122. Configuring TileCache
    TileCache is written in Python and can run on most modern platforms with minimal configuration.
    Define layers to be cached using a text-based configuration file.
    WMS Service
    Configured for use in a Google-style mashup.
  • 123. Pieces In Place
    We now have the pieces to develop our own Distributed GIS system.
    GeoServer– rendering and processing our GIS data
    OpenLayers –providing a map interface in a web browser
    TileCache –optimizing delivery of map data
  • 124. Section 6Putting The Pieces Together
  • 125. Your Distributed GIS
    We have covered the various options available to move your data into a Distributed GIS.
    Not every tool will work for you, but one or more may be a part of your Distributed GIS.
    Let’s take a look at a few examples of Distributed GIS systems and see how they are implemented.
  • 126. National Weather Service
    The NWS uses KML to distribute weather updates, advisories and radar/satellite imagery.
    The KML files use network links, allowing for automatic refreshing of the weather data.
    Weather data is always changing and the interface has to suit a general audience.
  • 127. Rowan’s Land Change Viewer
    Built as a part of the ongoing “Changing Landscapes of the Garden State” research jointly conducted by Rowan & Rutgers.
    Series of animated web maps showing changes in land use in New Jersey over 21 years.
    Developed using a multiple Distributed GIS technologies and distributed across the Web.
  • 128. Distributed Land Change Viewer
  • 129. Distributed Land Change Viewer
    Land Change Viewer
    Google MapsBase Maps
    Bing MapsBird’s Eye
    Amazon S3
  • 130. Land Change Viewer
    The Land Change Viewer relies on a mix of hosted and cloud-based services.
    GeoServer was used to render the Land Use data for the entire state.
    TileCache generated local and S3-based map tile caches for the interactive maps.
    Amazon S3 was used to store the production map tiles & CloudFront to distribute.
  • 131. Tile Creation
    By using CloudFront to distribute the map tiles using Amazon’s infrastructure, we needed to pre-build our cache.
    Map tiles were limited to zoom level 8 (all of NJ) through 15 (small town/neighborhood scale)
    Tile rendering had to begin well in advance of the release date.
  • 132. Tile Math
    For the extent of NJ, zoom levels 8-15, approximately 60,000 tiles needed to be created.
    Each animation frame was one set of tiles.
    Approximately 1.5 million tiles had to be generated.
  • 133. Land Change Viewer
    After testing other possible implementation strategies, we selected a JS-based web map.
    Authoring the JS, configuring the server and rendering the tiles took about 4 weeks.
    Distributed GIS allows the user interface to be quick and responsive.
    More on the NJ Land Change Viewer at the MAC URISA Interactive Expo.
  • 134. Section 7Final Thoughts
  • 135. Just the Beginning…
    While we covered many different technologies and topics, this is just a preview of the new direction GIS is heading.
    Distributed GIS has been around for several years, but it has never been as easy or available to smaller firms and groups as it is today.
  • 136. Implementing Your GIS
    While the goals of your individual organizations vary, informing the public is likely a common goal.
    A Distributed GIS system can help you in delivering your data while also making it easier for the public to access and understand.
    The key is finding the right mix of technology to achieve that goal.
  • 137. Available Technology
    ArcGIS Server
    Google AppEngine
    FME 2010
    Amazon AWS
    ERDAS Apollo
    Windows Azure
    Change Components To Suit Your Needs
    Bing Maps
    Yahoo! Maps
    Google Maps
    ESRI JS & Flex
    Map TileCreation
  • 138. Community Support
    While not all of the open source packages have technical support, all have a community of users and developers to help with a project.
    Get involved with your platform’s community.
    Provide assistance to others.
    Show off your work.
    The community drives interest in the technology and sets the course for future development.
  • 139. After the Workshop
    Try some of the different applications out with your own data. Many of the applications are free.
    Start a discussion in your organization on how you can better distribute your data using Distributed GIS technology.
  • 140. Thank You
    I hope you enjoyed this discussion of Distributed GIS.
    Questions or comments:John Reiserjohn@njgeo.org (twitter)856-347-0047