Consider:

• enableAtmosphere
• enableCompass
• enableCoordinates
• enableDayNight
• enableStars
• enableTessellation

Deprecate the use of the layers prop for establishing these settings.

Add the capability to attach the Globe to existing canvas if a canvas' element ID is supplied as a property.

Adjust the Bing layers' detailControl to improve clarity of labels.

• Bing Roads
• Bing Aerial with Labels

See: https://medium.com/@jakub_43881/display-layers-provided-in-mercator-projection-b93f894d3fc2

@balhar-jakub

So I have one test project set up that takes in data from a websocket and display the location on a worldwindjs (vanillajs) map. I am now testing this library with this npm project and cannot figure out how to add a the location image to the map.

In the vanillajs implementation I am adding with (sudo code):

var renderableLayer = new WorldWind.RenderableLayer();
var location = new WorldWind.Position(lat, long, alt);
var placemark = new WorldWind.Placemark(location);

renderableLayer.addRenderable(placemark);

In the worldwind-react-globe project I console logged the globeRef and cannot find any prototype of the Object where I can call the WW.Position() or WW.Placemark() function to add a renderable.

Is this possible in the worldwind-react-globe? If so do you have examples of how to do this?

I have a renderable layer available for use and have verified its existence within the globeRef.

Thanks,

James

Use Travis-CI for continuous integration. Builds in the master branch should be published to npm and deployed to gh-pages.

Add a rotation prop (PropType.number) that controls the Globes rotation animation. The rotation value is a simple multiplier where 1 is one rotation in 24 hours, 2 is 2x, etc.

• a value of 0 is no rotation (default)
• values > 0 rotate the globe in the normal direction
• values < 0 rotate the opposite direction
• a value of 1 rotates one rotation in 24 hours

Improve the support for layer categories :

• The order addLayer is called should define the draw order of layers within their category. I.e., addLayer should add the layer to the end of its category, inserting it into the overall layer list if necessary.
• A defaultCategories array should define the draw order of the categories themselves.

Add optional React props to establish the globe's latitude, longitude, range and tilt. Also, a prop to indicate whether to animate a change in view.

E.g.:

  static propTypes = {
    lat: PropTypes.number, 
    lon: PropTypes.number,
    range: PropTypes.number,
    tilt: PropTypes.number,
    animateGoto: PropTypes.bool
  }

Add a date prop that controls the behavior of the day/night setting.

Application may want to add custom categories and/or change the order of categories. Add a setter to allow the categories to be replaced.

• Add a setter for categories property
• Add a defaultCategory property

I am pretty new to react, what the heck is going on here?

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^0.13.0 || ^0.14.0 || ^15.0.0 || ^16.0.0" from [email protected]
npm ERR! node_modules/mobx-react
npm ERR!   peer mobx-react@"^5.1.2" from [email protected]
npm ERR!   node_modules/worldwind-react-globe
npm ERR!     worldwind-react-globe@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Add an interface that accepts a WMS service address and then populates a list of with the available WMS layers.

Allow a layers configuration array to be passed into the Globe as a React props array.

Allow drag-n-drop of local gis/geospatial data onto a Globe, such as:

• Shapefiles
• KML
• GeoJSON
• GeoTiff

See: https://github.com/OBarois/drop2worldwind

Add the enableNavigation prop to the Globe to control whether the user can move the globe with mouse or touch gestures. The default value should be true.

Setting this prop to false would establish a static globe/map whose location can only be changed programmatically.

Add documentation to README for the Globe props and API.

Manifest an array of string literals for all the default layers available to the Globe. The individual layer names can be used by the developer to add layers to the Globe without having to traverse the WorldWind library to discover them on his or her own.

Add a backgroundColor property to the Globe so the background color can be set by the application. E.g.:

import React, { Component } from 'react'
import Globe from 'worldwind-react-globe'

class App extends Component {
    render () {
        return (
            <div>
                <Globe backgroundColor='rgb(36,74,101)' />
            </div>
        )
    }
}