export to KMZ question... file size or face count?

export to KMZ question... file size or face count?

Postby matthew.robert » Wed Feb 27, 2008 6:12 am

This is sort of a Google Earth question, but I hope someone here knows the answer. When exporting to a KMZ 4 file from SketchUp, is it better to shoot for minimal face count or smallest file size? I have some models that I can communicate with either textured facades but I could also communicate those models with 'linework' or geometries and no textures. Even small textures seem to take up valuable kilobytes whereas I can have hundreds of faces (used as varying components) and the kmz is actually smaller in digital footprint. It is something along the lines of 200 KB with the textured file or 32 KB with the 'many faces' KMZ file.
0

matthew.robert 
Premium Member
Premium Member
 

Re: export to KMZ question... file size or face count?

Postby remus » Wed Feb 27, 2008 7:45 am

Id go for textured faces personally as i find you get a more realistic look to the whole thing. But if you dont need that extra level of detail don't bother. Keeping the file size down is often more of a priority for google earth.
0

remus 
 

Re: export to KMZ question... file size or face count?

Postby Gaieus » Wed Feb 27, 2008 11:33 am

As far as I investigated, using components in SU does not affect the size of the resulting KMZ file that much. In fact, I have just made a test and exported a SU file (with lots of components) into kmz. The one using components came out bigger than the one that I exported after exploding the components( and purging the components from the browser). See attatched file.

I'm not too much in scripting but to my understanding, xml format (simple text files) cannot support components at all (Tomasz could confirm this - or anyone who regularly export into Kerkythea).

Rename your kmz file to zip (that actually it is) and you will see a kml file in there. That's the geolocation info only. Now there's also a folder in there called Model or what (I'm too lazy to check) inside which there's a collada file (with dae extension) and the images if you used any. Both files (the dae and the kml) can be opened in a plain text editor and you will notice that in the collada file there's no info about components or anything.

So as a final "verdict" - with excessive geometry instead of photos you cannot keep the size of a kmz file smaller when it comes to a certain level of details and complexity. I made some Gothic churches with ribbed vaults and window tracery and ended up with GE almost being unnavigatable when playing around with placing them.

When a model loads, first the geometry loads and then the images (sometimes one by one). So you are already able to see things and navigate around while it is still loading. If you use excessive geometry, this will not be the case. A colonnade however should really be modelled for instance - you cannot substitute all detailing with images. You need to find a healthy balance between them.

I hope I haven't been too exhaustive :)
0
User avatar
Gaieus 
 

SketchUcation One-Liner Adverts

by Ad Machine » 5 minutes ago



Ad Machine 
Robot
 



 

Return to Google Earth

Who is online

Users browsing this forum: No registered users and 7 guests

Visit our sponsors: