We recently completed 425 miles of 360° imagery collection using the Mosaic camera. The data have been processed into an Oriented Imagery Dataset (OID) for use in ArcGIS Pro and ArcGIS Enterprise Portal 11.5.
When we publish and view the dataset through ArcGIS Online (via Collaboration from Portal → AGO) everything works as expected — the Oriented Imagery Viewer Widget in AGO Instant Apps displays and navigates the imagery perfectly.
However, when using the same dataset and web map inside Portal, the Oriented Imagery Viewer Widget is essentially broken.
Problems observed in Portal 11.5
Image selection – When clicking a map location, the widget displays the furthest image from that point instead of the closest.
Directional Navigation – Not available in Portal, but fully available in AGO. (I believe this functionality has not been added to Portal yet, so not a deal breaker...but it NEEDS to be!)
Map-Image Location Tool – Clicking a point in the image shows the corresponding map point far off from the correct location; AGO’s tool is accurate.
Current Footprint Display – Footprint graphic is not working, while AGO displays it correctly.
All of these tests were performed on the exact same dataset and web map — the only difference is the environment (Portal 11.5 vs AGO).
The biggest problem by far is that Portal chooses the furthest image, making the viewer unusable. The other discrepancies (directional navigation, footprint, map-image accuracy) compound the issue.
Environment details
ArcGIS Enterprise Portal 11.5
Oriented Imagery Dataset built in ArcGIS Pro 3.x
360° equirectangular JPEGs from Mosaic camera
Collaboration established to AGO for validation
Request
When can we expect feature parity and functional reliability of the Oriented Imagery Viewer Widget in ArcGIS Enterprise?
At minimum, the Portal widget should:
Select the closest image to the clicked map location,
Display the current footprint correctly, and
Produce accurate map-image correspondence when using the location tool.
Until then, the Portal implementation is effectively unusable for oriented-imagery workflows.