seth peery senior gis architect virginia tech geospatial information sciences
Skip this Video
Download Presentation
Web Mapping

Loading in 2 Seconds...

play fullscreen
1 / 23

Web Mapping - PowerPoint PPT Presentation

  • Uploaded on

Seth Peery , Senior GIS Architect Virginia Tech Geospatial Information Sciences. Web Mapping. FDI April 16, 2012. Objective: Understand how web maps work, what goes on behind the scenes, and how to actually deploy them in production IT environments

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about ' Web Mapping' - nishi

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
seth peery senior gis architect virginia tech geospatial information sciences
Seth Peery, Senior GIS Architect

Virginia Tech Geospatial Information Sciences

Web Mapping


April 16, 2012

Objective: Understand how web maps work, what goes on behind the scenes, and how to actually deploy them in production IT environments
  • Common architectural features of web mapping applications
  • Web Mapping Workflows
  • Examples from Google Maps and ArcGIS Server
web mapping vs supporting gis components
Web Mapping vs. Supporting GIS components

Web Mapping

You are here.


Data Management

software architecture
Software Architecture
  • This layer consists of web content that’s not the web application – look and feel, formatting, etc.
  • This layer addresses the functionality of your application – e.g., what happens when the user clicks?
  • This layer concerns the transport of data from its source format, with the appropriate presentation., to the web application.
  • This layer concerns map symbology. It is more of a workflow item than a subsystem – it may be handled in the source data or the map svc.

Everything from here down is data

functional components of all web mapping applications
Functional Components ofAll Web Mapping Applications
  • Source data
  • Data accessible to the web app
    • Basemap (increasingly coming from third party services)
    • Thematic layers (your data)
  • Representation/symbology of the data
  • Web service to return thematic data
  • Web map object and application logic
  • Web application container/interface for the map (presentation)
arcgis server in the scheme of things
ArcGIS Server in the Scheme of Things

At web applications tier, we can choose between the {Java | .NET} ADF, the JavaScript API, Flex API, Silverlight API

SOC/SOM (GIS Server Components) respond to requests for maps and return data or images (e.g., MapService, WMS)

ArcGIS Server doesn\'t care about anything below this point, so you can plug and play with different supported data sources... filesystem vs ArcSDE, etc.

arcgis server deployment workflow
ArcGIS Server Deployment Workflow

ESRI says “Author, Publish, Use”… the details are a bit more complex!

  • Identify source data
  • Identify server platform
  • Move source data to a location visible to the server (e.g., ArcSDE, file GDB on server)
  • Make an MXD with data source references to “production” copy of data
  • Upload MXD to server or ensure it is visible in a shared location
  • Author a Map Service based on the MXD, set capabilities
  • Create a web application that consumes the service
    • Web API (Flex/SilverLight/JavaScript)
    • Web ADF (Deprecated)
  • Customize web application
  • Publish to Production environment
esri developer resources
ESRI Developer Resources
  • Main ArcGIS Server Resource Center:
  • Flex API Reference:
  • JavaScript API Reference:
initial setup
Initial Setup
  • Assemble data, make a map and make sure the server can access it
rest services directory
REST Services Directory
  • The map we created in ArcMap is now available as a REST endpoint and can be accessed via the REST services directory by a web mapping application.

rest preview
REST preview
  • Web Services have no UI – they’re meant to be used by computer programs
  • The REST services directory provides a minimal preview web application for human viewers
  • We’re not done yet – this is not a “real” web application.

sample flex viewer
Sample Flex Viewer
  • SFV is a configurable web mapping application from
  • The app is a Flash-based viewer that can be modified (to an extent) via a set of XML files

flex viewer example
Flex Viewer Example

flexviewer source
FlexViewer Source

arcgis server javascript viewer example blacksburg rcl over esri terrain
ArcGIS Server JavaScript Viewer Example: Blacksburg RCL over ESRI terrain

arcgis server javascript viewer example 2 google maps extension
ArcGIS Server JavaScript Viewer Example 2: Google Maps Extension

google maps deployment workflow
Google Maps Deployment Workflow
  • No need to worry about the basemap!
  • Identify a web server (no special capabilities needed)
  • For Gmaps v2, obtain an API key (omit in APIv3)
  • Identify source data, copy to server (or load into DB)
  • Write page logic to render map and symbology
  • Design web front-end
  • Google Maps API Reference is found at
google maps examples
Google Maps Examples
  • For all the examples below, refer to the ViewSource for code comments, which provide detailed explanation of each feature.
  • Basic Google Map of VT Campus
  • Basic Map with place name search
  • All of the above, plus VT Buildings
  • All of the above, plus icon styling
contact information
Contact Information

Seth Peery

Senior GIS Architect, Enterprise GIS

Virginia Tech Geospatial Information Sciences

2060 Torgersen Hall (0197) Blacksburg, VA 24061

(540) 231-2178

[email protected]