-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SceneLayer queries are not available without companion feature layer #5
Comments
@simongis thanks for your question. You will definitely need the Feature Layer for queries, so publishing the SLPK alone will not be enough. The 2 recommended workflows are: |
Thanks @gutierrezj I had a building layer (feature class) that I ran the 'Layer 3D to Feature Class' tool on (in Pro) to create my multipatch layer. Are you saying publish the original feature class from Pro instead of the multipatch? |
Take a look at this blog, the section on "Publishing Hosted 3D Object Scene Layers", about how to do it from Pro: https://blogs.esri.com/esri/arcgis/2017/09/25/authoring-3d-layers-and-creating-web-scenes-in-arcgis-online/ Alternatively you can Zip your FGDB with your multipatch Feature Class and if the ZIP file is smaller than 1GB you can upload it directly to your ArcGIS Online Content. This is also explained in this blog: https://blogs.esri.com/esri/arcgis/2017/01/03/72321/ |
Perfect, that blog helped a lot http://simonjackson.s3.amazonaws.com/PublicFacing/geoscape/index.html?demo Any idea why the page is loading up with the bottom right slider below the scene and off-screen? |
Ill raise a new issue, thanks! |
If I create a scene package from Pro and upload to an ArcGIS Online account, tweak the settings in your app, the side panel fails to load with the following reported in the browser console:
"SceneLayer queries are not available without companion feature layer"
I assume there is not an easy workaround to getting this to work via ArcGIS Online using scene packages?
I also tried publishing a multipatch scene to ArcGIS Enterprise, but ran into problems (post on GeoNet)
The text was updated successfully, but these errors were encountered: