Latest Contributions by KristianEkenes

I'm looking into this as well... will reply if I learn anything. FYI, the expression could also be condensed to the following (but it doesn't really matter. Depends on your preference): var unitVal = $feature.unit; var stVal = $feature.snumber; IIF(unitVal == ' ', stVal, Concatenate([stVal,unitVal], ':'));‍‍‍ ... View more

Sorry. Syntax error. Here's the corrected version of an alternate approach somewhat similar to IN:  var items = [ “Green River Plant”, “Red Creek Mine”, “Blue Mountain Refinery”, “Yellow Enterprises” ]; IIF ( IndexOf(items, $feature.Facility_short) > -1, $feature.Facility_short, null); ‍‍‍‍‍ ... View more

I presented on this topic at Dev Summit last year (and will again this year). Here's a recording of that presentation in which Dave Bayer and I show a lot of different samples demonstrating ways you can use GeometryEngine: Home | Esri Video  Just a little background...GeometryEngine was originally designed for editing apps that required immediate feedback to the user, such as performing measurements, topology validation, etc. While many of the methods cater more to editing apps, there are probably other creative scenarios where you may find it useful. I'm always interested in seeing how others are using it in their own apps. ... View more

In that case, you can use the workflow of the second snippet. Call load() on the webmap, this gets the layers in the webmap. Then you can call load() on individual layers to load them when you want in the app and add them to the map. Here's a test case: JS Bin - Collaborative JavaScript Debugging  var webmap = new WebMap({   portalItem: { // autocasts as new PortalItem()     id: "f2e9b762544945f390ca4ac3671cfa72"   } }); var view = new MapView({   map: new WebMap({     basemap: "satellite"   }),   container: "viewDiv" }); webmap.load().then(function(){    var layers = webmap.layers;    var firstLayer = layers.getItemAt(0);    console.log("first layer loaded? ", firstLayer.loaded);    return firstLayer.load(); }).then(function(layer){    view.map.add(layer); });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ You could also query a portal or a portalGroup, but it sounds like you really want the layers from a specific webmap. If that's the case, then you should use this workflow. ... View more

I'm not entirely familiar with the other workflow you're using, but Layer.fromPortalItem() isn't designed to take a webmap id. It can only accept item ids of individual layers. To access individual layers of a webmap, you can add the webmap to your view and run the following: view.then(function(){ webmap.layers.forEach(function(layer, i){    console.log("webmap layer ", i, ": ", layer); }); });‍‍‍‍‍ see the live sample here: JS Bin - Collaborative JavaScript Debugging  Or call load() on the webmap outside the view: webmap.load().then(function(){ webmap.layers.forEach(function(layer, i){    console.log("webmap layer ", i, ": ", layer); }); });‍‍‍‍‍ ... View more

2D labeling isn't supported in 4.2. FeatureLayer | API Reference | ArcGIS API for JavaScript 4.2  A lot of the focus on the 4.x series of the API has been driven by the 3D components. 4.x will support 2D labeling in the near future. ... View more

Hi David, The smartMapping API is all about generating a new renderer based on the statistics of your data. So the existing renderer on your service doesn't play a factor in this scenario. I'll try to go over the workflow as best I can. Please continue to ask questions if this is still confusing or if it's not exactly what you're looking for. > Turns out the FetureLayer in the sample has this all set up with "Drawing Info" in the FeatureLayer's service: https://services.arcgis.com/V6ZHFr6zdgNZuVG0/ArcGIS/rest/services/Enriched%20World%20Cities/FeatureServer/0 This drawingInfo is ignored in the sample. We want to generate a renderer on our own when the data loads. The renderer we generate will contain the visual variables you're looking for. So we call call colorAndSizeRendererCreator.createContinuousRenderer() to do this. The response object from this method also contains the visual variables conveniently so you don't have to search for specific ones in the renderer. To call the method, first set your params... var params = {     layer: povLyr, // your layer     basemap: map.basemap,  // basemap to choose "best" color scheme     field: "POP",  // field used to generate the visual variables     view: view,  // the initial sizes are based on your current view (this will actually likely change in a future release)     symbolType: "3d-volumetric",  // This indicates 3D object symbols will be used.     minValue: 0  // this is optional };‍‍‍‍‍‍‍‍ >  So how do I set up these important statistics and visualVariables for my schools FeatureLayer by JS code. When the method resolves you can then grab the generated visual variables and statistics objects and set them in the slider widget. They are properties of the response object. See - univariateColorSize | API Reference | ArcGIS API for JavaScript 4.2  colorAndSizeRendererCreator.createContinuousRenderer(params) .then(function(response) {   // set generated renderer on the layer and add it to the map   povLyr.renderer = response.renderer;   map.add(povLyr);   // set the queried statistics and generated visual variable   // to the slider parameters     var sizeVV = response.size.visualVariable;   var colorVV = response.color.visualVariable;   var sliderParams = {     container: "sliderDiv",     statistics: response.statistics,  // this is generated for you as well     visualVariables: [sizeVV, colorVV]   };     var slider = new UnivariateColorSizeSlider(sliderParams); });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ The histogram is optional, but if you want to use that as well, then follow the example code you're looking at. In short, you don't need visual variables on the default renderer on the layer for this to work. If you already have them, then you can use them without generating the renderer every time the app loads. in that case you could do something like the following: layer.then(function(){   var renderer = layer.renderer.clone();    sliderParams = {       container: "sliderDiv",       visualVariables: renderer.visualVariables       statistics: //stats object generated from summaryStatistics()    };  });‍‍‍‍‍‍‍‍ For the stats use: summaryStatistics | API Reference | ArcGIS API for JavaScript 4.2  But if you use createContinuousRenderer() then this is already done for you under the hood. > There must be a straightforward code example to set up a common slider scenario with size, color, field max/min values, etc. This is about as straightforward as it gets. If the snippets on the description page are confusing, then take look at the code in the sandbox. That should provide more context as to where the visual variables and statistics are coming from. We can also look at reworking that description so it doesn't cause as much confusion. I'll be working on a blog post going into a little more depth on this topic. Will link to it when it goes live. Hope that helps! ... View more

Perfect. Thanks. ... View more

We've seen problems with the textHalo in Chrome in certain scenarios and have a couple of open issues for it. This one looks slightly different though. Can you send a live test case so we can check it out further?  Thanks. ... View more

When loading a symbol from JSON the range is 0-255.  See ArcGIS REST API. ... View more