POST
|
As previously mentioned, we are working on exposing more functionality in a future release, but for now we only exposed the widget and the viewmodel, which allow you to plug the widget in your app and use as is. The most that users can do at the moment is to have their own UI for it and listen for changes in the state. Currently with public API you can't programmatically activate the widget, nor deactivate it. You also cannot change the style. My question is again: can you tell us your use case? We will definitely expose the activation mechanism once we decide on the public API. But changing the style is currently not in our radar. Unless we have feedback on how this might be used.
... View more
06-04-2018
07:36 AM
|
0
|
0
|
875
|
POST
|
nice, in 4.8 you'll have it one more month to go with a dark universe hehe
... View more
05-30-2018
01:26 AM
|
0
|
0
|
575
|
POST
|
Hi Michal, to me it sounds like you want to create your own 3D measurement tool? Could you give us feedback on why you need to do this? We tried to design this tool so that people don't have to do all the work from scratch. Indeed, most of it is internal API and the actual calculation, the line generation and the labeling are not public and we don't really plan to make them. We use WebGL to render the 3D line and the labels are HTML elements. We considered adding options to change the color of the line. Would that help you already? Let me know what your requirements are, as I mentioned in the other post we are still working on the public API.
... View more
05-29-2018
02:45 AM
|
0
|
1
|
875
|
POST
|
hmm now I wonder in which software you need to do this. If it happens to be the ArcGIS API for JavaScript, then in one month we will have this feature. So watch out for version 4.8. In the SceneViewer in ArcGIS Online we won't have that functionality yet. In any case, I'd be curious to hear about your use case for setting an image behind the scene.
... View more
05-29-2018
02:34 AM
|
2
|
1
|
575
|
POST
|
Can you share a snippet to repro? Popup shows in this sample: Add edges to a SceneLayer | ArcGIS API for JavaScript 4.7
... View more
05-28-2018
04:09 AM
|
1
|
0
|
506
|
POST
|
Did you pre-calculate the elevation in ArcGIS Pro and then published the lines? I guess you can also do that client-side by manipulating the z values in the polyline geometry, but it's probably better to save the computation for something else if they have values that never change.
... View more
05-25-2018
11:18 AM
|
0
|
0
|
660
|
POST
|
Hi Michal, The measurement widgets in 3D are still work in progress. However to have more control of the interaction I would advise to use the ViewModel of the widget: DirectLineMeasurement3DViewModel | API Reference | ArcGIS API for JavaScript 4.7 There you can watch for changes of the `state` attribute to figure out when the measurement started. The pattern in the API is that all properties are watch-able, so we don't really use event listeners so much. You can read about it in this guide topic: Working with properties | ArcGIS API for JavaScript 4.7 Indeed, for now the only public way to stop measuring is to destroy it. We are working on a public API that would work for all the widgets that have an enabled/disabled state, but we didn't implement it yet.
... View more
05-25-2018
07:34 AM
|
1
|
0
|
497
|
POST
|
The webGL report for your machine contains Major Performance Caveat set to true and it uses Software rendering: Unmasked renderer -> Google Swiftshader. It might be a problem with Chrome blacklisting your GPU. A possible solution could be to update the GPU driver on that machine. In general there might be certain GPUs that are blacklisted by browsers and when the user is exactly on such a machine the only thing you can do is to give him a warning message. In the API we catch this case and we don't create the view. I guess the safe thing to do is to catch when the view fails to create and send an error message to the user that they could try to update their driver. Practically in code you can do this: view.when(function() {
// View successfully loaded, show viewDiv
}).catch(function(err) {
console.log(err);
// { message: "WebGL is required but not supported.", ...}
}); Here is the whole sample where we show app developers how to catch these cases: ArcGIS API for JavaScript Sandbox Hope that helps.
... View more
05-18-2018
05:43 AM
|
0
|
1
|
964
|
POST
|
hmm I can't reproduce...can you open this link and send me a screenshot of the page? WebGL Report In case you don't want to post your setup here, feel free to send it to my email: rnicola@esri.com.
... View more
05-17-2018
01:37 AM
|
0
|
0
|
964
|
POST
|
ok, let me know more, that looks like we should be able to repro, but we haven't seen this behaviour so far.
... View more
05-14-2018
01:39 PM
|
0
|
2
|
964
|
POST
|
Late to the party. Is this still an issue? If so, can you try with 4.7? And if it still doesn't work can you tell us what os are you using + version, which browser version? Maybe we can reproduce if we happen to have the same machine config.
... View more
05-14-2018
12:13 PM
|
0
|
4
|
964
|
POST
|
Did I understand correctly that you want to visualize the buildings based on the status or type of the parcel that is used for the query? The most performant way to achieve this would be to do a preprocessing in ArcGIS Pro: spatial join of buildings with polygons and add the corresponding attributes to the buildings. Now if your building data is "light" and you need to do this on the client side, a unique value renderer based on object ids might work too. I made a new example where I change the color of the buildings returned from the query based on the objectid. This is not optimal though, if there are thousands of unique values at some point the browser might run out of memory. SceneLayer polygon intersection with renderer
... View more
05-14-2018
09:33 AM
|
2
|
1
|
705
|
POST
|
Awesome, happy that it works. We'll also get it fixed to not choke on null values. Thanks for sharing.
... View more
05-13-2018
02:54 PM
|
0
|
0
|
1066
|
POST
|
Does your scene layer have an associated feature layer? You can check that with the getFieldUsageInfo method. If `supportsLayerQuery` is `true`, then you can do spatial queries and your query above only needs the spatial relationship and the spatial reference. Here is a working snippet that is setting a polygon geometry on a query and when the query executes it returns all the ID's of the buildings that intersect that polygon: SceneLayer polygon intersection. The important part is: var query = sceneLayer.createQuery();
query.geometry = polygon;
query.spatialRelationship = 'intersects';
query.inSpatialReference = SpatialReference.WebMercator;
query.outSpatialReference = SpatialReference.WebMercator;
sceneLayer.queryObjectIds(query)
.then(function(result){
console.log(result);
})
.catch(function(err){
console.log(err);
});
... View more
05-13-2018
02:37 PM
|
2
|
3
|
705
|
POST
|
ok, here's a snippet, I hope it helps somehow: Edit fiddle - JSFiddle It is a very restrained case: polygons are planar, no inner rings and you always look at the intersection of a vertical line with the polygons. For the more complex case where your polygon is not planar you would have to triangulate the polygon and then check each triangle to see if it intersects with the line.
... View more
05-11-2018
01:00 PM
|
1
|
1
|
1811
|
Title | Kudos | Posted |
---|---|---|
1 | 01-24-2024 04:54 AM | |
1 | 01-23-2024 02:52 AM | |
3 | 01-19-2024 12:49 AM | |
4 | 03-27-2023 10:34 AM | |
7 | 03-13-2023 08:00 AM |
Online Status |
Offline
|
Date Last Visited |
Sunday
|