WorldWindJava
WorldWindJava copied to clipboard
NASAWorldWind
Community Edition
There is a need for a community edition of WorldWind. This will essentially be a community-managed fork that incorporates pull requests not belonging in the stable upstream version, but still being useful enough to the community that it should be maintained and kept up-to-date. See the discussion at pull-request #77 for some background on this.
I agree with you, there is a lot of work that risk to be abandoned. I have improvement for handling HTTP Redirection, drawing ground line for air track, increase detail rendering of 2D maps so it would be nice to have a common shared community fork where all those improvements could be available. If I can help, I am available.
Good, I think we need a lot of people on-board to get the community-edition going. But, first we have to wait for the NASA guys to post the community contribution guidelines (this was mentioned in pull-request #77). The pull-request labels will be needed to determine what pull-requests are fit for the community-fork. In your case, you would probably have to then create pull-requests for the various additions in this repository. If it should go to the community-fork the NASA guys will then mark it with a label "community-edition" (or whatever label is decided) where it will then be picked up by the community-fork owners and merged into that repository.
I believe, as already stated on the pull-request-77 that the community fork needs some members of the board from the NASA Team so we can better coordinate integration of derivative work into stable nwwj product.
@wcmatthysen Thanks for opening a dedicated issue for this discussion.
The NASA team is certainly on board with a coordinated community fork. We're very busy at the moment working on sponsored feature deliverables for the Android and Web SDKs, but have this on our Kanban board to address as soon as we can.
Thanks for your patience. We haven't forgotten about this need. It's on our backlog of tasks to address after we finish our current round of sponsor-requested features.
I think a community edition is now more relevant than ever (just my 2 cents).
I agree, it is time to create the community edition of Nasa World Wind. What is not clear is we are allowed to do this without a prior authorization by NASA.
Il giorno ven 5 apr 2019 alle ore 10:30 Wiehann Matthysen < [email protected]> ha scritto:
I think a community edition is now more relevant than ever (just my 2 cents).
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480193061, or mute the thread https://github.com/notifications/unsubscribe-auth/AJYth0mZEWRCN7WqCRs4NHji29B_bcq6ks5vdwmbgaJpZM4Ldu1G .
We do not need NASA's permission as far as I understand. It is open-source after all. We can just fork it and go our separate ways. It would be great to get their blessing though.
I see there is already an official community fork for WebWorldWind. Maybe we can reach out to @emxsys to host the community edition of WorldWindJava under the WorldWindEarth banner as well.
Sounds good--I somehow totally missed the announcement of the suspension of the WorldWind projects.
I'd be happy to lend a hand if there's anything needed to get this initiative off the ground.
perfect. we would be in as well. we have quite some potential contribution, (e.g. javaFX port) but since nasa was too refusive on merging anything, we gave up.
I think we should set up a rough road-map of what we want to accomplish. I would personally like to switch the project's build system over to Maven (or Gradle for that matter) instead of the clunky, archaic way that they have built the project using Ant. I have managed to do that in my own fork of the project, so it can be done with a bit of effort. I think the JavaFX additions would be great seeing as that is where everything is moving towards nowadays. We could probably go through the current pull request list and merge a lot of the useful ones into our own version. Bug-fixes should take priority. We can also focus some effort on modernising the project by introducing some Java 8 features as we go along.
I don't know how we can increase the visibility on this issue, seeing as it is quite old. It doesn't show up at the top of the issue-list on the project's GitHub page. We need to get the word out to as many other people that are interested as possible or this is not going to take off. I tried to get the fork going a year or two ago but no-one was really interested. You can see my post here on the forums as well (it never got any real traction).
I think two pull requests that we should already consider a priority is the JOGL upgrade (see pull-request #1) and the GDAL upgrade (see pull-request #146). I mean the JOGL pull request has been waiting for a merge now for over 3 years.
These pull-requests: #18, #19, #30, #138, #139 that are bug-fixes have also been unmerged for roughly 2 to 3 years now. Not to mention the more recent pull-requests such as #150 and #157 that should probably be inspected and merged.
A community edition with an updated design would be great, count me in for what is worth. I think a javafx por would be great. I don't know if a javafx version would use jogl. Also maven would be great! If someone builds it, we will follow :) Cheers, Tomas Lund Petersen
El vie., 5 abr. 2019 09:14, Wiehann Matthysen [email protected] escribió:
I think two pull requests that I would already consider a priority is the JOGL upgrade (see issue #1 https://github.com/NASAWorldWind/WorldWindJava/pull/1) and the GDAL upgrade (see issue #146 https://github.com/NASAWorldWind/WorldWindJava/pull/146).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480253581, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G .
A community edition with an updated design would be great, count me in for what is worth. I think a javafx por would be great. I don't know if a javafx version would use jogl. Also maven would be great! If someone builds it, we will follow :) Cheers, Tomas Lund Petersen El vie., 5 abr. 2019 09:14, Wiehann Matthysen [email protected] escribió: … I think two pull requests that I would already consider a priority is the JOGL upgrade (see issue #1 <#1>) and the GDAL upgrade (see issue #146 <#146>). — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#81 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G .
Not sure about the JavaFX port either. I know that JavaFX has its own 3D API. I haven't personally worked with it. I am not sure whether work has already been done to port WorldWind to run in JavaFX. But any contributions with respect to that would be a welcome addition to the community edition. I know it can at least be embedded in a SwingNode and displayed in a JavaFX application (but that is different than porting it to JavaFX's 3D API).
I think we should just find a proper home for this project. It would probably be best if it lives alongside the other community editions, hence the reason I mentioned Bruce Schubert's (@emxsys) community fork of WebWorldWind.
I also think we should concentrate on providing replacement for the basemap layers that point to the nasa servers that are going down may 4rth. Bing aereal, sentinel2, places and roads seems to me te most importants. I guess elevations would be important to some people also. Cheers, Tomas
El vie., 5 abr. 2019 09:33, Tomas Lund Petersen [email protected] escribió:
A community edition with an updated design would be great, count me in for what is worth. I think a javafx por would be great. I don't know if a javafx version would use jogl. Also maven would be great! If someone builds it, we will follow :) Cheers, Tomas Lund Petersen
El vie., 5 abr. 2019 09:14, Wiehann Matthysen [email protected] escribió:
I think two pull requests that I would already consider a priority is the JOGL upgrade (see issue #1 https://github.com/NASAWorldWind/WorldWindJava/pull/1) and the GDAL upgrade (see issue #146 https://github.com/NASAWorldWind/WorldWindJava/pull/146).
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480253581, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G .
I also think we should concentrate on providing replacement for the basemap layers that point to the nasa servers that are going down may 4rth. Bing aereal, sentinel2, places and roads seems to me te most importants. I guess elevations would be important to some people also. Cheers, Tomas El vie., 5 abr. 2019 09:33, Tomas Lund Petersen [email protected] escribió: … A community edition with an updated design would be great, count me in for what is worth. I think a javafx por would be great. I don't know if a javafx version would use jogl. Also maven would be great! If someone builds it, we will follow :) Cheers, Tomas Lund Petersen El vie., 5 abr. 2019 09:14, Wiehann Matthysen @.***> escribió: > I think two pull requests that I would already consider a priority is the > JOGL upgrade (see issue #1 > <#1>) and the GDAL > upgrade (see issue #146 > <#146>). > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#81 (comment)>, > or mute the thread > https://github.com/notifications/unsubscribe-auth/AB_pYAATm6AVFSIWtjxkep1s_xuWHjdeks5vdz4qgaJpZM4Ldu1G > . >
Yes, I think that is also important. I have a Sentinel2 layer configuration file that I can share to replace the LandSat layer. It connects directly to the EOX::Maps server to get the s2cloudless layer. I don't know about an OpenStreetMap layer that we can use. Maybe we can get a layer from EOX::Maps as well. The elevation data is very important. I don't know if the NASA guys have made any plans to host it somewhere else. It would be nice to at least get some info on how to setup and host the data ourselves.
Again, all sounds good. Merging in pull request #1, a Gradle build, and alternative base layers would all be great. Not so sure about JavaFX, both because of OpenGL issues, and its exclusion from future JDKs, but I'm not too clued up on that stuff. Might be best to make anything that relies on JavaFX a separate optional module?
As for visibility, it might be worth bumping your original thread in the forum, and posting on this one as well: https://forum.worldwindcentral.com/forum/world-wind-community/worldwind-general/158839-worldwind-suspension.
Though, once a home for this project has been found then issues/features can be decided upon & tracked there, and that location can be advertised. Probably worth dropping @emxsys an e-mail to get his thoughts, if he hasn't already gotten notifications from being tagged here, and then moving forward from there.
so our JavaFX port works in parallel to the Swing components. so no issue. it also uses openGL. we also have our own jogl and GDAL patches.... as probably most of you. and we are also on maven... we even have tried to file fundamentaly bugs like a math bug in matrix determinant computation... and they havent picked it...
So is this version available? Id like to give it a try. Where can i get a hold of it? Tks, Tomas
El vie., 5 abr. 2019 10:21, caller [email protected] escribió:
#155 https://github.com/NASAWorldWind/WorldWindJava/issues/155
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480272861, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_pYEgSSCIEyc3zlZ0If9En71hMESd7ks5vd03LgaJpZM4Ldu1G .
Yes I think that we need to create separated module of the Nasa World Wind SDK, isolating math-projection library, common utility to the core features
So which are the next steps? Some one has get in touch with Bruce Schubert's?
we havent polished our javaFX version jet for release... that might take some weeks in our processes. I might also need mgmt approval. Im working for a quite big company ;-)
Again, all sounds good. Merging in pull request #1, a Gradle build, and alternative base layers would all be great. Not so sure about JavaFX, both because of OpenGL issues, and its exclusion from future JDKs, but I'm not too clued up on that stuff. Might be best to make anything that relies on JavaFX a separate optional module?
As for visibility, it might be worth bumping your original thread in the forum, and posting on this one as well: https://forum.worldwindcentral.com/forum/world-wind-community/worldwind-general/158839-worldwind-suspension.
Though, once a home for this project has been found then issues/features can be decided upon & tracked there, and that location can be advertised. Probably worth dropping @emxsys an e-mail to get his thoughts, if he hasn't already gotten notifications from being tagged here, and then moving forward from there.
I bumped some threads in the forum. I think Bruce Schubert would probably be notified via GitHub as a result of all the mentions. I'll email him too just in case.
more things I might have for sharing:
- fast mercator tile layer
- mercator elevation tile layer (mapbox)
I found this new server for the image layers to wich we could all switch i think. https://worldwind.earth/explorer https://worldwind.earth/explorer Also id like to bring to notice that the date for the black out has been moved from april 9th to may 3rd.
El vie., 5 abr. 2019 10:33, Alessio Iannone [email protected] escribió:
I have added support for DXF (Autocad) and MapBox
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindJava/issues/81#issuecomment-480276828, or mute the thread https://github.com/notifications/unsubscribe-auth/AB_pYKRVnyde5moy8mJv0vurchDGSNhGks5vd1CYgaJpZM4Ldu1G .