No announcement yet.

World Wind Java v2.1.0 now available

This is a sticky topic.
  • Filter
  • Time
  • Show
Clear All
new posts

  • World Wind Java v2.1.0 now available

    NASA World Wind Java v2.1.0 is now available on GitHub Releases.

    World Wind Java v2.1.0 contains major improvements for security, functionality, and automation, including: HTTPS map services, Travis CI integration, world-class 2D map support, improved shape dragging, general shape editor, new USGS high resolution imagery layer, new USGS topographic layers, Shapefile rendering performance improvements, Shapefile XML layer configuration files, OGC Web Coverage Service (WCS) elevations, plus many more improvements and bug fixes.

    With the release of v2.1.0, please be aware that all NASA World Wind map services (imagery, terrain, placenames, etc.) require HTTPS connections. Existing versions of World Wind (including v2.0.0) will not connect unless map service links are updated to use the HTTPS protocol. There is an HTTP to HTTPS redirect in place for all NASA World Wind map services, but the Java VM will not automatically follow the redirect. The requirement to host map services exclusively through HTTPS is a U.S. Government mandate.

    World Wind Java v2.1.0 marks our full transition to GitHub for code, releases, and issue management.. Please post any release issues to GitHub Issues.

    The NASA World Wind Team
    Last edited by Patrick Hogan; 12-28-2016, 02:20 PM.
    World Wind Team

  • #2
    Awesome! and the new website looks great too!


    • #3
      You're right, the new website does look great, I'll take a moment to give it a quick plug

      The layout of the Android section is where we hope to be with all three SDK's in the future!
      World Wind Team


      • #4
        Is 2.1 compatible with Java 7? It looks like the release on was built with Java 8. Is a minimum Java version documented?


        • #5
          The source should still be compatible with Java 1.6, and it is somewhat documented here: Design and Coding Guidelines.html. For this release, we have been using Java 8 for building and testing, but the language compatibility level is set at 1.6 (as enforced by our default IDE, IntelliJ).
          World Wind Team


          • #6
            Hi guys,
            Congratulations for the new version,
            However I have a few remarks (as usual!) after having tried all online demos:
            1/ the Political Boundaries server is broken again... Why don't you use the FAO borders that are much most reliable and complete ?
            2/ the Flat world is.... really flat. It is pity to have the elevations zeroed, the tilt resetted abruptly, and the 3D icons also flattened...
            3/ Therefore, the Terrain Profiler is unusable in this mode (there is a GIT issue on this). Really a pity, because users are still used to 2D.
            4/ the new Layer Panel is not my favorite one, too many blue arrows, just unusable. The industry generally uses tree-checkboxes. Furthermore, it doesn't seem to operate (I tried to put the NASA Blue Marble behind the Bing Layer with no success)
            5/ The applets have disappeared from the demos... Probably a good thing for security, but painfull to have extra JNLP windows in a web app... no chance. Yes the web version is here but brings his own problems.
            6/ Some other things on the flat world : Mercator is chopped on half Greenland and a large piece of Antarctica... Is it to avoid projection problems ? or to avoid precision problems (i recall the needToSplit() method that have a few difficulties to get the right layer level...:-). The Transerve Mercator projection seems to be buggy too, it is clear you use a local projection over west africa, because TM is a family of projections, not a single one.
            7/ Finally elevations are still corrupted over some places like shetlands, columbia and others I mentioned in the forum.

            Personnaly, I went through all these problems on my version, plus many others features collected/implemented over the years. All java8 (lambdas) and javaFX'ed.
            I will push next year to try to have it utilized in my work place. It could be added to the current implementation in an amazing way.
            BTW, Happy Holidays to all and a prosperous 2017 !

            Last edited by frenchy; 12-17-2016, 06:25 PM. Reason: formatting


            • #7
              Good comments and dearly appreciated! We'll try to address these as best we can. And hopefully keep you posted with encouraging news.


              • #8
                Hey Frenchy,

                Thanks for the comments, I'll do my best to address each one.

                1. I took a look at the FAO source, and it was very nice, but we'll likely be sticking with our current setup and server. Most of our server issues in the last month are due to the transition to https. While adding the certificate wasn't a challenge, the cache which takes a significant load off of our servers wasn't compatible at first. I think we've worked out most of the errors/issues but there are a lot of servers, and so issues sometimes aren't evident to us. Reporting here or on GitHub will help us get tabs until all of our monitoring systems are back online.

                2. The Globe2D projections are indeed flat. The examples on the SDK set the elevation model to the ZeroElevationModel which is why the elevations are zeroed. If you don't set the ZeroEleveationModel, you'll get the default elevations, but what we really want to do at one point is to make the default elevation model available as data supporting the Globe2D projections and not explicitly tied to the rendering.

                3. If you don't set the elevation model to the ZeroElevationModel (see above) the terrain profiler will work; however, we've done no testing while using an elevation model with Globe2D projections. Like I mentioned in number 2, our end goal would be to have the Globe2D projections appear as they do now but be backed by elevation data not tied to rendering.

                4. The layer list/manager isn't my favorite either. It wasn't changed as it was already done for the 2.0 release and wasn't a priority for this release. I'm not seeing the issue you're describing, when I move the Bing Imagery layer above the Blue Marble May 2004 they switch. Perhaps you were talking about the NASA Blue Marble Image? It is set to disappear once you reach a certain zoom level and I believe the Bing Imagery doesn't start loading until past the zoom level.

                5. We're following Oracles/Chrome/Safari/etc. lead in dropping NPAPI capability, see this article for Java specifics (Oracle Blog

                6. I see what you're talking about with Greenland, let me talk to our projection experts

                7. I'll have to get more familiar with the issues your describing. If you open an issue on GitHub and provide some screen shots or other evidence it will put it on our radar

                Thanks for the notes and well wishes! We hope 2017 is prosperous for you!
                Blogs.Oracle.Com - Java Platform Group, Product Management blog
                World Wind Team