Latest Contributions by RalucaNicola1

Hi Richard, sorry for the late reply! You are right, a Geoprocessing Service is for now the clean solution, as we don't have this exposed in the API. We will add these calculations to the GeometryEngine, but as of now, we don't have them there and they will surely not be there by the summer release. And yes, this should boil down to solving the intersection of a line with the plane in which the polygon resides. One more question: is each polygon lying in a plane? I couldn't see the video, I think it's not linked.. I will try to write a small sample for this; when I have it done, I'll link it here. However, if the polygon is more like a mesh type of geometry then it might need triangulation and then it gets complicated.  ... View more

hmm still a bit confused when you say surface - does that mean an elevation surface? or do you just have polygons with height values? And are you trying to figure out only which 3D surfaces are intersected by the lines or also where exactly they intersect to do some other measurement? Anyway your use case sounds quite similar to an app Kristian Ekenes‌ wrote: https://www.esri.com/arcgis-blog/products/js-api-arcgis/mapping/build-3d-web-apps-with-your-2d-data/  about airspace encroachment, so I want to point you to it. ... View more

Hey Richard,  Can you tell us more about your use case? What are you trying to do? If you have vector features that have z values, why are you bringing in raster data? Unfortunately we don't support 3D geometry operations for now, we write that in the geometryEngine documentation: geometryEngine | API Reference | ArcGIS API for JavaScript 4.7: "A client-side geometry engine for testing, measuring, and analyzing the spatial relationship between two or more 2D geometries." ... View more

ok, I see. Yes, that makes sense to spare the requests. In 4.8 you can remove the workaround, sorry again about the bug.. ... View more

Hi Qi, awesome, sorry that you had to work around things to make it work. Next release it will be fixed and you can go back to normal workflow. One thing I thought about: is it really mandatory that you query the layer view? I tried it out and querying the extent on the layer works. Best, Raluca ... View more

Hi Auerlie, we don't have out of the box tools for calculating 3D volumes. I guess you could build your own, but it probably wouldn't be extremely accurate. I didn't really understand your workflow: what do you mean by selection of surface?  I imagine that if you wanted to calculate the volume between two surfaces, you would have to draw a polygon or somehow select the area for which you want to calculate the volume. Then you could split the polygon in a grid and for each point in the grid I would get the elevation in each of the surfaces and then calculate the volume as grid cell area * height difference. Summing up the volumes for each of the cuboids should you give you an approximation of the whole volume (not very accurate though). As for making a widget out of it, check out this tutorial: Create a custom widget | ArcGIS API for JavaScript 4.6 or have a look at this video from devsummit 2017: Building Your own Widget with ArcGIS API for JavaScript - YouTube  Raluca ... View more

ok, thanks for the data, I'll have a look at it by the end of this week and come back with a reply. ... View more

Could you guys tell me why you prefer this over the public API? If I understood correctly you want to have only one request with all the data in the beginning rather than making several requests? What is the end goal for you Yunpiao? ... View more

hmm, that sounds like a bug. Did the buildings display? Do you still have the service? It would be useful if you could pass it along so we can investigate. ... View more

First of all some theory about how this works:  1. Publishing a scene layer from an slpk will create a scene layer without an associated feature layer. Therefore, you can't query the scene layer (queries on scene layer are redirected to the associated feature layer which doesn't exist in your case). The only option in this case is to query the scene layer view. 2. Scene layer view queries on the other hand have a more limited functionality. First of all you can only query the features that are currently loaded (so not the whole layer). Second of all the number of properties that can be used for a query is limited: you can't use where for example (therefore the error). For queryFeatures only outFields and objectIds properties can be used. You don't need to send dummy variables on the renderer‌, you can set them in the outFields and that will return them in the query on the layer view (FYI @Thomas_Solow). Second: what is your use case? We might help you better by knowing what the goal is. And a few more tips: If you need to query features based on attributes then one options is to publish the scene layer from a feature layer in AGO (see here a blog post on how to do this or official documentation if you prefer) and then use the query on the scene layer which supports where and which in this case will work because you'll have an associated feature layer. Another options is to publish a feature layer with the attributes and the same objectIds as the features have in the scene layer and manually link the two like in this sample: Query a SceneLayer's linked FeatureLayer | ArcGIS API for JavaScript 4.5. ... View more

There's nothing obvious that you are missing, it's a known issue... Only the vertices get information about how they should be aligned to the ground. We can't tell where the center of the polygon should be placed because there's no geometry there. Therefore polygons that spread along the globe will have their inner parts sunk into the ground.  One thing you can do is use a local scene? that way the center of the polygon won't be underground because of the earth curvature. I noticed that the polygons paths (the margins) are also sinking. That one you can fix by densifying the path using geometryEngine. Here's an example on how to do that client side on a line so that it follows the terrain: Edit fiddle - JSFiddle  You could apply it to polygons as well. ... View more

Leave the uniqueValueInfos as they are uniqueValueInfos: [{     value: "Section_99_7",     symbol: ssiSym,     label: "Special Security Instructions" }, {     value: "Section_91_137_a"     symbol: hazardSym,     label: "Disaster/Hazard Area" }, {     value: "Section_91_145",     symbol: sportSym,     label: "Aerial Demonstration / Sporting Event" }, but instead of the renderer field add a valueExpression that will extract the type from the tfr_type columns. I'm not an expert in Arcade, so I've put together something like this: var s = "Section_21_7_a_21"; var splitArray = Split(s, "_"); var typeArray = []; for (var i in splitArray) {     IIf(i < Count(splitArray) - 1, typeArray[i] = splitArray[i], null); } return Concatenate(typeArray, "_");‍‍‍‍‍‍‍‍ Kristian Ekenes do you know if there is a straightforward way to remove the last 2 characters from a string with Arcade? This seems like a workaround. We currently don't support your last idea...volume visualization will come, but it's not on our priority list right now. I was trying to think of a workaround, but I guess you can't really connect the vertices if the 2 polygons are not the same? ... View more

ok, in this case I guess queryExtent is the best way to get the location of the popup. Happy to hear that it worked. ... View more