Latest Contributions by RalucaNicola1

Hi Ryan, when visualizing data at the poles the best is to use a polar projection. However, then you can only use a local scene, because global scenes only support WGS84 and WebMercator. Here is an example of a local scene with Arctic Imagery: Scene Viewer. Can you try to overlay your data here and if you still have this issue write back to me? ... View more

Sorry for the late reply. This is currently not possible out of the box and it is not on our road map.  Thinking about it, it should be possible to watch for updates on the observer and offsetting it. There is a risk in running into an infinite loop, that's why I am removing the watcher when I set the observer with the new height. Also the user experience is not so nice if I offset the observer right after the user changes it, so I am waiting for the user to not interact with the view anymore. And to catch also the case when a user places an observer for the first time (the view is interacting in that case), I am also checking whether the change in value was from null to a new value. Long story short, here is the code: https://codepen.io/nicolaraluk/pen/wvGRxPE?editors=1000  Jason Jordan‌ Jethro Leevers‌, let me know if this helps. ... View more

We extrude along the edges of the polygon and the interior of the polygon might end up under the terrain in case the terrain is higher in that area. As Rickey suggested, a workaround might be to try and generate multiple polygons and extrude them. So unfortunately, no straight-forward solution as of now. ... View more

Hi, Unfortunately not  that project we worked on back then closed without adding this feature. It's still on our backlog, but it is not planned for the next few releases. This would require quite a big change in our current lighting system and that makes it hard for this feature to get to the top of the prio list. Can you tell me a bit about your use case Michael? I'll add it to our list of use cases for this feature. ... View more

Thanks Michal, we have a ticket for this waiting in the pipeline and I've added your use case to it. I'll let you know when we'll start working on it. ... View more

Hi Benett, sorry for the late reply! Indeed, this is a bit of a more advanced workflow and the ArcGIS API for JavaScript doesn't support it currently.  However, your input is very useful, I added it to our editing use cases for when we'll start working on editing 3D geometry. ... View more

Hi Bennett, From what you said, you want to build a web application, so here's some state of the art for ArcGIS API for JavaScript. Can you explain to me a bit your use case and how you imagine the user experience? So your initial data are polygons (footprints of buildings I assume)? And then the user goes in and starts extruding the polygon? How would he add the rooftop?  Currently what we have in the API in 4.14:  - sketching a polygon and drawing it with a given extrusion: Sketch in 3D | ArcGIS API for JavaScript 4.14  - importing a 3D model as a GLTF and scaling/rotating it and moving it around: Import glTF 3D Models | ArcGIS API for JavaScript 4.14  We are now working on editing the z values of points/lines/polygons and their vertices. This should be a new feature in the upcoming release. However, from what you wrote it sounds like you would really need to modify 3D geometry, which is currently not possible and we aren't going to work on it in the next releases... ... View more

Hi, that would be possible, but I'm not sure it's optimal, there are a lot of queries involved and I'm not sure you need them. Can you tell me more about your use case? If you have time attributes in the SceneLayer I guess you could use a watch on the timeExtent for the TimeSlider and then when it changes, you could set a filter on the SceneLayerView where you filter by those attributes.  Also if you can share the data then I could create an example. Thanks, Raluca ... View more

Unfortunately there is no client-side hack around this. The limitations are also described in the TileLayer documentation. Otherwise the tiling scheme looks good to me. Let me know if you run into other issues. ... View more

Sorry for missing your question Michael, currently you can change the style or remove the highlight by setting highlightOptions on the view. Be aware though that these are set globally. We want to change this behavior for the future but we're still in the design phase. Could you give us more info on why do you want to change it? Is it because of the color, or does is it obscure the original object too much? That would help us to design the new behavior. If it's just about the bug you mentioned where the graphic becomes invisible but it still keeps the highlight, then we fixed that for 4.14.  ... View more

Unfortunately we don't guarantee anything about the 'next' version. I would really not recommend using it in production or live demos. I spoke to my colleagues and I modified my previous answer as well, best is to use the cdn version after the official API release date. Until then we make patches and the API can still change. For the conference, maybe you could record a video of how it will work and tell the users this will be available starting with December 19th? Sorry that I can't give you any better news... ... View more

Hi Efim, this is a documentation problem, I'll work on getting this fixed in the next documentation update. Until then, the solution is to pass the AbortSignal in the esriRequest method:  // This method fetches tiles for the specified level and size. // Override this method to process the data returned from the server. fetchTile: function(level, row, col, options) { // call getTileUrl() method to construct the URL to tiles // for a given level, row and col provided by the LayerView var url = this.getTileUrl(level, row, col); // request for tiles based on the generated url return esriRequest(url, { responseType: "image", signal: options.signal }).then(...) ... }‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Here's the working sample: https://codepen.io/ralucanicola/pen/abbjwax?editors=1000  Thank you for reporting this! ... View more

oh I see, if your z values match the terrain elevation then you could se `elevationInfo.mode = "absolute-height"`. If they don't match then maybe try setting the `elevationInfo.mode = "relative-to-scene"`. That ignores z values and aligns the vertices on your lines to the ground (but also extruded polygons and buildings in case you have that in your scene!). ... View more