Latest Contributions by RalucaNicola1

I can't reproduce it (here is my sample where it works: https://codepen.io/ralucanicola/pen/OKZJKe?editors=1000). If it worked on 4.11 it means it might be a bug on our side or an intended change. It would be super helpful if you could post a code snippet of how you are using the search widget so we can reproduce it and get it fixed and provide you a workaround if possible. Does the point layer have any elevation offset? ... View more

Like Kelly said, this is a bug on our side and we'll work on a fix for 4.13. In the meantime a possible workaround is to add the layer to the map like Kelly suggested. ... View more

Hi Angelina, could you post a code snippet? There's a lot of things that could go wrong, so it's hard to tell what's going on. Another thing to try is if it works in 4.11. ... View more

So I understand that you want to search for a feature in a layer that is in your webscene and once the search widget finds it, you want to zoom to it and display more information. The features have 3D volumetric symbols and are offset from the ground. If this is correct, then here are some things are to keep in mind: the service doesn't know anything about your symbology and the offset that you apply. So when you query the service, then you will only get back the geometry and no offset (in your case I think you have to pass returnGeometry: true to the query - https://developers.arcgis.com/javascript/latest/api-reference/esri-tasks-support-Query.html#returnGeometry otherwise you don't get the geometry). So my solution would be to pass the layer that you visualize in your view directly to the SearchWidget like this: view.when(function() { var treesLayer = view.map.layers.find(layer => layer.title === "Landscape Trees") var searchWidget = new Search({ view: view, autoNavigate: true, //have tried with and without, still doesn't work autoSelect: true, //have tried with and without, still doesn't work sources: [{ name: "Trees", layer: treesLayer, searchFields: ["Tree_ID"], displayField: "Tree_ID" }] }); view.ui.add(searchWidget, "bottom-right");‍‍‍‍‍‍‍‍‍‍‍‍ });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Then it will automatically zoom to it and display a popup. Here's an example with some data from one of our samples: https://codepen.io/ralucanicola/pen/eqebWX?editors=1000 Let me know if this doesn't work for you and we can brainstorm for some other solution. ... View more

Solid is indeed the only symbol style we currently support in SceneView. We have an issue for this, so it's in our roadmap, but it's not planned for the close future... can you tell us a bit about your use case for it? I can add your use case to the issue to increase the prio a bit. We could maybe also suggest a workaround in the meantime. ... View more

Robert is right, drawing tools are currently not supported in the SceneView. ... View more

Is the data protected? I don't have access to the apps you posted. It would be super useful to be able to look at the apps, otherwise I'm really not sure what it is. Is it a Web AppBuilder application? If the data is not public could you create a small repro case with some fake data? ... View more

We released! Check out this sample to see how to make the background transparent:  Custom background for SceneView | ArcGIS API for JavaScript 4.8  Have fun! ... View more

A line has several z values, one for each vertex. That Arcade expression will not work for lines. I assume you need to set new z values for each vertex on a line. You can't do that client-side, unless you recreate all the geometries, which is not optimal. I would really recommend to correct the vertex z values in your desktop client (Pro or ArcMap, whatever you used to create the line geometry) and then to use the API only for visualization. In case the feature service is editable, you could edit the z values using JavaScript by using applyEdits: FeatureLayer | API Reference | ArcGIS API for JavaScript 4.7  Like this you can change z values, and the next time you will visualize the layer, the newly set z values will be used. ... View more

ok, got it now. More questions: so you have lines with z values for end points, but the z values are not correct? and you have the correct z values in the attributes? I'm afraid that is a workflow that you can only do with ArcGIS Pro. However, the image that you showed above in the SceneViewer can be done with the API if this is what you are looking for. In the API you can only use an offset per feature, so I don't think that helps, unless you know by how much you need to lower the horizontal pipes. This is a sample that shows how to do that: Elevation options | ArcGIS API for JavaScript 4.7  ... View more

1. What is your input data? Points? 2. Are you trying to create underground lines from given points? As Russ said, as long as you have the point coordinates (even if z values are just in the attributes) and you know which points should be connected to create a line, then you can create the graphics client side (see this sample: ArcGIS API for JavaScript Sandbox) The best would be to do this in ArcGIS Pro and publish it as a line feature layer. But seen the fact that you don't have ArcGIS Pro, then you can also do this in code on the client side (as long as you don't have too many lines, otherwise it might not be very performant). ... View more

In the end the data will be a multipatch, which is the standard for most 3D object scene layers. Performance depends on how detailed the area is, a whole state sounds like a pretty big surface, so the coarser, the better...but I can't give you any clear numbers. A bit of explanation with regards to scene layers: at the platform level (so in Pro and ArcGIS Online) scene layers can have multiple data sources: points, multipatch, integrated mesh, lidar data. In the API we distinguish between them even further: SceneLayer can use points or multipatch, IntegratedMeshLayer uses only drone mesh data and PointCloudLayer uses lidar data. In your case you have multipatch data which is more or less standard for 3D Object SceneLayer. Here is an article with this overview: A guide to SceneLayers | ArcGIS API for JavaScript 4.7   ... View more

Yes, scene layers are also supported in the API, you can see some examples here: SceneLayer Samples. They are mostly used for displaying building data, but some users also display geological surfaces with it. I just had another idea, but this depends a lot on how big the area that you want to visualize is and what data you want to visualize: we also have a Mesh API, that can be used to display 3D geometry (this is not used in the SceneViewer). Have a look at this sample: Low poly terrain using mesh geometry | ArcGIS API for JavaScript 4.7  The surface is generated based on an elevation layer. This surface is created on the client side and can not be persisted in AGOL. It's just for visualization purposes. It also probably doesn't perform very well when you have a big area... Sure, keep it open, we don't really have a clean solution for it right now. ... View more

Hi Richard, sorry, but this is currently not possible out of the box with the JavaScript API. It is planed, but not for this year. You would need to do some sort of workaround. In  some web scenes of geological surfaces, they convert the data to a scene service. For example in this scene: Scene Viewer. Is this what you are after? I've never done it myself, but I've asked around and the following workflow would lead you to something like that: - Use Raster to TIN to covert your DEM to a polygon based representation: http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/raster-to-tin.htm - Use Interpolate Polygon to Multipatch: http://pro.arcgis.com/en/pro-app/tool-reference/3d-analyst/interpolate-polygon-to-multipatch.htm - for large areas, you can experiment with having a grid of polygons (rather than one big one) to create multiple multipatch features per surface for improved performance. ... View more

Hi James, could you post a snippet with your code? That way it's easier to debug... But on a first glance looks like you're passing a symbol layer directly to the constructor of the symbol. You should pass it to the symbolLayers property, like this:  symbol: new MeshSymbol3D({    symbolLayers: [       new FillSymbol3DLayer({         material: {            color: "#ffffff"         }      })    ] })‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more