August 31

AerisWeather Android SDK v2.4.1

The latest update for the Android SDK is now available! AerisWeather Android SDK v2.4.1 includes many bug fixes, along with updates to the map animations and even some spiffy new tropical map layers!

Tropical Map Layers

We already know that the AeriWeathers Mapping Platform provides tons of awesome map layers to help your users visualize your app’s data.

So it’s no surprise that the AMP team would crank out another set of layers, just in time for the Hurricane season!

With the latest update, AerisWeather Android SDK v2.4.1 includes the new tropical layers and all their various modifiers and options.

Like most of the AMP layers, the new tropical offerings have many different options. So go ahead and tweak the layer to display the data exactly how you need it.

The new tropical layers in AMP and AerisWeather Android SDK v2.4.1 are brand new, so be sure to check back often to see how this important and exciting addition to the Aeris family of maps grows and evolves!

Map Animations

There’s an old saying that goes something like “Don’t go looking for trouble because you just might find it.”. That definitely applies to software development! Once you start digging into fixing bugs, there’s always one more thing to tweak.

Animating Is Fun When We Do It Right

First up, we fixed a bug dealing with retrieving and working with the current time when building the array of images used for the map animation. Though in most cases the issue did not significantly impact the number of images presented in the animation, it did result in the potential for some frames/images to be skipped/omitted as we built the animation. The fix assures that we get the best animation available for each use case.

Oh, and as long as we were already in there touching the code, we went ahead and added support for animating the future wind and temperature layers too.

Say What You Mean

Another issue we stumbled upon was in the documentation for the maps library. The method definition for setAnimationInterval( ) and getAnimationInterval( ) both contained typos regarding the units passed for the interval between images. The documentation stated that the interval was in minutes, whereas it’s actually in seconds.

As we know from our own experiences with third-party software, something as silly as a copy and paste error like this can be really frustrating. We sincerely hope it didn’t cause too many sleepless nights.