Latest Contributions by KristianEkenes

Labelling does work in beta 3. The issue Marc is referring to is slightly different. It doesn't refer to data attributes. See this example of how you can add labels in 3D - Symbol layers outline This uses polygons, but the same principles should apply to points. Here's the code for the sample: esri-js-samples/symbol-layer-outline.html at master · ekenes/esri-js-samples · GitHub ... View more

This will be possible with the 4.x JavaScript API (CityEngine not required). The tools you describe would need to be developed on your own, but this type of app would certainly be possible. Note that feature editing won't be part of the 4.0 release, so you would need to look out for 3D editing coming in a future release post 4.0 (although if you're saving to a text file, feature editing may not necessarily be required, but it could certainly make your work easier). ... View more

Hmmm. This doesn't look right. I can see the popupTemplate in the SceneViewer but as you said, it doesn't display correctly in the app. Could you file a bug report for this so we can take some time to look at what's going on in this case behind the scenes? In the mean time, you can do the following work around with  the API. Since the view is a promise and doesn't resolve until the scene's resources have loaded, you can chain another function and set a custom popup template on the layer. .then(function(){         var content = "{*}";         var title = "Whatever you want";                 var pTemplate = {           content: content,           title: title         };                         var lyrs = view.map.layers;                 var droneLyr = lyrs.find(function(lyr){           return lyr.id === "3f14aa6ac0a94ebeb7794744b1578cb1";         });                 droneLyr.popupTemplate = pTemplate;      }); Here's a live view at the updated app on jsbin: JS Bin - Collaborative JavaScript Debugging Hope that helps! ... View more

The options between MapView and SceneView are not the same for animateTo() in beta3. This will change since we're still refining the design for animateTo(). We are trying to keep the two methods as consistent as possible, but be aware that it does not mean the options for animateTo() will be equal in MapView and SceneView when we release 4.0 final. This may change in a future release after 4.0, however. ... View more

> Are you saying that elevationInfo will be a property in the final release of 4.0? Yes, but only for points. Not multipatch geometries. > This is functionality I ultimately seek for multipatch (and all) scene layers. You can easily do this in ArcGIS Pro for all types of features. Something to keep in mind is that Pro, being a desktop application, does not have the same limitations as web applications because it has more resources at its disposal (since it's a 64-bit application). Implementing elevationInfo for multipatch geometries on SceneLayers has proven to be quite expensive in JavaScript. You would see a significant hinderance to your performance depending on the number and complexity of your features. Improving performance of 3D apps in the browser is something we are constantly striving to do. > With all this said, I still think that adding the elevationInfo property and functionality to SceneLayer is important so as to mitigate for when web map users want to turn off the elevation layer (if the option is provided) they won't see floating scene layers. Additionally, it would be nice if when publishing the scene layer, the elevation properties in the ArcGIS Pro layer were also published with scene layer so it was automatic That's great that you were able to use a tool to store the actual z-values of your features. I can't speak for ArcGIS Pro, but I can reach out to someone from that team who can chime in. For now, I would make a decision between using elevation, or not in the web application(s) you're working on since it's not easy to switch between the two. Is switching elevation on/off a requirement of your application? ... View more