Latest Contributions by ArnoFiva

There are different approaches to achieving this. If you want to persist the altered elevation, it is best to publish the new elevation as a layer and add it as an additional elevation layer to your scene. This is something you can achieve for example with ArcGIS CityEngine: align the elevation to your buildings and publish it for a specific extent. You can do some things also in the client using the ArcGIS Maps SDK for JavaScript. Using a base elevation layer you can change the height values that are returned by the elevation service. Here is a sample app that does this for arbitrary polygons, you can change the polygon using sketch tool: https://codepen.io/arnofiva/pen/YzoQNeq?editors=0010   ... View more

Thanks for your feedback @SveinungBertnesRåheim! We are actively working on supporting georeferenced models being uploaded through the web and should be released first half of 2025. Can you provide some more insights into how your 3D models are georeferenced? e.g. what IFC version, what coordinate system, are you using a world file? ... View more

Thanks for posting, we would need a running app or at least the details: {...} in your error message above to be able to help. ... View more

Because of rotation and tilt, an extent can never correctly cover the camera's visible area in 3D. We currently offer two possibilities SceneView.extent: I assume you are already using that. GroundView.extent: similar to the above, but specifically tailored to the ground elevation, making it more precise for some situations. It might help to know that we are currently working on a property with the visual area. Because this will be provided as a polygon, it will take tilt and rotation into account. This is planned to land this year, potentially in the upcoming 4.30 release. In the meantime you could increase the size of the extent returned by SceneView using Extent.expand. Computing the extent or visible area yourself is rather complex and I cannot point you to any recourses. Our own implementation takes various factors into account, such as the elevation or visible geometries in the view. ... View more

Thank you for your question and providing screenshots! We would like to look into this but are unable to reproduce on our side. Can you provide us more details, such as: The exact sample you are using. Are you connected to an external monitor? If not, could you try and see if it makes a difference? What version of Safari and other browsers are you using. Can you provide us more details on the graphics card? Could you provide us the output of https://webglreport.com/?v=2 Thanks! ... View more

Thanks for your question! I believe the Indoors data model works with relative-to-ground z-values. So your floor is configured to be 6 meters above ground, while in a web scene with elevation layer, it is actually placed 219 meters above sea level. This could explain the discrepancy, but this is just guessing without being able to access the actual data. ... View more

Hi Christophe Thanks for your response and elaborating on the use case. One more thing that came to mind, visualizing a glTF model in the client. You could increase the rendering quality using view.qualityProfile = "high". Besides using high resolution renderings, the scene view also allocates more memory. https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#qualityProfile I tested this in your above CodePen and still see the memory limit exceeded message, however it continues to show the glTF and integrated mesh as expected. Thanks, Arno ... View more

  Uploading 3D models is a capability currently being developed and planned to release this year, therefore all information is subject to change. The upload will be based on the ArcGIS CityEngine runtime (PRT), so whatever formats are supported by PRT, should also work for in the web. Here is a list of the supported file formats: https://esri.github.io/cityengine-sdk/html/esri_prt_codecs.html As mentioned in previous posts, the glTF being used is rather large for client-side consumption. Would be great if you could share more information with us about the use case and the source of the model.   ... View more

Thanks for bringing this up, we are aware and currently investigating potential solutions.  In the meantime we recommend using one of the workarounds (can also be combined): 1) Adding callouts to the symbol, see PointSymbol3D.callout or the following callout sample. This will make your blue icon appear above the room while having the callout pinpoint the exact location in the room. 2) Make your contextual building (walls, floors, etc.) transparent and visualize the location using a volumetric 3D symbology (ObjectSymbol3DLayer or WebStyleSymbol) instead of an icon. This will make your symbol visible through the transparent building.  That being said, it would be interesting to hear what your expected behavior is. We understand the need of being able to see that there is a feature behind the wall. The solution to the problem is not straightforward and there are different approaches. Please let us know if you have anything in mind. I will bookmark this thread in our backlog and update you here, once we release anything related to this topic. ... View more

Similar to your other question regarding camera, the spatial references of the "osm-light-gray" basemap does not match with the one from your building scene layer. Either you have to provide a basemap in the same spatial reference, or you have to initialize the Map object without a basemap.  For more information about supported coordinate system and what projections can be combined, see the SceneView documentation: https://developers.arcgis.com/javascript/latest/api-reference/esri-views-SceneView.html#supported-coordinate-systems   ... View more

If you create a new camera object like this, the position of the camera defaults to WGS84:  camera: { heading: 90, tilt: 45, position: [ -122, 38, 20000 ] } This is most likely incompatible with the spatial reference of your building scene layer, which is why scene view throws an error. Granted, the error message could provide a bit more information. You can create a valid camera object like this: camera: { position: { x: -122, /* replace with projected coordinate */ y: 38, /* replace with projected coordinate */ z: 20000, spatialReference: { wkid: 28992 /* Replace with wkid of your scene layer */ } }, heading: 90, tilt: 45 }   Also, instead of adding your building scene layer as a basemap, better add it as a layer to your map. This will make sure widgets like the layer list and legend work properly out-of-the-box:  const bSceneLayer = new BuildingSceneLayer({ url: my_url, }); var map = new Map({ layers: [bSceneLayer], });   Hope this helps! Otherwise as Rene already pointed out, it would be good to have a running sample app you can share. ... View more

Thanks for your message, are you saying you have StreamLayer.purgeOptions configured to remove old observations and it is not working as expected? Can you confirm it works properly for MapView (2D)? Regarding labels we are aware of flickering in 3D, but they should follow the feature if the track ID is properly configured. Would you be able to share a repro case with us? Stream layers support for Scene Viewer and web scenes is on the roadmap but no release date yet. Would be interested to hear more about your use case! ... View more

I am unable to reproduce what you are describing. Can you provide a running sample (CodePen)? ... View more