This article was previously published on GeoChalkboard, and has been reproduced here with permission. It is based on a sub-section of the he Geospatial Training Services course Google Earth for ArcGIS users.

Introduction

A frequently overlooked capability of Google Earth is its ability to cache data on your local computer and therefore allow for field based visualizations of GIS data. In a typical office setting, Google Earth uses streaming imagery over a high speed Internet connection to provide you with images and vector datasets. However, many GIS users need to be able to visualize Google Earth imagery and their own internal datasets while in the field where high speed connections to the Internet are not available or impractical. In this article we are going to take a look at how you can cache Google imagery and vector datasets to your laptop for offline viewing in the field. In addition, we are also going to take a brief look at a number of tools that you can use to integrate your existing vector ArcGIS datasets with this cached data.

This article is the final part of a five part article that we have been publishing this week. The article was previously published on GeoChalkboard, and has been reproduced here with permission. It is based on course material published by Geospatial Training Services.

Introduction

In the fifth and final installment of our series on building a wildfire mashup with ArcGIS Server and Google Maps we will access the Drive Time geo-processing task provided on the ESRI Sample Server to create drive time polygons for an address that has been selected on the grid.

This article is part three of a five part article that was previously published on GeoChalkboard, and has been reproduced here with permission. It is based on course material published by Geospatial Training Services. We will be publishing all five parts this week.

In the second part of this series on building mashup applications with ArcGIS Server and Google Maps, we built on what we accomplished in the first post by adding the polygon that defines the perimeter of the Witch fire to the Google Map that we developed in the first post. The perimeter of the Witch fire was pulled from the USGS_FirePerimeterAlt_SoCal_2D map service on an ArcGIS Server instance hosted by ESRI. In this, the third part in our series, we will add in the markers corresponding the residences that were burned in the Witch Fire.

If you’d like to construct your own instance of this application please feel free to do so. You’ll need to read the first post for details on where you can download the supporting files.