nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SceneLayer and ScenLayerView query support

Yunpiao_WhitneyBai

Hello,

I published a sceneLayer to AGOL through a scene layer package. I'm trying to query the scene layer view / this scene layer using queryFeature() method. But I found that none of the attributes support query when I use getFieldUsageInfo(field) to check the field.

Since the this scene layer contains a large dataset, I really want to query the layerView instead of the whole layer using queryTask or linked Featurelayer. Does anyone know how can I fix this issue to make the field support query?

thanks,

Najděte více příspěvků označených jako

Accepted answers

All comments

Yunpiao_WhitneyBai

Hi Raluca,

Sorry for the late response. Here are some data some data you can use for testing. Case#01955480.ppkx - Google Drive

The building can display correctly but only with the drawing info.

Also, I found that if I publish feature class with z value, the z value actually get stripped off if it is a donuts polygon. We really hope can solve some of the publishing issue with scene layer.

thanks,

RalucaNicola1

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?

RalucaNicola1

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.

Yunpiao_WhitneyBai

I tried to remove the where clause and use a filter after it is resolved. And it works now. I actually tried hack into renderer.requiredFields instead of adding dummy field. I guess it works in the same way.

thank you

Yunpiao_WhitneyBai

Hi Raluca,

Thanks for your detailed explanation. Actually, I tried exactly same thing to publish scene layer from pro, but I found the field information is not included when I tried to publish a scene layer using feature service in AGO. Below is a sample back to July this year. The scene layer published from feature service only includes drawing information and no fields info at all. Therefore, I choose to use slpk instead. Do you have any idea why this happens?

thanks,

ThomasSolow

Raluca Nicola wrote:
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).

That's a good point. For most users this does seem like the right approach.

But if you set outFields on the Query, the layer will send one request to the scene service for each attribute in outFields, and this question did specify wanting to avoid querying the service.

SceneLayerView.queryFeatures seems to stick to what's in the client already as long as you don't specify outFields. The goal of forcing the scene layer to fetch attributes with dummy variables (or however you do it) is to keep subsequent queries for specific features in the client while still including all the attributes the user is interested in.

Eliminating those later requests in exchange for requesting the attributes up-front may be of questionable value, but there are probably some situations where it's a good idea. Imagine you know in advance that you want access to a certain field on every feature that gets rendered, say for a feature table, or in order to mark each feature in a custom way.

RalucaNicola1

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.

ThomasSolow

Try setting the where property of your Query object to null. Setting outFields to null is also probably a good idea.

Yunpiao_WhitneyBai

Hi Thomas,

Thanks for the response.

I tried to add additional visualVariables to my sceneLayer before the query, and It worked, I can see that my layer.renderer.requiredFields has those additional fields that I added in visualVariables, but still I'm catching errors with queryFeatures().

If I use the sceneLayer.queryFeatures(), it gives me this:

If I use its sceneLayerView.queryFeatures(), I got an different error:

Thank you

ThomasSolow

You could use various methods to force the scene layer to fetch the fields you're interested in. One way to do this is to modify the visualVariables of your simple renderer (assuming you're using a simple renderer) by adding "dummy variables," like this:

<SPAN class="punctuation token">{</SPAN>
&nbsp; type<SPAN class="punctuation token">:</SPAN> <SPAN class="string token">"opacity"</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp; field<SPAN class="punctuation token">:</SPAN> <SPAN class="string token">'NAME'</SPAN><SPAN class="punctuation token">,</SPAN>
&nbsp; legendOptions<SPAN class="punctuation token">:</SPAN> <SPAN class="punctuation token">{</SPAN>
&nbsp;&nbsp;&nbsp; showLegend<SPAN class="punctuation token">:</SPAN> <SPAN class="keyword token">false</SPAN>
&nbsp; <SPAN class="punctuation token">}</SPAN>
<SPAN class="punctuation token">}</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

This will force the scene layer into fetching the attribute NAME. Then, when you perform sceneLayerView.queryFeatures() the returned graphics will have the NAME attribute.

You could also overwrite the collectRequiredFields method on your render like this:

renderer<SPAN class="punctuation token">.</SPAN>collectRequiredFields <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">function</SPAN><SPAN class="punctuation token">(</SPAN>fields<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">{</SPAN>
&nbsp; sceneLayer<SPAN class="punctuation token">.</SPAN>fields<SPAN class="punctuation token">.</SPAN><SPAN class="token function">forEach</SPAN><SPAN class="punctuation token">(</SPAN>fieldInfo <SPAN class="operator token">=</SPAN><SPAN class="operator token">></SPAN> fields<SPAN class="punctuation token">[</SPAN>fieldInfo<SPAN class="punctuation token">.</SPAN>name<SPAN class="punctuation token">]</SPAN> <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">true</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="punctuation token">}</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

That should force the scene layer to fetch all fields, but it might break something else. When I try it on a sample layer it looks like one of the fields is not able to be fetched, so a lot of errors get thrown.

Keep in mind that the attributes on the scene layer can't be changed. My understanding is that this is what the companion feature layer is for.

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.