Latest Contributions by KristianEkenes

Hi Selvaraj, Could you be a little more specific with your issue? Are you having trouble with QueryTask, zooming to a feature's extent in general? Or only in the SceneView (you get it to work in MapView)? I was able to query features using this sample as a base. Here is my sample app in a jsbin: JS Bin - Collaborative JavaScript Debugging Here are the highlights: QueryTask - This module essentially works the same as it does in 3.x. The main difference is that it returns a Promise instead of a Deferred, so to get the features you need to use .then(). This also allows you to chain multiple functions, which makes your code easier to read. If you're not familiar with using Promises, I encourage to you read the Working with Promises page in our SDK. ZoomTo - This can easily be done using the animateTo() method on the view. You can animate to a point, geometry, graphic, ViewPoint, and camera (only in SceneView). In my sample app, I passed in the first graphic returned from the query. You are supposed to be able to animate to an array of graphics or geometries, but I wasn't getting that to work properly in my app. That may be a bug, so I'll look in to it. Here are the main lines of code you should focus on: //Set base parameters of query     var q = new Query({       distance: 150,  //get features within 150ft of mouse click       units: "feet",       returnGeometry: true,       spatialRelationship: "esriSpatialRelIntersects",       outFields: ["*"]     });         view.then(function(){       view.on("click", qFeatures);     });         //Executes a query task based on mouse click     function qFeatures(evt){       q.geometry = evt.mapPoint;             var qTask = new QueryTask({         url: featureLayer.url       });             qTask.execute(q).then(function(response){         return response.features;       }).then(highlightGraphics).then(zoomTo);  //chain functions     }         var highlight = new SimpleMarkerSymbol({       color: "yellow",       size: 8,       outline: new SimpleLineSymbol({         color: "red",         width: 8       })     });         //highlight queried features     function highlightGraphics(graphics){       resultLayer.clear();       graphics.forEach(function(item, i){         item.symbol = highlight;       });       resultLayer.add(graphics);       return graphics;     }         //animateTo those features - This acts like a zoomToExtent method     function zoomTo(features){         view.animateTo({           target: features[0],  //you should be able to pass the entire array here           scale: 1200         });     } Does this help? This sample should work in a SceneView as well; although the FeatureLayer rendering doesn't perform great at the moment, but you still should be able to observe the animation to the graphics. ... View more

Is the following line pointing to your proxy file in some way? esriConfig.defaults.io.proxyUrl = "localhost:8083"; What type of proxy are you using (PHP, JSP, DotNet)? ... View more

Austin, Thanks for posting the suggestion. This will be discussed and evaluated in the near future. ... View more

Yes, there are many good use cases for subsurface capabilities. It will be supported by the time 4.0 moves out of beta. We're just don't have a timeline on when it could be released while we're still in beta. ... View more

Chris, Tim is correct. If you can't find it in the API reference, then there is no current support. The features you're familiar with in 3.14 will eventually be integrated into 4.0 by the final release next year. ... View more

I should have noticed the proxy extension. Sorry about that. 😕 Try using the urlUtils like you do in 3.14. The import is different though: It's now "esri/core/urlUtils". This isn't documented, which means things can change in beta2, so keep an eye out for doc updates related to this in the future betas. ... View more

Did you include the URLs you want proxied in your proxy.config file? Which proxy are you using, PHP, DotNET, or JSP? ... View more

You should only expect updates coming with each beta release. ... View more

Cees van Altena​ Yes, this is a bug. However, you can also set the height of the view directly in the MapView constructor (view.height). Here's a link to the doc: https://developers.arcgis.com/javascript/beta/api-reference/esri-views-MapView.html#height. When you set the height inside the constructor instead of CSS, it seems to work as expected in your sample. View my bin here demonstrating this: JS Bin - Collaborative JavaScript Debugging This can be a current work around to your issue, although setting the CSS directly should work as well. ... View more