Skip to main content
Solved

Exceptionally long writing time for textured multipatch to ESRI File GeoDB


mhab
Contributor
Forum|alt.badge.img+10
  • Contributor

Hello

I took CityGML LOD2 RoofSurfaces (~1700) and textured them with an Orthofoto.

 

If I write this to a 3D PDF or glTF it takes 1min and produces output of 50Mb in PDF and 15Mb in glTF

If I write the same data to an ESRI File GeoDB it takes 5h+ and produces a File GeoDB with ~6Gb size .

What is going on here ? Do I need to specially treat the surfaces before writing them to the File GeoDB ?

Best answer by mhab

Thanks for the explanation.

Clipping each texture brought down the writing time to 2min and the FileGDB size to 15Mb.

New problem is, that writing this to ffs results in 1700+ files *.frs

So I have to switch my workflow to ffs-Zipped writing, which works well for ffs+frs.

Amazing integration of ZIP handling.

View original
Did this help you find an answer to your question?

5 replies

daveatsafe
Safer
Forum|alt.badge.img+19
  • Safer
  • February 6, 2018

Hi @mhab,

It is a quirk of Geodatabase that it stores individual texture images for each multipatch geometry. So each roof surface is storing a copy of the entire orthophoto.

For most 3D formats we would recommend keeping the large orthophoto image and using it to texture all the roofs, but for GDB it's better to clip out a separate image for each roof and use that to texture the surface.


mhab
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • Best Answer
  • February 12, 2018

Thanks for the explanation.

Clipping each texture brought down the writing time to 2min and the FileGDB size to 15Mb.

New problem is, that writing this to ffs results in 1700+ files *.frs

So I have to switch my workflow to ffs-Zipped writing, which works well for ffs+frs.

Amazing integration of ZIP handling.


houyi0315
  • February 7, 2020
mhab wrote:

Thanks for the explanation.

Clipping each texture brought down the writing time to 2min and the FileGDB size to 15Mb.

New problem is, that writing this to ffs results in 1700+ files *.frs

So I have to switch my workflow to ffs-Zipped writing, which works well for ffs+frs.

Amazing integration of ZIP handling.

Hi. I'm also facing this problem now. May I know how to clip out a separate image for each roof and wall? And how to rewrite the CityGML file? Now all the texture is written in a big image. Thanks a lot.

 


mhab
Contributor
Forum|alt.badge.img+10
  • Author
  • Contributor
  • February 7, 2020
houyi0315 wrote:

Hi. I'm also facing this problem now. May I know how to clip out a separate image for each roof and wall? And how to rewrite the CityGML file? Now all the texture is written in a big image. Thanks a lot.

 

Use a SurfaceFootprintReplacer on the 3D feature + Clipper


houyi0315 wrote:

Hi. I'm also facing this problem now. May I know how to clip out a separate image for each roof and wall? And how to rewrite the CityGML file? Now all the texture is written in a big image. Thanks a lot.

 

can we know more on how to clip an existing texture atlas containing many faces from CityGML to new CityGML file


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings