Latest Contributions by RalucaNicola1

ArcGIS Online release is estimated for December 10th, but API official release (final version with patches, documentation site, plugins, typings and other resources) is December 19th. ... View more

Hi Navya, I can't access your service. Do your features come with z values? If you make it public, I can have a look. Generally though, we only align lines with the ground at the point where they have vertices. So to get a better alignment you might also need to densify the vertices. (no need to modify your original data, you can also do it with geometryEngine.densify()). And for more info on different elevation modes you can read about it here: FeatureLayer | ArcGIS API for JavaScript 4.13  ... View more

Happy to hear that it works! next is the current development build and it is meant to be used to try out new features and see that they work for your use case. For production ready apps only use the official release version. Once we release in december, next will be the development build reflecting the 4.15 release... Hope this helps, let me know if you have any other questions. ... View more

Hey, You've got a bunch of errors in the code: you should specify the renderer type (I assume it's a SimpleRenderer), then the `defaultSymbol` becomes `symbol`. Your line symbols should have a `line-3d` type, not a `polygon-3d` type. Also it's important that you specify the color, otherwise you won't see anything. Here's how the code would look like with the changes mentioned above: require([ "esri/Map", "esri/views/SceneView", "esri/layers/FeatureLayer", "esri/widgets/Legend" ], function(Map, SceneView, FeatureLayer, Legend) { var map = new Map({ basemap: "topo-vector", ground: "world-elevation" }); var view = new SceneView({ container: "viewDiv", map: map, zoom: 15, center: [103.805699, 1.276566], heading: 300, tilt: 75 }); const options = { profile: "quad", cap: "round", join: "miter", width: 5, height: 30, color: [200, 200, 200], profileRotation: "all" }; var renderer = { type: "simple", symbol: { type: "line-3d", symbolLayers: [ { type: "path", profile: options.profile, width: options.width, height: options.height, material: { color: options.color }, join: options.join, cap: options.cap, anchor: "bottom", profileRotation: options.profileRotation } ] } }; const PipelineLayer = new FeatureLayer({ url: "https://services6.arcgis.com/itEfD6Bf5W0iWJuO/arcgis/rest/services/PipeLine1/FeatureServer/0", elevationInfo: { mode: "relative-to-ground", offset: 3 }, renderer: renderer }); map.add(PipelineLayer); });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

You're right about that, I'll make sure to add these limitation in the documentation for all tile layers that use a tiling scheme. ... View more

Hey, It sounds like your tiling scheme does not fulfill these requirements:  256x256 or 512x512 pixel tiles Scale levels must increase or decrease by a power of two At level  0  there shouldn't be more than 30 root tiles. All tiled layers must have the same tiling scheme and SpatialReference. You can read about it in the TileLayer documentation: TileLayer | ArcGIS API for JavaScript 4.13  The coordinate system shouldn't be a problem as long as you have a local scene. ... View more

Hi Arne, navigating underground can be tricky and even more so if you try to pan against the horizon. So adding features in the background is a good advice. However, which API version are you using? We did make some improvements in navigation to make it a bit more stable a couple of releases ago. And just out of curiosity, is navigation in your scene more difficult than in this sample? Local scene  ... View more

This is a feature indeed, in 3D you might sketch objects that get occluded by other features and then highlight is the way to see the entire shape of your sketch when some parts are occluded.  If you absolutely want to get rid of it, then I would go for Robert's solution. Not very nice, but the only one for now. We were discussing how to improve this behavior and one option would be to make the highlight more subtle. Would that work for you or would you just want to be able to turn it off? ... View more

Unfortunately this is a bug in the API and we don't have a workaround at the moment. We have an issue open for it and we'll look into it. Sorry about the inconvenience. ... View more

I'm not sure I understand your question very well, but assuming you have a style item with myltiple symbols (either published by you or by esri) you could request the symbols in that style and they have thumbnails that you can display in a drop-down list.  So for example for the icons style: https://www.arcgis.com/home/item.html?id=a91ce080e9414810b71d55edc51b5837 you could make a request to get the item and then request the data associated with it using fetchData(). const portal = new Portal({url: "https://www.arcgis.com"}); portal.load().then(function() { // Create query parameters for the portal search const queryParams = new PortalQueryParams({ query: "id: a91ce080e9414810b71d55edc51b5837" }); // Get the item based on the queryParams created from portal above portal.queryItems(queryParams).then(function(items){ return items.results[0].fetchData(); }) .then(createDropDown); });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I made a live sample here: https://codepen.io/ralucanicola/pen/PoYNrNJ?editors=1000  ... View more

I have the feeling there's something specific about the service. Just to make sure: is this a point geometry FeatureLayer with ObjectSymbol3DLayer symbol? I don't understand why you would get an error about passing in a multipatch geometry... ... View more

As Robert mentioned, Kelly provided a workaround for this: https://community.esri.com/message/867376-search-widgetauto-navigate#comment-869293. Let us know if you encounter issues using that. And I'd like to reinforce what Ken and Joshua said: posting a user's name as the question subject is not helpful at all, but code snippets are, so that we can reproduce the issue and help with it. ... View more

Hey James, I think I'll need a bit more help to figure out what's going on. Using layers.find() is just a way of getting the layer from your webscene, so that shouldn't really cause any issues. Because you wrote "at times" it sounds like there might be a racing condition and the layer might not be loaded yet when the  layers.find()  gets run? Do you have the problem that the camera doesn't pan for the same features or does it randomly fail for different features? Do you get any console errors? Are you still implementing the view.goTo() separately on `search-complete`? If you could post an updated version of your snippet that would help a lot. Thanks! ... View more