In time to upgrade over the holidays, ArcGIS JavaScript API 3.15 is here with updates that enable us to use many of the new server features that have been announced over the past few months.

ArcGIS JavaScript API 3.15 - no more beta!

The biggest improvement to this release is the move from beta to production for both the GeometryEngine and the FeatureTable modules. Using before this release there was fear that something could change or disappear - thankfully now that they are in production, using them will not be as much of a gamble. A few new methods are also included with the GeometryEngine for Geodesic Densification (used to draw a line of the geometry along great circles).

ArcGIS JavaScript API 3.15 - New stuff

Lots of new features added to this release, mostly related to recent server side enhancements:

  1. New layer type for Vector Tile Layers: One of the biggest updates on the server side is the addition of Vector Tiling which can now be accessed by the API. This includes client side rendering of individual layers on-the-fly.
  2. New rendering (Smart Mapping) method called “PredominanceRenderer”. Which ”allow[s] you to generate a UniqueValueRenderer showing the predominant value in each feature among a set of two or more competing fields” (Esri).
  3. A new Sample of samples: A new sample has been introduced to help with symbol styles, the ArcGIS Symbol Playground. Make a unique symbol with this sample, and copy the rendering code to add directly to your application. That’s right, spend less time in your browser hitting F5 to refresh!
  4. Over 35 new events/methods and enhancements added

ArcGIS JavaScript API 3.15 - Squished Bugs

A total of 15 bugs were fixed - although expect many fixes in the next release as vector tiles are just getting warmed up. Many of the fixes are related to Geocoding, symbols and the legend. Oh, and the annoying Measure Widget always opened by default even if you didn’t want it to issue is now fixed - thank you!!

Side note - you can now create a custom build of the API using Bower. This is a much better alternative to the Web Optimizer which can be a little complicated to get working properly. Want to give it a try? Esri has a great tutorial on this very subject!