ArtemisFili
Esri Contributor
since ‎07-04-2014
15 Badges Earned
One Year Anniversary Welcome Back!
View All Badges Earned
‎06-17-2025
49 Posts created
6 Kudos given
6 Solutions
23 Kudos received
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

My Ideas

(0 Idea Submissions)

Latest Contributions by ArtemisFili

POST
0
8
3368
POST
1
0
743
POST
1
0
1341
POST
1
0
777
POST
1
0
551
POST
0
0
777
POST
1
0
712
POST
1
0
656
POST
1
0
598
BLOG


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 -->
0
0
2280
POST
1
0
683
BLOG
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 -->
0
0
832
POST
0
0
439
POST
0
0
661
POST
0
5
1505
Activity Feed