| Numéro d’ID de bogue |
BUG-000179777 |
| Envoi | September 30, 2025 |
| Dernière modification | October 17, 2025 |
| S’applique à | ArcGIS Pro |
| Version trouvée | 3.5.3 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 11.0 64 bit |
| Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
This behavior is due to a limitation on the WFS server. The WFS server does not support result paging (use of startIndex and count), and the layers seem to have a set maximum feature limit.
For example, if requesting 20,000 features for the 'Cadastral parcel polygons' layer, the WFS service returns the "Response truncated due to too many objects in requested area/query (max. 20000 for this feature)!" exception error message.
Similarly, the maximum number of features allowed for the 'Cadastral Zoning polygons' layer is 1,000. The WFS server should implement result paging to address this limitation so that a client can request all features in pages to avoid exceeding the maximum allowed.
This explains why zooming in and requesting an extent area works, as the client is requesting fewer features than the maximum number allowed by the WFS server.
Finding these server limitations was challenging, as it is not advertised in the GetCapabilities response. The server could implement the WFS CountDefault property to advertise the limit (if unable to support response paging).
Solution de contournement
- Use a spatial extent filter at a smaller scale to visualize the layers.
- Set the maximum features to a value matching the WFS server's limitation. For example, 1,000 for zoning or 20,000 for parcel polygons.
Étapes pour reproduire
ID de bogue: BUG-000179777
Logiciel: