Esri / i3s-spec

This repository hosts the specification for Scene Layers which are containers for arbitrarily large amounts of geographic data. The delivery and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified.
Other
315 stars 84 forks source link

SLPK attribute issue - in spec or in arcgis pro tool after 2^24 = 16 777 216 records #155

Open chritomix opened 1 year ago

chritomix commented 1 year ago

Hi, When using geoprocessing tool "Create 3D Object Scene Layer Content" in arcgis Pro 2.9.X or 3.X – I am coming to some limit of that tool / Script. I am using the tool to create SLPK based on polygon multipatch feature class representing buildings.

My guess is that within the script (written in C++ ?) , there is some variable , assign as float, so that it can only store value up to 2^24 numbers, and then it restarts from 1 again…

The tool correctly creates scene layer package with the right geometry (height) for each building. However, within SLPK, not all attribute data are correctly assigned: • Up to 2^24 = 16 777 216 records the attribute data from SLPK corresponds to attribute data of multipitch feature class (in fact up to 16 777 214 records, the last two records have “empty “ information”). • Then, the next building has the right geometry, but no attribute: the attribute data is the same exactly as the first building. • The second building has the right geometry, but its attributes are the same as the second building • etc… Workflow: • Open arcgis pro – GLOBAL SCENE (projection WME). • Add MultiPatch feature class ( I am going to provide you two – one with 38 records only - to run fast small test, and second one containing more than 16mln records of buildings) • From Tools open “Create 3D object Scene layer Content” – SLPK:

• Once SLPK is generated. Compare attributes information between multipatch feature class and SLPK (the best is to open map viewer (with multipatch ) and scene viewer (with SLPK) next to each other and compare them.

PRE- REQUIEREMENTS:

Ivonne-S commented 1 year ago

Hello, we analyzed the issue and found a solution for the problem. We used your provided data for testing. We are planning to include the fix in ArcGIS Pro 3.2 as well as part of plan of a ArcGIS Pro 3.1 patch.

chritomix commented 1 year ago

Good news. thank you. regards