This is from Randy Kim’s presentation at the USG World Wind Workshop.  As I was writing my wrap up, I decided that it needed to be a post in it’s own right just because of the value of the information if you want to serve your own data for World Wind Java.  I will also be supplementing this post with information from Lado Garakanidze.

Why would you want to host your own servers and data?  Because it is part of the complete package.

You are also dealing with large volumes of data such as CADRG and DTED. This is also data that has been optimized for your users computers and supports exporting of raw elevation data.

Getting the WWJava WMS server is as easy as downloading from here.  The WWJava WMS uses Java, GDAL (for image processing) and Squid (for caching data).

Now that you know why and how, you need something to serve it on.  What do you need?  You need something with lots of storage space, such as a NAS server.

What is the typical data set for a MS Server setup?  Blue Marble NG, US and Global elevation, LandSat i3 (These three come to about three Terabytes in size) other data coming soon includes the NAIP imagery.

That concludes the Randy Kim portion, now for some detailed information from Lado Garakanidze.

NASA WorldWind WMS server configuration

This post details the way to configure your WWJava WMS server.  Current implementation of the NASA WorldWind WMS Server v0.6 is able to serve imagery sets (BMNG, i3 LANDSAT, NITF/RPF/CADRG/CIB) and elevations (SRTM 30, SRTM 3 v2 and v4.1, USGS NED, DTED 0/1/2, and a pyramid of BIL files created by WorldWind client).

How to configure DTED elevations in the WorldWind WMS server

This post details how to configure DTED elevation data for serving and the changes needed for the WWJava client.

How to configure SQUID to cache WMS server responses

Configuration changes needed for Squid Cache to work with WWJava WMS.