Whitebox GAT 3.3.0 has been released

I am very pleased to announce that the open-source geographical information system (GIS)and remote sensing package Whitebox GAT version 3.3.0 (codename Glasgow) has now been released. This version was somewhat delayed because of the transition from Google Code to a GitHub based code repository. However, the transition has now been successful and this new version of Whitebox GAT boasts numerous improvements, enhancements, and bug fixes. Please see the release notes for a detailed description of changes.

The Whitebox GAT project (http://www.uoguelph.ca/~hydrogeo/Whitebox/) began in 2009 and was intended to provide a platform for advanced geospatial data analysis with applications in both environmental research and the geomatics industry more broadly. It was envisioned from the outset as providing an ideal platform for experimenting with novel geospatial analysis methods. Equally important is the project’s goal of providing a tool that can be used for geomatics-based education. Its unique open-access development model provides easy opportunities for the user community to inspect, modify, and build upon the source code of Whitebox’s many powerful spatial analysis tools.



7 thoughts on “Whitebox GAT 3.3.0 has been released

  1. OUATTARA Ismaila says:

    Hello Dear. I’m Ismaila and a user of Whitebox. It’s thery useful and thank you for this Job. I use it in my Thesis to calculate some hydrological index. My question is this:
    1) How to create a Specific Contributing Area (SCA) raster or can i have further information about this raster?

    Thank you

    • Hello Ismaila, I received your email and have replied to your question there. It’s probably best not for me to post detailed instructions as a comment. Please let me know if you have further questions.

  2. Is there a way to estimate how large files whitebox can handle given a specific amount of RAM? I know you ran the Nile basinwhich was 4.28 GB in size a while ago. Is there a simple way of knowing how large files i can use for hydrological modelling with 32 GB or 64 GB of RAM? My input data is around 1 TB and I’m currently splitting it up into isobasins which i run in parallel. More isobasins means more edge effects ect. Whats your record in terms of DEM size?

    • Hi William,

      Unfortunately, Java cannot see all of the RAM available on the machine. One of my reasons for exploring natively compiled options for Whitebox development as of late is because of the strange and large memory requirements that Java has. Additionally, it’s somewhat difficult to calculate ahead of time how much memory a tool will require. First, a raster is represented in memory as an array of 64-bit (8 byte) floating point values regardless of how the data are stored. It is very common for data, for example, to be stored in a file as 32-bit floats, and so it is effectively twice as large in memory. But the story is more complex than that since if a raster is large enough, Whitebox will actually swap regions of the raster into and out of memory as needed. Then there is the issue of how many rasters (inputs, outputs, and in-memory temporary rasters) a specific tool uses. Clearly the more rasters there are the larger the memory requirement.


  3. Daniel Linton says:

    Small question,

    I haven’t been able to use the ruler tool (measure distance) I don’t know where the result appears. I also think the profile tool should be searchable in the toolbox.

  4. johnwallx says:

    Is there a list of supported file formats for Whitebox GAT? I have not been able to find a conclusive list like what is available for ArcGIS or QGIS.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s