Skip navigation
All Places > Esri Technical Support > Blog > Author: AFili-esristaff
Web AppBuilder for ArcGIS (Developer Edition) version 2.4 supports a Report class with which you can print a file with a map, tables, and other supporting elements.

Check out the ArcGIS blog post, Creating a Custom Widget for Web AppBuilder for ArcGIS using the Report Class, that describes how you can extend the Report class to create your own custom widget to use in Web AppBuilder for ArcGIS (Developer Edition).
Artemis F. - Technology Lead, SDK
This blog pertains to web maps and layer items that have both of these characteristics:
  • Web maps and layers authored with ArcGIS Online prior to the June 2016 update.
  • Contains polygon layers that are styled using Smart Mapping tools to adjust symbol size and/or outline width automatically based on scale

Smart Mapping tools allow you to select between various methods for using attribute values to drive the size of marker symbols when mapping data associated with polygons. You can specify a concrete size range for the symbols, or use automatic sizing so that they are optimized for the initial map zoom level and will automatically adjust so they look better across more zoom levels. We discovered an issue when using the automatic sizing option where the size of each symbol was being incorrectly represented in the web map with pixel values rather than point values (points are the correct unit of measure according to the web map specification). The ArcGIS API for JavaScript was also using pixel values. The result was inconsistent sizing between ArcGIS clients.

You also have the ability to automatically adjust the width of the outline of the polygon based on the current scale. Automatic sizing of polygon outline widths were also being represented using pixels rather than points.

Starting with the June update of ArcGIS Online, sizing values will be correctly represented using points which will enable marker sizing in web maps to be displayed consistently in all ArcGIS clients. The ArcGIS API 3.17 for JavaScript was also updated to use point values rather than pixels. While this update resolves the inconsistencies with auto sizing values going forward, it also means that web maps that were created before the June 2016 update of Online will have marker symbols and polygon outline widths that appear 1.3 times larger than the initial sizes you saw when originally authoring your map.Example map with automatic sizing before the update            Before-resaved-300x173.jpgExample map with automatic sizing after the updateAfter-resaved-300x174.jpgWhat can you do if your web map was affected by this update?

If you created a web map or layer item in Online prior to the June update with layer styles that take advantage of automatic sizing based on scale, we recommend that you reauthor your web map. This process will resave your web map with the correct sizing values for consistent display in all ArcGIS clients. Here are the steps to reauthor your web map:
  1. Open your web map or layer item
  2. Click on "Change Style" in the layer menu for the polygon layer(s) that use automatic sizing of symbols. Note: You might want to write down the options you have selected so that you can easily reselect them in step 4.
  3. Select a different style for your symbols than you originally had selected and click "Done."
  4. Click "Change Style" again on the same layer and reselect the original styling options you had, and click "Done." Any options that were configured within the original style must be reconfigured.
  5. Save your web map or layer item. Your web map will now have size represented using point values.

For information on changing the style of your web map or layer item, see this help topic.Note: this issue also occurs in web maps and layers that were created in Portal for ArcGIS and will be addressed in Portal for ArcGIS version 10.5. This article will be updated once a solution is available.Julie Powell Technical Product Manager, ArcGIS API for JavaScript
Beta versions of Esri vector basemaps are now available through ArcGIS Online as vector tile layers. These vector basemaps are accessible as both ready-to-use web maps and as vector tile layers you can add to a map. Additionally, vector basemaps include a variety of styles, some new and some that are similar to existing Esri basemaps. Web maps you create that contain vector tile layers can be used in web applications you configure or build using Web AppBuilder for ArcGIS. As a developer, you can build your own custom applications that use these vector tile layers using the ArcGIS API for JavaScript.

Please consider the following before deciding to use the current release of vector tile layers:
  • Vector tile layers are only supported in applications built with the ArcGIS API for JavaScript. This includes configurable applications, applications built with Web AppBuilder, and custom applications built with the JavaScript application programming interface (API). ArcGIS Runtime SDKs will add support in 2016.
  • Vector tile layers can be displayed in Internet Explorer 11 and in most other current versions of desktop browsers, including Chrome, Firefox, and Safari.
  • Vector tile layers have the best performance on machines with newer hardware.
  • There are issues displaying vector tile layers at a large scale.
  • Maps containing an Esri vector basemap are printed with the Esri Streets basemap. All other maps containing vector tile layers are printed without the vector tile layers.
  • The Esri vector basemaps are currently in the beta stage and are subject to change during this period. You may need to update or replace vector tile layers built using the beta versions of the vector basemaps. The Esri vector basemaps have some known limitations that Esri will address during the beta period, including the following:
    • Labels in languages that display right-to-left scripts, such as Arabic, are not drawn properly.
    • Labels along vector tile boundaries sometimes do not display completely.
    • The topographic map style does not contain some layers (for example, contours, landform labels, and spot elevations) that are included in World Topographic Map.
    • The topographic and streets (with relief) maps, which reference a hillshade base layer, only enable users to zoom in to about a 1:10k scale.
    • The tiles do not include layers for one-way arrows or address labels.
    • Some parks and land polygon features extend into the adjacent ocean areas.
    • River labels along very curvy lines are sometimes too compressed and difficult to read.
    • In some areas, local road labels and shields display, but not the underlying local roads.

Learn more about vector tile layers here.
Julie P. - Technical Product Manager, ArcGIS API for JavaScript
ArcGIS Runtime SDK for WPF version 10.2.5 is significant in that it is the final release of this product. While technical support will be available through July 1, 2016, maintenance of this product has been discontinued. Customers who develop with this product should begin exploring solutions that are based on ArcGIS Runtime SDK for .NET.

More information on the ArcGIS Runtime SDK for WPF lifecycle can be found here.

The Transition to ArcGIS Runtime SDK for .NET

Two years ago, we announced the creation of a new, high-performance ArcGIS Runtime SDK for .NET to support offline workflows, sync-enabled feature services, shapefiles, client-side labeling, and much more. The SDK includes three APIs that support building ArcGIS Runtime apps for Windows Desktop (WPF), Store, and Phone. The APIs share a common design and structure, which encourages sharing implementation logic across multiple Windows platforms. To prepare WPF developers for the transition from the Runtime SDK for WPF to the Runtime SDK for .NET, we published a blog post and shared a technical session on the topic. We encourage you to utilize this information today and, if necessary, contact our Support team to answer any questions as the ArcGIS Runtime SDK for WPF product moves from mature support to the retired phase.- Esri Support Services

Filter Blog

By date: By tag: