The map does not display all the data from the referenced feature service when using a large dataset in ArcGIS Maps SDK for .NET version 200.4.
ArcGIS Maps SDK for .NET
漏洞 ID 编号
BUG-000168938
已提交
July 5, 2024
上次修改时间
November 1, 2024
适用范围
ArcGIS Maps SDK for .NET
找到的版本
200.4
操作系统
Windows OS
操作系统版本
11.0 64 bit
状态
As Designed
经开发团队审核,已确定此行为符合设计。 有关详细信息,请参阅“其他信息”部分。
附加信息
This issue is closed As-Designed.
The issue described arises from variations in how services are published to enterprise versus hosted environments. These two types have metadata differences that lead to rendering disparities.
Specifically, the discrepancy highlighted in this problem is attributed to the supportsMaxRecordCountFactor property being set to false for enterprise services. Conversely, hosted services have this property configured as true, with maxRecordCountFactor defaulting to 4. ArcGIS Maps SDKs for Native Apps do not directly control these published properties. However, it does adhere to these settings under the surface to query data accordingly. For instance, in hosted services where supportsMaxRecordCountFactor is true and maxRecordCountFactor is greater than 1, each request for fetching features in a tile retrieves four times more features. On the other hand, for enterprise services where this property is false and maxRecordCountFactor defaults to 1, it retrieves less data compared to hosted services, resulting in rendering fewer data.
In Native Maps SDKs, subscribe to LayerViewState and monitor the layerviewstate error. When excessive data is requested, a warning is triggered stating a layer has requested more features than the service maximum feature count.
The behavior of enterprise services is designed with performance in mind, and any alterations should be approached cautiously. These values are managed through the ArcGIS REST API services. As a workaround, utilize the ArcGIS Enterprise Administrator API to adjust the maxRecordCountFactor value to exceed 1. However, it is important to note that this is not a supported workflow and falls outside the scope of Esri Technical support. It is advised that GIS data analysts/authors/publishers comprehend the data and evaluate the implications of modifying the max factor, as it directly impacts rendering in Native Maps SDKs, particularly for mobile device development.