Latest Contributions by JoelBennett

I have a map service published to ArcGIS Server whose spatial reference is WGS 84 UTM Zone 6N (WKID 32606).  One of the layers in the service has labeling information defined, and the labelExpressionInfo.expression is set to: Round(Length(Geometry($feature),"feet"),2).  I load this layer into a map as a 2D FeatureLayer.  The spatial reference of the map is Web Mercator (WKID 3857).   The data being retrieved from the server is returned by ArcGIS Server projected into Web Mercator (WKID 3857).  Nonetheless, labels do not show up, and the following error appears in the console:   Cannot work with geometry in this spatial reference. It is different to the execution spatial reference.   This should not be happening because the data queried from the service is already in the Web Mercator projection.  The problem is that the API, when processing the FeatureSets returned from the server, assigns the layer's spatial reference (WKID 32606) to the data, even though the coordinates are Web Mercator.   The most convenient place I've found to insert a fix for this is in the esri.views.2d.layers.features.support.FeatureSetReaderJSON module, in the "fromFeatureSet" method.  The published implementation looks like this:   static fromFeatureSet(a, f) { a = q.convertFromFeatureSet(a, f.objectIdField); return l.fromOptimizedFeatureSet(a, f) }   The "a" parameter is the FeatureSet returned from the query, still in JSON format.  The "f" parameter is an object containing various settings from the layer, including the spatial reference.   Basically, I clone the "f" object, and set its spatial reference to the same as the FeatureSet:   static fromFeatureSet(a, f) { var g = {}; Object.getOwnPropertyNames(f).concat(Object.getOwnPropertyNames(Object.getPrototypeOf(f))).forEach(function(h) { if (typeof f[h] != "function") g[h] = f[h]; }); if (a.spatialReference) g.spatialReference = f.spatialReference.constructor.fromJSON(a.spatialReference); f = g; a = q.convertFromFeatureSet(a, f.objectIdField); return l.fromOptimizedFeatureSet(a, f) }   As can be seen, I've added lines 2-9, and everything else is the same.  With this fix in place, no errors occur and the labels show up properly.  I was using 4.31 for this, but other versions may be affected as well. ... View more

A bug in the 4.31 SDK (and possibly previous versions) causes trouble when moving Circle geometries via the SketchViewModel.  Basically, if you move a circle graphic once, it's fine.  But if you move it after that, it will "jump back" to its original location and then move in relation to the mouse.  To illustrate, this can be reproduced with the following steps: 1) Open the sandbox for the "Sketch temporary geometries" sample. 2) Replace the contents of the script tag found on line 21 with the following: require([ "esri/Color", "esri/Graphic", "esri/Map", "esri/geometry/Circle", "esri/geometry/Point", "esri/geometry/Polygon", "esri/layers/GraphicsLayer", "esri/symbols/SimpleFillSymbol", "esri/views/MapView", "esri/widgets/Sketch/SketchViewModel", ], (Color, Graphic, Map, Circle, Point, Polygon, GraphicsLayer, SimpleFillSymbol, MapView, SketchViewModel) => { const graphicsLayer = new GraphicsLayer(); const map = new Map({ basemap: "topo-vector", layers: [graphicsLayer] }); const view = new MapView({ container: "viewDiv", map: map, zoom: 18, center: [139.5716, 35.6964] }); view.when(() => { var sketchViewModel = new SketchViewModel({ layer: graphicsLayer, view: view }); var extent = view.extent; var yDiff = extent.height / 4; var xDiff = extent.width / 4; var circle1 = new Circle({ center: new Point({x:extent.xmin + xDiff, y:extent.ymax - yDiff, spatialReference:extent.spatialReference}), geodesic: true, numberOfPoints: 100, radius: 50, radiusUnit: "meters" }); var circle2 = new Circle({ center: new Point({x:extent.xmax - xDiff, y:extent.ymin + yDiff, spatialReference:extent.spatialReference}), geodesic: true, numberOfPoints: 100, radius: 50, radiusUnit: "meters" }); var graphic1 = new Graphic({ geometry: circle1, attributes: [], symbol: new SimpleFillSymbol({color:new Color("red"), style:"solid"}) }); var graphic2 = new Graphic({ geometry: Polygon.fromJSON(circle2.toJSON()), attributes: [], symbol: new SimpleFillSymbol({color:new Color("green"), style:"solid"}) }); graphicsLayer.add(graphic1); graphicsLayer.add(graphic2); }); });   3) Click the "Refresh" button at the top-right of the map. 4) Click the red circle on the map to activate editing mode. 5) Drag the red circle to a new location (this works fine). 6) Now, attempt to drag it to a new location.  It "jumps back" to its original location, and then updates itself relative to that location according to your mouse movements.  All subsequent movements do this as well. In contrast, the green circle does not exhibit this behavior and you can move it around normally.  This is because the green circle is not an instance of Circle, but an instance of Polygon.  See line 60 above, where an object created as a Circle is "converted" to an instance of Polygon.  Therefore, this is a current workaround for this problem. ... View more