Export textured models to Geodatabase

4109
2
Jump to solution
02-06-2015 07:07 AM
GaëtanLAVENU
Esri Contributor

Hi,

I built a CityEngine with buildings generated from a rule that affect roof textures by extracting pixels from an aerial photography. My issue is that when I export these building to a File Geodatabase (with "one feature by shape" option), the size of my Geodatabase is extremely large because the full orthophoto seems to be exported for every shape. For example, exporting 20 buildings leads to GDB size of 1,5 Gb. Is it an expected behaviour, how to proceed ?

I'm using CityEngine 2014.1.

Thanks for your help.

Gaëtan Lavenu

Esri France

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
SimonHaegler
Esri Contributor

hi gaetan

this behaviour is (unfortunately) expected and is the result of two things:

1. the FileGeodatabase format is not efficient when multipatches of multiple features reference the same image - the image is stored separately for each feature. put differently, there is no common texture storage per feature class.

2. CityEngine does not do any image/texture cropping - it simply exports texture coordinates and the full image.

we recognize that in your case these two things result in pathological gdb sizes. would you be able to pre-segment (or simply subdivide) the orthophoto beforehand to reduce the redundancy? you could use CGA to find and assign the corresponding orthophoto tiles.

i'll also reach out to some of our ArcGIS data processing experts, maybe there is a way to "throw away" all pixels which are not referenced by the multipatches, i.e. basically cropping down each texture to its active texture coordinate region.

sorry for the mixed answer & kind regards,

simon

View solution in original post

2 Replies
SimonHaegler
Esri Contributor

hi gaetan

this behaviour is (unfortunately) expected and is the result of two things:

1. the FileGeodatabase format is not efficient when multipatches of multiple features reference the same image - the image is stored separately for each feature. put differently, there is no common texture storage per feature class.

2. CityEngine does not do any image/texture cropping - it simply exports texture coordinates and the full image.

we recognize that in your case these two things result in pathological gdb sizes. would you be able to pre-segment (or simply subdivide) the orthophoto beforehand to reduce the redundancy? you could use CGA to find and assign the corresponding orthophoto tiles.

i'll also reach out to some of our ArcGIS data processing experts, maybe there is a way to "throw away" all pixels which are not referenced by the multipatches, i.e. basically cropping down each texture to its active texture coordinate region.

sorry for the mixed answer & kind regards,

simon

GaëtanLAVENU
Esri Contributor

Hi Simon,

Thank you for your answer. I agree with the 2 reasons you mentioned, it confirms my diagnosis. Building such CGA rule could be the best way, but how to manage the case where the building footprint overlaps two tiles ? If you have a sample of such script it would be welcomed :)

Regards,

Gaëtan.

0 Kudos