Latest Contributions by EmreCan

Hello, I am using ArcGIS REST Api version 10.6.1. I have the following problem: Geometries are not displayed in 3D mode because the requests may be incorrect. In 2D mode (MapView) everything works fine. My analysis: If I do not support queries with returnCountOnly & returnIdsOnly in the query interface, then everything works. So if I return an empty object in the following query: Request: http://localhost:8080/rest/arcgis/features/4242/4242/query?f=json&returnIdsOnly=true&returnCountOnly=true&outSR=3857&spatialRel=esriSpatialRelIntersects&where=1%3D1 Response:    {}   As soon as I return an object with the Count value as usual it doesn't work.   {"count": 1}   Because the subsequent requests then look like this: Request:     http://localhost:8080/rest/arcgis/features/4242/4242/query?f=json&outFields=objectId%2Cdescription&outSR=102100&spatialRel=esriSpatialRelIntersects&where=1%3D1   But I don't want to support query calls without a geometry. My expected subsequent request would be:     http://localhost:8080/rest/arcgis/features/4242/4242/query?f=json&geometry=<geometry>&maxAllowableOffset=3261.313206833336&outFields=objectId%2Cdescription&outSR=102100&spatialRel=esriSpatialRelIntersects&where=1%3D1&geometryType=esriGeometryEnvelope&inSR=102100     I also get the following error message on #fetchTile(): What is the best way to solve the problem? I don't want to remove the returnCountOnly function from the interface. Why does it work at all if I return something wrong (empty object) so to speak?   Thanks for any help!   *** EDIT *** I found out that when the feature count is over 50,000 that the request is split into multiple requests. So where does the limit "50,000" come from and how can I override it? I didn't find anything about this in the docs. ... View more

With the current @types/arcgis-js-api it is not possible to autocast classes, because every propertie is required. Furthermore, the property 'type' is missing in the TextSymbolProperties. I can't generate a new TextSymbol like this:      layer.featureReduction = { type: "cluster", labelingInfo: [{ labelExpressionInfo: { expression: "$feature.cluster_count" }, deconflictionStrategy: "none", labelPlacement: "center-center", symbol: { type: "text", // Error color: "white", font: { size: "12px" }, haloSize: 1, haloColor: "black" } }] };       I get this error message:  "Object literal may only specify known properties, and 'type' does not exist in type 'TextSymbolProperties | LabelSymbol3DProperties'"   I have to use // @ts-ignore over and over. And this is just an example. The same could be applied to many things! ... View more

I am trying to create a service with tags via REST. When I look at the service in the portal, the tags were not applied. What am I doing wrong? I created the service with the createService operation.  This is what my request and my response look like: Request URI: https://<usercontent-url>/createService Method: POST Body: createParameters={"name": "Sample"}&outputType=featureService&description=Should be tagged&tagss=custom-tag&snippet=Exported data for Sample&isView=false&f=json Response Body: {"encodedServiceURL":"<url>","itemId":"<itemId>","name":"Sample","serviceItemId":"<serviceItemId>","serviceurl":"<serviceUrl>","size":-1,"success":true,"type":"Feature Service","description":"Should be tagged","tags": "custom-tag","snippet":"Exported data for Sample","isView":false} When I look for the service in the portal afterwards, there are no tags added. ... View more