Not using third-party frameworks and want to stick with loading in the API in a familiar way? No problem. You can continue using the AMD modules for the foreseeable future, according to this announcement on the 4.18 release.
How data is represented is extremely important in GIS. It impacts how viewers understand and process the data. Having too many points can be overwhelming and confusing, obscuring important information. At the same time, summarizing data can lead to generalizations, and important details can be lost in a larger group. Enter cluster querying! Personally, cluster querying is one of my favorite things about this update.
With cluster querying, geodevs are able to marry the idea of clustering data to make the map more digestible with the need to keep important information accessible. Developers can query the aggregateIds property of a cluster to get all the ObjectIds of the represented features, and, thereby, their attributes.
As a result of cluster querying, maps can display the extent or convex hull of all the features represented in a cluster. Additionally, all of the features represented in a cluster can be displayed (perhaps for a more focused view upon selecting a particular region to dig into). Since the attributes for the features are still accessible, it is also easy to calculate and display statistics for the cluster.
To see the magic in action, check out this visual from Esri:
Moon and Mars Scene Support
While support for these coordinate systems is still experimental, it is very exciting. With advancements in astronomical research, as well as established coordinate systems for other extraterrestrial bodies, this functionality is something to keep an eye on for sure.
Custom Coordinate Systems
Don’t know how to get the WKT for your coordinate system? Esri already has the answer for you! Simply save a projection file (.prj) and open it in your text-editor of choice. Your WKT will be right there. (You can also see a number of them here or here, if you’re the curious type.)
- IE11 and Edge Legacy No Longer Supported
Esri is a global company, and it recognizes that many of the people who build solutions with their API need those solutions to work in a variety of languages. Supporting translations for text in custom widgets is easier with expansions to the intl class. For more information, please refer to the section of the release notes linked at the start of this bullet.
The 3.x version of the API is currently being updated with bugfixes only. Esri has stated they will retire it on August 1, 2022. They have more information about this in the link above.