This site is the home for the WorldWind Explorer web app, the WorldWindJS library--a community edition of NASA Web WorldWind, and the WorldWind Java-Community Edition SDK--a fork of NASA WorldWind Java, plus other WorldWind programming resources.
Table of Contents
- TOC {:toc}
The Explorer is an HTML5/JavaScript geo-browser powered by WorldWindJS and the Knockout and Bootstrap libraries. It is implemented as a single-page web application (SPA) using JQuery to dynamically load content.
The WorldWind Explorer is a geospatial web application for visualizing Earth. It uses the WorldWindJS library (forked from the NASA WebWorldWind SDK) to display a 3D globe with terrain and imagery as well as 2D maps. It displays the sunrise and sunset times and solar angles for any point on the earth. It shows the terrain's aspect and slope for any location. It features user-defined markers and point weather forecasts. It has a search feature to find places.
- Explorer User and Developer Guides — How to use or customize the Explorer.
- Explorer Issue Tracker — Provide feedback and file bug reports.
- Explorer Source Code — If you are a developer, pull requests are welcomed.
WorldWindJS is a fork of the popular Web WorldWind library from NASA (with contributions from ESA). This fork provides a release channel for builds based on the latest fixes and features from the WebWorldWind develop branch integrated with several enhancements from the WorldWind community. WorldWindJS is a drop-in replacement for the NASA Web WorldWind library.
WorldWindJS releases can be downloaded from GitHub or from npm. Of course, you can fork or clone this project and build the library yourself using the instructions in the README.
Do you want to start developing right away?
- Browse the source code for the web-app-template
- View/edit a completed app in JSFiddle
Are you interested in building a WorldWindJS geo-browser or embedding a globe in a web page using React? Checkout these resources:
- worldwind-react-globe - A Globe component that encapsulates WorldWindJS
- worldwind-react-globe-bs4 - Bootstrap UI components for the Globe component
- worldwind-react-app - An example geo-browser web app
Here some examples of applications built with WorldWindJS:
- WorldWind Explorer - A feature rich geo-browser built with Bootstrap and KnockoutJS.
- Wildfire Management Tools - An Explorer-based geo-browser for predicting the potential behavior of wildfire.
- WorldWind React Demo - An example geo-browser built with React.
This tutorial shows you how to build a WorldWindJS web app using Bootstrap and Knockout. You will build a feature-rich, responsive, customizable web app ready to be deployed to your site. This tutorial demonstrates:
- Initializing WorldWindJS with 3D globes and/or 2D maps
- Configuring and managing layers and settings
- Place name searches and geocoding
- Creating placemarks
- Going to locations
- Multi-globe support
This is what we will build:
<script async src="//jsfiddle.net/emxsys/e0a2z1km/embed/result/"></script>{:.no_toc}
Let's begin!
- Lesson 1: HTML with Bootstrap
- Lesson 2: WorldWind Globe
- Lesson 3: Layer Management with Knockout
- Lesson 4: Place Search and Geocoding
Here is a feature-rich worldwind-web-app template for quickly building a web app using the WorldWindJS library with Bootstrap and KnockoutJS. Simply fork/clone the project and publish to gh-pages.
-
Sample Application Project - a template project for a feature-rich, responsive, customizable web app ready to be deployed to your site.
-
Sample Application Demo - live demonstration of the application hosted out of the project's gh-pages.
A very simple example showing to embed a WorldWind globe into a web page.
WorldWindJava Community Edition (WWJ-CE) is a community supported fork of the NASA WorldWind Java SDK. It is hosted at https://github.com/WorldWindEarth along with other WorldWind-based projects. WWJ-CE seeks to mitigate the effects of the suspension and continue the development of WorldWind Java. Pull requests are accepted.
WorldWindAndroid Community Edition (WWA-CE) is a community supported fork of the NASA WorldWind Android SDK. Like the WWJ-CA, WWA-CE is also hosted at https://github.com/WorldWindEarth. WWA-CE seeks to mitigate the effects of the suspension and continue the development of WorldWind Android. Pull requests are accepted.
- Elevation Server - How to create a WorldWind elevation server
- Elevation Data - Sources for elevation data and conversion scripts
NASA announced a impending shutdown on March 8, 2019:
WorldWind team would like to inform you that starting May 3, 2019, NASA WorldWind project will be suspended.
All the WorldWind servers providing elevation and imagery will be unavailable. While you can still download the SDKs from GitHub, there will be no technical support. If you have questions and/or concerns, please feel free to email at: [email protected]
Here is important information for mitigating issues caused by the shutdown in NASA Web WorldWind SDK based applications. The ramifications of the suspension are severe, including:
-
Critical: Web applications linked to https://files.worldwind.arc.nasa.gov/artifactory/web/0.9.0/worldwind.min.js will fail if the files.worldwind.arc.nasa.gov server is shutdown. The globe will not be displayed. Applications that use a local copy of worldwind.js or worldiwnd.min.js should continue to work, but image resources linked to "files.worldwind..." will not be displayed (e.g., the globe background, view controls, compass, etc.).
-
Severe: Working web applications that use the built-in elevation services at https://worldwind26.arc.nasa.gov/elev will display a smooth globe – 3D terrain visualizations will not work and all earth elevations will be zero. This will affect nearly every WorldWind-based web application.
-
Caution: Working web applications that use the built-in imagery from https://worldwind25.arc.nasa.gov/wms will no longer have access to the Blue Marble and Landsat base map layers. Layers from other source should still work (e.g., Bing, USGS National Map, etc.)
If the files.worldwind.arc.nasa.gov service is offline, an alternative source for the 'worldwind.js' library is required.
{:.no_toc}
The WorldWindJS library is designed as a drop in replacement for worldwind.js (and worldwind.min.js). Here are two implementations
for using WorldWindJS.
For npm based applications: change the @nasaworldwind/worldwind dependency to worldwindjs. For example:
Example: Original package.json
"dependencies": {
"@nasaworldwind/worldwind": "^0.9.0"
},
Example: New package.json
"dependencies": {
"worldwindjs": "^1.7.0"
},
For scripts: change the src from files.worldwind...worldwind.js to WorldWindJS' npm-based CDN at unpkg.com:
Example: Old script element, using files.worldwind.arc.nasa.gov
<script src="https://files.worldwind.arc.nasa.gov/artifactory/web/0.9.0/worldwind.min.js"></script>
Example: New script element, using WorldWindJS at unpkg.com
<script src="https://unpkg.com/[email protected]/build/dist/worldwind.min.js"></script>
{:.no_toc}
Change script element's src from files.worldwind to the npm-based CDN at unpkg.com :
Example: Old script element, using files.worldwind.arc.nasa.gov
<script src="https://files.worldwind.arc.nasa.gov/artifactory/web/0.9.0/worldwind.min.js"></script>
Example: New script element, using unpkg.com
<script src="https://unpkg.com/@nasaworldwind/[email protected]/build/dist/worldwind.min.js"></script>
{:.no_toc}
Deploy the Web WorldWind source code, either directly or in compiled form, to your web server. This solution is the most flexible as it provides the capability to customize the sources for resources, imagery and elevations, and it ensures any changes at NASA or WorldWind Earth do not have a direct affect your project's runtime.
I have an alternative server for NASA elevations (from worldwind26.arc.nasa.gov/elev) staged for production should the WorldWind shutdown become a reality. I will make this server available if needed.
{:.no_toc}
The WorldWindJS library v2.0 (to-be-released) does not have dependencies on the NASA elevation services.
I have been beta-testing the serving of application/bil elevations from my own servers (which I pay for out of pocket).
If/when a shutdown becomes imminent I will transition WorldWindJS to use my servers.
{:.no_toc}
- Elevation Server - How to create a WorldWind elevation server
- Elevation Data - Sources for elevation data and conversion scripts
{:.no_toc}
Here's an example for using alternative elevation services. In this example, two custom elevation coverages are defined, a custom elevation model is then defined, and finally, the WorldWindow is configured with the custom elevation model.
Example: a custom GEBCO elevation coverage class:
/**
* @exports MyGebcoElevationCoverage
*/
define(['worldwind'],
function (WorldWind) {
"use strict";
/**
* Constructs an Earth elevation coverage using GEBCO data.
* @alias MyGebcoElevationCoverage
* @constructor
* @augments TiledElevationCoverage
* @classdesc Provides elevations for Earth. Elevations are drawn from the custom elevation service.
*/
var MyGebcoElevationCoverage = function () {
WorldWind.TiledElevationCoverage.call(this, {
coverageSector: WorldWind.Sector.FULL_SPHERE,
resolution: 0.008333333333333,
retrievalImageFormat: "application/bil16",
minElevation: -11000,
maxElevation: 8850,
urlBuilder: new WorldWind.WmsUrlBuilder("https://mapserver.somewhere.net/elev", "gebco", "", "1.3.0")
});
this.displayName = "GEBCO Earth Elevation Coverage";
};
MyGebcoElevationCoverage.prototype = Object.create(WorldWind.TiledElevationCoverage.prototype);
return MyGebcoElevationCoverage;
});
Example: a custom SRTM elevation coverage class:
/**
* @exports MySrtmElevationCoverage
*/
define(['worldwind'],
function (WorldWind) {
"use strict";
/**
* Constructs an Earth elevation coverage using CGIAR SRTM data.
* @alias MySrtmElevationCoverage
* @constructor
* @augments TiledElevationCoverage
* @classdesc Provides elevations for Earth. Elevations are drawn from the custom elevation service.
*/
var MySrtmElevationCoverage = function () {
WorldWind.TiledElevationCoverage.call(this, {
coverageSector: new WorldWind.Sector(-60, 60, -180, 180),
resolution: 0.000833333333333,
retrievalImageFormat: "application/bil16",
minElevation: -11000,
maxElevation: 8850,
urlBuilder: new WorldWind.WmsUrlBuilder("https://mapserver.somewhere.net/elev", "srtm-cgiar", "", "1.3.0")
});
this.displayName = "SRTM-CGIAR Earth Elevation Coverage";
};
MySrtmElevationCoverage.prototype = Object.create(WorldWind.TiledElevationCoverage.prototype);
return MySrtmElevationCoverage;
});Example: a custom elevation model class that uses the custom coverages:
/**
* @exports MyElevationModel
*/
define([
'model/globe/elevations/MyGebcoElevationCoverage',
'model/globe/elevations/MySrtmElevationCoverage',
'worldwind'
],
function (MyGebcoElevationCoverage,
MySrtmElevationCoverage,
WorldWind) {
"use strict";
/**
* Constructs an MyElevationModel consisting of two elevation coverages GEBCO, SRTM.
* @alias MyElevationModel
* @constructor
*/
var MyElevationModel = function () {
WorldWind.ElevationModel.call(this);
this.addCoverage(new MyGebcoElevationCoverage());
this.addCoverage(new MySrtmElevationCoverage());
};
MyElevationModel.prototype = Object.create(WorldWind.ElevationModel.prototype);
return MyElevationModel;
});Example: the function for creating a WorldWindow with the custom elevation model:
var wwd = new WorldWind.WorldWindow("globe-canvas", new MyElevationModel());I have an alternative server for NASA core imagery (from worldwind25.arc.nasa.gov/wms) staged for production should the WorldWind shutdown become a reality. I will make this server available if needed.
{:.no_toc}
The WorldWindJS library v2.0 (to-be-released) will not have dependencies on the NASA imagery services. I have been beta-testing the serving of Blue Marble and Landsate imagery from own servers (which I pay for out of pocket). If/when a shutdown becomes imminent I will transition WorldWindJS to use my servers.
TODO
{:.no_toc}
TODO
{:.no_toc}
TODO
I have alternative servers for NASA core imagery (from worldwind25.arc.nasa.gov/wms) and NASA elevations (from worldwind26.arc.nasa.gov/elev) staged for production should the WorldWind shutdown become a reality. I will make these servers available if needed.
To leverage these servers, you will need to alter the URLs in the src/config/config.Earthfolder.
TODO
WorldWindEarth, WorldWindJS and the Explorer are personal projects of Bruce Schubert. He was a software engineer on the NASA WorldWind team, but these projects were built and maintained in his spare time. We, the WorldWind Community Edition contributors, support these projects in memory of him.