Urabn freezes when trying to position a .glb file.

Question

I am trying to import a building model into a scenarios. When I try to import a .glb model into my scenario, it comes in half submerged about a half mile away from the location I placed it in ArcPro. When I try to delete or position it or simply select it, the webpage crashes. This does not happen with Collada files of the same model. They simply come in about half a mile away from the point that would originally be their location and that is also where the anchor point is to move them.  But at least it doesn't crash nor is it submerged. It is not a very big or complex model, but creating a new scenario after this happens is really inconvenient. I've tried to recalculate the extent before Exporting the 3D Object to .dae or .glb. Exporting as .gltf returns a very quick 'File Upload Failed, Upload a file in a supported format...'. The documentation online is rather sparse for extra details. Any help would be appreciated.

MHolmquist2 · Answer

Hi Thierry,

Thanks for checking it out. I didn't realize it had so many objects. I'll try to minimalize my model and see if that helps. Meanwhile, I've discovered that in order to bring my model into a web scene with attributes I should export it as a dwg file, convert it to a feature in a feature dataset, run a script to xtract the attributes into seperate fields, create a building layer, cretae filters, create a scene layer content package, but in order to hen get my scene into a dashboard I can't have building layers so I need to go back and convert it to a 3D object and now try to put that into a web scene into a dashboard. So far, still possible I hope!

tweber · Answer

@MHolmquist2  , I had a closer look at the provided 3D model. It seems like it has a lot (~3000) separate objects within itself, which is not ideal for moving it around on the web. The "crashing" behavior you're seeing is because the web app slows down in order to load the 3D model while positioning it. My recommendation is to reduce the number of individual object in the 3D model and bringing its origin closer to the building itself. Or as you mentioned using another file format can help as well. Meanwhile, we continue working on supporting more complex 3D models. I hope this helps.

Let me know if you have any more questions.

tweber · Answer

Thank you for sharing your 3D model. The origin I'm talking about is not about the geolocation of the 3D model but rather about the models internal coordinate point of origin, dictating the objects local geometry. This point is usual used as an anchor point and for georeferencing.

I'll try to repro your case with the provided model to figure out why ArcGIS Urban crashes when uploading this specific model.