geometry/quantizationParameters vs. cacheHint/resultOffset/resultRecordCount

SCS_ANST — Fri, 03 Jun 2022 12:04:32 GMT

Dear ESRI Community

Hope for your help!

Very simple code, something like this:

const featureLayer = new FeatureLayer({ url: "https://domain.org/arcgis/rest/services/Layer1/FeatureServer/0", }); map.add(featureLayer);

This generates me automatically requets with payload like this:

The result is not satisfying.

When I load the same featurelayer within the new Map Viewer Beta it makes requests with a payload like this, so with a geometry parameter:

And the performance is much better!

If I change with my first sample only from Layer1 to Layer2 it takes the same payload as within the Map Viewer Beta, with the geometry parameter.

So somehow it's not depending to the code and also not to the published layer?! What it depends on and is it possible to force the request with the geometry/quantzationParameters instead of cacheHint/resultOffset somehow?

Thank you very much!

topic geometry/quantizationParameters vs. cacheHint/resultOffset/resultRecordCount in ArcGIS JavaScript Maps SDK Questions

geometry/quantizationParameters vs. cacheHint/resultOffset/resultRecordCount