POST
|
Thanks for reporting, this seems to be a bug. Sent to dev team for further investigation. I did a few tests but at the moment I can't provide a good workaround. Use "on-the-ground" of course if that's an option. Or clone/recreate the whole layer (with new callout config in constructor), but clearly not great either depending on your use case. Will keep you posted if more intel comes up.
... View more
a week ago
|
0
|
0
|
54
|
POST
|
Hmm, really hard to say what causes this without an actual reproduction case. Could you still share the codepen (even if it doesn't reproduce the problem), so we have a starter what to look? (We specifically need to know what data and renderer / symbology is used, and how featureFilter is applied) Also, can you check the following: Can you check if it also happens with 4.29? Can you confirm the flicker does not happen when FeatureFilter is not applied? As said, hard to say but from the current recording I would say: it's not z-fighting (happens only with coplanar faces) FeatureLayer, GeoJSON, OGCFeature should not make a difference (the internal rendering is the same on those)
... View more
a week ago
|
0
|
0
|
44
|
POST
|
Identified as bug / regression in 3D SceneView (missing antialiasing). Fixed, lines are smooth again. Will be shipped with next ArcGIS Online release, Feb 2024.
... View more
11-23-2023
11:22 AM
|
0
|
0
|
383
|
POST
|
Draco compression is currently not supported for 3D Symbol resources. This is in our backlog but not yet planned for a release. Basis Universal compressed textures are supported though. If the models contain large textures, maybe this could be worthwhile to reduce size?
... View more
11-17-2023
03:46 AM
|
0
|
0
|
270
|
POST
|
First answer from the linked post also applies here: Use Color VisualVariables. This concept works for both CIMSymbols and non-CIM 3D symbols. See samples: * https://developers.arcgis.com/javascript/latest/sample-code/visualization-multivariate-3d/ * https://developers.arcgis.com/javascript/latest/sample-code/layers-scenelayer-edges/ Hope this helps.
... View more
11-06-2023
06:17 AM
|
0
|
0
|
114
|
POST
|
> We've seen performance benefits from using 512x512 tile sizes over 256x256 on high-res or large screens. Oh that's interesting! Would it be possible to share some more specific details (either here or DM if you prefer)? What particular improvements? Improved FPS? Faster loading of data? Definitely something we'd like to hear more about. I assume a 512 tile cover the same area as 4 256 tiles (and not the same area at 4x resolution)? AFAICT this reduces the number of network requests to 1/4, which could indeed help with certain aspects of performance. The whole terrain is then split less granular (again 1/4 tiles), I wonder if this comes with any downsides. > If supporting mixed tile sizes (even limited to 256 and 512) in 3D is complex Mixing arbitrary tiling schemes is tough: Tiling is at the core of the terrain logic and controls a lot of both internal and user-facing behavior. Mixing 256 and 512 would definitely be less tricky but still not a freebie.
... View more
11-02-2023
11:18 AM
|
0
|
1
|
565
|
POST
|
> Raster API tiles only work when all other layers have same tiling size. Correct. In SceneView tiling scheme of all (tiled) layers must match. First layer that is loaded determines the scheme (typically the first basemap layer). FYI: This limitation in SceneView stems from the fact that in contrast to top-down-only MapView, oblique views in SceneView requires tiles to be displayed in different scales (different distance to camera). Mixing different tiling schemes would require the current single-tiling-pattern of the ground surface to be extended to support multiple overlayed tiling patterns. > I think ESRI ArcGIS Maps SDK for JavaScript maps require a basemap layer right? No, a basemap layer is not required (was the case in older versions but not anymore). If you do not need the basemap, maybe removing it is the quickest "fix" for your case?
... View more
10-31-2023
07:49 AM
|
1
|
0
|
589
|
POST
|
Assumption confirmed: Data is the same in older versions (e.g. 10.6.1): The same "steps" can be seen on the grid when basemap is disabled. In older versions those steps were not or barely noticeable due to the flat shading where surface normals were ignored. With the new terrain shading (think dynamic relief) these terrain details become visible. So the problem lies in the data / the DEM, or the way it was created. I'm not an expert on DEMs, I would say though that the data resolution is lower than the resolution of the DEM, and that could create these step-like artefacts. I'm also not clear if there are additional interpolation options which allow to control this behavior. I would try to create the DEM with a lower resolution, which matches the resolution of the source data. For more detailed help I recommend to ask again in the ArcGIS Pro section, or whichever product is used to create the DEM.
... View more
10-09-2023
09:56 AM
|
0
|
0
|
362
|
POST
|
Thanks Maxime We were able to read the service and reproduce the reported behavior. We'll do some more investigations and get back to you.
... View more
10-06-2023
07:59 AM
|
0
|
0
|
379
|
POST
|
Thanks for the service link. Unfortunately it is not working for me. https://cartes.ville.sherbrooke.qc.ca/arcgis/rest/services/DEM_3857/ImageServer Browser reports "connection has timed out" / "took too long to respond". * Can you doublecheck the url, and check if it still works for you? * Confirm that it is indeed publicly available, not limited to your intranet, and no credentials are needed to access it?
... View more
10-02-2023
04:47 PM
|
0
|
1
|
389
|
POST
|
ArcGIS Online enabled terrain shading in a recent release: https://developers.arcgis.com/javascript/latest/4.26/#improved-terrain 10.6.1 did not have terrain shading yet. Our assumption is that the terrain data is actually the same, i.e. already not smooth 10.6.1, but the steps are not visible without terrain shading. To doublecheck this assumption we'd need some more info: * is this a custom DEM? Or the default world elevation service provided by Esri? * if custom, is it possible to share a url to the layer / the service? * if not custom: please share the exact location where the problem occurs so we can investigate further. You can do this in SceneViewer Share Dialog, Share link, which will include viewpoint in the url.
... View more
10-02-2023
06:05 AM
|
1
|
0
|
405
|
POST
|
Hi Despite the (impressive) analysis we unfortunately can't see an obvious culprit. We would need to have access to the service in question to do deeper performance investigations. Hence the question: is it possible to share the service with us? If so please DM me for details.
... View more
09-05-2023
04:11 PM
|
0
|
1
|
266
|
IDEA
|
Did a test of this scenario now, and can confirm it works for me. * If elevation comes from z-values: use Arcade expression Geometry($feature).z * factor * if elevation comes from attributes: use Arcade expression $feature.attributename * factor In my test in both cases the published webscene has the correct expression set, and point features display on the expected exaggerated elevation in Scene Viewer (same elevation as in Pro). See also: https://developers.arcgis.com/javascript/latest/arcade/#z-values ---- In case this still does not work for you we'd need to see the problematic webscene, and the version of Pro used to track this down further.
... View more
09-05-2023
04:01 PM
|
0
|
0
|
443
|
IDEA
|
Hmm this is unexpected. Would it be possible to share the published webscene / the published layer with us (i.e. make it public and share the link)? This would allow us to track down if the problem is in Scene Viewer (when consuming the scene / layer) or in Pro (when publishing the layer). > If the scene viewer can handle the expression, wouldn't it be more or less easy to implement this capability in the scene viewer in the future? Yes it is correct that the underlying ArcGIS Maps SDK for JS supports this already. Adding UI to Scene Viewer for features supported in the underlying SDK is not always a trivial change though unfortunately. In this case for example new UI for editing arbitrary expressions is needed. As mentioned we understand this is an important feature and is on our roadmap, but without a specific date yet.
... View more
09-01-2023
02:48 AM
|
0
|
0
|
466
|
IDEA
|
I stand corrected: Completely forgot we actually have support for this case: using featureExpressionInfo one can exaggerate vertical position of point features using expressions, see this sample. There is currently no UX to set this in Scene Viewer. However when such an expression is set in ArcGIS Pro and exported to a webscene it is supposed to come over and display as expected (as in Pro). In SceneViewer UI elevationMode will show as `<<custom>>`. Could you try if this is working for you?
... View more
08-28-2023
08:40 AM
|
0
|
0
|
503
|
Title | Kudos | Posted |
---|---|---|
1 | 10-31-2023 07:49 AM | |
1 | 10-02-2023 06:05 AM | |
1 | 08-25-2023 06:07 AM | |
1 | 08-02-2023 03:23 AM | |
1 | 05-04-2023 05:41 AM |
Online Status |
Offline
|
Date Last Visited |
yesterday
|