Baseline for GIS Applications

The application I introduced here yesterday can best be understood via its author's explanation: "As I developed several different WorldWind-based applications, I noticed that they all started out the same. Terramenta was born so I wouldn't have to recreate the baseline every time, I could just provide NetBeans plugin modules to introduce the new features required by different projects."

So, to try it out for myself, I checked out the sources from the Mercurial repo today, built them, and ran them.

hg clone

On Windows, things worked fine, on Ubuntu they didn't because the relevant native libraries aren't provided yet out of the box.

Here's the result:

The above provides the WorldWind globe, together with all the standard options, e.g., for showing names and other WorldWind features, together with several features that I don't understand yet, such as tools for creating shapes and a recorder for replaying sequences.

The complete application is like this, i.e., one single functionality module is provided, which exposes several API packages that can be extended:

It would really be cool if the above module could also be added to a Maven-based application via a reference to a Maven repository, in the way that Timon Veenstra and the AgroSense team have made available their GeoViewer.

One cool thing from the GeoViewer solution is the Flamingo menubar, which I added to Terramenta by simply putting the dependency below into the application POM:


The result, without doing anything other than the above:

I am looking forward to helping to document the use cases and developer scenarios for Terramenta! Something like this, created by Timon to demonstrate the GeoViewer use case would be cool to have:


I would be sweet to know how to use a custom map from a map server. A lot like the openmap modules.

Posted by Javier Ortiz on August 30, 2012 at 06:46 AM PDT #

I really like the use of the flamingo bar!
I'm building it right now but I'm a bit thrown off by the amount of dependencies the nl.cloudfarming.client menu is requiring...

Posted by guest on August 30, 2012 at 06:51 AM PDT #

You can connect to any standard WMS to add imagery layers at runtime.
The default layers are controlled by the worldwind.config file which can be customized and referenced in the options panel.

Posted by heidtmare on August 30, 2012 at 08:00 AM PDT #

"I'm building it right now but I'm a bit thrown off by the amount of dependencies the nl.cloudfarming.client menu is requiring..."

The menu artifact itself does not have much dependencies.
7 netbeans api modules and lib-flamengo

It could be caused by having a different netbeans platform version in your application. 1.0.24 is build on RELEASE71, if you use a different version, all RELEASE71 versions of the netbeans api modules will be downloaded, including their RELEASE71 dependencies etc etc.

I'm not sure how to solve this though.
We could build artifacts based on different netbeans platform versions, but that would require including the platform version in our own version
(something like 1.0.24-NBRELEASE71, 1.0.24-NBRELEASE169 etc)

Posted by Timon Veenstra on August 30, 2012 at 09:14 AM PDT #

We're in the process of preparing help files and tutorials, so stay tuned--help is on the way! We just published three tutorial videos on the Team Ninjaneer Channel:

Posted by Travis on August 30, 2012 at 08:40 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed

Geertjan Wielenga (@geertjanw) is a Principal Product Manager in the Oracle Developer Tools group living & working in Amsterdam. He is a Java technology enthusiast, evangelist, trainer, speaker, and writer. He blogs here daily.

The focus of this blog is mostly on NetBeans (a development tool primarily for Java programmers), with an occasional reference to NetBeans, and sometimes diverging to topics relating to NetBeans. And then there are days when NetBeans is mentioned, just for a change.


« October 2016